Web Response Monitor Script Recorder - CA Technologies
{{search ? 'Close':'Search'}}

Web Response Monitor Script Recorder

Overview - The script recorder monitors the activity between a browser and a web server by acting as a proxy. The browser connection settings must be modified to use the recorder as a proxy. If a proxy is required to access the server, then the recorder will send requests via the "real" proxy. If you are using one of the supported browsers, the proxy information will be set and the browser will be opened when recorder is started. Other browsers may still be used with the recorder but the proxy settings will have to be modified manually.

Note: You must not specify Automatically Detect Settings in Internet Explorer browser settings. When this is set, the recorder will fail to produce a script.

Configuration - On the script editor, open the configuration by selecting "Recorder Configuration" on the Options pull down menu. The field usage is as follows:

Recorder Port: This is the port that the recorder will listen on. Change the default if this port is already in use by another application.

Use Wininet: Check this box if Integrated Windows authentication is being used by the web server or by the proxy.

Browser Type: Check the appropriate browser to enable automatic proxy setting modification and browser opening. For Netscape, you must also specify the path where the profile is located. This path is specified when you create a Netscape profile.

If Other is checked, then you will have to modify the connection settings manually. Set the browser to use a proxy and specify Localhost as the proxy and the recorder listen port as the proxy port. Only specify the recorder for the http protocol. Http is the only protocol supported by Web Response Agent scripts. (See the note below concerning the https protocol)

Connection Timeout: The time in seconds that the recorder will wait to connect to a web server.

SSL Character: The special character used to represent an https URL. (See the note below concerning the https protocol)

SSL Version: What versions of SSL will be supported when connecting to a secure server. Specifying both versions will support the largest number of servers. NOTE: Only specify SSLv3 if the web server is IBM's version of Apache which is used with WebSphere.

Log Level: Specify a level of 2 or 3 to get a more detailed log. The log name is the script name and will be located in the log directory under wrmml.

Encrypt Configuration: By checking this option, the configuration file will be encrypted. You may want to do this if security information is required by your proxy.

Include Redirects: By default, the Web Response Monitor will automatically handle redirected URLs so this is the default for the recorder as well. Any redirected URLs will be excluded from the script unless this check box is selected.

HTTP Proxy and SSL Proxy: Specify this information if a proxy is required to connect to the web server. If you are using one of the supported browsers, this information will be extracted automatically from the browser settings. Any proxy and proxy port information specified in the recorder configuration will override any settings that the recorder retrieves from the browser.

HTTP Proxy User/Pswd and SSL Proxy User/Pswd: This information must be specified to the recorder if your proxy requires user authentication. Specifying a user and password via the usual browser proxy security dialog will not work with the recorder.

Operation - On the New Script dialog, enter a name and select Record. The global parameters dialog will displayed. This will have no effect on the recorder, but allows you to specify the global attributes to be generated with the script rather that going back later and inserting it. On the recorder dialog, press start to begin recording. If one of the supported browsers was selected in the configuration, it will be launched with a blank page. Enter the first URL and proceed through the entire transaction. Press stop to close the browser and stop the recorder. The generated script will appear in the editor. You can now edit the base script and insert other specifications to do accuracy checks, etc.


HTTPS protocol - SSL is fully supported between the recorder and web servers, but is not supported between the browser and the recorder. To do so would add to the complexity as well as result in a "man in the middle attack". To record an SSL transaction, specify the first URL using the "special" SSL character. For example, instead of entering https://www.test.com/page.html, enter http://&www.test.com/page.html . This will tell the recorder to use SSL when retrieving this page. The recorder will edit the page before returning it to the browser, changing any https:// specifications to http://&. Any subsequent click on an SSL link will result in the correct request of the https URL.

Other browsers - If you are using a non-supported browser, you must configure it to point to the recorder as a proxy. Enter localhost for the proxy address and the recorder listen port for the proxy port. If a proxy is required to access the web server, enter this information in the recorder configuration. After starting the recorder, launch the browser manually. If you have a home page other than a blank, then this URL will be recorded and will have to be manually deleted from the script. The browser settings must be changed before it is launched. If the browser supports multiple profiles, then may want to define one to be used just for the recorder. Then you just select this profile when you launch the browser.

Frames -Because the Web Response Monitor automatically returns all frames that make up a frameset page, frame source URLs are excluded from a recorded script. If included, they would result in duplicate requests.

Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required


We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile

  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.

    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

agent is typing