AppManager Response Time for Web 7.4.0.4 Release Notes

Date Published: December 2018

AppManager Response Time for Web helps you to monitor the organization’s Web infrastructure to ensure availability and performance of critical Web sites and services.

This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.

The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials Web site.

1.0 What’s New?

This release of AppManager Response Time for Web provides the following enhancement:

  • Support for Transport Layer Security 1.2 (TLS): This release of AppManager Response Time for Web provides support for TLS 1.2.

This release of AppManager Response Time for Web resolves the following issue:

  • Failure of multiple URLs with HTTP response code 12030: Monitoring websites, which supports only TLS 1.2 protocol, causes URL check to fail with error code 12030. This release of AppManager Response Time for Web resolves this issue.(ENG347186)

To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the “Upgrading Knowledge Script Jobs” section in the Management Guide.

This release of AppManager Response Time for Web replaces all Previous Releases.

2.0 System Requirements

For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.

AppManager Response Time for Web has the following system requirements:

Software/Hardware

Version

NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Response Time for Web computers you want to monitor (agents), on all console computers, and on any computer where you want to run Web Recorder or URL Check Recorder

8.0.3, 8.2, 9.1, 9.2, 9.5, or later

One of the following AppManager agents are required:

  • AppManager agent 7.0.4 with hotfix 72616 or later

  • AppManager agent 8.0.3, 8.2, 9.1, 9.2, 9.5, or later

Microsoft Windows operating system on the agent computers

One of the following:

  • Windows Server 2016

  • Windows 10 (64-bit)

  • Windows Server 2012 R2

  • Windows Server 2012

  • Windows 8 (32-bit and 64-bit)

  • Windows Server 2008 R2

  • Windows Server 2008 (32-bit and 64-bit)

  • Windows 7 (32-bit and 64-bit)

  • Windows Vista (32-bit and 64-bit)

  • Windows Server 2003 R2 (32-bit and 64-bit)

  • Windows XP Professional with Service Pack 3 (32-bit and 64-bit)

Microsoft Internet Explorer installed on the console and agent computers

8.0, 9.0, 10.0 or later

Microsoft Edge installed on the console and agent computers

20.10240.16384.0

Microsoft .NET Framework on the WebRecorder computer

3.5 Service Pack 1 or later

Microsoft SQL Server Native Client 11.0

(for TLS 1.2 support)

11.3.6538.0 or later

NOTE:The SQL Server Native client can be installed from this Microsoft download link.

AppManager Response Time for Web also has the following requirements:

  • Any agent computer where you plan to run WebTransaction Knowledge Scripts created using the Web Recorder requires a logged-in user.

  • You cannot run the Knowledge Scripts through a Terminal Services session unless you use the /console command line parameter. For more information about command line parameters, see the Remote Desktop Connection documentation.

For more information on hardware requirements and supported operating systems and browsers, see the AppManager Response Time for Web Management Guide, included in the download package.

NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.

3.0 Contents of the Download Package

AppManager Response Time for Web includes managed objects and Knowledge Scripts to discover and monitor Response Time for Web resources. The download package includes this Release Notes, a Management Guide, Help for Knowledge Scripts, and several files that are used during installation:

  • AM70-Web-RT-7.4.60.0.msi, the module installer.

  • AM70-Web-RT-7.4.60.0.ini, a configuration file used with the AppManager setup program.

  • AM70-Web-RT-7.4.60.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.

  • AM70-Web-RT-7.4.60.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.

  • ckWeb-RT.exe, the pre-installation check used with the AppManager setup program.

  • DefaultRule_Web-RT.xml, a configuration file used for deploying the module with Control Center.

When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.

4.0 Installing This Module

Run the module installer to install the module components in the following locations:

  • On the Response Time for Web computers you want to monitor (agents) to install the agent components.

  • On all console computers to install the Help and console extensions.

    NOTE:On all the console computers, close the console before you run the module installer. If you do not close the console, the module installation might fail.

Run the module installer only once on each of these computers.

When installing to each QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.

IMPORTANT:This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.

Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.

For more information about installing this module, see the AppManager Response Time for Web Management Guide, included in the download package.

