Release Notes. Version 5.2-M English Edition. Ingenieurbüro David Fischer AG A Company of the Apica Group - PDF

Description
Ingenieurbüro David Fischer AG A Company of the Apica Group Release Notes Version 5.2-M 2012, 2013, 2014, 2015 Last Revised: March 5, 2015 All Rights Reserved Table of Contents

Please download to get full document.

View again

of 52
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information
Category:

News & Politics

Publish on:

Views: 24 | Pages: 52

Extension: PDF | Download: 0

Share
Transcript
Ingenieurbüro David Fischer AG A Company of the Apica Group Release Notes Version 5.2-M 2012, 2013, 2014, 2015 Last Revised: March 5, 2015 All Rights Reserved Table of Contents 1 V New Functions and Features Major Release V5.2-A (Installation Kit dated May 23, 2014) Minor Release V5.2-C (Installation Kit dated June 19, 2014) Minor Release V5.2-D (Installation Kit dated July 4, 2014) Minor Release V5.2-E (Installation Kit dated August 29, 2014) Minor Release V5.2-G (Installation Kit dated November 11, 2014) Minor Release V5.2-H (Installation Kit dated November 17, 2014) Minor Release V5.2-I (Installation Kit dated November 21, 2014) Minor Release V5.2-J (Installation Kit dated November 28, 2014) Minor Release V5.2-M (Installation Kit dated March 5, 2015) Discontinued Functions Modified Java CLASSPATH Version 5.2 Compatibility Installation Notes for Upgrade to ProxySniffer V Necessary Preparations before You Upgrade Performing the Upgrade V New Functions and Features Major Release V5.1-B (Installation Kit dated November 13, 2013) Minor Release V5.1-C (Installation Kit dated January 10, 2014) Minor Release V5.1-F (Installation Kit dated February 21, 2014) Minor Release V5.1-G (Installation Kit dated March 1, 2014) Minor Release V5.1-M (Installation Kit dated April 25, 2014) Minor Release V5.1-N (Installation Kit dated May 6, 2014) Version 5.1 Compatibility Installation Notes for Upgrade to Proxy Sniffer V Necessary Preparations before You Upgrade Performing the Upgrade V New Functions and Features Minor Release V5.0-P (Installation Kit dated April 12, 2013) Additional Features / Updated V5.0-P (Installation Kit dated May 5, 2013) Additional Features / Updated V5.0-P (Installation Kit dated May 15, 2013) Additional Features / Updated V5.0-P (Installation Kit dated May 20, 2013) Major Release V5.0-K Additional Features / Updated V5.0-K (Installation Kit dated November 1, 2012) , 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 2 of 52 Additional Features / Updated V5.0-K (Installation Kit dated November 18, 2012) Additional Features / Updated V5.0-K (Installation Kit dated December 28, 2012) Additional Features / Updated V5.0-K (Installation Kit dated January 20, 2013) Errors Fixed Version 5.0-K Version 5.0-P (Installation Kit dated April 12, 2013) Updated V5.0-P (Installation Kit dated May 15, 2013) Version 5.0 Compatibility Illustrations of New Functions and Features (Major Release V5.0-K) Multi-Threading Support per Simulated User Integration with the Apica LoadTest Portal Searching a Text-String inside the Error-Snapshots Enabling inbound Firewall Rules for the Proxy-Recorder on Pure Cloud Machines Rebooting EC2 Machines from the GUI Automatic Termination of Unused Amazon Load Generators Illustrations of New Functions and Features (Minor Release V5.0-P) DNS Statistic , 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 3 of 52 1 V New Functions and Features Major Release V5.2-A (Installation Kit dated May 23, 2014) ProxySniffer V5.2-A includes an update of the cryptographic libraries and contains the following new features: Support of TLS 1.1 added. TLS 1.1 is now supported by ProxySniffer. Support of ECC added. Elliptic Curve Cryptography (ECC) is now supported by ProxySniffer. Support of DER and PEM encoded client certificates added. Similar to PKCS#12 client certificates, DER and PEM encoded client certificates are now also supported by ProxySniffer. Support for Appending URLs from Web Tools Test HTTP(S) Request added. URLs that are called from the menu Web Tools Test HTTP(S) Request can now be appended to the recoded Web Session Minor Release V5.2-C (Installation Kit dated June 19, 2014) Support for New Version of Apica LoadTest Portal added. ProxySniffer supports now the latest version of the Apica LoadTest Portal. Local files that are uploaded to the portal can now be labeled with tags. Exec Agent Option Minimum Page Break Delay added. By using the new optional startup argument -minpagebreakmillis milliseconds Exec Agents can be configured in such a way that a minimum delay per each page break is applied for all load test programs. 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 4 of 52 1.1.3 Minor Release V5.2-D (Installation Kit dated July 4, 2014) Support for Exporting Recorded Web Sessions as HTTP Archives (HAR) added Recorded Web Sessions can now exported as HTTP Archives (*.har files, HAR version 1.2). The corresponding function can be called from Main Menu Export Icon Export Session Data HAR Format Support for Importing/Converting HTTP Archives (HAR) to Recorded Web Sessions Load Test Programs added HTTP Archives (*.har files) that are uploaded in any Project Navigator directory ( upload icon) can then converted to a ProxySniffer Web Session (*.prxdat file) by clicking on the corresponding icon of the *.har file. After that the Web Session can post processed in a normal way and transformed into a load test program. Command Line Tools for converting HTTP Archives (HAR) added There are also two new command line tools available that can be used to converting a ProxySniffer session (*.prxdat file) to a HTTP Archive (*.har file) and vice versa. Convert a ProxySniffer session (*.prxdat file) to a HTTP Archive (*.har file): java ProxyDataDumpToHAR *. prxdat file *.har file Convert a HTTP Archive (*.har file) to a ProxySniffer session (*.prxdat file): java HARToProxyDataDump *.har file *.prxdat file Proxy Recorder REST API added The Proxy Recorder can now be controlled by a REST API that provides the following functions: 1. Get the product version from Proxy Recorder process 2. Get the current recorder state (recoding started or stopped) 3. Trigger start of recording 4. Trigger stop of recording 5. Clear all recorded data 6. Insert (append) a page break 7. Set the user s think time for all page breaks 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 5 of 52 8. Enable/disable parallel execution of URL calls when running the session as load test 9. Get the total number of recoded page breaks and URL calls. 10. Get a short dump about the recorded session 11. Get the session filter 12. Set the session filter 13. Get the recoded session in ProxySniffer data format (*.prxdat file content) 14. Get the recorded session in HAR data format (HTTP Archive 1.2) 15. Load a recorded session (ProxySniffer data format) into the Proxy Recorder 16. Load a recorded session (HAR data format) into the Proxy Recorder Further information about the Proxy Recorder REST API is available in the updated Application Reference Manual, chapter Proxy Recorder REST API Minor Release V5.2-E (Installation Kit dated August 29, 2014) Optimization for Large Clusters of Load Generators The startup-speed when launching cluster jobs have been substantially increased (up to 20 times faster). Additionally, the stability for large clusters of load generators that contain many hundreds of cluster members (Exec Agents) has been improved. 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 6 of 52 1.1.5 Minor Release V5.2-G (Installation Kit dated November 11, 2014) OS-Independent DNS Configuration for Proxy Recorder added The Proxy Recorder can now configured to use specific (own) DNS server(s) to resolve host names rather than using the DNS library of the underlying operating system. In addition the Proxy Recorder can also configured to use specific own Hosts file information. The DNS configuration can be set by using special startup arguments of the ProxySniffer process, or when using the ProxySniffer Console, by adding special startup parameters to the configuration file prxsniff.dat which is located in the installation directory. Detailed information is available in the updated Application Reference Manual. Blacklist and Whitelist for Proxy Recorder added The Proxy Recorder can now configured with a blacklist that can be used to suppress HTTP forwarding and recording of URLs containing specific DNS names and/or IP addresses. This means that suppressed URL requests are not forwarded to the web server(s) and also not recorded. Instead of this the web client (web browser) receive a faked response directly from the proxy recorder. A DNS name or an IP address of the blacklist can also contain multiple times the wildcard char *. Because the wildcard char * is supported, it s also additionally supported to configure a whitelist which contains exceptions of the blacklist. The configuration can be made by creating the (optional) files recorderblacklist.dat and recorderwhitelist.dat in the installation directory. Detailed information is available in the updated Application Reference Manual. New Functions to the Proxy Recorder REST API added The following functions have been added to the Proxy Recorder REST API: o Get the DNS/IP blacklist configuration o Set the DNS/IP blacklist configuration o Get the DNS/IP whitelist configuration o Set the DNS/IP whitelist configuration o Get the DNS configuration o Set the DNS configuration Detailed information is available in the updated Application Reference Manual. 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 7 of 52 1.1.6 Minor Release V5.2-H (Installation Kit dated November 17, 2014) Log of SSL Handshake to Error Snapshots added A log of the SSL Handshake is now added to all captured Error Snapshots if the Load Test Job argument -dssl (debug SSL) is set. Elliptic Curve Cryptography (ECC) Disabled by Default Because of performance degradation ECC is now disabled by default for all components of ProxySniffer, inclusive for the Proxy Recorder and also for all executed load test programs. o To re-enable ECC when Recording Web Sessions you can add a line containing the text -ecc (w/o double quotes) to the (optional) configuration file prxsniff.dat which is located in the ProxySniffer installation directory. Or alternatively, when you start the ProxySniffer process directly w/o ProxySniffer Console, you can pass the optional startup argument -ecc to the ProxySniffer process, and to the WebAdmin process (see revised Application Reference Manual). o To re-enable ECC for specific Load Test Jobs you can enter in the Execute Load Test Menu the new argument -ecc into the input field Additional Options. ECC should always be disabled for all Stand-Alone Load Generators (Exec Agents). So you should never pass the startup argument -ecc to an ExecAgent process. Nonetheless any load generator supports ECC for its executed load test jobs if the load test job argument -ecc is set even if the Exec Agent (-process) startup argument -ecc is not configured. Update of Amazon AWS Libraries and Support of EC2 Data Center Frankfurt added The integrated libraries for accessing Amazon EC2 was updated to the latest AWS API version 1.9.4, and the new EC2 data center Frankfurt is now also supported for launching EC2 load generators and for launching Pure Cloud instances. Note that older versions of ProxySniffer may fail to communicate with Amazon EC2. Therefore you should upgrade first to V5.2-H, before reporting an EC2 related a bug to our support team. 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 8 of 52 1.1.7 Minor Release V5.2-I (Installation Kit dated November 21, 2014) Configurable Random Generator for SSL Handshakes The random generator used for the SSL Handshakes can now be configured. You can enter in the Execute Load Test Menu the new argument -sslrandom type into the input field Additional Options. Possible options for the type are java, iaik or fast . java: Use the standard Java secure random generator for SSL handshakes. This random generator generate secure random numbers, but its usage is non-recommended for load test execution because it may be very slow and may block on Linux-like systems. iaik: Use the IAIK random generator for SSL handshakes (SHA256PRNG-FIPS). This random generator is used by default. fast: Use a fast but very weak (non-)secure random generator for SSL handshakes. This random generator will never block on any operating system. Note that only load test programs which are generated with ProxySniffer version 5.2-I (or later) will consider this option. All other load test programs generated with older ProxySniffer versions will always use the default random generator type iaik Minor Release V5.2-J (Installation Kit dated November 28, 2014) Configurable Java Memory for Load Test Jobs ExecAgents support now the new startup argument -enablejoboverridejavamemory that allows load test Jobs to override the pre-configured size of the Java memory. Alternatively this new argument can also set at the ExecAgent in the configuration file prxsniff.dat which is located in the ProxySniffer installation directory. If this option is enabled by an ExecAgent the size of the Java memory can be overridden by entering the option -Xmx megabytes into the input field Additional Options in the Execute Load Test Menu. If this option is not enabled by an ExecAgent (default behavior) you get the error message unsupported job option on exec agent when starting the load test job with the additional option -Xmx megabytes . Java Memory Size shown when Pinging Exec Agents When pinging ExecAgents via the Exec Agent Network Configuration menu the configured default value for the Java memory size applied for each executed load test job is now shown. Note: this value is locally configured on the ExecAgents in the file javasetup.dat. 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 9 of 52 1.1.9 Minor Release V5.2-M (Installation Kit dated March 5, 2015) Installing V5.2-M as a patch: V5.2-M contains updated versions of the IAIK SSL/TLS libraries (new against V5.2-A). If you install V5.2-M as a patch you have to replace/update the files prxsniff.jar, iaik_jce_full.jar, iaik_ssl.jar, iaik_eccelerate.jar and iaikpkcs11provider.jar. These new versions of files can extracted from any V5.2-M installation kit. We recommend that you also download the newly available Recorder Plug-Ins at and unzip them in the ProxySniffer installation directory. ProxySniffer V5.2-M contains the following new features: Load Test Arguments Stored in Result Files All arguments of a load text job are now stored in the result file (*.prxres file). You can review the arguments of a job in the Load Test Result Detail menu Test Scenario . Support of TLS 1.2 and SNI added TLS 1.2 and SNI (Server Name Indication) is now supported by ProxySniffer and enabled by default. Debugging of SSL/TLS Handshakes Option added to Personal Settings Menu SSL/TLS Handshakes can now debugged during the recording of a Web surfing session by enabling the corresponding (new) option in the Personal Settings menu. The debug information is written to stdout, or respectively to the ProxySniffer Console. Note: Debugging of SSL/TLS Handshakes for executed load test programs is already fully supported since Version 5.2-H. Debugging of Outbound TCP/IP Connections for Proxy Recorder added Outbound TCP/IP connections of the Proxy Recorder can now debugged by passing the ProxySniffer startup argument -debugrecordersocketpools DNS, TCP/IP and SSL Information added for each Recorded URL Each recorded URL contain now the following additional data which can be shown in the Web GUI: o DNS resolve time (only if an OS-independent DNS configuration for the Proxy Recorder is used) o Source TCP/IP address o Source TCP/IP port number o Target TCP/IP address o Target TCP/IP port number o SSL session Id (for encrypted HTTPS URL calls only) 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 10 of 52 Support of DNS Translation File added A DNS Translation File is a DNS configuration file (similar to the DNS hosts file), that contains on each line a translation between two DNS names. If the first DNS name in the file match to the DNS name that is passed to the DNS resolver then the second DNS name is used to resolve the IP address. The first DNS name can also contain one or more wildcard characters ('*' = wildcard for multiple characters, '?' = wildcard for single character). Lines or a part of a line can be commented out by using the hash char '#'. For recording Web surfing sessions you can configure this option by passing the ProxySniffer startup argument -dnstranslation file-name , or alternatively, you can configure this option also in the prxsniff.dat configuration file (all options have to be set in this file at the same, single line). The DNS Translation File can also configured on the fly by using the Proxy Recorder REST API. When executing a load test program you can configure this option by entering -dnstranslation file-name into the Additional Options input field. You have to ZIP the DNS translation file together with the compiled class of the load test program. Note 1: It could be needed that TLS SNI (Server Name Indication) must be disabled if a DNS translation file is used. Note 2: The HTTP request header field Host is not updated, so it might happen that you call the Web server with the wrong host name. Debugging of DNS Cache and DNS Resolves added For recording Web surfing sessions you can configure the debugging of the DNS cache and its resolves by passing the ProxySniffer startup argument -debugdns, or alternatively, you can configure this option also in the prxsniff.dat configuration file (all of the options have to be set in this file at the same, single line). The debug information is written to stdout, or respectively to the ProxySniffer Console. When executing a load test program you can configure this option by entering -dnsdebug into the Additional Options input field. The debug information is written to the stdout file (*.out) of the load test job. New: Support for Recorder Plug-Ins added Proxy Sniffer Recorder Plug-ins are Extension Modules to the Proxy Sniffer product and can be automatically executed during the recording of a Web surfing session. Furthermore, Recorder Plug-ins can also manually called from the Web Admin GUI or called from the Proxy Recorder REST API. Such Recorder Plug-Ins have direct access to the recorded session data and also to the internal Var Handler which means that such Plug-Ins can modify HTTP Request and Response data before, during and after the recording, and that such Plug-Ins can also create variables, variable extractors and variable assigners. Furthermore such plug-ins can also reconfigure the HTTP response content test settings of URL calls. The main purpose for using Recorder Plug-Ins is to automate some parts of the post-processing steps after a session has been recorded. Another purpose is to modify HTTP request data during recording on the fly just before they are sent to the Web server. Detailed information about Recorder Plug-Ins is available in the new PDF document Recorder Plug-In Developer Handbook. New Functions to the Proxy Recorder REST API added The following functions have been added to the Proxy Recorder REST API: o Clear the DNS resolve cache o Get the DNS translation map 2012, 2013, 2014, 2015 Ingenieurbüro David Fischer AG, Switzerland All Rights Reserved Page 11 of 52 o Set the DNS translation map o Get outline information about all Recorder Plug-Ins o Change the state of a Recorder Plug-In to active or to inactive o Manually call a Recorder Plug-in o Trigger a re-scan for Recorder Plug-Ins Detailed information is available in the updated Application Reference Manual. 1.2 Discontinued Functions Selecting SSL V2 as a SSL protocol option has been removed Kerberos authentication has been removed 1.3 Modified Java CLASSPATH The Java CLASSPATH required to run any component of ProxySniffer V5.2 must contain the following elements: - The
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks