HP Business Availability Center 7.50 Readme Software version: 7.50 / May 2008 This file provides information about HP Business Availability Center 7.50. 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://h20230.www2.hp.com/selfsolve/manuals). 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 HP Business Availability Center comes with Lightweight Single Sign-On (LW-SSO) capability, which enables you to log in to a single application and then permits you to access other supported applications configured in the original application's group. For limitations, security warnings, and general reference on using LW-SSO, see the Lightweight Single Sign-On Authentication - General Reference section in the Platform Administration guide of the HP Business Availability Center Documentation Library. The Data Collectors and Components Setup program does not copy the file HP .NET Probe (x64).msi to the Downloads page due to the parentheses in the name. Workaround: Manually copy the file from the Data_Collectors_and_Components\components directory on the DVD to the <HP Business Availability Center root directory>\AppServer\webapps\site.war\admin\install directory on the Business Availability Gateway Servers.  When running the Data Collectors and Components Setup program on a Solaris operating system, several of the TransactionVision and Diagnostics files will not be copied correctly to the Downloads page. Workaround: Install the files directly from the TransactionVision or Diagnostics DVD.  When running the Data Collectors and Components Setup program on a Solaris operating system, the file Microsoft WSE 2.0 SP3 Runtime.msi gets copied to the Downloads page as Microsoft WSE 2.0 SP3 Runti.msi. Workaround: Copy the file manually from the Data_Collectors_and_Components\components directory on the DVD to the <HP Business Availability Center root directory>\AppServer\webapps\site.war\admin\install directory on the Business Availability Gateway Servers and then rename the file back to its original name. The verification procedure (run_db_verify.bat) cannot be run against 7.0 schemas; it can only be run against the upgraded 7.5 schemas. Custom Reports containing SLA Alerts components that have been upgraded from version 7.0x to 7.50 may contain the wrong filter. Workaround: Recreate the report in version 7.50. The following issue is relevant if you are performing an upgrade in staging mode in an HP Business Availability Center environment in which HP Diagnostics is integrated and you want to register a different Diagnostics server to the staged Business Availability Center instance. During the staging process, do not unregister the Diagnostics server from within the Diagnostics registration page in the staging environment. Doing so will unregister the Diagnostics server from the production environment. Instead, change the Diagnostics server host registration directly in the Business Availability Center management database. Update the CUSTOMER_PROP table with the correct Diagnostics server name by running the following query against the management database: Update CUSTOMER_PROP set CPP_PROP_VALUE='<<<New Diagnostics server host name>>>' Where CPP_PROP_NAME=' OPAL_FULL_HOST' When opening the Upgrade Wizard for the second time, 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. The instructions in the HP Business Availability Center 7.50 upgrade wizard, and the license information displayed when installing HP Business Availability Center in a non-English locale, are displayed only in English. 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 The infrastructure setting Maximum height in pixels, which you use to standardize the height of portlets, is applied to only a limited number of 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 Personalize, 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 If you send a custom report to Outlook 2007 users in HTML/MHTML embedded format, it is received with an error message at the top of the report (for example, "An unexpected error occurred generating this report component..."). If the report data was generated correctly, the errors can be ignored. Workaround: Send reports to Outlook 2007 users in an e-mail as attachments. 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. Reports that include the time period during which a Daylight Savings Time (DST) change took place (change to or change from DST) will either be missing one hour (in cases where clocks are moved forward) or have two sets of data for the same hour (in cases where clocks are moved back). To view reports, Adobe Flash Player 8.0 or later is required. If a report's time range includes the time of a Daylight Savings Time (DST) 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. 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. Service Level Management During SLA creation or editing using the Agreement Wizard in CI-based mode, 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 CI. 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 Agreement Wizard in CI-based mode (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 copy 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 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 (ICMP-based WebTrace) is supported. (WebTrace is supported for Windows 2000 or 2003, and Windows XP without SP2.) 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. System Availability Management 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. Business Availability Center for SOA Only scripts that are recorded in HP Virtual User Generator version 9.10 or later are supported for SOA breakdown. To use a script recorded with HP Virtual User Generator version 9.00, detach the script from a profile (if attached), open and save the script in HP Virtual User Generator version 9.10 or later, and reattach the script to the profile. Scripts recorded with HP Virtual User Generator version 8.10 FP3 and earlier are not supported and you must record the script again using HP Virtual User Generator version 9.10 or later. Business Availability Center for SAP The Problem Isolation feature in Business Availability Center for SAP does not show any results. A patch to fix this issue will be published post-7.5 release. HP SiteScope Refer to the SiteScope release notes for all SiteScope limitations. 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. Platform The recommended setting for Oracle parameter NLS_LENGTH_SEMANTICS is the default setting of BYTE; setting this value to CHAR may affect database performance. 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. Universal CMDB Discovery J2EE Discovery Wizard might not be able to import large JAR files (>30MB). You may need to copy such files manually to the proper location in the Discovery probe's installation folder. When upgrading from 6.x to 7.50, the newly installed Discovery Probes need to be configured as belonging to the External domain, rather than the default Customer domain. Application UCMDB 7.50 consists of an applet that is run by a JRE. The supported JRE versions are 1.6.0_x or later (latest version recommended). To optimize the user experience in UCMDB, choose "Yes" when asked about changing Java configuration. This will enable the UCMDB application to use an additional 192MB of memory, which will help it perform much better. After accepting the change, you will need to reopen the application for the change to take effect. After finding the relevant CI in the CMDB Search, the context menu on the left-hand side is synchronized only after map selection. Reports It is not possible to automatically schedule and send reports by email. It is not possible to search inside reports exported to PDF (since the reports are saved as images). It is not possible to export chart reports to Excel and CSV. 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 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. The Problem Isolation application is translated and partly supports i18n: Reactive analysis - supports I18n Proactive analysis - does not support I18n. HP Business Availability Center Support Matrixes This section describes matrixes for various environments and components supported by HP Business Availability Center 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) Windows Server 2003 Enterprise x64 Edition SP2   Solaris Solaris 9, 10 For information on using Solaris Zones, contact HP Customer Support. 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.6   Sun Java System Web Server 6.1 SP 5   Business Process Monitor - Operating Systems Windows Windows 2000 Server/Advanced Server (SP4) and later 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 Server 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 Red Hat Enterprise Linux version 5.0 (RHEL5), 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 or later)   Windows 2003 Standard/Enterprise editions (SP1, SP2) Note: System health is based on SiteScope - please see SiteScope supported operating systems. Database Support Matrixes Hardware Requirements Deployment Size Number of Processors Physical Memory Standard 1 dual core Minimum: 2G RAM Recommended: 4G RAM Large 2 dual core or 1 quad core Minimum: 4G RAM Recommended: 8G RAM For information on sizing criteria, see the HP Business Availability Center Database Guide. Software Requirements - Oracle Server Support Level Database Release Operating System Version BIT Set Certified Oracle 10.2.0.3 Enterprise Edition plus latest critical patches 64 BIT Linux Enterprise Edition Oracle 10.2.0.3 RAC Enterprise Edition plus latest critical patches 64 BIT Linux Enterprise Edition Oracle 10.2.0.3 Enterprise Edition plus latest critical patches 64 BIT Solaris 10 Supported Oracle 9.2.0.7 Enterprise Edition plus latest critical patches 64 BIT Linux Enterprise Edition Oracle 9.2.0.8 Enterprise Edition plus latest critical patches 64 BIT Linux Enterprise Edition Oracle 10.2.0.3 Enterprise Edition plus latest critical patches 32 BIT Windows 2003 Enterprise Edition Service Pack 2 Oracle 10.2.0.3 Enterprise Edition plus latest critical patches 64 BIT AIX 5L Oracle 10.2.0.3 Enterprise Edition plus latest critical patches 64 BIT HP-UX 11.31 Note: It is strongly recommended to apply the latest critical Oracle patches per your operating system. For details, consult the Oracle documentation. For information on Oracle Client software requirements, see the HP Business Availability Center Database Guide. Software Requirements - Microsoft SQL Server Support Level Database Release Operating System Microsoft Data Access Components (MDAC) Certified Version BIT Set Service Pack   Microsoft SQL Server 2005 Enterprise Edition 32 BIT Service Pack 2 Windows 2003 Enterprise Edition Service Pack 2 2.8 SP1 Refresh (installed automatically during server installation) Microsoft SQL Server 2005 Enterprise Edition 64 BIT Service Pack 2 Windows 2003 Enterprise Edition Service Pack 2 Supported Microsoft SQL Server 2000 Enterprise Edition 32 BIT Service Pack 4 Windows 2000 Enterprise Edition Service Pack 2 2.5; 2.52; 2.61; 2.62; 2.7 SP1 Refresh Business Availability Center Component Support Matrixes Business Process Monitor 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.50 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.50 (VuGen 9.1) √ (Recommended) √ √ √ √ √ 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) √ Business Process Monitor 7.50 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. ** Indicates new protocols that were added in 7.50. 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 Flex ** √ 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] √ √ Web Click and Script √ √ Windows sockets √ X Business Process Monitor Changes Business Process Monitor Version Changes 7.50 Compatible with LoadRunner 9.1. Support QTP 9.5 Support Business Availability Center for SOA solution. 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 7.50, QTP 9.5 is supported with the following new protocol: Power Builder Add-in 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 SiteScope Support Matrix Compatibility Matrix HP Business Availability Center 7.50 HP Business Availability Center 7.0 Business Availability Center 6.5-6.7 Business Availability Center 6.2 Business Availability Center 6.1 Business Availability Center 6.0 SiteScope 9.5 √ (Recommended) √ √ √ √ √ SiteScope 9.0, 9.01 √ √ √ √ √ √ SiteScope 8.x √ √ √ √ √ √ SiteScope 9.01 recommended with BAC 7.01, SiteScope 9.0 recommended with BAC 7.0, SiteScope 8.5 recommended with BAC 6.5, SiteScope 8.2.1 recommended with BAC 6.2 SiteScope/Business Availability Center Compatibility Matrix There are three 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 System Availability Management Administration which refers to configuring SiteScope in System Availability Management Administration. The following table contains compatibility information regarding the above aspects and the various combinations of SiteScope and Business Availability Center releases. 1 = Data logging support 2 = Monitor Administration support 3 = System Availability Management support SiteScope Version Business Availability Center Version   7.50 7.0x 6.x SiteScope 9.5 1, 3 1, 3 1 SiteScope 9.0, 9.01 1, 3 1, 3 1 SiteScope 8.8 8.7, 8.6, 8.5 1 1 1, 2 SiteScope 8.2.1 1 1 1, 2 SiteScope 8.1, 8.1.1, 8.0 SP3, 8.0 SP2 1 1 1, 2 SiteScope 8.0, 8.0 SP1 1 1 1 Real User Monitor Support Matrix Compatibility Matrix HP Business Availability Center 7.50 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 Real User Monitor Engine 7.50 √ X X X X X Real User Monitor Probe 7.50 √ X X X X X Real User Monitor Engine 7.0 X √ X X X X Real User Monitor Probe 7.0 X √ X X X X Real User Monitor Engine 6.5 X X √ √ (Recommended, together with Real User Monitor Probe 6.5) X X Real User Monitor Probe 6.5 X X √ √ (Recommended, together with Real User Monitor Engine 6.5) X X Real User Monitor Engine 6.2 X X X √ X X Real User Monitor Probe 6.2 X 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 √ X Real User Monitor Probe 6.1 X X X X √ X Note: Real User Monitor 7.01 (probe and engine) works only with Business Availability Center 7.01. Real User Monitor 6.6 (probe and engine) works only with Business Availability Center 6.6 and 6.7. DDM Discovery Probe Support Matrix Compatibility Matrix HP Business Availability Center 7.50 HP Business Availability Center 7.0 Business Availability Center 6.5 Business Availability Center 6.2 Business Availability Center 6.1 Discovery Probe 7.50 √ 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 √ Note: Discovery Probe 7.01 works only with Business Availability Center 7.01. Security Matrix Section Component Name Fix/Patch Target HP Business Availability Center servers operating system Windows 2000 Server/Advanced Server SP4 and all Microsoft security patches that were released through February 2008 Windows 2003 Standard /Enterprise Server SP2 and all Microsoft security patches that were released through February 2008.   Sun Solaris 9, 10 All recommended patch clusters HP Business Availability Center Web servers MS IIS 5/6 (Windows 2000/2003) All Microsoft security patches that were released through February 2008. Apache 2.2.6   Sun Java System Web Server 6.1 SP5 Business Availability Center for Siebel Component Support Matrix 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, 8.0 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 Business Availability Center 6.2 for Siebel works with SiteScope 8.2 only (all previous versions are not supported). Business Availability Center/Business Process Insight (BPI) Integration Matrix Integration Matrix HP BPI 7.50 HP BPI 2.20 HP BPI 2.10 HP BPI 2.0 HP BPI 1.1 BAC 7.50 √ X X X X BAC 7.01 X √ X X X BAC 6.8 X √ X X X Business Availability Center/TransactionVision Integration Matrix Integration Matrix HP TV 7.50 BAC 7.50 √ BPI 7.50 √ Diagnostics 7.50 √ Business Availability Center/Diagnostics Integration Matrix Integration Matrix HP Diagnostics 7.50 HP Diagnostics 7.0 HP Diagnostics 6.6/6.5 BAC 7.50 √ X X BAC 7.0 √ √ X BAC 6.8 √ √ X BAC 6.7 √ √ X BAC 6.6 √ √ X BAC 6.5 √ √ √ BAC 6.4 X X √ BAC 6.3 X X √ BAC 6.2 X X √ Business Availability Center 7.50/ServiceCenter/Service Manager Integration Matrix Integration Matrix ServiceCenter 6.26 Service Manager 7.0 Incident Submission √ √ Problem Isolation √ X Federation √ √ Ticketing √ √ EMS √ √ 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.