5.0 Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.

  • Compatibility issue between Web Recorder and Internet Explorer. When you record web pages in the WebRecorder, some of the web pages might not render properly in the WebRecorder browser and the transaction might fail. You might also receive the Explorer is too old error message. (DOC340907 and ENG341762)

    To work around this issue, modify the registry setting as follows:

    1. Click Start.

    2. Type regedit in the search box and click OK to open Registry Editor.

    3. Do one of the following:

      • On 32-bit agent, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION

      • On 64-bit agent, go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION

    4. Right-click the FEATURE_BROWSER_EMULATION folder and then select New > DWORD (32-bit) Value. Specify the file name as webrecorder.exe.

    5. Double-click the webrecorder.exe file, select Decimal and type the appropriate value in Value data based on the Internet Explorer version installed on your machine, for example, if Internet Explorer 11 is installed on the agent machine, type 11000.

      NOTE:Ensure that you enter the appropriate value available in the BROWSER EMULATION section in the Microsoft article.

    6. Right-click the FEATURE_BROWSER_EMULATION folder and then select New > DWORD (32-bit) Value. Specify the file name as QWEBA6.EXE.

    7. Double-click the QWEBA6.EXE file, select Decimal and type the appropriate value in Value data based on the Internet Explorer version installed on your machine.

    8. Click OK and then close Registry Editor.

  • Running Web-RT on Windows 2008 R2 Service Pack 1 or Windows 7 computer with Internet Explorer 10 or Internet Explorer 11 might cause memory leak. Running Web-RT on Windows Server 2008 R2 Service Pack 1 or Windows 7 computer with Internet Explorer 10 or Internet Explorer 11 might cause memory leak in the Network Store Interface (NSI) services. To prevent the memory leak, NetIQ recommends that you install Microsoft hotfix 2847346, available from Microsoft Support. (DOC334133)

  • On a computer running Internet Explorer 9, Web Recorder fails during playback if you select Yes to the Security Warning messages. Web Recorder playback fails in this situation because the messages are not handled properly by Internet Explorer 9. To work around this issue, you can suppress the security messages. (ENG319861)

    To suppress security messages:

    1. In Internet Explorer, select Internet Options from the Tools menu and click the Security tab.

    2. Click Custom level.

    3. In the Settings table, under the Miscellaneous heading, select Enable for Display Mixed content.

    4. Click OK.

    5. On the Advanced tab, under the Security heading, disable Warn if changing between secure and not secure mode.

    6. Click OK.

  • Playback fails if you press Enter key after entering credentials while recording a transaction. On Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 computers, if you press Enter while recording, your credentials will be submitted, but the Web Recorder will not record this step. As a result, the entire playback will fail. To prevent this failure, click OK instead of pressing Enter when you submit your credentials at Web sites where you are recording transactions. (DOC319134)

  • Running simultaneous Web-RT_SendAndReceiveInternetMail jobs from multiple agents to the same POP3 mailbox can cause errors. If you run SendAndReceiveInternetMail jobs from more than one Web-RT agent to the same POP3 server and mailbox, collisions can occur. The script raises an event indicating that a POP3 error occurred. To avoid collisions like these, each Web-RT agent should run the SendAndReceiveInternetMail Knowledge Script to a different mailbox on the POP3 server. (DOC308003)

  • The AppManager ResponseTime for Web agent stops prematurely if you run a large job load on a computer running Windows Server 2003. A large job load includes hundreds of jobs on each agent. As a workaround, NetIQ Corporation recommends you install AppManager ResponseTime for Web on a 64-bit computer running Windows Server 2008. (ENG252109)

  • No hot key support. Some Web sites allow visitors to use hot keys such as Alt+G. The Web Recorder does not capture hot key sequences. To work around this issue, click the control instead. (ENG227251)

  • The Report_Web-RT_URLCheck report does not return data for the Web-RT_CheckURL Knowledge Script. To create a report containing results returned by the Web-RT_CheckURL Knowledge Script, use the default reports provided by AppManager. For more information about running reports, see the Control Center User Guide for AppManager. (DOC231510)

  • Reports do not work with data that have customized legends. The Web-RT reports included with the module do not report on data with customized legends. (DOC232262)

  • The data point does not display correctly. If you change certain options such as Measure Download Time, Validate, or Search in the Web-RT_CheckURL Knowledge Script while the job is running, the Operator Console or Control Center might display the data point incorrectly. To work around this issue, stop the job and then start a new job with the options you want to change. (ENG233418)

