HP Business Availability Center 7.03 Readme Software version: 7.03 / October 2008 This file provides information about HP Business Availability Center 7.03, HP Business Availability Center 7.02 (for 7.02 information, click here), HP Business Availability Center 7.01 (for 7.01 information, click here), and HP Business Availability Center 7.0 (for 7.0 information, click here). Business Availability Center 7.03 Files Installation Prerequisites Installation Uninstallation Version Content and Limitations Updated Components Updated HP Business Availability Center Support Matrixes Business Availability Center 7.03 Files Business Availability Center 7.03 includes the following files: Business Availability Center 7.03 setup file Setup.exe (Windows installation) Setup.bin (Solaris installation) Component setup files New: Real User Monitor Probe 7.03 (Linux) New: Real User Monitor Engine 7.03 (Windows) Note: You need to separately download new component setup files. Documentation files whatsnew.html readme703.html (includes 7.02, 7.01, and 7.0 Readmes) SLA_Dynamic_Update.pdf - describes Dynamic Business Process Monitor locations in Service Level Management Service_Manager_adapter.pdf - describes how to work with the ServiceCenter/Service Manager federated adapter plug-in component Upgrade_RUM.pdf - contains instructions on upgrading the Real User Monitor probe and engine. Additional files tzupdater.jar - file needed for Daylight Savings Time definition update Installation Prerequisites Business Availability Center 7.03 must be installed on top of Business Availability Center 7.0, 7.01, or 7.02. Installation If you do not yet have Business Availability Center 7.0 installed, install it according to the instructions in the Business Availability Center 7.0 Deployment Guide. Then install Business Availability Center 7.03 on every Business Availability Center server by double-clicking on the relevant setup file (Windows or Solaris) and following the on-screen instructions. If relevant, after installation is complete run the Daylight Savings Time update procedure using the updated tzupdater.jar file included with Business Availability Center 7.03. This provides your system with the latest DST definitions. Note that the tzupdater.jar file included with Business Availability Center 7.03 only includes time zone updates for the following countries: Brazil, Argentina, Morocco, Pakistan, Turkey, Mauritius. Copy the tzupdater.jar file to the <HP Business Availability Center root directory>\bin directory. Stop HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Disable Business Availability Center). Open a Command Prompt window (DOS shell) and change the directory to <HP Business Availability Center root directory>\bin. Run the following command to set JAVA_HOME: set JAVA_HOME=%TOPAZ_HOME%\jre Run the following command to install the patch: %JAVA_HOME%\bin\java -jar tzupdater.jar -u -bc Start HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Enable Business Availability Center). For additional details on updating Daylight Savings Time definitions, including the procedure for using the tzupdater.jar file on Business Process Monitor instances, see the Business Availability Center 7.0 Deployment Guide. If you are experiencing network errors, for example buffer overflow, in the log, then try removing the /3GB flag from your Windows Boot.ini file on the Business Availability Center servers and restart Windows. If you are installing Business Availability Center 7.03 on top of 7.02, 7.01, or 7.0 and are working with an external UCMDB architecture, you must perform the below workaround to deploy the 7.03 BAC packages to the UCMDB server (as they are not deployed automatically to the external UCMDB server during the installation). Perform the workaround after installing Business Availability Center 7.03 and UCMDB 7.02 on the external UCMDB machine. Manually copy the packages from <Business Availability Center root directory>\mam_lib\bac_packages directory on the Business Availability Center Data Processing Server to the root\lib\packages directory on the UCMDB server. Start the UCMDB server. Open the JMX console running on the UCMDB Server (http://<UCMDB_server_name>:8080/jmx-console) and under MAM Packaging Services, locate the deployPackages JMX. Invoke the JMX. Start Business Availability Center servers. Federated Adapters upgrade notes: Out of the box adapters. If you changed any configuration files for out-of-the-box Service Desk adapter or Generic DB adapter, back up these files to a different location before 7.03 installation. Otherwise you will lose your data. After 7.03 installation, copy the backed up configuration files back to their original locations: Service Desk adapter: Back up the serviceDeskConfiguration.xml file in the <HP Business Availability Center Data Processing Server root directory>\fcmdb\CodeBase\ServiceDeskAdapter directory. Generic DB adapter: Back up the files in the <HP Business Availability Center Data Processing Server root directory>\fcmdb\CodeBase\GenericDBAdapter\META-INF directory. Proprietary adapters. Save all proprietary adapters before installing 7.03, and then copy them to their original location after 7.03 installation. Uninstallation For instructions on completely uninstalling Business Availability Center, see the Business Availability Center 7.0 Deployment Guide. To roll back an installation of Business Availability Center 7.03 to Business Availability Center 7.0, 7.01, or 7.02 follow the instructions below. Stop the HP Business Availability Center service on all servers and confirm they are stopped. Stop the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers. From Control Panel, select Add/Remove Programs > Change or Remove Programs > HP Business Availability Center 7.03. On Windows 2003 Server make sure to check the Show Updates check box in order to display version 7.03 beneath the root HP Business Availability Center entry. When the uninstall process is complete, restart the machine if requested. Restart the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers. Restart the HP Business Availability Center service on all servers. When uninstalling or rolling back HP Business Availability Center, make sure to uninstall or rollback the data collectors as well. Version Content and Limitations In Service Level Management, the Agreements Wizard now includes the Include Locations option, used when the Business Process Monitoring source adapter is set to work with Transaction/Location hierarchy structure. You select the Include Locations option to enable the agreement to be dynamically updated with new Business Process Monitor locations for transactions. For details, see separate SLA_Dynamic_Update.pdf located in the Download area. Added out-of-the-box ServiceCenter/Service Manager federated adapter plug-in to support federated queries to ServiceCenter/Service Manager. For details, see separate Service_Manager_adapter.pdf located in the Download area. Known Limitation and Workaround: When changes are made in View Manager and these changes affect the results of a TQL, federated CIs in the view are not updated. This is because federated TQLs are calculated ad-hoc only and are not updated when a view is recalculated. To update the federated CIs, right-click the view in View Explorer and select "Full View Recalculation." (Note that the recalculation may take a long time.) Bug fixes - see table below for details: Description SR/E-Sar Number Area Fixed issue of selected recipients not appearing in Scheduled Reports administration 42083 BAC_Applications Fixed issue causing error: "BLE Service is currently unavailable. Please try again in a few minutes" 3601815044 BAC_Dasboard Upgraded Geographical Map engine to latest supported version 45611 BAC_Dasboard Fixed issue of reaggregation in non-partitioned environment 203681 BAC_DataEntry Fixed issue of Web Data Entry process getting stuck during sample publishing 43895 BAC_DataEntry Fixed issue of alert engine cache not updating after CMDB restart 42397 BAC_Platform Added support for various GMT offsets in scheduled Trend reports 43003 BAC_Platform Fixed issue in event-based alerts of schedule for receiving alerts being ignored 3602731079 / 4000270200 BAC_Platform Fixed issue of ConcurrentModificationException error when editing alert with complex dominant alert tree 3602998493 / 4000295406 BAC_Platform Fixed issue of users not being able to open the CMDB interface when a user is associated with more than one group 1601350738 BAC_PlatformAdmin Fixed issue related to removing or moving a group of users in User Management 1601419886 BAC_PlatformAdmin Fixed issue of calculation error in Service Level Management - SiteScope Monitor Rule 1601825610 BAC_SLM Fixed issue related to Service Level Management permissions 3602931611 BAC_SLM Internal bug fixes Updated Components The following updated components are included with Business Availability Center 7.03: Real User Monitor Probe 7.03 Build 7.0.88 (Linux)  For instructions on upgrading the Real User Monitor probe, see separate Upgrade_RUM.pdf located in the Download area. Added the ability to configure the probe to handle X-forwarded-for differently. Real User Monitor Engine 7.03 Build 15 (Windows) For instructions on upgrading the Real User Monitor engine, see separate Upgrade_RUM.pdf located in the Download area. Performance improvements Updated HP Business Availability Center Support Matrixes This section describes updated matrix sections for various environments and components supported by HP Business Availability Center. Business Availability Center Component Support Matrix Only HP Business Availability Center 7.03 compatibility is shown in this table. For 7.02, 7.01, and 7.0 tables, see the matrix in the relevant section below. (For each BPM version, the latest supported VuGen version is mentioned. All previous versions of VuGen are supported as well.) √=supported, X=not supported Compatibility Matrix HP Business Availability Center 7.03 BPM 7.0 (VuGen 9.0) √ (Recommended) BPM 6.5 (VuGen 8.1 FP 3) √ BPM 6.4.1 (VuGen 8.1 FP3) √ BPM 6.4 (VuGen 8.1) √ BPM 6.3 (VuGen 8.1) √ BPM 6.2 (VuGen 8.1) √ QTP SAP R/3 7.31 √ QTP 9.1/2 √ QTP 9.0 √ SiteScope 9.02 √ (Recommended) SiteScope 9.01 √ SiteScope 9.0 √ SiteScope 8.6-8.8 √ SiteScope 8.5 √ SiteScope 8.2.1 √ SiteScope 8.1.2 √ SiteScope 8.1.1 √ SiteScope 8.0 SP2 √ SiteScope 7.9.5.0 √ Real User Monitor Engine 7.03 √ (Can also work with BAC 7.0) Real User Monitor Engine 7.02 √ (Can also work with BAC 7.0) Real User Monitor Engine 7.01 √ (Can also work with BAC 7.0) Real User Monitor Engine 7.0 √ Real User Monitor Probe 7.03 √ (Can also work with BAC 7.0) Real User Monitor Probe 7.02 √ (Can also work with BAC 7.0) Real User Monitor Probe 7.01 √ (Can also work with BAC 7.0) Real User Monitor Probe 7.0 √ Real User Monitor Engine 6.5 X Real User Monitor Probe 6.5 X Real User Monitor Engine 6.2 X Real User Monitor Probe 6.2 X Real User Monitor Engine 6.1 X Real User Monitor Probe 6.1 X Discovery Probe 7.02 √ Discovery Probe 7.01 X Discovery Probe 7.0 X Discovery Probe 6.5 X Discovery Probe 6.2 X Discovery Probe 6.1 X HP Business Availability Center 7.02 Readme Software version: 7.02 / May 2008 This file provides information about HP Business Availability Center 7.02, HP Business Availability Center 7.01 (for 7.01 information, click here), and HP Business Availability Center 7.0 (for 7.0 information, click here). Business Availability Center 7.02 Files Installation Prerequisites Installation Uninstallation Version Content and Limitations Updated Components Updated HP Business Availability Center Support Matrixes Business Availability Center 7.02 Files Business Availability Center 7.02 includes the following files: Business Availability Center 7.02 setup file Setup.exe (Windows installation) Setup.bin (Solaris installation) Component setup files New: Real User Monitor Probe 7.02 (Linux) New: Real User Monitor Engine 7.02 (Windows) New: Discovery Probe 7.02 (Windows) New: SiteScope 9.02 (Windows, Solaris, Linux) Note: You need to separately download new component setup files. Documentation files whatsnew.html readme702.html (includes 7.01 and 7.0 Readmes) SLA_Dynamic_Update.pdf - describes Dynamic Business Process Monitor locations in Service Level Management Service_Manager_adapter.pdf - describes how to work with the ServiceCenter/Service Manager federated adapter plug-in component Upgrade_RUM.pdf - contains instructions on upgrading the Real User Monitor probe and engine. Additional files tzupdater.jar - file needed for Daylight Savings Time definition update Installation Prerequisites Business Availability Center 7.02 must be installed on top of Business Availability Center 7.0 or 7.01. Installation If you do not yet have Business Availability Center 7.0 installed, install it according to the instructions in the Business Availability Center 7.0 Deployment Guide. Then install Business Availability Center 7.02 on every Business Availability Center server by double-clicking on the relevant setup file (Windows or Solaris) and following the on-screen instructions. If relevant, after installation is complete run the Daylight Savings Time update procedure using the updated tzupdater.jar file included with Business Availability Center 7.02. This provides your system with the latest DST definitions. Note that the tzupdater.jar file included with Business Availability Center 7.02 only includes time zone updates for the following countries: Argentina, Chile, Cuba, Iraq, Syria, and Venezuela. Copy the tzupdater.jar file to the <HP Business Availability Center root directory>\bin directory. Stop HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Disable Business Availability Center). Open a Command Prompt window (DOS shell) and change the directory to <HP Business Availability Center root directory>\bin. Run the following command to set JAVA_HOME: set JAVA_HOME=%TOPAZ_HOME%\jre Run the following command to install the patch: %JAVA_HOME%\bin\java -jar tzupdater.jar -u -bc Start HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Enable Business Availability Center). For additional details on updating Daylight Savings Time definitions, including the procedure for using the tzupdater.jar file on Business Process Monitor instances, see the Business Availability Center 7.0 Deployment Guide. If you are experiencing network errors, for example buffer overflow, in the log, then try removing the /3GB flag from your Windows Boot.ini file on the Business Availability Center servers and restart Windows. If you are installing Business Availability Center 7.02 on top of 7.01 or 7.0 and are working with an external UCMDB architecture, you must perform the below workaround to deploy the 7.02 BAC packages to the UCMDB server (as they are not deployed automatically to the external UCMDB server during the installation). Perform the workaround after installing Business Availability Center 7.02 and UCMDB 7.02 on the external UCMDB machine. Manually copy the packages from <Business Availability Center root directory>\mam_lib\bac_packages directory on the Business Availability Center Data Processing Server to the root\lib\packages directory on the UCMDB server. Start the UCMDB server. Deploy the packages. For details, see the Package Manager section of the Model Management guide. Start Business Availability Center servers. Federated Adapters upgrade notes: Out of the box adapters. If you changed any configuration files for out-of-the-box Service Desk adapter or Generic DB adapter, back up these files to a different location before 7.02 installation. Otherwise you will lose your data. After 7.02 installation, copy the backed up configuration files back to their original locations: Service Desk adapter: Back up the serviceDeskConfiguration.xml file in the UCMDB\UCMDBServer\j2f\fcmdb\CodeBase\ServiceDeskAdapter directory. Generic DB adapter: Back up the files in the UCMDB\UCMDBServer\j2f\fcmdb\CodeBase\GenericDBAdapter\META-INF directory. Proprietary adapters. Save all proprietary adapters before installing 7.02, and then copy them to their original location after 7.02 installation. Uninstallation For instructions on completely uninstalling Business Availability Center, see the Business Availability Center 7.0 Deployment Guide. To roll back an installation of Business Availability Center 7.02 to Business Availability Center 7.0 or 7.01, follow the instructions below. Stop the HP Business Availability Center service on all servers and confirm they are stopped. Stop the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers. From Control Panel, select Add/Remove Programs > Change or Remove Programs > HP Business Availability Center 7.02. On Windows 2003 Server make sure to check the Show Updates check box in order to display version 7.02 beneath the root HP Business Availability Center entry. When the uninstall process is complete, restart the machine if requested. Restart the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers. Restart the HP Business Availability Center service on all servers. When uninstalling or rolling back HP Business Availability Center, make sure to uninstall or rollback the data collectors as well. Version Content and Limitations In Service Level Management, the Agreements Wizard now includes the Include Locations option, used when the Business Process Monitoring source adapter is set to work with Transaction/Location hierarchy structure. You select the Include Locations option to enable the agreement to be dynamically updated with new Business Process Monitor locations for transactions. For details, see separate SLA_Dynamic_Update.pdf located in the Download area. Added out-of-the-box ServiceCenter/Service Manager federated adapter plug-in to support federated queries to ServiceCenter/Service Manager. For details, see separate Service_Manager_adapter.pdf located in the Download area. Known Limitation and Workaround: When changes are made in View Manager and these changes affect the results of a TQL, federated CIs in the view are not updated. This is because federated TQLs are calculated ad-hoc only and are not updated when a view is recalculated. To update the federated CIs, right-click the view in View Explorer and select "Full View Recalculation." (Note that the recalculation may take a long time.) Bug fixes - see table below for details: Description SR/E-Sar Number Area Fixed issue of switching between Transaction Analysis and Location Analysis not keeping time interval of five minutes 39663 BAC_Platform Fixed issue of EUM Status Snapshot showing "Internal error" when transaction deleted 39713 BAC_EUM Internal bug fixes Updated Components The following updated components are included with Business Availability Center 7.02: Real User Monitor Probe 7.02 Build 7.0.84 (Linux)  For instructions on upgrading the Real User Monitor probe, see separate Upgrade_RUM.pdf located in the Download area. Bug fixes Real User Monitor Engine 7.02 Build 10 (Windows) For instructions on upgrading the Real User Monitor engine, see separate Upgrade_RUM.pdf located in the Download area. Added ability to filter out specific users (like synthetic users) Fixed issue of SSL Key store not rejecting incorrect SSL keys Fixed upgrade issue of export/import not handling certain files (hosts file and mtime.xml) Fixed issue of upgrade not considering the hosts files Fixed issue of user name resolution not working when large file was used Fixed issue of JMX property "AccumulatePagesInTransactions" not surviving restart Fixed issues related to Turkish environments Fixed minor issues related to stability Fixed issue of Session Analyzer reports not sorted by time. Now, latest sessions are listed first. Discovery Probe 7.02 Build 23 To install the Discovery Probe, first uninstall the existing Discovery Probe via Start > Programs > UCMDB > Uninstall UCMDB Discovery Probe. Then run Discovery_probe.exe. Bug fixes SiteScope 9.02 Build 927 (Windows, Solaris, Linux) Bug fixes (for details, see the SiteScope readme file, ReleaseNotes.htm) Updated HP Business Availability Center Support Matrixes This section describes updated matrix sections for various environments and components supported by HP Business Availability Center. Business Availability Center Component Support Matrix Only HP Business Availability Center 7.02 compatibility is shown in this table. For 7.01 and 7.0 tables, see the matrix in the relevant section below. (For each BPM version, the latest supported VuGen version is mentioned. All previous versions of VuGen are supported as well.) √=supported, X=not supported Compatibility Matrix HP Business Availability Center 7.02 BPM 7.0 (VuGen 9.0) √ (Recommended) BPM 6.5 (VuGen 8.1 FP 3) √ BPM 6.4.1 (VuGen 8.1 FP3) √ BPM 6.4 (VuGen 8.1) √ BPM 6.3 (VuGen 8.1) √ BPM 6.2 (VuGen 8.1) √ QTP SAP R/3 7.31 √ QTP 9.1/2 √ QTP 9.0 √ SiteScope 9.02 √ (Recommended) SiteScope 9.01 √ SiteScope 9.0 √ SiteScope 8.6-8.8 √ SiteScope 8.5 √ SiteScope 8.2.1 √ SiteScope 8.1.2 √ SiteScope 8.1.1 √ SiteScope 8.0 SP2 √ SiteScope 7.9.5.0 √ Real User Monitor Engine 7.02 √ (Can also work with BAC 7.0) Real User Monitor Engine 7.01 √ (Can also work with BAC 7.0) Real User Monitor Engine 7.0 √ Real User Monitor Probe 7.02 √ (Can also work with BAC 7.0) Real User Monitor Probe 7.01 √ (Can also work with BAC 7.0) Real User Monitor Probe 7.0 √ Real User Monitor Engine 6.5 X Real User Monitor Probe 6.5 X Real User Monitor Engine 6.2 X Real User Monitor Probe 6.2 X Real User Monitor Engine 6.1 X Real User Monitor Probe 6.1 X Discovery Probe 7.02 √ Discovery Probe 7.01 X Discovery Probe 7.0 X Discovery Probe 6.5 X Discovery Probe 6.2 X Discovery Probe 6.1 X HP Business Availability Center 7.01 Readme Software version: 7.01 / February 2008 This file provides information about HP Business Availability Center 7.01 and HP Business Availability Center 7.0 (for 7.0 information, click here). Business Availability Center 7.01 Files Installation Prerequisites Installation Uninstallation Version Content and Limitations Updated Components Updated HP Business Availability Center Support Matrixes Business Availability Center 7.01 Files Business Availability Center 7.01 includes the following files: Business Availability Center 7.01 setup file Setup.exe (Windows installation) Setup.bin (Solaris installation) Component setup files New: Real User Monitor Probe 7.01 (Linux) New: Real User Monitor Engine 7.01 (Windows) New: Discovery Probe 7.01 New: SiteScope 9.01 (Windows, Solaris, Linux) Note: You need to separately download new component setup files. Documentation files whatsnew.html readme701.html (includes 7.0 Readme) SLA_Dynamic_Update.pdf - describes Dynamic Business Process Monitor locations in Service Level Management Service_Manager_adapter.pdf - describes how to work with the ServiceCenter/Service Manager federated adapter plug-in component Updated Documentation Library (installed during 7.01 installation) - includes updates to several guides Additional files tzupdater.jar - file needed for Daylight Savings Time definition update Installation Prerequisites Business Availability Center 7.01 must be installed on top of Business Availability Center 7.0. Installation If you do not yet have Business Availability Center 7.0 installed, install it according to the instructions in the Business Availability Center 7.0 Deployment Guide. Then install Business Availability Center 7.01 on every Business Availability Center server by double-clicking on the relevant setup file (Windows or Solaris) and following the on-screen instructions. After installation is complete, run the Daylight Savings Time update procedure using the updated tzupdater.jar file included with Business Availability Center 7.01. This provides your system with the latest DST definitions. Copy the tzupdater.jar file to the <HP Business Availability Center root directory>\bin directory. Stop HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Disable Business Availability Center). Open a Command Prompt window (DOS shell) and change the directory to <HP Business Availability Center root directory>\bin. Run the following command to set JAVA_HOME: set JAVA_HOME=%TOPAZ_HOME%\jre Run the following command to install the patch: %JAVA_HOME%\bin\java -jar tzupdater.jar -u -bc Start HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Enable Business Availability Center). For additional details on updating Daylight Savings Time definitions, including the procedure for using the tzupdater.jar file on Business Process Monitor instances, see the Business Availability Center 7.0 Deployment Guide. Uninstallation For instructions on completely uninstalling Business Availability Center, see the Business Availability Center 7.0 Deployment Guide. To roll back an installation of Business Availability Center 7.01 to Business Availability Center 7.0, follow the instructions below. Stop the HP Business Availability Center service on all servers and confirm they are stopped. Stop the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers. From Control Panel, select Add/Remove Programs > Change or Remove Programs > HP Business Availability Center 7.01. On Windows 2003 Server make sure to check the Show Updates check box in order to display version 7.01 beneath the root HP Business Availability Center entry. When the uninstall process is complete, restart the machine if requested. Restart the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers. Restart the HP Business Availability Center service on all servers. When uninstalling or rolling back HP Business Availability Center, make sure to uninstall or rollback the data collectors as well. Version Content and Limitations In Service Level Management, the Agreements Wizard now includes the Include Locations option, used when the Business Process Monitoring source adapter is set to work with Transaction/Location hierarchy structure. You select the Include Locations option to enable the agreement to be dynamically updated with new Business Process Monitor locations for transactions. For details, see separate SLA_Dynamic_Update.pdf located in the Download area. Added out-of-the-box ServiceCenter/Service Manager federated adapter plug-in to support federated queries to ServiceCenter/Service Manager. For details, see separate Service_Manager_adapter.pdf located in the Download area. Known Limitation and Workaround: When changes are made in View Manager and these changes affect the results of a TQL, federated CIs in the view are not updated. This is because federated TQLs are calculated ad-hoc only and are not updated when a view is recalculated. To update the federated CIs, right-click the view in View Explorer and select "Full View Recalculation." (Note that the recalculation may take a long time.) Bug fixes - see table below for details: Description SR/E-Sar Number Area Fixed issue of broken Korean characters when included in subject of an email alert template 2215563785 BAC_Alerts Fixed inability to send transaction error message to executable in event-based alerts 3600308720, 4000020812 BAC_Alerts Fixed issue of alert recipient with more than one recipient not working correctly 38520 BAC_Alerts Fixed issue of alert engine notification module generating false alert samples 199529 BAC_Alerts Fixed issue of follow-up alerts not working on X/Y alerts 199550 BAC_Alerts Fixed issue of alert email subject not supporting i18n 199542 BAC_Alerts Fixed slow loading of Dashboard Topology Map 198276 BAC_Dasboard Fixed MyBAC portlets returning Tomcat error when there are two SLM reports on the page, when using BAC with Single-Sign-On 197799 BAC_Dasboard Adjusted Geographical Map in Dashboard to work with supported version of Microsoft Virtual Earth 198344 BAC_Dasboard Fixed issue of duplicate objective created after threshold change from EUM Administration and adapter soft sync 197154, 197483 BAC_Dasboard Fixed issue of Dashboard last sample dialog not opening although being configured to open 196604 BAC_Dasboard Added support for CHAR NLS_LENGTH_SEMANTICS in DBVerify 197843 BAC_DataEntry Fixed Raw Data Report copy/paste problem 197057 BAC_EUM Optimized Triage Report collector health row query 198954 BAC_EUM Performance improvements to TCBD report 196377 BAC_EUM Fixed CMDB database passwords appearing in plain text in several locations on the BAC and UCMDB file systems 196317 BAC_MAM Fixed inability of BAC 7.0 to work with UCMDB 7.0 external server when CMDB server name contains the domain 4000036577 BAC_MAM Upgraded Apache Server to Apache 2.2.6 to support SSL 199003 BAC_PlatformAdmin Filter type in Cross-Performance Report is now saved correctly in database 197446 BAC_SiteScope Fixed issue of Siebel admin password in clear text causing security breach 195537 BAC_SiteScope Fixed issue of SLM Custom Report error when CI does not have shared objective for its KPIs 197572 BAC_SLM Internal bug fixes Updated Components The following updated components are included with Business Availability Center 7.01: Real User Monitor Probe 7.01 Build 7.0.82 (Linux)  For instructions on upgrading the Real User Monitor probe, see separate Upgrade_RUM.pdf located in the Download area. Added support for RH EE 5 Added support for SSL domains in Discovery Added disk explosion fuse Fixed issue with probe recovery after disk explosion Fixed issue of snapshots not compressing by default When running in Snapshot on Transaction mode Fixed issue of resource caching saving unneeded files in some cases Real User Monitor Engine 7.01 Build 9 (Windows) For instructions on upgrading the Real User Monitor engine, see separate Upgrade_RUM.pdf located in the Download area. Fixed issue of correct username not always updating properly in the database if login page is not the first in the session Fixed issue of newly defined user being ignored when an end user is defined in End User Management Administration such that its IP range exactly matches an end user that was already inserted into the database Discovery Probe 7.01 Build 17 Bug fixes SiteScope 9.01 Build 911 (Windows, Solaris, Linux) Bug fixes (for details, see the SiteScope readme file, ReleaseNotes.htm) Updated HP Business Availability Center Support Matrixes This section describes updated matrix sections for various environments and components supported by HP Business Availability Center. Supported Environments Component Brand Version Comments Web Servers Apache 2.2.6   Business Availability Center Component Support Matrix Only HP Business Availability Center 7.01 compatibility is shown in this table. For the complete table, see the matrix in the 7.0 section below. (For each BPM version, the latest supported VuGen version is mentioned. All previous versions of VuGen are supported as well.) √=supported, X=not supported Compatibility Matrix HP Business Availability Center 7.01 BPM 7.0 (VuGen 9.0) √ (Recommended) BPM 6.5 (VuGen 8.1 FP 3) √ BPM 6.4.1 (VuGen 8.1 FP3) √ BPM 6.4 (VuGen 8.1) √ BPM 6.3 (VuGen 8.1) √ BPM 6.2 (VuGen 8.1) √ QTP SAP R/3 7.31 √ QTP 9.1/2 √ QTP 9.0 √ SiteScope 9.01 √ (Recommended) SiteScope 9.0 √ SiteScope 8.6-8.8 √ SiteScope 8.5 √ SiteScope 8.2.1 √ SiteScope 8.1.2 √ SiteScope 8.1.1 √ SiteScope 8.0 SP2 √ SiteScope 7.9.5.0 √ Real User Monitor Engine 7.01 √ (Can also work with BAC 7.0) Real User Monitor Engine 7.0 √ Real User Monitor Probe 7.01 √ (Can also work with BAC 7.0) Real User Monitor Probe 7.0 √ Real User Monitor Engine 6.5 X Real User Monitor Probe 6.5 X Real User Monitor Engine 6.2 X Real User Monitor Probe 6.2 X Real User Monitor Engine 6.1 X Real User Monitor Probe 6.1 X Discovery Probe 7.01 √ Discovery Probe 7.0 X Discovery Probe 6.5 X Discovery Probe 6.2 X Discovery Probe 6.1 X Security Matrix Section Component Name Fix/Patch Target HP Business Availability Center Web servers Apache 2.2.6   HP Business Availability Center 7.0 Readme Software version: 7.0 / 31 August 2007 This file provides information about HP Business Availability Center 7.0. Documentation What's New System Requirements Notes and Limitations Multilingual Support HP Business Availability Center Support Matrixes Support Legal Notices Documentation HP Software is continually updating its product documentation with new information. To check for recent updates, or to verify that you are using the most recent edition of a document, go to the HP Software Product Manuals Web site (http://ovweb.external.hp.com/lpe/doc_serv/). What's New To view a list of new features for this release, select Help > What's New in HP Business Availability Center, or double-click whatsnew.html from the root directory of the HP Business Availability Center DVD. System Requirements To view a complete list of system requirements, see the HP Business Availability Center Deployment Guide. Notes and Limitations Deployment and Upgrade When opening the Upgrade Wizard for the second time (for example, to check the data upgrade status or to complete the configuration upgrade), HP Business Availability Center must be up for the wizard to be able to access the relevant pages. On a Solaris platform, when you click the Help button in the Upgrade Wizard, the Help is not displayed. During the installation of HP Business Availability Center in a non-English locale, the license information displayed on the License page is not translated. On machines with four or more CPUs, the offline aggregation engine may crash due to a bug in the Sun Hotspot JVM. When this happens, the event will be logged in the file < HP Business Availability Center root directory>\log\offline_engine_boot.log with the following JVM Internal error ID: # An unexpected error has been detected by HotSpot Virtual Machine: # # Internal Error (4E4D4554484F440E4350500529) If this problem occurs on your system, apply the following workaround: In the file < HP Business Availability Center root directory >\bin\offline_engine_run.bat, add the parameter -XX:ParallelGCThreads=1 to the end of the line that begins with set SERVICE_MANAGER_OPTS. For example: set SERVICE_MANAGER_OPTS=-DhacProcessName=%PROCESS_NAME% -Dlog.folder.path.output=%PROCESS_NAME% -Dlog.folder=%PROCESS_NAME% -DuseCustomClassLoader=true -XX:ParallelGCThreads=1 Restart HP Business Availability Center. My BAC When creating or configuring a module, the Administrator Access settings in the Configure Access pane are not supported in this version. The infrastructure setting Maximum height in pixels, which you use to standardize the height of portlets, does not affect most portlets. When viewing EMS events in My BAC, the Clear Event option on the context menu does not work. If required, clear the event from Dashboard. In My BAC, in Preferences, if you right-click a page and do not select an option, the context menu stays open. To close it, click anywhere in the left pane. Dashboard and Reporting When editing a parameter for a rule in the Business Rules repository, changing the value in the Name box actually changes the value of the reference key for the parameter. Since the reference key is used for the rule calculation in the Business Logic Engine, changing the value may cause the calculation to fail. Do not edit the display name for a parameter. The PNR KPI in Dashboard does not have persistency in case of a Data Processing Server failure or a system restart. The PNR KPI shows an initialized status until the SLA is recalculated, at which time the PNR value is updated. Scheduled reports are not affected by daylight savings (DST) time changes. To view reports, Adobe Flash Player 8.0 or later is required. To view Asian characters properly in reports, HP Business Availability Center servers must be installed with Asian charsets. In Internet Explorer 7.0, you cannot open custom reports, published reports, or old reports in CSV format. If a report's time range includes the time of a daylight savings (DST) time change, the data for the period after the DST time change is incorrect. To obtain correct data for the entire time range, print two separate reports, one for the time range before the DST time change and one for the time range after the DST time change. Service Level Management During SLA creation or editing using the SLA Legacy Wizard, the Define KPIs page may not display CIs that were added in the previous Select CIs page. To update the display, click the Refresh button in the View Explorer pane. In Service Level Management, you cannot attach more than one PNR KPI (defined in Dashboard) to a configuration item. If the KPI Definition window has not been closed by clicking the OK or Cancel button, Service Level Management does not display the correct objectives for a KPI on the next occasion that the window is accessed. If the location name is changed for a Business Process Monitor after the associated CI has been added to an SLA, the CI is no longer included in the SLA's calculations and the CI's descendants are not displayed in the SLA hierarchy. Furthermore, Service Level Management cannot recalculate the SLA. To prevent this occurring, avoid making changes to the location name of a Business Process Monitor for which SLAs are defined. Also, configure the Business Process Monitor source (in the Source Manager) to use the "Regular" hierarchy structure and not "Transaction/Location." In the SLA Legacy Wizard (on the Select CIs page), Service Level Management may take a few minutes to process an SLA that includes many configuration items, before continuing to the Define KPIs page. You cannot add a CI to an SLA when the CI includes a descendant of itself in the original definition in the CMDB. This is because nesting is meaningless in the SLA calculation (Service Level Management cannot calculate a CI using the CI result as a value). If you add such a CI to an SLA, Service Level Management truncates the CI at the point at which the CI appears for the second time in the SLA hierarchy. However, you can add the same CI to an SLA more than once if the CI does not include a descendant of itself. In this case, Service Level Management calculates the CI only once, so the objectives are the same no matter where the CI appears in the SLA hierarchy. Service Level Management KPIs: The "No data time out" parameter is relevant only when "Time Based" is chosen for the "Calculation Method" parameter (that is, the rule calculates the KPI using the sample duration). The External Source Average Value rule includes a further parameter: "Performance field." This is the name of the performance field in the external source sample. End User Management Business Process Monitor Business Process Monitor 7.0 is no longer supported on a Linux platform. When you run a script written in VuGen that uses proxy settings from an automatic configuration script (.pac file) configured in the run-time settings of the script, if one of the proxies in the .pac file is unavailable, replaying the script in either VuGen or Business Process Monitor may result in a high response time and, in some instances, the script may fail due to a timeout. The script can be run in Internet Explorer without this problem, as it ignores the unavailable proxy. Business Process Monitor does not support WebTrace on Windows XP SP2 platforms. On Windows XP SP2 platforms, traceroute (UDP based WebTrace) is supported. (WebTrace is supported for Windows 2000 or 2003, and Windows XP without SP2.) Do not create a Dynamic Node Factory CI that includes Business Process Monitor transactions; If Business Process Monitor transactions are included in the Dynamic Node Factory, there may be a conflict between the adapter and the Dynamic Node Factory mechanism that could lead to an unpredictable state of the CIs. Business Process Monitor registers with HP Business Availability Center using http://<HP Business Availability Center Gateway Server name>/topaz, and not with HPBAC or MercuryAM at the end of the URL. You must use this format when creating instances for Business Process Monitor. Large scripts (larger than 10 MB) cannot be uploaded to the database. When running a page component breakdown (from End User Management or Business Process Monitor), the target URL is limited to 144 characters. Real User Monitor In the Custom Report Manager, report components of the Real User Monitor (Old) type may be removed in forthcoming versions. It is recommended to remove these report components from your custom reports and to replace them with the corresponding new report component of the Real User Monitor type. Session replay does not work with Java 1.6. In such an instance, copy the stax-api-1.0.1.jar file from the HPBAC\AppServer\webapps\site.war\static\eum\applets\snapshotreplay directory on the Gateway Server to the <jre directory>\lib\endorsed directory on your client machine. Session replay does not work if the Real User Monitor engine is configured to use a client-side certificate. Client Monitor As of HP Business Availability 7.0, Client Monitor is no longer supported. System Availability Management You cannot add a SiteScope 7.9.5 profile from System Availability Management Administration. To add a SiteScope 7.9.5 profile, create an empty profile in System Availability Management Administration and from SiteScope, connect to that profile in HP Business Availability Center. In System Availability Management Administration, when copying objects from one SiteScope to another, there is no dependency check. This means that you can copy an object that depends on another object to a different SiteScope, even though the object on which it depends does not exist on the target SiteScope. In System Availability Management Administration, when the SiteScope service is down, instead of receiving an error to this effect, you will see a Page cannot be displayed error. If a SiteScope is being reset when HP Business Availability Center is not running, the SiteScope will appear as registered with a configurable profile in System Availability Management Administration once HP Business Availability Center is running again. The SiteScope must be reset when HP Business Availability Center is running. On the New Monitor page, the Recently Used Monitors list is not saved when you exit System Availability Management Administration. When creating a SiteScope profile in System Availability Management Administration, if you change the profile display name after having received any error during the profile creation process, the default profile name is not changed accordingly. Ensure that the profile name and SiteScope agent machine location fields contain the desired values. When working in languages other than English, some event detail information in the Event Log is still in English. In System Availability Management Administration, there is no notification for successful actions in the user interface. HP SiteScope SiteScope configuration changes are not entered in the HP Business Availability database when the database primary instance is down. To update the database with the configuration changes, perform a manual synchronization once the database primary instance is up. In SiteScope alerts, when creating an e-mail type alert action, do not select Default in the Recipients field. Select any other recipients listed in the Recipients field (configured in Mail Preferences) or enter the intended recipient's e-mail address in the Addresses field. Adapters and Views In Source Manager, if you perform an adapter synchronization that does not finish before the adapter's scheduled synchronization, the adapter will no longer synchronize automatically. To solve this issue, disable the problematic adapter and enable it again. When editing the SiteScope source adapter in Source Manager, if you change the Include measurements value to None, the previous SiteScope monitor configurations are deleted from the CMDB. This may affect, for example, SLAs in Service Level Management that are based on SiteScope measurements. When synchronizing a SiteScope source adapter in Source Manager, if the adapter includes a large number of objects, then adapter performance might be slow, taking several minutes. When editing the SiteScope source adapter in Source Manager, if you select the Include machines option, the hierarchy in the System Monitors View (as shown in View Explorer) includes CIs for the monitored host machines. However, for each appearance of a host in the view, the child CIs for the host includes all monitors monitoring that host. This means that: a) monitor CIs may be duplicated, appearing under multiple instances of a host CI. b) monitor CIs may appear under SiteScopes or SiteScope groups to which they do not belong. Platform System health monitors will not function if you change the JNDI port. The JNDI port must not be changed from its default value. Changes to infrastructure settings are not included in the Audit Log. Oracle 10g tracing cannot be applied against HP Business Availability Center sessions due to a driver limitation. Do not apply tracing when HP Business Availability Center is running. You cannot create a schema that starts with a digit. Downtime events are rescheduled incorrectly after a daylight savings (DST) time change. Integrations More than one HP OVO monitor can be created on the same port using the Copy function, resulting in duplicate OVO events. In such cases, delete the copied monitor. The maximum size of an expression in the EMS Integration configuration file is 4000 characters. An EMS monitor may not find its configuration file when upgrading the SiteScope version. In such cases, manually copy the contents of the configuration file to the EMS monitor configuration in the user interface. When adding a CI to a BPI Business Process in the Business Processes view, the view does not show the addition. Documentation Library If you experience a JavaScript error when opening the HP Business Availability Center Documentation Library online help system, disable the "Show Exception Dialog Box" in the Java Console and open the help again. Multilingual Support When upgrading to HP Business Availability Center 7.0 from versions earlier than Business Availability Center 6.5, the transition through Business Availability Center 6.5 is not translated. The new multilingual user interface (MLU) feature enables you to view HP Business Availability Center in different languages by configuring your browser language. For considerations and limitations when working in non-English locales, see Working in Non-English Locales in the Reference Information guide of the HP Business Availability Center Documentation Library. In Dashboard Top View, Non-English characters of a specific language will be displayed only if the operating system is using the same language. For example, to see Japanese characters you should use Japanese OS and locale. Problem Isolation (PI) does not support I18N and is not translated. The Dashboard Ticker user interface is not translated and is in English only. When working in a Korean locale, the e-mail subject in legacy alerts is truncated. HP Business Availability Center Support Matrixes This section describes matrixes for various environments and components supported by HP Business Availability Center and Topaz versions. In each Table, √=supported, X=not supported. Supported Environments Component Brand Version Comments HP Business Availability Center Servers - Operating Systems Windows Windows 2000 Server/Advanced Server (SP4), Windows 2003 Standard/Enterprise Server (SP1, SP2)   Solaris Solaris 9, 10   Database Oracle Server 9i, 10g Oracle 10.2.0.1 Enterprise Edition is the recommended environment for use with HP Business Availability Center. Oracle 9.2.0.6 Enterprise Edition is a supported environment. Oracle is recommended over Solaris 9,10 OS. Solaris 8 is supported. Solaris OS environments are 64-bit only; Windows OS environments are 32-bit only. RAC deployment is supported on Linux (64-bit only) environment. Oracle Client 9, 10 Oracle 10.2.0.1 is the recommended environment for use with HP Business Availability Center. Oracle 9.2.0.6 is a supported environment. SQL Server 2000 Enterprise (SP4) SQL 2005 (SP1) Recommended on Windows 2003 Standard/Enterprise Server (SP1, SP2) Supported on Windows 2000 Server/Advanced Web Browsers IE 6.0 7.0   FireFox 2.0 Note that FireFox does not support all HP Business Availability Center functions. Support is limited to: Dashboard application (except topology map) EUM reports SLM reports SAM Admin Web Servers IIS 5, 6   Apache 2.2.3   Sun Java System Web Server 6.1 SP 5   Business Process Monitor - Operating Systems Windows Windows 2000 Server/Advanced Server (SP4) WebTrace functionality is not available on Windows XP SP2 because Microsoft has disabled low level socket access as part of the Windows XP SP2 security lockdown. Windows 2000 Professional (SP4) Windows XP Professional SP1, SP2 Windows 2003 Standard/Enterprise editions (SP1, SP2) Solaris Sun Solaris 9 + latest recommended patch cluster, Solaris 10   SiteScope - Operating Systems Windows Windows 2000 Server/Advanced Server (SP4) Removed support for: Linux RH 9.0 Windows 2003 Standard/Enterprise editions (SP1, SP2) Windows 2003 SRV R2 SP1 Solaris Sun Solaris 9, 10 - both with latest recommended patch cluster Linux Linux Red Hat ES\AS 3, 4 Real User Monitor Probe - Operating Systems Windows Not supported   Solaris Not supported Linux Linux Red Hat Enterprise 4.0 (RHEL4) Real User Monitor Engine - Operating Systems Windows Windows 2000 Server/Advanced Server (SP4)   Windows 2003 Standard/Enterprise editions (SP1, SP2) Discovery Probe - Operating Systems Windows Windows 2000 Server/Advanced Server (SP4)   Windows 2003 Standard/Enterprise editions (SP1, SP2) Note: System health is based on SiteScope - please see SiteScope supported operating systems. Business Availability Center Component Support Matrix For each BPM version, the latest supported VuGen version is mentioned. All previous versions of VuGen are supported as well. Compatibility Matrix HP Business Availability Center 7.0 Business Availability Center 6.5 Business Availability Center 6.2 Business Availability Center 6.1 Business Availability Center 6.0 BPM 7.0 (VuGen 9.0) √ (Recommended) √ √ √ √ BPM 6.5 (VuGen 8.1 FP 3) √ √ (Recommended) √ √ √ BPM 6.4.1 (VuGen 8.1 FP3) √ √ √ √ √ BPM 6.4 (VuGen 8.1) √ √ √ √ √ BPM 6.3 (VuGen 8.1) √ √ √ √ √ BPM 6.2 (VuGen 8.1) √ √ √ (Recommended) √ √ QTP SAP R/3 7.31 √ √ √ √ √ QTP 9.1/2 √ √ (BPM 6.5) X X X QTP 9.0 √ √ √ (Recommended) √ (BPM 6.1) √ SiteScope 9.0 √ (Recommended) √ √ √ √ SiteScope 8.6-8.8 √ √ √ √ √ SiteScope 8.5 √ √ (Recommended) √ √ √ SiteScope 8.2.1 √ √ √ (Recommended) √ √ SiteScope 8.1.2 √ √ √ √ √ SiteScope 8.1.1 √ √ √ √ √ SiteScope 8.0 SP2 √ √ √ √ √ SiteScope 7.9.5.0 √ √ √ √ √ Real User Monitor Engine 7.0 √ X X X X Real User Monitor Probe 7.0 √ X X X X Real User Monitor Engine 6.5 X √ √ (Recommended, together with Real User Monitor Probe 6.5) X X Real User Monitor Probe 6.5 X √ √ (Recommended, together with Real User Monitor Engine 6.5) X X Real User Monitor Engine 6.2 X X √ (Recommended) X X Real User Monitor Probe 6.2 X X √ (Recommended, together with Real User Monitor Engine 6.2) √ (Recommended, together with Real User Monitor Engine 6.1) X Real User Monitor Engine 6.1 X X X √ X Real User Monitor Probe 6.1 X X X √ X Discovery Probe 7.0 √ X X X X Discovery Probe 6.5 X √ X X X Discovery Probe 6.2 X X √ X X Discovery Probe 6.1 X X X √ X SiteScope Support Matrix Compatibility Matrix BAC 7.0 BAC 6.6, 6.7 BAC 6.0-6.5 SiteScope 9.0 √ √ √ SiteScope 8.8 √ √ √ SiteScope 8.7 √ √ √ SiteScope 8.6, 8.5, 8.2.1 √ √ √ SiteScope 8.1.1, 8.1.2, 8.0 SP3, 8.0 SP3 √ √ √ SiteScope 7.9.5.0 √ √ √ SiteScope/Business Availability Center Compatibility Matrix There are two main aspects of compatibility between SiteScope and Business Availability Center: Data logging which is the process of logging data collected by SiteScope to Business Availability Center for the purposes of real-time status, reporting, Service Level Management, and so forth. Monitor Administration which refers to configuring SiteScope (including deploying monitors) from within Business Availability Center. This compatibility issue is only relevant for pre 7.x versions of Business Availability Center since, from 7.0, Monitor Administration is deprecated and SiteScope is configured in System Availability Management Administration The following table contains compatibility information regarding the above two aspects and the various combinations of SiteScope and Topaz/Business Availability Center releases. 1 = Data logging support 2 = Monitor Administration support SiteScope Version Business Availability Center Version   7.0 6.x SiteScope 9.0 1 1 SiteScope 8.8 8.7, 8.6, 8.5 1 1,2 SiteScope 8.2.1 1 1,2 SiteScope 8.1, 8.1.1, 8.0 SP3, 8.0 SP2 1 1,2 SiteScope 8.0, 8.0 SP1 1 1 SiteScope 7.9.5.x 1 1,2 Real User Monitor Support Matrix Real User Monitor 7.0 (probe and engine) works only with Business Availability Center 7.0. Real User Monitor 6.6 (probe and engine) works only with Business Availability Center 6.6 and 6.7. Security Matrix Section Component Name Fix/Patch Target HP Business Availability Center servers operating system Windows 2000 server/Advanced Server SP4 and all MS security patches that were released up to June 1, 2007. Windows 2003 standard /enterprise additions SP2 and all MS security patches that were released up to June 1, 2007.   Sun Solaris 9, 10 All recommended patch cluster HP Business Availability Center Web servers MS IIS 5/6 (Windows 2000/2003) All MS security patches that were released up to June 1, 2007. Apache 2.2.3   Sun Java System Web Server 6.1 SP5 Business Process Monitor Changes Business Process Monitor Version Changes 7.0 Compatible with LoadRunner 9.0. 6.6, 6.6.1 Bug fixes. Support QTP 9.1, 9.2 (in addition to QTP 9.0) 6.5 Moved to use LoadRunner 8.1 FP3 replay and support three new protocols (WebGUI, Citrix, WSE). Scripts in the new protocols are supported from this version and up only. 6.4.1 EA version of the functionality introduced in Business Process Monitor 6.5 6.4 Fix for Siebel transaction coloring 6.3 Changes and fixes in NTLM and authentication Starting from BPM 6.6, the following versions of QTP are supported: 9.0, 9.1, 9.2 Supported protocols: Web QuickTest Professional Oracle Add-in (Web-based & Java-based Oracle applications) QuickTest Professional Add-in for SAP Solutions (Windows-based & Web-based SAP solutions) QuickTest Professional Siebel Add-in QuickTest Professional Web Services Add-in QuickTest Professional PeopleSoft Add-in QuickTest Professional Java Add-in QuickTest Professional .NET Add-in QuickTest Professional Terminal Emulator Add-in QuickTest Professional Stingray Add-in QuickTest Professional VisualAge Smalltalk Add-in Business Process Monitor 7.0 Protocol Support Matrix The following table describes the supported protocols for each platform on which you can install Business Process Monitor. * Indicates new protocols that were added in 7.0. Protocol Windows Solaris .NET * √ X AJAX * √ √ (ActiveX is not supported) C VUser √ √ Citrix 1.8 √ X COM/DCOM √ X CORBA-java √ X DB2 CLI √ X DNS √ X EJB √ X FTP √ X IMAP √ X I-mode √ X Informix √ X Jacada √ X JAVA Record\Replay * √ X Java VUser √ X JavaScript VUser √ X JMS * √ X LDAP √ X MSSQL Server √ X Multi protocol Web √ √ ODBC √ X Oracle (2-tier) √ X Oracle NCA √ X PeopleSoft - 8 √ √ POP 3 √ X RDP * √ X Real √ X RMI-java √ X SAP Click and Script * √ √ SAP GUI √ X SAP Web √ √ Siebel - Web √ √ Siebel DB2 CLI √ X Siebel MSSQL √ X Siebel Oracle √ √ SMTP √ X SOAP √ X Sybase CtLib √ X Sybase DBlib √ X Terminal Emulation [RTE] √ X Tuxedo 6 √ X Tuxedo 7 √ X VB VUser √ X Voice XML √ X WAP √ √ Web [HTTP/HTML] √ √ Windows sockets √ X Business Availability Center for Siebel Component Support Matrix Business Availability Center 6.2 for Siebel works with SiteScope 8.2 only (all previous versions are not supported). Component Siebel Version Windows Operating System Version for Siebel Servers Solaris Operating System Version for Siebel Servers Monitors SiteScope Monitors Siebel 7.5.3 Windows 2000 Solaris 5.9 Siebel 7.7 Solaris 9 Siebel 7.8 Solaris 9 Business Availability Center for Siebel Diagnostic Tools Tasks, Processes, Database Breakdown, SARM Siebel 7.5.3 Windows 2000 * Solaris 5.9 * SARM on mixed environment - Not supported Siebel 7.7 Solaris 9 Siebel 7.8 (to work with SARM you must use SARMAnalyzer version 7.7) Solaris 9 Support You can visit the HP Software Support Web site at: http://www.hp.com/go/hpsoftwaresupport HP Software online support provides an efficient way to access interactive technical support tools. As a valued support customer, you can benefit by using the support site to: Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services Enter into discussions with other software customers Research and register for software training Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To find more information about access levels, go to: http://h20230.www2.hp.com/new_access_levels.jsp To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html Legal Notices © Copyright 2005 - 2008 Mercury Interactive (Israel) Ltd. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. Intel®, Pentium®, and Intel® Xeon™ are trademarks of Intel Corporation in the U.S. and other countries. Java™ is a US trademark of Sun Microsystems, Inc. Microsoft®, Windows®, Windows NT®, and Windows® XP are U.S registered trademarks of Microsoft Corporation. Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California. Unix® is a registered trademark of The Open Group. © Copyright 2008 Mercury Interactive (Israel) Ltd.