6.0 Previous Releases

This release of AppManager Response Time for Web includes enhancements added in previous releases.

6.1 Release 7.4.0.3, March 2018

This release of AppManager Response Time for Web resolved the following issues:

  • Running the CheckURL Knowledge Script might return the 12175 security error. This error occurred when the website uses the TLS 1.2 secure protocol. In this release, the issue is fixed. (ENG344332)

  • Running the CheckURL Knowledge Script might return the 12029 status code. This error occurred when the website uses the TLS 1.2 secure protocol. In this release, the issue is fixed. (ENG345525)

6.2 Release 7.4.0.2, April 2017

This release of AppManager Response Time for Web provided the following enhancement:

  • Support for Microsoft Windows Server 2016. This release supports Windows Server 2016. For more information, see System Requirements.

This release of AppManager Response Time for Web resolved the following issues:

  • WebRT stops collecting data with the attached settings in place. WebRT stopped unexpectedly in every iteration when webexsm.exe found null lines in nqWeb.cpp. In this release, a null check was inserted in nqWeb.cpp allowing a null check and logging it. (ENG339931)

  • CheckURL performs DNS Lookup even if the Include DNS Lookup time (if applicable)? parameter is disabled. The CheckURL Knowledge Script resolved the IP address of the URL even though the Include DNS Lookup time (if applicable)? parameter was not selected. In this release, the issue is fixed. (ENG342858)

6.3 Release 7.4.0.1, January 2016

This release of AppManager Response Time for Web resolves the following issues:

  • Web Recorder sometimes crashes while recording text nodes. This release resolves an issue in which the Web Recorder stopped unexpectedly when you performed Add Advance Search Step while recording text nodes in a web page. With this release, Web Recorder can add advanced search step on text nodes without crashing. (ENG339658)

6.4 Release 7.4, October 2015

This release of AppManager Response Time for Web provided the following enhancements:

  • Support for Microsoft Windows Server 2012 R2 and Windows 10. This release supports Windows Server 2012 R2 and Windows 10 (64-bit) installed on the agent computers. For more information, see the System Requirements.

  • Recording of overall processing time of Web-RT scripts. This release provides an enhancement in which Web-RT records the overall processing time of the steps when you run the Knowledge Script even when a particular step fails. (ENG247104)

  • URL Check Recorder detects the encoded URLs. This release provides an enhancement in which URL Check Recorder detects all the encoded URLs that have special characters such as %2D, %20. (ENG307132)

  • Web Recorder Playback runs successfully on the websites that use jQuery. This release provides the Add Click Step option in the Web Recorder that allows you to add a click step in the text input controls on the websites that use jQuery. (ENG332758)

This release of AppManager Response Time for Web resolved the following issues:

  • URL Check Recorder does not display the updated URL Verification Summary. This release resolves an issue in which the URL Check Recorder did not verify the URL that was placed at the end of the URL list. The problem occurred when you typed the URL in the URL list and without clicking outside the list, you directly clicked the Verify button. With this release, an update to URL Check Recorder ensures that all the URLs in the list are verified and generates the complete URL Verification Summary. (ENG255527)

  • Web Recorder Playback does not fail when there is a mismatch in the drop-down options. This release resolves an issue in which the Web Recorder Playback did not fail when a mismatch occurred in the drop-down options during the recording and the playback. With this release, an update to Web Recorder ensures that the playback fails when there is a mismatch in the drop-down options and detects the step that fails. (ENG326086)

  • Web Recorder Navigation Errors Playback fails to produce the Outcome for Status Code 403 and 404. This release resolves an issue in which Outcome of Web Recorder Navigate Errors Playback failed to follow the action that you had specified for Status Code 403 and 404. The failure occurred when you modified Status Description. With this release, Outcome follows the action that you specify for Status Code 403 and 404 irrespective of any modification in Status Description. (ENG255322)

  • URL Check Recorder fails to collect data from a page that has frames. This release resolves an issue in which the search string option of URL Check Recorder failed for the web pages with frames. With this release, an update to URL Check Recorder enables it to search strings on the web page that has frames. (ENG338923)

  • URL Check Recorder fails to monitor the URLs that have SSL certificate enabled. This release resolves an issue in which URL Check Recorder failed to monitor the URLs that have the SSL certificate enabled. With this release, an update to URL Check Recorder ensures that the URLs that have SSL certificate enabled are monitored successfully. (ENG337664)

  • URL Check Recorder fails to collect data. This release resolves an issue in which URL Check Recorder failed to collect data on connection time, download time and availability in certain instances. With this release, an update to URL Check Recorder prevents this failure. (ENG333749, ENG337064, ENG338067)

  • Web Recorder fails during playback with an error. This release resolves an issue in which Web Recorder failed during playback with status code 0X80004004. With this release, an update to Web Recorder ensures that the playback is successful. (ENG333339)

  • Web Recorder displays an error while recording a website in Internet Explorer 8. This release resolves an issue in which Web Recorder displayed the error: Our site is not optimized for your browser while recording a few websites that are optimized for Internet Explorer 8 or later. With this release, Web Recorder records the websites without the error. (ENG330119)

6.5 Release 7.3.39.0, January 2013

This release of AppManager Response Time for Web provided the following enhancements:

  • Support for Microsoft Windows Server 2012 and Windows 8. This release supports Windows Server 2012 and Windows 8 installed on the agent computers.

  • Support for Internet Explorer version 10. This release now supports Internet Explorer version 10. For more information, see System Requirements.

This release also resolved the following issues:

  • Web-RT_SendAndReceiveInternetMail and Web-RT_SendInternetMail Knowledge Scripts allow authentication with the SMTP server before sending emails. This release resolves an issue where the SMTP server required authentication before anyone could send email through it. This release enables the Web-RT_SendAndReceiveInternetMail and Web-RT_SendInternetMail Knowledge Scripts to allow users to authenticate themselves with the SMTP server before sending emails. (ENG263689)

  • Web Recorder Playback allows the wildcard character to replace dynamic characters. This release resolves an issue where the Web Recorder Playback failed because the dynamic characters on the website had changed between the recording and the playback. This release enhances the Web Recorder Playback to support the wildcard character in the select step so that users can replace dynamic characters. (ENG325236)

  • Web Recorder supports the editing of URL in the navigation and Open in New Window steps. This release resolves an issue where the URL in the navigation steps, which got changed, was not editable in the script and the script was not reusable. This release enables the Web Recorder to support modification to the URL in the Navigation and Open in New Window steps. (ENG275161)

  • Web Recorder sometimes fails to record the Onclick and OnMouseDown events in the SharePoint site. This release resolves an issue where the SharePoint Web page was cancelling the OnClick and OnMouseDown events and the recording failed. With this release, two new options OnMouseUp and OnMouseDown have been included, which can be configured to record the left-button mouse click. (ENG323983)

  • Web-RT_SendAndReceiveInternetMail uses the same email address for the sender and receiver. This release resolves an issue in which the Web-RT_SendAndReceiveInternetMail script used the receiver’s email address as the sender address, which caused the script to fail where policies were in place to block messages with the same sender and receiver. With this release, the script includes new parameters to specify sender details or use the same settings as the POP3 server. (ENG244690)

  • Web-RT screen captures are blank when the console is locked. This release resolves an issue where Web-RT Knowledge Scripts captured blank screens if a script was running on an agent computer and the primary desktop session was locked. With this release, the Web-RT Knowledge Scripts capture non-blank screens, even if a script is running on an agent computer and the primary desktop session is locked. (ENG304927)

  • Web Recorder sometimes fails to Record or Playback if JavaScript events are associated with Text Box or Text Area Controls. This release resolves an issue in which Recording or Playback did not invoke the event to manipulate text entered in a text box or Text Area if the Web site used JavaScript events associated with Text box or Text Area. With this release, the JavaScript events associated with Text Box or Text Area are handled properly. (ENG240690 and ENG308557)

  • The Search button does not activate after entering the search string while recording a Web transaction using the Web Recorder. This release resolves an issue where the Search button did not activate after you entered text in the search text box if a JavaScript event is associated with the search text box. With this release, the JavaScript event associated with the search text box is handled properly and the Search button activates when you enter the text in the search text box. (ENG230763)

  • The Web-RT_CheckURL Knowledge Script does not collect data points correctly. This release resolves an issue in which the Knowledge Script was not collecting data when an event was generated. This error occurred only when the Start collecting data when an event is generated parameter is selected. With this release, the Knowledge Script collects data when an event is generated. (ENG322975)

  • Web Recorder fails to navigate to a target Web page while recording a transaction at a Web site. This release resolves an issue where the browser window of the Web Recorder tool failed to navigate to a target Web page on an anchored link. The user was not able to record and play back the steps on the target Web page. Also during recording, the background controls were not recorded for the step that contains Option and the playback failed. With this release, the Web Recorder tool navigates to the target Web page correctly and also the background controls for the Option step display properly during the playback. (ENG323077)

6.6 Release 7.2.37.0, June 2012

This release of AppManager Response Time for Web provided the following enhancement:

  • Support for Internet Explorer versions 8 and 9. This release now supports Internet Explorer versions 8 and 9. For more information, see System Requirements.

This release also resolved the following issues:

  • Web-RT_FTP Knowledge Script generates a transaction failure when connecting to the FTP server. This release resolves an issue in which the Web-RT_FTP script raises a transaction failure event when the FTP server is configured with a password that contains special characters, such as an "@". With this release, an update to the Web-RT_FTP Knowledge Script prevents the transaction failure from occurring. (ENG297322)

  • Web-RT Knowledge Scripts do not encode XML data in dynamic XML legends. With this release, the Web-RT Knowledge Scripts encode XML data in dynamic XML legends, which prevents the script from failing even if you entered an invalid XML character, such as an "&", in the step name. (ENG243315)

  • Actions for a custom Web-RT script stop working if you rename the script with URL Check Recorder. This release resolves an issue in which renaming a script created with the URL Check Recorder caused the script's actions to break. With this release, you can rename a script in URL Check Recorder without causing the script to fail. (ENG319173)

  • Web Recorder does not let you select all objects in a JSP-based page. This release resolves an issue in which you could not select some of the objects on a Web site created primarily with JavaServer Pages (JSP), such as drop-down menus with multiple tiers or options on them. With this release, you can select all the objects on a site built with JSP. (ENG241360)

  • Web Recorder Knowledge Scripts could not be opened if created on a computer with a locale set to Japan. This release resolves an issue in which you could not open a Web Recorder script created on a computer localized to Japan. If you set the locale of the Web-RT client computer to Japan and then recorded a web transaction for a Japanese Web site, the next time you opened the script it failed with the following error: "An error occurred while reading the file. The file is not a Web Recorder file or may have a bad format. Operation aborted." With this release, the computer locale setting no longer prevents you from opening Web Recorder scripts. (ENG274649)

6.7 Release 7.1.240.0, March 2012

This release of AppManager Response Time for Web resolved the following issues:

  • The Web-RT_URLCheck Knowledge Script generates different results than Web Recorder for the same site. This release resolves an issue in which the results from running the Web-RT_URLCheck script were different from the Web Recorder results. This inconsistency was caused by the URLCheck script not properly recognizing all of the items on the monitored Web site, such as some scripts and images. With this release, an update to the URLCheck Knowledge Script ensures that the script properly monitors all the items on the Web site so that its results more closely match the Web Recorder results. (ENG314849)

  • The event severity for a Navigate Error is not set properly. This release resolves an issue in which, when a recorded script generated a Navigate Error, the script used an incorrect event severity. With this release, Web-RT scripts use the correct event severity for a Navigate Error. (ENG316620)

  • Replacing the ampersand (&) symbol causes the Web-RT Knowledge Scripts to fail when an Internet resource is unavailable. This release resolves an issue in which you used the Web-RT_CheckURL Knowledge Script to monitor a URL with an ampersand in its name and a timeout occurred. Because the Web-RT scripts did not properly handle URLs containing one or more ampersands, the script could not connect to the URL after the timeout. With this release, an update to the Web-RT Knowledge Scripts allow the scripts to properly monitor URLs containing one or more ampersand symbols, even if a timeout occurs. (ENG313978)

  • In the previous version of Web-RT, you could not check in a script with Web Recorder using Windows Authentication. This release resolves an issue in which, after upgrading to release 7.1.216.0 of Web-RT, you could not use Windows authentication to successfully check in a recorded script through Web Recorder. With this release, you can use Windows authentication as well as SQL authentication to check in recorded scripts with Web Recorder. (ENG313472)

6.8 Release 7.1.216.0, September 2011

This release of AppManager Response Time for Web resolved the following issues:

  • Graph data summary in Chart Console shows extra response time data. This release resolves an issue in which the Chart Console displayed correct data for each data point, but also displayed an extra set of inaccurate response time data below the correct data. With this release, the extra set of data no longer displays in the Chart Console. (ENG304661)

  • Cannot save long Knowledge Script names in URL Check Recorder and Web Recorder. This release resolves an issue with the URL Check Recorder and the Web Recorder in which you could not save Knowledge Script names that contained more than 40 characters. With this release, you can save names with more than 40 characters. (ENG307889)

6.9 Release 7.1.199.0, May 2011

This release of AppManager Response Time for Web resolved the following issues:

  • Web Recorder scripts do not generate actions. This release addresses an issue in which Knowledge Scripts you created in Web Recorder did not generate actions when you set them to do so. With this release, a change to the Knowledge Scripts in Web Recorder allows actions to be successfully generated. (ENG262944)

  • Threshold titles contain extraneous numeric value. This release addresses an issue in which threshold titles you created in URL Check Recorder appeared in event messages and data stream legends with the value "-1" appended. The addition of the "-1" occurred when URL index variables ([x], [d], or [l]) were removed from event legends and data stream legends in URL Check Recorder. The actual threshold value was correct, but the title was incorrect. With this release, the threshold titles appear as you set them, without the appended value. (ENG265638)

    NOTE:As a best practice, use URL index variables for Knowledge Scripts that monitor multiple URLs. The variables ensure event and data stream legends for each monitored URL are unique. If you remove URL indexes, it is recommended that you do so only for Knowledge Scripts that monitor a single URL.

  • Running multiple Web-RT_SendAndReceiveInternetMail jobs leads to timeout errors. This release addresses an issue in which running multiple instances of the Web-RT_SendAndReceiveInternetMail Knowledge Script job on the same agent computer resulted in queue and job timeout errors. With this release, a change in the way messages are queued and an increase in the length of the job timeout allow multiple instances of the SendAndReceiveInternetMail job to run successfully. (ENG267032)

  • Dynamic legends are not generated for processing time for the Web-RT_CheckURL Knowledge Script. This release addresses an issue in which the Web-RT_CheckURL script did not generate dynamic legend information in the data header for processing time. As a result, the data did not get processed by Analysis Center. With this release, a change to the Knowledge Script enables the dynamic legends to be generated properly and processed by Analysis Center. (ENG307048)

  • URL Check Recorder cannot verify the connectivity of all URLs. This release addresses an issue in which verifying the connectivity of all of your URLs with the URL Check Recorder resulted in a 404 Error due to an error with URL redirection. With this release, the URL redirections work properly, enabling you to verify URL connectivity. (ENG279374)

  • A disk full message occurs when you try to save screen captures. This release addresses an issue in which a Disk is full message occurred when you attempted to save a screen capture, even if you had sufficient drive space. The previous release could not handle volume sizes greater than 2 gigabytes. This release lets you monitor hard drives that are greater than 2 gigabytes in size. (ENG284093)

  • The Web-RT_URLCheck Knowledge Script failed to collect data on a URL containing an ampersand (&) character. This release addresses an issue that occurred when the target URL included an ampersand, which prevented the Web-RT_URLCheck job from properly creating its data stream. (ENG270104)

  • The Web-RT_URLCheck Knowledge Script fails to raise an event when validating all links if one of the specified links is down. This release addresses an issue in which the Web-RT_URLCheck Knowledge Script fails to raise an event for a broken link in a group of links that the script is attempting to validate. (ENG293983)

  • The Web-RT_URLCheck Knowledge Script generates invalid status code events. This release addresses an issue in which the Web-RT_URLCheck script generated an Invalid status code event message. (ENG281240)

6.10 Release 7.1.147.0, September 2009

This release of AppManager Response Time for Web resolved the following issues:

  • Edited Knowledge Scripts lose associated actions. Before you install this release, URLCheckRecorder and WebRecorder Knowledge Scripts lose associated actions when the scripts are checked out, edited, and then checked back in. After you install this release, you can check out, edit, and check in a URLCheckRecorder or WebRecorder Knowledge Script and maintain any actions you selected on the Action tab and any customizations you selected on the Advanced tab. (ENG266911)

  • Redirection does not preserve the host header or post data with the URL Check Recorder. Before you install this release, the host header and post data is not preserved with a redirect with the URL Check Recorder. After you install this release, you can choose to include a header with redirection and also include post data with a URL redirection, using the new options on the General tab on the URL Property dialog box. You can also set these new parameters under the General heading of the CheckURL Knowledge Script. (ENG270352)

6.11 Hotfix 71499, March 2009

Hotfix 71499 resolved the following issue:

  • Multiple redirections to same site raise looping error. Before you install this release, URL Check Recorder identifies multiple redirections to the same site as looping and raises an event. In your Web environment, redirections of this type may not be an error. After you install this release, a new parameter on the Availability tab of the URL Properties dialog box and the Availability tab of the Default URL Properties dialog box allows you to indicate how many times a URL can be redirected to the same location before an event is raised for looping. For more information, see the Help for the Availability tab of the URL Properties and Default URL Properties dialog boxes in URL Check Recorder. (ENG262593)

6.12 Hotfix 71311, November 2008

Hotfix 71311 resolved the following issues:

  • Support for Windows Server 2008, Standard or Enterprise edition. You can install AppManager ResponseTime for Web on 32-bit or 64-bit Windows 2008 computers, Standard or Enterprise edition. Installing on a 32-bit or 64-bit Windows Server 2008 computer also prevents AppManager ResponseTime for Web from stopping prematurely when running a large job load, a situation that occurred when running AppManager ResponseTime for Web on a computer with Windows Server 2003. (ENG254547)

    NOTE:Support for monitoring a system running Windows Server 2008 requires the AppManager Agent for Windows Server 2008.

  • The URL Check Recorder does not prompt you to save after pasting URL properties. Before you install this release, if you copy and paste URL properties in the URL Check Recorder application, the URL Check Recorder fails to notice a change in the document. As a result, no asterisk appears in the Title Bar and you are not prompted to save if you close the Recorder, which could lead to lost data. After you install this release, the act of pasting URL properties is marked as an edit, and the Recorder prompts you to save to prevent your changes from being lost. (ENG254546)

6.13 Hotfix 71263, October 2008

Hotfix 71263 resolved an issue in which the URL Check Recorder detects a false loop condition. Before you install this release, the URLCheck Knowledge Script creates a loop when checking a URL that has a redirect attached to it, and the destination URL does not get checked. After you install this release, the script handles a redirected URL in the proper manner, without looping. (ENG251962)

6.14 Hotfix 71186, September 2008

Hotfix 71186 resolved the following issues:

  • A URLCheck Knowledge Script does not follow a redirect. Before you install this release, a URLCheck Knowledge Script that you create with URL Check Recorder might not correctly access a URL if that URL includes a redirect to another site. After you install this release, a URLCheck script follows a redirect successfully. (ENG245506)

  • Redirection from a secure site considered looping in a URLCheck Knowledge Script. Before you install this release, a URLCheck Knowledge Script you create with URL Check Recorder might consider the act of redirecting you from a secure, encrypted site (https://) to a non-encrypted site (http://) to be looping, and the script generates an event. After you install this release, the URLCheck script no longer mistakes redirection from a secure site as looping. (ENG248944)

  • SendAndReceiveInternetMail Knowledge Script fails for Microsoft Exchange Server 2007. Before you install this release, the SendAndReceiveInternetMail Knowledge Script fails when you attempt to run it on Microsoft Exchange Server 2007. In Exchange Server 2007, changes to the Message Header caused a POP3 time out for SendAndReceiveInternetMail. After you install this release, the SendAndReceiveInternetMail Knowledge Script parses the Message Header correctly. (ENG234144)

6.15 Release 7.1, September 2007

Release 7.1 offered the following enhancements and fixes:

  • Reduced Duplication of Information and Simplification of Installation. As of AppManager 7.0.1, NetIQ no longer provides Knowledge Base content for AppManager Knowledge Scripts. You can continue to find information about any Knowledge Script in the AppManager Help.

  • Console Integration of URL Check Recorder and Web Recorder Job Configuration. This version integrates the Operator and Control Center Consoles with the Web Recorder and URL Check Recorders. Previously, if you wanted to modify parameters that were available only within the Web or URL Check Recorder, you had to check in the script again and start a new job. This version allows you to modify the additional parameters in running Web-RT jobs. To access the parameters, on the Values tab in the Properties of the job, click Recorder.

    This feature requires you to install the Web and URL Check Recorders on the Operator and Control Center Console computers. This feature also requires AppManager version 7.0 Service Pack 1. For more information about requirements, see the AppManager Response Time for Web Management Guide.

  • Improved Web Recorder Ease of Use. This version improves the Web Recorder by adding several features:

    • The search capabilities have been improved to allow you to add a search step without highlighting text, add a search step after recording has completed, and to generate an event and continue when a search fails.

    • The HTML Structure window has been improved to provide a new Menu bar and Status bar.

    • In this version, the HTML Structure Window provides the following new commands: Copy, Copy Value, Find, Auto Refresh, and Refresh Now.

    • Snapshots are now also available for navigate errors. Previously, snapshots were available only for object not found errors.

    • The snapshots file format has changed from BMP to JPEG, which produces a smaller file size.

    • New parameter for WebTransaction Knowledge Script: Include in Overall Response Time row in Step section.

  • Improved Web Recorder Results. This version improves the Web Recorder results by adding several features:

    • Playback results are now provided in an HTML format.

    • The Options window includes a new Recorder tab to configure playback result options.

    • You can customize navigation errors to change the outcomes. This version also provides new outcomes. You can also add custom navigation errors.

    • You can set the severity of an error by modifying the Event Severity on Navigate Error parameter.

  • Improved Web Recorder Form Handling. This version allows you to add a submit step for forms that do not contain a submit button.

  • Improved URL Check Recorder User Interface and Functionality. This version improves the URL Check Recorder by adding several features:

    • All failures discovered by the URLCheck Knowledge Script will generate separate events. Previously, all failures were consolidated into a single event.

    • New table provided to show all the URL redirections.

    • This version includes a new toolbar to make the user interface consistent with Web Recorder.

    • Improved import of URLs to use a text file that can include descriptions and custom delimiters.

  • Ability to Provide Description in a Knowledge Script. This version allows you to add a short and a long description to a Knowledge Script while checking in the Knowledge Script.

  • New and Updated Knowledge Scripts:

    • URLCheck: You can specify that a URLCheck Knowledge Script raise an event when a URL redirects to another URL. There is also a new set of parameters to monitor the processing time necessary to run the Knowledge Script. Also, all parameters have been reorganized.

    • WebTransaction: There is a new parameter, Event Severity on Navigate Error, which allows you to indicate the importance of the event when any individual step fails because of a navigate error.

    • CheckURL: This new Knowledge Script allows you to monitor the availability and performance of a single URL, including measuring connection and download time and validating and searching for text, links, and objects.

7.0 Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information Web site.

For general corporate and product information, see the NetIQ Corporate Web site.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.