HP Business Availability Center 7.54 Readme Software version: 7.54 / July 2009 This file provides information about HP Business Availability Center 7.54, 7.53 (for 7.53 information, click here), 7.52 (for 7.52 information, click here), 7.51 (for 7.51 information, click here), and 7.50 (for 7.50 information, click here). Business Availability Center 7.54 Files Installation Prerequisites Installation Uninstallation Version Content and Limitations Universal CMDB Content and Limitations Updated Components Updated HP Business Availability Center Support Matrixes Business Availability Center 7.54 Files Business Availability Center 7.54 includes the following files: Business Availability Center 7.54 setup file Setup.exe (Windows installation) Setup.bin (Solaris installation) Component setup files New: Real User Monitor Probe 7.54 (Linux) New: Real User Monitor Engine 7.54 (Windows) New: Discovery Probe 7.54 (Windows) New: SiteScope 10.10 (Windows, Solaris, Linux) Note: You need to separately download new component setup files. Documentation files whatsnew.html readme754.html (includes 7.54, 7.53, 7.52, 7.51, and 7.50 Readmes) Upgrade_RUM.pdf - contains instructions on upgrading the Real User Monitor probe and engine Interactive Service Manager integration document - contains information on integration with HP Service Manager ProblemIsolation_for_SAP.pdf - contains information on the Problem Isolation feature in Business Availability Center for SAP CILifecycleAging.pdf - contains information on the CI Lifecycle aging mechanism Additional files tzupdater.jar - file needed for Daylight Savings Time definition update Installation Prerequisites Business Availability Center 7.54 must be installed on top of Business Availability Center 7.50, 7.51, 7.52, or 7.53. Installation Read all of the issues listed in this section before starting the 7.54 upgrade process. If you have Business Availability Center 7.50, 7.51, 7.52, or 7.53 installed, stop Business Availability Center on all servers and make sure it is stopped before installing the service pack. Install the 7.54 service pack by double-clicking the setup.exe file for Windows (or by running the setup.bin script for Solaris) and following the on-screen instructions.  Do this on every Business Availability Center server. If you do not yet have Business Availability Center 7.50 installed, install it according to the instructions in the Business Availability Center Deployment Guide included with 7.54 (this is a more updated version of the 7.50 Deployment Guide). After installing 7.50, do not run the upgrade wizard or Server and Database Configuration utility, or start Business Availability Center until after 7.54 is installed. After installing Business Availability Center 7.50, install Business Availability Center 7.54 on every Business Availability Center server as per above instructions. After 7.54 is installed, run the Server and Database Configuration utility or upgrade wizard (depending on whether you are installing 7.54 as a new installation or whether you are upgrading from an earlier Business Availability Center version) as per instructions in the Deployment Guide. 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.54. This provides your system with the latest DST definitions. Note that the tzupdater.jar file included with Business Availability Center 7.54 is cumulative and includes the latest time zone updates for the following countries: Morocco, Tunisia, Argentina, Syria, Jordan, Pakistan, Egypt, Bangladesh 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.50 Deployment Guide. Update the UCMDB class model: After installing 7.54 and starting Business Availability Center, enter the following URL in the browser: http://<HP Business Availability Center Data Processing Server machine name or IP address>:8080/jmx-console Click the Topaz > service=CMDB Class Model Services link. In the JMX MBEAN View page, locate the following operation: updateClassModelFromFolder(). In the customerID box, enter 1. In the folderPath box, enter the full path to the federation CMDB class model XML file, for example, <HP Business Availability Center Data Processing Server root directory>\cmdb\classmodel\deployment\fcmdb_deployment.xml. Click Invoke. Restart Business Availability Center on the Data Processing Server. During the upgrade to 7.54, the log file <HP Business Availability Center install directory>\logs\EJBContainer\upgradeFramework.log may remain empty, though the following other log files catch the log input: <HP Business Availability Center install directory>\logs\EJBContainer\admincenter.log and <HP Business Availability Center install directory>\logs\topaz_all.ejb.log Perform the below workaround before starting the upgrade process to enable writing to the upgradeFramework.log file. Open the file <HP Business Availability Center install directory>\conf\core\Tools\log4j\EJB\upgradeFramework.properties. Go to the END of LAST FILE LINE (make sure you are on the end of line by pressing the End key). Press Enter. Make sure the marker went to next line. Save the file. The logger should now work properly and logging will appear in <HP Business Availability Center install directory>\logs\EJBContainer\upgradeFramework.log. If you are upgrading from a 7.0x version of Business Availability Center and are accessing via reverse proxy, you may not be able to log into Business Availability Center. Workaround: Install 7.50, 7.54, and run the full upgrade procedure in either staging or direct mode. Before logging into Business Availability Center for verifications, disable the reverse proxy as follows for the upgrade environment: Access the JMX console via http://<HP Business Availability Center machine>:8080/jmx-console and enter the user name and password. Click service=Infrastructure Settings Manager. Invoke the void setGlobalSettingValue() method with the following parameter values: contextName=platform settingName=enable.reverse.proxy newValue=false Check that you can now log into Business Availability Center. If you still cannot log in, remove the values from the reverse proxy URL settings as follows: Access the JMX console via http://<HP Business Availability Center machine>:8080/jmx-console and enter the user name and password. Click service=Infrastructure Settings Manager. Invoke the void setGlobalSettingValue() method with the following parameter values: contextName=platform settingName=default.centers.server.url newValue=<leave empty> Invoke the void setGlobalSettingValue() method again but with the following parameter values: contextName=platform settingName= default.core.server.url newValue=<leave empty> Access Business Availability Center directly and not through the reverse proxy. If you upgraded in staging mode, proceed with your verifications of the upgrade environment. If verified, declare the upgrade environment as the new production environment. For details on configuring the reverse proxy again, see "Using a Reverse Proxy in HP Business Availability Center" in the Business Availability Center Hardening Guide. If implementing Business Availability Center 7.54 - Service Manager 7.02 (or later) integration for Incident Submission, and you are running Business Availability Center servers on a Solaris operating system using an Iplanet Web server, at the end of the 7.54 installation you must restart the Iplanet Web server. If you are installing Business Availability Center 7.54 and are working with an external UCMDB architecture, you must perform the following procedure to copy and deploy the updated BAC packages to the UCMDB server, as they are not deployed automatically to the external UCMDB server during the installation. Perform the procedure after installing Business Availability Center 7.54 on the Business Availability Center machines and HP Universal CMDB 7.54 on the external UCMDB machine. Open the file < Business Availability Center 7.54 setup package root directory>\updated_bac_packages\updated_bac_packages.txt to view a list of the updated packages. The file contains four lists: updated packages from 7.50 to 7.51 (relevant if you have not previously deployed updated 7.51 packages to the external UCMDB server) updated packages from 7.51 to 7.52 (relevant if you have not previously deployed updated 7.52 packages to the external UCMDB server) updated packages from 7.52 to 7.53 (relevant if you have not previously deployed updated 7.53 packages to the external UCMDB server) updated packages from 7.53 to 7.54 Manually copy the relevant packages listed in updated_bac_packages.txt from the <Business Availability Center root directory>\ mam_lib\patch_packages directory on the Business Availability Center Data Processing Server to the root\lib\factory_packages directory on the UCMDB server. Only copy the .zip files and only copy the relevant packages listed in updated_bac_packages.txt, not all the contents of the patch_packages directory. Start the UCMDB server. Deploy the updated packages you copied to the UCMDB server using the UCMDB JMX Console: Launch your Web browser and enter the following address: http://<server_name>:8080/jmx-console, where <server_name> is the name of the machine on which HP Universal CMDB is installed. Under MAM, click service=MAM Packaging Services to open the JMX MBEAN View page. Locate java.lang.String deployPackages. In the ParamValue box for the parameter customerId, enter the <customer id>. For non-multi-customer installations, the default customer ID is 1. Leave the ParamValue box for the parameter dir empty. In the ParamValue box for the parameter packagesNames, enter the names of the packages (separate the package names using commas). Select True to override DDM job configurations changed in the DDM user interface. Click Invoke to deploy the packages. For more information on the UCMDB JMX Console, see the Package Manager section of the Model Management guide. Start Business Availability Center servers. HP UCMDB and Federated Adapters upgrade notes: CMDB RMI adapter: The CmdbRmiAdapter.zip package is overwritten during upgrade. If you modified the CmdbRmiAdapter package follow the below instructions: Copy the existing <HP Business Availability Center Data Processing Server root directory>\mam_lib\factory_packages\CmdbRmiAdapter.zip file to a temporary directory before starting the upgrade process. After the upgrade process, edit the files in the new CmdbRmiAdapter.zip package to match the changes you had made to the old adapter package. You must make the changes in the new CmdbRmiAdapter.zip and not overwrite with your old package. Replication. When upgrading from Business Availability Center 7.0x or 7.50 (but not from 7.51, 7.52, or 7.53), it is recommended to perform a diff replication on your current system prior to upgrading to 7.54. This will prevent losing data for removal during the full synch. Then, after upgrading to 7.54, each replication job should be run in full replication mode. For details on running diff and full replication, see the Replication Jobs Tab section in the Model Management guide. Service Desk adapter: Perform the following procedures to make sure you do not lose your existing Service Desk adapter configuration information during the upgrade process: Before upgrading to 7.54: Back up the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\ServiceDeskAdapter\serviceDeskConfiguration.xml file. After installation of 7.54: Copy the backed up file back to its original location. Proprietary adapter configured in Generic DB Adapter default folder: If you created a proprietary adapter in the default Generic DB Adapter folder, you must perform the following procedures to make sure you do not lose your existing Generic DB Adapter configuration information during the upgrade process. Before upgrading to 7.54: Back up the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF directory. After installation of 7.54: Copy the backed up directory back to its original location. Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.51, 7.52, or 7.53 to 7.54): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter, after upgrading from HP Business Availability Center 7.51, 7.52, or 7.53 to 7.54. Copy all .jar files from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter to the proprietary adapter folder. Overwrite any existing files with the same name, if such files exist. Reload the adapter Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.0x or 7.50 to 7.54): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter, after upgrading from HP Business Availability Center 7.0x or 7.50 to 7.54 (if upgrading from 7.51, 7.52, or 7.53, see previous issue). Copy all .jar files from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter to the proprietary adapter folder. Overwrite any existing files with the same name, if such files exist. Copy plugins.txt from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF to <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF. Open <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF\orm.xml using a text or XML editor. In orm.xml, for each CI type that is defined as a multinode in the reconciliation_rules.txt file, change the mapped attribute name from <CI type name>_<attribute name> to <attribute name>. For example, if "host" is a multinode, change: <basic name="host_host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> to:        <basic name="host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> Note: If a reconciliation rule includes a link, attributes of end2 should still be prefixed by the corresponding CI type name. For example, if one of the reconciliation rules is multinode[host] expression[host.host_hostname or ip.ip_address] end1_type[host] end2_type[ip] link_type[contained], then ip.ipaddress should still be mapped as: <basic name="ip_ip_address"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> In orm.xml, completely delete any entities whose name starts with IdClass2PK or IdClass3PK. For example, an entity defined as <entity class="generic_db_adapter.IdClass2PK_cpu" name="IdClass2PK_cpu"> should be deleted. In orm.xml, delete all lines that are similar to: <id-class class="generic_db_adapter.IdClass2PK_something"/> or <id-class class="generic_db_adapter.IdClass3PK_something"/>. Delete the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\dynamic_classes folder, if it exists. Reload the adapter. This note is relevant if you are also upgrading SiteScope and are working with the Business Availability Center/ServiceCenter or Service Manager integration. When setting up the Service Manager/ServiceCenter monitor in SiteScope, a file called peregrine.jar is created and placed in the WEB-INF\lib directory on the SiteScope machine. This file must be backed up before upgrading SiteScope or it will be deleted during the upgrade. After the upgrade is complete, copy the backed up peregrine.jar file back to the WEB-INF\lib directory. Business Availability Center for SAP users only: After upgrading to 7.54, but before logging into Business Availability Center, you must clean the repository. To do so, log into the following page in the JMX console, http://< Business Availability Center Server>:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=Topaz%3Aservice%3Drepositories_manager, and invoke java.lang.String cleanDefaultRepositoryTypeDBAndCache(). For more information on this process, contact HP Software Support. Uninstallation For instructions on completely uninstalling Business Availability Center, see the Business Availability Center 7.50 Deployment Guide (an updated version of which is included with 7.54). To roll back an installation of Business Availability Center 7.54 to Business Availability Center 7.53, 7.52, 7.51 or 7.50, 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.54. On Windows 2003 Server, select the Show Updates option to ensure that version 7.54 is displayed 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. When rolling back from 7.54 to any earlier 7.5x version, you must perform the below procedure. Before starting the procedure and before rolling back, note the following: Some of the steps are performed before the rollback and some after. This procedure is not relevant in an external UCMDB architecture. This procedure deletes Federation Data Stores previously configured in Business Availability Center as well as all defined replication jobs. Before uninstalling 7.54, and while Business Availability Center is running, enter the following URL in the browser: http://<HP Business Availability Center Data Processing Server machine name or IP address>:8080/jmx-console Click the Topaz > service=CMDB Class Model Services link. In the JMX MBEAN View page, locate the following operation: deleteByClassType(). Invoke the deleteByClassType operation with the following parameters: in the customerID box, enter the customer ID (1 by default); in the className box, enter federation_config; in the chunkSize box, enter 100; for isDerived select False. Invoke the deleteByClassType operation again with the following parameters: in the customerID box, enter the customer ID (1 by default); in the className box, enter lookup_classes_destinations; in the chunkSize box, enter 100; for isDerived select False. Shut down Business Availability Center 7.54 on all servers. Perform rollback from 7.54 to any earlier 7.5x version on all Business Availability Center machines. Restart Business Availability Center on all servers. Version Content and Limitations See also 7.53 limitations, 7.52 limitations and 7.51 limitations below. Removed limitations are marked with prefix FIXED IN 7.54. Authentication: HP Business Availability Center's default authentication strategy is Lightweight Single Sign-On (LW-SSO). When LW-SSO is enabled, you must use a fully qualified domain name (FQDN) to access HP Business Availability Center. If you do not require LW-SSO, you can disable it. If LW-SSO is disabled, you do not need to enter a FQDN to access HP Business Availability Center. For details on disabling LW-SSO, see "Authentication Strategies" in the Platform Administration Guide. ServiceCenter/Service Manager Integration: Business Availability Center 7.54 includes interactive integration documentation for Business Availability Center-Service Manager/ServiceCenter integration. This new interactive document enables selecting specific integration parameters and viewing only the documentation relevant for the integration specified. The document is available by double-clicking trbl_sm_deploy.html in the SM_interactive_document directory, which is located in the Business Availability Center 7.54 Setup directory. ServiceCenter/Service Manager Integration. For additional information on integration with ServiceCenter/Service Manager, see relevant notes in 7.51 readme section below. For an updated Business Availability Center-Service Manager/ServiceCenter integration matrix, see the interactive integration document. HP Business Availability Center 7.54 contains the following updates that address security vulnerabilities: Update of Java Runtime Environment running on Business Availability Center servers to JRE 1.5.0_18 Update to Apache Web server available during Business Availability Center installation to Apache HTTP Server 2.2.11 When upgrading alerts configuration from Business Availability Center 6.x to 7.x, if the alert configuration in Business Availability Center 6.x included the definition of more than one SNMP target, the configuration is corrupted after you upgrade to Business Availability Center 7.x. It must be redefined manually. When saving a report (SLM, EUM, Dashboard reports) as a PDF, click OK rather than pressing the Enter button on the keyboard. Pressing Enter returns an error. Reports sent via email that are received in Outlook 2007 mail clients might include a redundant mail header with an error message. HP Business Availability Center bug fixes - see table below for details: Description SR/E-Sar Number Area Fixed performance issue in SAM reports 46676 Admin Fixed issue that prevented KES restart after initial start failure 52840 Dashboard Fixed issue of Dashboard Top views not being refreshed 53136 Dashboard Fixed issue of RUM page CIs belonging to SOAP applications being deleted after modifying the page in End User Management Administration 1604168921 EUM Fixed issue of Business Process Monitor Percentile Report failing when running several concurrent instances of the report 53191 EUM - Application Fixed issue of not all data being returned from the database in the Business Process Monitor Percentile Report 50660 EUM - Application Fixed issue of incorrect Total Network Time values in End Users by Transaction report 1604923987 EUM - Application Fixed issue of adapter possibly deleting configuration information when error in management database occurs 3605219140 EUM - BPM Fixed issue of application KPI selector including a field that does not exist in the sample 3604755845 EUM - BPM Fixed issue of empty clickstream for some of the sessions, when monitoring WebSphere portal URLs 1603287839 EUM - RUM Engine Fixed issue related to entering regular expression for Parameter Extraction in RUM application definition 3605457990 EUM - RUM Engine Fixed issue of flawed x-axis labels in charts with narrow width in printer-friendly format 2605096820 Platform Fixed issue of wrong decimal and thousand delimiters in Hungarian locale (, instead of .) in Excel and csv format 1602850232 Platform Fixed issue of wrong information in Alert Trigger Condition message 1601419114 Platform Fixed I18N issue of CSV files not being generated in Japanese (old reports and custom report) 50643 Platform Fixed issue of single quotes in Field formula not being saved in Custom Query Browser 3605184631 Platform Fixed issue of CI and SLA Alert report time format using server time zone instead of user time zone 52741 Platform Fixed issue of Custom Report with many components (30 or more) failing to be exported to CSV file 3604944784 Platform Fixed issue of System Health database monitor showing red on some tables that have correct statistics 2606152211 Platform Fixed issues related to security vulnerabilities by upgrading Apache Web Server and JRE versions 3604717898 Platform - Administration Fixed issue of superuser permissions enabling access to Data Collector Maintenance page in Admin > Platform > Data Collection 50372 Platform - Administration Fixed issue of BAC users created manually having problems accessing CRS when under IDM-SSO 3604088731 Platform - Administration Fixed issue of SNMP trap triggered by an alert causing a deadlock that prevents alerts from being sent 3605610245 Platform - Alerts Fixed issue of alerts for default recipients not being sent in staging (evaluation) mode 55014 Platform - Alerts Fixed issue related to WDE locking mechanism not functioning correctly during the publishing of a sample 3604645384 Platform - Data Processing Fixed issue of Custom Query Builder querying the CMDB in SaaS environment 52692 Platform - Data Processing Fixed issues related to Partition Manager-DBVerify integration for native partitions 3605681345 Platform - Data Processing Fixed issue of Data Marking tool being unavailable in Solaris environments 1605352820 Platform - Data Processing Fixed issue in custom report of not being able to navigate to the next page 55071 Platform - UI - Web UI Fixed issue that restricted the ability to add custom query component in user reports to only admin users 3605716505 Platform - User Reports Fixed issue in incorrect start dates in Cross-Performance report weekly reports 3605878553 SAM - Cross Performance Fixed issue of tooltip on Outage Description in Outage Summary Report not working 1603979664 SLM Fixed issue of ClassCastException when "Save KPI Over Time" is selected on Session KPI (Siebel) 50735 SLM Fixed SLM upgrade issue that caused SLAs over SiteScope topology to stop calculating the SiteScope monitors in the SLA scope and the profile database to grow non-stop 1605072711 SLM - Logic Fixed issue of SARM failing in deployments with Siebel appserver ID larger than 9 3605082006 SLM - Vertical Universal CMDB Content and Limitations Aging Mechanism. The mechanism is now more user-friendly and mature, and is now configured and managed through the CI Lifecycle page (Application > CI Lifecycle). (By removing CIs that no longer exist in the IT environment, aging reduces the load on the UCMDB and database servers, and improves server usability and stability.) For details on using the aging mechanism, see the CILifecycleAging.pdf located in the 7.54 Setup package root directory. Service Desk adapter: The adapter is delivered with a default configuration file (for ServiceCenter 6.xx). Before defining a data store, and if you are not working with ServiceCenter 6.xx, you must prepare the appropriate file, according to the version of Service Manager you are working with: Locate the <HP Business Availability Center Data Processing Server root directory>\fcmdb\CodeBase\ServiceDeskAdapter folder. This folder contains the following configuration files: serviceDeskConfiguration.xml.7.0x for Service Manager version 7.0x serviceDeskConfiguration.xml.7.1x for Service Manager version 7.1x serviceDeskConfiguration.xml.6.xx for ServiceCenter version 6.xx Delete the suffix of the appropriate configuration file. For example, if you are working with Service Manager 7.0x, locate the serviceDeskConfiguration.xml.7.0x file and delete .7.0x, so that the new name of the file is serviceDeskConfiguration.xml. HP Universal CMDB bug fixes - see table below for details: Description Area Fixed issue where aging mechanism can potentially delete internal CMDB configuration CIs Application Fixed issue with failure-handling in the HP UCMDB-Service Manager integration Application Fixed issue where TQLs with two self-links are calculated Application Fixed issue with topology calculation not taking into account the number of visited links Application Fixed issue with topology calculation not propagating "fuse" exceptions to users Application Fixed issue where enrichment cannot be saved when updating an attribute of type Enumeration or List Application Fixed issue where aging does not delete large numbers of expired CIs Application Fixed issue of memory peak in federation adapter Application Fixed performance issues in impact calculation Application Fixed issue with discovery of migratable WebLogic servers Discovery Fixed issue where aggregation tables exceed the maximum rows available (5000000) Discovery Fixed issue where discovery of Cisco switches fails (client.executeCmd() times out) Discovery Fixed issues with run now and run once for DDM jobs Discovery Fixed issue where DDM scripts are corrupted on the Probe in the discoveryManager folder Discovery Fixed issue with the HP-UX virtual interface Discovery Fixed issue where JBoss Connection by JMX discovery fails on a JBoss configured with JAAS Discovery Fixed issue with SAP site discovery Discovery Internal bug fixes Updated Components The following updated components are included with Business Availability Center 7.54: Real User Monitor Probe 7.54 (Linux)  For instructions on upgrading the Real User Monitor probe, see separate Upgrade_RUM.pdf located in the 7.54 Setup package root directory. Server filters now work for SSL Real User Monitor Engine 7.54 (Windows) For instructions on upgrading the Real User Monitor engine, see separate Upgrade_RUM.pdf located in the 7.54 Setup package root directory. Fixed Server Filters Editor issues Fixed Real User Monitor Health Monitor "Page Hits Processed by Engine" Fixed empty session clickstream issue that occurred when monitoring WebSphere Portal applications Discovery Probe 7.54 (Windows) To install the Discovery Probe, first uninstall the existing Discovery Probe via Start > Programs > UCMDB or HP DDM > Uninstall UCMDB Discovery Probe or Uninstall HP DDM Probe. Then run HPDiscoveryProbe_v754_win32.exe. Bug fixes  SiteScope 10.10 (Windows, Solaris, Linux) For instructions on installing SiteScope, see the SiteScope Deployment Guide. Content updates and bug fixes (for details, see the SiteScope readme file, ReleaseNotes.htm, available in the SiteScope installation directory) Updated HP Business Availability Center Support Matrixes This section describes updated matrix sections for various environments and components supported by HP Business Availability Center. Only specific updates for 7.54 are shown. For 7.53, 7.52 and 7.51 updates, see the relevant sections below. √=supported, X=not supported For an updated Business Availability Center 7.54/Service Manager-Service Center Integration Matrix, see the integration document. 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.54 HP Business Availability Center 7.53 HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 BPM 7.53 (VuGen 9.1) √ (Recommended) √ (Recommended) √ √ √ √ BPM 7.52 (VuGen 9.1) √ √ √ (Recommended) √ √ √ BPM 7.51 (VuGen 9.1) √ √ √ √ (Recommended) √ √ BPM 7.50 (VuGen 9.1) √ √ √ √ √ (Recommended) √ BPM 7.0 (VuGen 9.0) √ √ √ √ √ √ (Recommended) QTP SAP R/3 7.31 √ √ √ √ √ √ QTP 9.5 √ √ √ √ √ X QTP 9.1/2 √ √ √ √ √ √ QTP 9.0 √ √ √ √ √ √ Real User Monitor Support Matrix Compatibility Matrix HP Business Availability Center 7.54 HP Business Availability Center 7.53 HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 Real User Monitor Engine 7.54 √ √ √ √ √ X Real User Monitor Probe 7.54 √ √ √ √ √ X Real User Monitor Engine 7.53 √ √ √ √ √ X Real User Monitor Probe 7.53 √ √ √ √ √ X Real User Monitor Engine 7.52 √ √ √ √ √ X Real User Monitor Probe 7.52 √ √ √ √ √ X Real User Monitor Engine 7.51 √ √ √ √ √ X Real User Monitor Probe 7.51 √ √ √ √ √ X Real User Monitor Engine 7.50 √ √ √ √ √ X Real User Monitor Probe 7.50 √ √ √ √ √ X Real User Monitor Engine 7.0 X X X X X √ Real User Monitor Probe 7.0 X X X X X √ DDM Discovery Probe Support Matrix Compatibility Matrix HP Business Availability Center 7.54 HP Business Availability Center 7.53 HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 Discovery Probe 7.54 √ X X X X X Discovery Probe 7.53 X √ X X X X Discovery Probe 7.52 X X √ X X X Discovery Probe 7.51 X X X √ X X Discovery Probe 7.50 X X X X √ X Discovery Probe 7.0 X X X X X √ Note: Discovery Probe 7.01 works only with Business Availability Center 7.01. SiteScope Support Matrix Compatibility Matrix HP Business Availability Center 7.5x HP Business Availability Center 7.0 SiteScope 10.x √ (Recommended) √ SiteScope 9.5x √ √ SiteScope 9.0x √ √ 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/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. 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 = System Availability Management support SiteScope Version Business Availability Center Version   7.5x 7.0x SiteScope 10.x 1, 2 1, 2 SiteScope 9.5x 1, 2 1, 2 SiteScope 9.0x 1, 2 1, 2 SiteScope 8.8 8.7, 8.6, 8.5 1 1 HP Business Availability Center 7.53 Readme Software version: 7.53 / March 2009 This file provides information about HP Business Availability Center 7.53, 7.52 (for 7.52 information, click here), 7.51 (for 7.51 information, click here), and 7.50 (for 7.50 information, click here). Business Availability Center 7.53 Files Installation Prerequisites Installation Uninstallation Version Content and Limitations Updated Components Updated HP Business Availability Center Support Matrixes Business Availability Center 7.53 Files Business Availability Center 7.53 includes the following files: Business Availability Center 7.53 setup file Setup.exe (Windows installation) Setup.bin (Solaris installation) Component setup files New: Real User Monitor Probe 7.53 (Linux) New: Real User Monitor Engine 7.53 (Windows) New: Business Process Monitor 7.53 (Windows, Solaris) New: Discovery Probe 7.53 (Windows) Note: You need to separately download new component setup files. Documentation files whatsnew.html readme753.html (includes 7.53, 7.52, 7.51, and 7.50 Readmes) Upgrade_RUM.pdf - contains instructions on upgrading the Real User Monitor probe and engine SM_integration.pdf - contains information on integration with Service Manager ProblemIsolation_for_SAP.pdf - contains information on the Problem Isolation feature in Business Availability Center for SAP Additional files tzupdater.jar - file needed for Daylight Savings Time definition update Installation Prerequisites Business Availability Center 7.53 must be installed on top of Business Availability Center 7.50, 7.51, or 7.52. Installation Read all of the issues listed in this section before starting the 7.53 upgrade process. If you have Business Availability Center 7.50, 7.51, or 7.52 installed, stop Business Availability Center on all servers and make sure it is stopped before installing the service pack. Install the 7.53 service pack by double-clicking the setup.exe file for Windows (or by running the setup.bin script for Solaris) and following the on-screen instructions.  Do this on every Business Availability Center server. If you do not yet have Business Availability Center 7.50 installed, install it according to the instructions in the Business Availability Center Deployment Guide included with 7.53 (this is a more updated version of the 7.50 Deployment Guide). Then install Business Availability Center 7.53 on every Business Availability Center server as per above instructions. After installing 7.50, do not run the upgrade wizard or database configuration process, or start Business Availability Center until after 7.53 is installed. 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.53. This provides your system with the latest DST definitions. Note that the tzupdater.jar file included with Business Availability Center 7.53 is the same as the one included with 7.52, so if you are upgrading from 7.52, you do not need to run it again. The .jar only includes time zone updates for the following countries: Argentina, Brazil, Cuba, Egypt, Iran, Mauritius, Morocco, Pakistan, Turkey, 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.50 Deployment Guide. During the upgrade to 7.53, the log file <HP Business Availability Center install directory>\logs\EJBContainer\upgradeFramework.log may remain empty, though the following other log files catch the log input: <HP Business Availability Center install directory>\logs\EJBContainer\admincenter.log and <HP Business Availability Center install directory>\logs\topaz_all.ejb.log Perform the below workaround before starting the upgrade process to enable writing to the upgradeFramework.log file. Open the file <HP Business Availability Center install directory>\conf\core\Tools\log4j\EJB\upgradeFramework.properties. Go to the END of LAST FILE LINE (make sure you are on the end of line by pressing the End key). Press Enter. Make sure the marker went to next line. Save the file. The logger should now work properly and logging will appear in <HP Business Availability Center install directory>\logs\EJBContainer\upgradeFramework.log. If you are upgrading from a 7.0x version of Business Availability Center and are accessing via reverse proxy, you may not be able to log into Business Availability Center. Workaround: Install 7.50, 7.53, and run the full upgrade procedure in either staging or direct mode. Before logging into Business Availability Center for verifications, disable the reverse proxy as follows for the upgrade environment: Access the JMX console via http://<HP Business Availability Center machine>:8080/jmx-console and enter the user name and password. Click service=Infrastructure Settings Manager. Invoke the void setGlobalSettingValue() method with the following parameter values: contextName=platform settingName=enable.reverse.proxy newValue=false Check that you can now log into Business Availability Center. If you still cannot log in, remove the values from the reverse proxy URL settings as follows: Access the JMX console via http://<HP Business Availability Center machine>:8080/jmx-console and enter the user name and password. Click service=Infrastructure Settings Manager. Invoke the void setGlobalSettingValue() method with the following parameter values: contextName=platform settingName=default.centers.server.url newValue=<leave empty> Invoke the void setGlobalSettingValue() method again but with the following parameter values: contextName=platform settingName= default.core.server.url newValue=<leave empty> Access Business Availability Center directly and not through the reverse proxy. If you upgraded in staging mode, proceed with your verifications of the upgrade environment. If verified, declare the upgrade environment as the new production environment. For details on configuring the reverse proxy again, see "Using a Reverse Proxy in HP Business Availability Center" in the Business Availability Center Hardening Guide. If implementing Business Availability Center 7.53 - Service Manager 7.02 (or later) integration for Incident Submission, and you are running Business Availability Center servers on a Solaris operating system using an Iplanet Web server, at the end of the 7.53 installation you must restart the Iplanet Web server. If you are installing Business Availability Center 7.53 on top of 7.52, 7.51 or 7.50 and are working with an external UCMDB architecture, you must perform the below workaround to deploy the 7.53 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.53 and UCMDB 7.53 on the external UCMDB machine. Manually copy the packages (all .zip files in the directory) from <Business Availability Center root directory>\mam_lib\bac_packages directory on the Business Availability Center Data Processing Server to the root\lib\factory_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. HP UCMDB and Federated Adapters upgrade notes: CMDB RMI adapter: The CmdbRmiAdapter.zip package is overwritten during upgrade. If you modified the CmdbRmiAdapter package follow the below instructions: Copy the existing <HP Business Availability Center Data Processing Server root directory>\mam_lib\factory_packages\CmdbRmiAdapter.zip file to a temporary directory before starting the upgrade process. After the upgrade process, edit the files in the new CmdbRmiAdapter.zip package to match the changes you had made to the old adapter package. You must make the changes in the new CmdbRmiAdapter.zip and not overwrite with your old package. Replication. When upgrading from Business Availability Center 7.0x or 7.50 (but not from 7.51 or 7.52), it is recommended to perform a diff replication on your current system prior to upgrading to 7.53. This will prevent losing data for removal during the full synch. Then, after upgrading to 7.53, each replication job should be run in full replication mode. For details on running diff and full replication, see the Replication Jobs Tab section in the Model Management guide. Service Desk adapter: Perform the following procedures to make sure you do not lose your existing Service Desk adapter configuration information during the upgrade process: Before upgrading to 7.53: Back up the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\ServiceDeskAdapter\serviceDeskConfiguration.xml file. After installation of 7.53: Copy the backed up file back to its original location. Proprietary adapter configured in Generic DB Adapter default folder: If you created a proprietary adapter in the default Generic DB Adapter folder, you must perform the following procedures to make sure you do not lose your existing Generic DB Adapter configuration information during the upgrade process. Before upgrading to 7.53: Back up the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF directory. After installation of 7.53: Copy the backed up directory back to its original location. Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.5.1 or 7.52 to 7.53): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter, after upgrading from HP Business Availability Center 7.5.1 or 7.52 to 7.53. Copy all .jar files from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter to the proprietary adapter folder. Overwrite any existing files with the same name, if such files exist. Reload the adapter Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.0x or 7.50 to 7.53): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter, after upgrading from HP Business Availability Center 7.0x or 7.50 to 7.53 (if upgrading from 7.51 or 7.52, see previous issue). Copy all .jar files from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter to the proprietary adapter folder. Overwrite any existing files with the same name, if such files exist. Copy plugins.txt from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF to <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF. Open <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF\orm.xml using a text or XML editor. In orm.xml, for each CI type that is defined as a multinode in the reconciliation_rules.txt file, change the mapped attribute name from <CI type name>_<attribute name> to <attribute name>. For example, if "host" is a multinode, change <basic name="host_host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> to:        <basic name="host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> Note: If a reconciliation rule includes a link, attributes of end2 should still be prefixed by the corresponding CI type name. For example, if one of the reconciliation rules is multinode[host] expression[host.host_hostname or ip.ip_address] end1_type[host] end2_type[ip] link_type[contained], then ip.ipaddress should still be mapped as: <basic name="ip_ip_address"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> In orm.xml, completely delete any entities whose name starts with IdClass2PK or IdClass3PK. For example, an entity defined as <entity class="generic_db_adapter.IdClass2PK_cpu" name="IdClass2PK_cpu"> should be deleted. In orm.xml, delete all lines that are similar to: <id-class class="generic_db_adapter.IdClass2PK_something"/> or <id-class class="generic_db_adapter.IdClass3PK_something"/>. Delete the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\dynamic_classes folder, if it exists. Reload the adapter. This note is relevant if you are also upgrading SiteScope and are working with the Business Availability Center/ServiceCenter or Service Manager integration. When setting up the ServiceCenter monitor in SiteScope, a file called peregrine.jar is created and placed in the WEB-INF\lib directory on the SiteScope machine. This file must be backed up before upgrading SiteScope or it will be deleted during the upgrade. After the upgrade is complete, copy the backed up peregrine.jar file back to the WEB-INF\lib directory. Business Availability Center for SAP users only: After upgrading to 7.53, but before logging into Business Availability Center, you must clean the repository. To do so, log into the following page in the JMX console, http://< Business Availability Center Server>:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=Topaz%3Aservice%3Drepositories_manager, and invoke java.lang.String cleanDefaultRepositoryTypeDBAndCache(). For more information on this process, contact HP Software Support. Uninstallation For instructions on completely uninstalling Business Availability Center, see the Business Availability Center 7.50 Deployment Guide (an updated version of which is included with 7.53). To roll back an installation of Business Availability Center 7.53 to Business Availability Center 7.52, 7.51 or 7.50, 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.53. On Windows 2003 Server, select the Show Updates option to ensure that version 7.53 is displayed 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 See also 7.52 limitations and 7.51 limitations below. Authentication: HP Business Availability Center's default authentication strategy is Lightweight Single Sign-On (LW-SSO). When LW-SSO is enabled, you must use a fully qualified domain name (FQDN) to access HP Business Availability Center. If you do not require LW-SSO, you can disable it. If LW-SSO is disabled, you do not need to enter a FQDN to access HP Business Availability Center. For details on disabling LW-SSO, see "Authentication Strategies" in the Platform Administration Guide. LDAP Authentication: See also relevant notes in 7.51 readme section below. LDAP Authentication: The following limitation applies to configuring automatically created user roles when user synchronization is enabled between HP Business Availability Center and an LDAP server, and HP Business Availability Center is configured with an Oracle Database: Navigate to Admin > Platform > Infrastructure Settings, select Foundations > LDAP Configuration, in the LDAP Configuration > LDAP General table, locate the Automatically created user roles field. Modify the value of the field so that it is empty, to ensure that LDAP users logging into HP Business Availability Center do not have any roles assigned. The Value column in the field defaults back to the last configured role. If you do not want LDAP users that are created in HP Business Availability Center to inherit any HP Business Availability Center roles, enter a space or any other syntax that is not a recognized HP Business Availability Center role in the Value field of the Edit Setting dialog box for this field. The Value column now is displayed empty, and LDAP users logging into HP Business Availability Center will not inherit any HP Business Availability Center roles. SiteScope: When changing the SiteScope data reduction mode, you must restart the Business Availability Center data processing server. ServiceCenter/Service Manager Integration: For information on integration with ServiceCenter/Service Manager see separate SM_integration.pdf located in the Download area, as well as relevant notes in 7.51 readme section below. For an updated Business Availability Center 7.53/ServiceCenter/Service Manager Integration Matrix, see the SM_integration.pdf. ServiceCenter/Service Manager Integration: The SM_integration.pdf included with Business Availability Center 7.53 consists of content that replaces existing sections in the 7.53 Documentation Library. The SM_integration.pdf contains newer versions of the following sections: The "HP Service Manager Integration with Dashboard and Service Level Management" chapter in the SM_integration.pdf replaces both the "HP Service Manager/HP ServiceCenter Integration" chapter and the "Configure HP ServiceCenter for Integration with HP Business Availability Center" chapter in the Solutions and Integrations guide The "Problem Isolation and HP Service Manager Integration" chapter in the SM_integration.pdf replaces the "Problem Isolation and HP Service Manager Integration" section and the "Configure Problem Isolation and HP Service Manager Integration" section in the "Problem Isolation Reactive Analysis" chapter in the Using Problem Isolation guide. The "The HP ServiceCenter/Service Manager Adapter" chapter in the SM_integration.pdf replaces the "The HP ServiceCenter/Service Manager Adapter" chapter in the Model Management guide. ServiceCenter/Service Manager Integration: Business Availability Center 7.53 offers the capability of automatically opening incidents in HP Service Manager/HP Service Center when a CI Status alert is triggered in Business Availability Center. Data about the alert is passed to HP Service Manager/HP Service Center and is used to open incidents that correspond to the alert. An incident previously opened is updated with new alert data when a CI Status alert is triggered with the same identifying information. FIXED IN 7.54: I18n: Exporting a report to Microsoft Excel format may display data with the wrong values if the browser locale is set to a language in which a number's decimal point is represented by a comma (",") and not a period ("."). This can happen with languages such as Hungarian, German, or French. In these cases, the user is able to see the number in the correct format in Business Availability Center (for example 33,333) but if the data is exported to Microsoft Excel, the wrong value is exported (for example 33333).: Workaround Option 1: Change the browser language to English and export the file to Microsoft Excel. The correct values appear but in English format (with a period instead of a comma). Once the data has been exported to Excel, you can change the decimal value format to a comma by selecting Control Panel > Regional and Language Options > Regional Options tab > Customize button > Decimal symbol enter a comma (,). Workaround Option 2: Use the export to XML option. In XML format, the values are correct and in the correct locale format. HP Business Availability Center bug fixes - see table below for details: Description SR/E-Sar Number Area Fixed problem of Scheduled Reports being sent prematurely after edit and after resume 3604680525 BAC_Platform Fixed issue of user being able to define CI alerts and create new recipients without permissions on first login 1602875529 BAC_PlatformAdmin Added default role setting for automatically created users 1603050342 BAC_PlatformAdmin Fixed issue of access URL in alert engine not working for follow-up alerts 207458 BAC_Platform Fixed problem of Dashboard Top View slow performance 3604202581 BAC_Dashboard Fixed out of memory problem 206576 BAC_SLM Fixed issue of Scheduled Reports that contain old EUM reports displaying the word "profile" and the X-axis labels (dates) in the server locale 48057 BAC_EUM Added to BLE ability to filter out events not needed for EMS Integration 3603829487 BAC_DataEntry Fixed issue of user with view permissions being able to create a relationship between two CIs 1602875529 BAC_MAM Fixed issue of user with view permissions on a specific view being able to generate reports for other views 1602875529 BAC_MAM Fixed issue of message "An unexpected error occurred generating this report component" appearing in HTML e-mail reports send from Outlook 2007 47916 BAC_AppCore Fixed issue of Message Broker process consuming up to 100% CPU 3603999454 BAC_BasicTopaz Fixed LDAP issue of Oracle database being case sensitive, while Active Directory is not, resulting in users being created twice 1603253921 BAC_PlatformAdmin Fixed issue in Service Level Management Time Range Comparison report of error being thrown in certain cases when two time periods matched 3604378552 BAC_SLM Fixed problem of Business Availability Center being unable to start due to inability of nanny to execute Cygwin library and tools (because of a collision with several versions of Symantec Endpoint) 2605300722 BAC_Platform Fixed issue or RUM Transaction and RUM Pages alert description containing wrong number of unavailable transactions 1603607497 BAC_Platform Fixed inability in SaaS/multi-customer environments to drill down from RUM Session Analyzer to Diagnostics without entering username and password 46785 BAC_Applications Fixed issue of customer event-based alerts not being triggered after editing alert configuration 47527, 46457 BAC_Platform HP Universal CMDB bug fixes - see table below for details: Description Area Fixed issue where a CI Type cannot be imported from an XML file Application Fixed issue where reports are sorted under Report Manager, but not under System Reports Application Fixed issue where sort function of System Reports does not work correctly Application Fixed issue where user name and password cannot be passed in the Impact Analysis Report URL when using I.E 6.x Application Fixed issue where user with only "view" permissions for a view can edit CIs properties Application Fixed issue with system reports generated in CSV format that do not conform to the CSV standard used in version 6.6 and earlier Application Fixed user permissions issues, including allowing access to all views in Asset Reports and enabling user with no permissions to create relationships in ITU Application Fixed issue of functional attributes missing from reports, when nodes are connected by a virtual compound link Application Fixed issue to enlarge timeout for remote process executions by adding a method DDM Fixed issue in SAP Solution Manager discovery DDM Fixed issue where DDM does not return all CIs when discovering WebLogic versions 8.1 and 9.2 DDM Internal bug fixes Updated Components The following updated components are included with Business Availability Center 7.53: Real User Monitor Probe 7.53 Build 2 (Linux)  For instructions on upgrading the Real User Monitor probe, see separate Upgrade_RUM.pdf located in the Download area. The issue of only being able to start the Real User Monitor probe as the root user has been fixed and you are now able to start the probe as another user. Real User Monitor Engine 7.53 Build 24 (Windows) For instructions on upgrading the Real User Monitor engine, see separate Upgrade_RUM.pdf located in the Download area. You can now successfully upgrade a Real User Monitor installation to a distributed environment (with the Real User Monitor engine and databases residing on different machines). Fixed issue of not being able to run Auto Discovery when the RUM engine Web console was configured to be HTTPS. You can now use the Siebel template to create a Real User Monitor application without stopping Real User Monitor from being able to retrieve its configuration from Business Availability Center. Business Process Monitor 7.53 Build 1046 (Windows, Solaris) To install Business Process Monitor, first uninstall the existing Business Process Monitor via Add/Remove Programs (Windows) or BPM_DIR\_uninst\uninstall (Solaris). Then run HPBPM_v7.53_win.exe (Windows) or HPBPM_v7.53_solv4.bin (Solaris). Business Process Monitor 7.53 contains fixes for replay issues for the Oracle NCA, RDP, Web-ajax, and SOAP protocols; Business Process Monitor 7.53 contains a fix for the VSlauncher problem when Business Process Monitor is installed on Windows 2003 servers in multi-processor environments. Discovery Probe 7.53 (Windows) To install the Discovery Probe, first uninstall the existing Discovery Probe via Start > Programs > UCMDB or HP DDM > Uninstall UCMDB Discovery Probe or Uninstall HP DDM Probe. Then run HPDiscoveryProbe_v75_sp_ win32.exe. Bug fixes  Updated HP Business Availability Center Support Matrixes This section describes updated matrix sections for various environments and components supported by HP Business Availability Center. Only specific updates for 7.53 are shown. For 7.52 and 7.51 updates, see the relevant sections below. √=supported, X=not supported For an updated Business Availability Center 7.53/ServiceCenter/Service Manager Integration Matrix, see the SM_integration.pdf, included with Business Availability Center 7.53. 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.53 HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 BPM 7.53 (VuGen 9.1) √ (Recommended) √ √ √ √ BPM 7.52 (VuGen 9.1) √ √ (Recommended) √ √ √ BPM 7.51 (VuGen 9.1) √ √ √ (Recommended) √ √ BPM 7.50 (VuGen 9.1) √ √ √ √ (Recommended) √ BPM 7.0 (VuGen 9.0) √ √ √ √ √ (Recommended) QTP SAP R/3 7.31 √ √ √ √ √ QTP 9.5 √ √ √ √ X QTP 9.1/2 √ √ √ √ √ QTP 9.0 √ √ √ √ √ Real User Monitor Support Matrix Compatibility Matrix HP Business Availability Center 7.53 HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 Real User Monitor Engine 7.53 √ √ √ √ X Real User Monitor Probe 7.53 √ √ √ √ X Real User Monitor Engine 7.52 √ √ √ √ X Real User Monitor Probe 7.52 √ √ √ √ X Real User Monitor Engine 7.51 √ √ √ √ X Real User Monitor Probe 7.51 √ √ √ √ X Real User Monitor Engine 7.50 √ √ √ √ X Real User Monitor Probe 7.50 √ √ √ √ X Real User Monitor Engine 7.0 X X X X √ Real User Monitor Probe 7.0 X X X X √ DDM Discovery Probe Support Matrix Compatibility Matrix HP Business Availability Center 7.53 HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 Discovery Probe 7.53 √ X X X X Discovery Probe 7.52 X √ X X X Discovery Probe 7.51 X X √ X X Discovery Probe 7.50 X X X √ X Discovery Probe 7.0 X X X X √ Note: Discovery Probe 7.01 works only with Business Availability Center 7.01. HP Business Availability Center 7.52 Readme Software version: 7.52 / December 2008 This file provides information about HP Business Availability Center 7.52, 7.51 (for 7.51 information, click here), and 7.50 (for 7.50 information, click here). Business Availability Center 7.52 Files Installation Prerequisites Installation Uninstallation Version Content and Limitations Updated Components Updated HP Business Availability Center Support Matrixes Business Availability Center 7.52 Files Business Availability Center 7.52 includes the following files: Business Availability Center 7.52 setup file Setup.exe (Windows installation) Setup.bin (Solaris installation) Component setup files New: Real User Monitor Probe 7.52 (Linux) New: Real User Monitor Engine 7.52 (Windows) New: Business Process Monitor 7.52 (Windows, Solaris) New: Discovery Probe 7.52 (Windows) Note: You need to separately download new component setup files. Documentation files whatsnew.html readme752.html (includes 7.52, 7.51, and 7.50 Readmes) Upgrade_RUM.pdf - contains instructions on upgrading the Real User Monitor probe and engine SM_integration.pdf - contains information on integration with Service Manager ProblemIsolation_for_SAP.pdf - contains information on the Problem Isolation feature in Business Availability Center for SAP Additional files tzupdater.jar - file needed for Daylight Savings Time definition update Installation Prerequisites Business Availability Center 7.52 must be installed on top of Business Availability Center 7.50 or 7.51. Installation If you have Business Availability Center 7.50 or 7.51 installed, install Business Availability Center 7.52 on every Business Availability Center server by double-clicking on the relevant setup file (Windows or Solaris) and following the on-screen instructions. If you do not yet have Business Availability Center 7.50 installed, install it according to the instructions in the Business Availability Center 7.50 Deployment Guide. Then install Business Availability Center 7.52 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.52. This provides your system with the latest DST definitions. Note that the tzupdater.jar file included with Business Availability Center 7.52 only includes time zone updates for the following countries: Argentina, Brazil, Cuba, Egypt, Iran, Mauritius, Morocco, Pakistan, Turkey, 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.50 Deployment Guide. If implementing Business Availability Center 7.52 - Service Manager 7.02 (or later) integration for Incident Submission, and you are running Business Availability Center servers on a Solaris operating system using an Iplanet Web server, at the end of the 7.52 installation you must restart the Iplanet Web server. If you are installing Business Availability Center 7.52 on top of 7.51 or 7.50 and are working with an external UCMDB architecture, you must perform the below workaround to deploy the 7.52 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.52 and UCMDB 7.52 on the external UCMDB machine. Manually copy the packages (all .zip files in the directory) from <Business Availability Center root directory>\mam_lib\bac_packages directory on the Business Availability Center Data Processing Server to the root\lib\factory_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. HP UCMDB and Federated Adapters upgrade notes: CMDB RMI adapter: The CmdbRmiAdapter.zip package is overwritten during upgrade. If you modified the CmdbRmiAdapter package follow the below instructions: Copy the existing <HP Business Availability Center Data Processing Server root directory>\mam_lib\factory_packages\CmdbRmiAdapter.zip file to a temporary directory before starting the upgrade process. After the upgrade process, edit the files in the new CmdbRmiAdapter.zip package to match the changes you had made to the old adapter package. You must make the changes in the new CmdbRmiAdapter.zip and not overwrite with your old package. Replication. When upgrading from Business Availability Center 7.0x or 7.50 (but not from 7.51), it is recommended to perform a diff replication on your current system prior to upgrading to 7.52. This will prevent losing data for removal during the full synch. Then, after upgrading to 7.52, each replication job should be run in full replication mode. For details on running diff and full replication, see the Replication Jobs Tab section in the Model Management guide. Service Desk adapter: Perform the following procedures to make sure you do not lose your existing Service Desk adapter configuration information during the upgrade process: Before upgrading to 7.52: Back up the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\ServiceDeskAdapter\serviceDeskConfiguration.xml file. After installation of 7.52: Copy the backed up file back to its original location. Proprietary adapter configured in Generic DB Adapter default folder: If you created a proprietary adapter in the default Generic DB Adapter folder, you must perform the following procedures to make sure you do not lose your existing Generic DB Adapter configuration information during the upgrade process. Before upgrading to 7.52: Back up the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF directory. After installation of 7.52: Copy the backed up directory back to its original location. Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.5.1 to 7.52): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter, after upgrading from HP Business Availability Center 7.5.1 to 7.52. Copy all .jar files from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter to the proprietary adapter folder. Overwrite any existing files with the same name, if such files exist. Reload the adapter Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.0x or 7.50 to 7.52): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter, after upgrading from HP Business Availability Center 7.0x or 7.50 to 7.52 (if upgrading from 7.51, see previous issue). Copy all .jar files from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter to the proprietary adapter folder. Overwrite any existing files with the same name, if such files exist. Copy plugins.txt from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF to <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF. Open <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF\orm.xml using a text or XML editor. In orm.xml, for each CI type that is defined as a multinode in the reconciliation_rules.txt file, change the mapped attribute name from <CI type name>_<attribute name> to <attribute name>. For example, if "host" is a multinode, change <basic name="host_host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> to:        <basic name="host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> Note: If a reconciliation rule includes a link, attributes of end2 should still be prefixed by the corresponding CI type name. For example, if one of the reconciliation rules is multinode[host] expression[host.host_hostname or ip.ip_address] end1_type[host] end2_type[ip] link_type[contained], then ip.ipaddress should still be mapped as: <basic name="ip_ip_address"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> In orm.xml, completely delete any entities whose name starts with IdClass2PK or IdClass3PK. For example, an entity defined as <entity class="generic_db_adapter.IdClass2PK_cpu" name="IdClass2PK_cpu"> should be deleted. In orm.xml, delete all lines that are similar to: <id-class class="generic_db_adapter.IdClass2PK_something"/> or <id-class class="generic_db_adapter.IdClass3PK_something"/>. Delete the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\dynamic_classes folder, if it exists. Reload the adapter. Issues related to Business Availability Center 7.52/Service Center or Service Manager integration and SiteScope: This note is relevant if you are also upgrading SiteScope and are working with the Business Availability Center/ServiceCenter or Service Manager integration. When setting up the ServiceCenter monitor in SiteScope, a file called peregrine.jar is created and placed in the WEB-INF\lib directory on the SiteScope machine. This file must be backed up before upgrading SiteScope or it will be deleted during the upgrade. After the upgrade is complete, copy the backed up peregrine.jar file back to the WEB-INF\lib directory. Business Availability Center for SAP users only: After upgrading to 7.52, but before logging into Business Availability Center, you must clean the repository. To do so, log into the following page in the JMX console, http://< Business Availability Center Server>:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=Topaz%3Aservice%3Drepositories_manager, and invoke java.lang.String cleanDefaultRepositoryTypeDBAndCache(). For more information on this process, contact HP Software Support. Uninstallation For instructions on completely uninstalling Business Availability Center, see the Business Availability Center 7.50 Deployment Guide. To roll back an installation of Business Availability Center 7.52 to Business Availability Center 7.51 or 7.50, 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.52. On Windows 2003 Server, select the Show Updates option to ensure that version 7.52 is displayed 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 See also 7.51 limitations below. HP Business Availability Center's default authentication strategy is Lightweight Single Sign-On (LW-SSO). When LW-SSO is enabled, you must use a fully qualified domain name (FQDN) to access HP Business Availability Center. If you do not require LW-SSO, you can disable it. If LW-SSO is disabled, you do not need to enter a FQDN to access HP Business Availability Center. For details on disabling LW-SSO, see "Authentication Strategies" in the Platform Administration Guide. LDAP Authentication. See relevant notes in 7.51 readme section below. ServiceCenter/Service Manager Integration. For information on integration with ServiceCenter/Service Manager see separate SM_integration.pdf located in the Download area, as well as relevant notes in 7.51 readme section below. For an updated Business Availability Center 7.52/ServiceCenter/Service Manager Integration Matrix, see the SM_integration.pdf. I18n: When working in a browser with Korean, Japanese, Chinese, or Russian locale setting, axis labels on reports generated using Flash can be shown only in horizontal mode. As a result, when working in those locales axis labels will not be displayed in those reports. I18n: When working in a browser with Korean, Japanese, Chinese, or Russian locale setting, axis labels on reports generated using Flash can be shown only in horizontal mode. As a result, when working in those locales axis labels will be displayed only in the following cases: Y-axis label are displayed only if the chart property rotateYLabelsInMB equals true in the relevant presentation xml. X-axis labels are displayed only if the chart property XAxisLabelsModeStr equals Horizontal or the property rotateXLabelsInMB equals true in the relevant presentation xml. All presentation xml files are located under <HP Business Availability Center root directory>\AppServer\webapps\<relevant_war>\WEB-INF\rfw\conf\applications where relevant_war can be site.war, bpi.war, or tvb.war. After modifying the properties, restart the Business Availability Center Gateway Server. The context menu goto report Planned changes is not working in Business Availability Center 7.52 and will be removed completely in Business Availability Center 8.00. The drilldown from Dashboard to Related Changes Report in Release Control (formerly CCM) is not working. The report is deprecated and will be removed in Business Availability Center 8.00. Bug fixes - see table below for details: Description SR/E-Sar Number Area Fixed issue of Service Level Management permissions 3602931611 BAC_SLM Fixed issue of Event-Based Alert report showing irrelevant profiles as filter when Real User Monitor is connected 3603763764; 44947 BAC_Platform Fixed issue in Alert Log of Details report displaying Tomcat error when selected for specific profiles 45062 BAC_Platform Added setting for maximum number of CIs in Dashboard Filter tab  3601714588 BAC_Dashboard Fixed issue of event-based alert being triggered even if the incoming sample improves its state 42276 BAC_BasicTopaz Geographical Map in Dashboard: upgraded VE version to Activate Map  45611 BAC_Dashboard Added support for simultaneous SiteScope and Business Process Monitor reports  45956 BAC_DataRetrieval Fixed issue of Business Availability Center creating persistent cookie 3603619038 BAC_Platform Fixed LDAP issue of group mapping not working properly when "\," in user DN  3603671405 BAC_PlatformAdmin Fixed issue of My BAC not working when Business Availability Center is configured with reverse proxy  1602916661 BAC_Dashboard Fixed incorrect logic issue with JVM Threads System Health monitor (removed Peak Thread Count measurement)  44574 BAC_SiteScope Fixed issue of required libraries for Windows authentication via data direct driver in 64-bit server environments missing from Business Availability Center setup 3603596158 BAC_Platform Set profile action to stop when customer is in staging mode, regardless of entire Business Availability Center staging state 45394 BAC_BPM_CM Fixed issue of LDAP Group Mapping not reading the LDAP groups when using Active Directory and special characters 1601579392 BAC_PlatformAdmin Added referrals support to UUM and java.naming.referalls as setting to LDAPIntegration.xml  3603736917 BAC_PlatformAdmin Fixed issue of Flash component in Custom Report not displaying in PDF format 1602135667 BAC_Platform Fixed issue of Cross-Performance reports not generating when selecting multiple profiles 37005 BAC_SAM In Cross-Performance report, added option to disable the auto-scale mechanism 3603235111 BAC_SAM In Cross-Performance report, fixed issue of Max scale and Min scale values not appearing in the report filter 44822 BAC_SAM Internal bug fixes Updated Components The following updated components are included with Business Availability Center 7.52: Real User Monitor Probe 7.52 Build 7.5.2.06 (Linux)  For instructions on upgrading the Real User Monitor probe, see separate Upgrade_RUM.pdf located in the Download area. Improved Probe performance Real User Monitor Engine 7.52 Build 17 (Windows) For instructions on upgrading the Real User Monitor engine, see separate Upgrade_RUM.pdf located in the Download area. Fixed Siebel frame unification Fixed the ability to disable clickstream data Business Process Monitor 7.52 Build 1041 (Windows, Solaris) To install Business Process Monitor, first uninstall the existing Business Process Monitor via Add/Remove Programs (Windows) or BPM_DIR\_uninst\uninstall (Solaris). Then run HPBPM_v7.52_win.exe (Windows) or HPBPM_v7.52_solv4.bin (Solaris). HP Business Process Monitor 7.52 contains a fix to the Citrix protocol replay mechanism, which improves the way the color quality and resolution are set during a Citrix session. This is essential to certain applications that have resolution and color depth limitations..  Discovery Probe 7.52 (Windows) To install the Discovery Probe, first uninstall the existing Discovery Probe via Start > Programs > UCMDB or HP DDM > Uninstall UCMDB Discovery Probe or Uninstall HP DDM Probe. Then run HPDiscoveryProbe_v75_sp_ win32.exe. Bug fixes  Updated HP Business Availability Center Support Matrixes This section describes updated matrix sections for various environments and components supported by HP Business Availability Center. Only specific updates for 7.52 are shown. For 7.51 updates, see below. √=supported, X=not supported For an updated Business Availability Center 7.52/ServiceCenter/Service Manager Integration Matrix, see the SM_integration.pdf, included with Business Availability Center 7.52. 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.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 BPM 7.52 (VuGen 9.1) √ (Recommended) √ √ √ BPM 7.51 (VuGen 9.1) √ √ (Recommended) √ √ BPM 7.50 (VuGen 9.1) √ √ √ (Recommended) √ BPM 7.0 (VuGen 9.0) √ √ √ √ (Recommended) QTP SAP R/3 7.31 √ √ √ √ QTP 9.5 √ √ √ X QTP 9.1/2 √ √ √ √ QTP 9.0 √ √ √ √ Real User Monitor Support Matrix Compatibility Matrix HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 Real User Monitor Engine 7.52 √ √ √ X Real User Monitor Probe 7.52 √ √ √ X Real User Monitor Engine 7.51 √ √ √ X Real User Monitor Probe 7.51 √ √ √ X Real User Monitor Engine 7.50 √ √ √ X Real User Monitor Probe 7.50 √ √ √ X Real User Monitor Engine 7.0 X X X √ Real User Monitor Probe 7.0 X X X √ DDM Discovery Probe Support Matrix Compatibility Matrix HP Business Availability Center 7.52 HP Business Availability Center 7.51 HP Business Availability Center 7.50 HP Business Availability Center 7.0 Discovery Probe 7.52 √ X X X Discovery Probe 7.51 X √ X X Discovery Probe 7.50 X X √ X Discovery Probe 7.0 X X X √ Note: Discovery Probe 7.01 works only with Business Availability Center 7.01. HP Business Availability Center 7.51 Readme Software version: 7.51 / September 2008 This file provides information about HP Business Availability Center 7.51 and HP Business Availability Center 7.50 (for 7.50 information, click here). Business Availability Center 7.51 Files Installation Prerequisites Installation Uninstallation Version Content and Limitations Updated Components Updated HP Business Availability Center Support Matrixes Business Availability Center 7.51 Files Business Availability Center 7.51 includes the following files: Business Availability Center 7.51 setup file Setup.exe (Windows installation) Setup.bin (Solaris installation) Component setup files New: Real User Monitor Probe 7.51 (Linux) New: Real User Monitor Engine 7.51 (Windows) New: Business Process Monitor 7.51 (Windows, Solaris) New: Discovery Probe 7.51 (Windows) Note: You need to separately download new component setup files. Documentation files whatsnew.html readme751.html (includes 7.51 and 7.50 Readmes) Upgrade_RUM.pdf - contains instructions on upgrading the Real User Monitor probe and engine ProblemIsolation_for_SAP.pdf - contains information on the Problem Isolation feature in Business Availability Center for SAP Additional files tzupdater.jar - file needed for Daylight Savings Time definition update Installation Prerequisites Business Availability Center 7.51 must be installed on top of Business Availability Center 7.50. Installation If you do not yet have Business Availability Center 7.50 installed, install it according to the instructions in the Business Availability Center 7.50 Deployment Guide. Then install Business Availability Center 7.51 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.51. This provides your system with the latest DST definitions. Note that the tzupdater.jar file included with Business Availability Center 7.51 only includes time zone updates for the following countries: Pakistan, Morocco, and Mongolia. 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.50 Deployment Guide. If you are installing Business Availability Center 7.51 on top of 7.50 and are working with an external UCMDB architecture, you must perform the below workaround to deploy the 7.51 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.51 and UCMDB 7.51 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. Universal CMDB and Federated Adapters upgrade notes: Replication. When upgrading from Business Availability Center 7.0x or 7.50, it is recommended to perform a diff replication on your current system prior to upgrading to 7.51. This will prevent losing data for removal during the full synch. Then, after upgrading to 7.51, each replication job should be run in full replication mode. For details on running diff and full replication, see the Replication Jobs Tab section in the Model Management guide. Service Desk adapter: Perform the following procedures to make sure you do not lose your existing Service Desk adapter configuration information during the upgrade process: Before upgrading to 7.51: Back up the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\ServiceDeskAdapter\serviceDeskConfiguration.xml file. After installation of 7.51: Copy the backed up file back to its original location. Proprietary adapters based on Generic DB Adapter. If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter, after upgrading from HP Business Availability Center 7.01 or 7.5 to 7.51. Copy all .jar files from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter to the proprietary adapter folder. Overwrite any existing files with the same name, if such files exist. Copy plugins.txt from <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF to <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF. Open <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\META-INF\orm.xml using a text or XML editor. In orm.xml, for each CI type that is defined as a multinode in the reconciliation_rules.txt file, change the mapped attribute name from <CI type name>_<attribute name> to <attribute name>. For example, if "host" is a multinode, change <basic name="host_host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> to:        <basic name="host_hostname"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> Note: If a reconciliation rule includes a link, attributes of end2 should still be prefixed by the corresponding CI type name. For example, if one of the reconciliation rules is multinode[host] expression[host.host_hostname or ip.ip_address] end1_type[host] end2_type[ip] link_type[contained], then ip.ipaddress should still be mapped as: <basic name="ip_ip_address"> <column updatable="false" insertable="false" name="[column_name]"/> </basic> In orm.xml, completely delete any entities whose name starts with IdClass2PK or IdClass3PK. For example, an entity defined as <entity class="generic_db_adapter.IdClass2PK_cpu" name="IdClass2PK_cpu"> should be deleted. In orm.xml, delete all lines that are similar to: <id-class class="generic_db_adapter.IdClass2PK_something"/> or <id-class class="generic_db_adapter.IdClass3PK_something"/>. Delete the <HP Business Availability Center Data Processing Server root directory>\fcmdb\Codebase\<proprietary adapter folder>\dynamic_classes folder, if it exists. Reload the adapter. Issues related to Business Availability Center 7.51/Service Center or Service Manager integration and SiteScope: This note is relevant if you are also upgrading SiteScope and are working with the Business Availability Center/ServiceCenter or Service Manager integration. When setting up the ServiceCenter monitor in SiteScope, a file called peregrine.jar is created and placed in the WEB-INF\lib directory on the SiteScope machine. This file must be backed up before upgrading SiteScope or it will be deleted during the upgrade. After the upgrade is complete, copy the backed up peregrine.jar file back to the WEB-INF\lib directory. Uninstallation For instructions on completely uninstalling Business Availability Center, see the Business Availability Center 7.50 Deployment Guide. To roll back an installation of Business Availability Center 7.51 to Business Availability Center 7.50, 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.51. On Windows 2003 Server, select the Show Updates option to ensure that version 7.51 is displayed 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 HP Business Availability Center's default authentication strategy is Lightweight Single Sign-On (LW-SSO). When LW-SSO is enabled, you must use a fully qualified domain name (FQDN) to access HP Business Availability Center. If you do not require LW-SSO, you can disable it. If LW-SSO is disabled, you do not need to enter a FQDN to access HP Business Availability Center. For details on disabling LW-SSO, see "Authentication Strategies" in the Platform Administration guide. LDAP Authentication. The below notes are relevant if you are using the LDAP authentication strategy: In the Lightweight Directory Access Protocol (LDAP) Authentication and Mapping section in the Platform Administration guide, there is a paragraph that begins with the following sentence: You can use an external LDAP server to store the authentication information instead of using the internal HP Business Availability Center service. The sentence at the end of that paragraph, "The LDAP server must be in the same subnet as the rest of the HP Business Availability Center servers.", should be replaced with the following: For optimal performance, it is recommended that the Business Availability Center servers and LDAP server be in the same subnet. For optimal security, it is recommended to either configure an SSL connection between the Business Availability Center Gateway server and LDAP server, or to have Business Availability Center servers and the LDAP server on the same secure internal network segment. When enabling the Group Mapping feature to connect the LDAP server to the HP Business Availability Center server, you can login to HP Business Availability Center with any unique user attribute that exists on the LDAP server (for example, email address). To select the LDAP attribute with which you want to log into HP Business Availability Center, navigate to Admin > Platform > Setup and Maintenance > Infrastructure Settings, select Foundations and choose LDAP Configuration, locate the LDAP Configuration - LDAP Options for Classes and Attributes table, and modify the User unique ID attribute to the attribute you want to log in with, as it appears on the LDAP server. Note: If there are users in the LDAP group that do not have the attribute with which you are logging in, none of the users in that group appear in the Group Mappings dialog box on the User Management interface (Admin > Platform > Setup and Maintenance > Users and Permissions). Therefore, you must ensure that the attribute you are using is present for all users on the LDAP server. User Synchronization maps user groups on an LDAP server to user groups in HP Business Availability Center, simplifying the process of managing users in HP Business Availability Center because all of the user management functions are done through the LDAP server. Once User Synchronization is enabled, you cannot create individual users on the HP Business Availability Center interface, as all user management operations are performed on the LDAP server. Authentication is performed by the LDAP server, and authorization is handled by the HP Business Availability Center server. You create groups in HP Business Availability Center with the appropriate roles to nest users into, and users adopt the permission level of the group they are nested in. These groups are then mapped to groups on the LDAP server. If users are moved between LDAP groups, they are automatically moved between the corresponding mapped groups on the HP Business Availability Center server. You can optionally map an LDAP group to multiple HP Business Availability Center groups, or multiple LDAP groups to an HP Business Availability Center group. An LDAP user that logs into HP Business Availability Center is created as an HP Business Availability Center user. If the user belongs to an LDAP group, they are automatically assigned to the HP Business Availability Center group that is mapped to their LDAP group. If they do not belong to an LDAP group, they are created as an HP Business Availability Center user with System Viewer permissions. Their permissions can then be modified on the Users and Permissions interface. A user that has been removed from the LDAP server is still displayed as an HP Business Availability Center user, even though they are no longer a registered LDAP user and will not be able to login to HP Business Availability Center. These users are called Obsolete Users. For details on removing Obsolete Users from HP Business Availability Center, see the section Delete Obsolete Users in the Platform Administration guide. In the Platform Administration guide, Database Administration section, Determine the Events Per Minute (EPM) for Data Arriving in HP Business Availability Center topic, step 2, replace the line: Statistics for: DB Summary:<database name>Sample:<sample name> - (collected over <time period>) with Statistics for: DB Name:<database name> Sample: <sample name> - (collected over <time period>) In addition, append the sentence below: If you have more than one Gateway Server, you must total the values obtained from each server. to the last paragraph of the section, following "The selected number represents the events per second. Multiply this number by 60 to retrieve the events per minute." ServiceCenter/Service Manager Integration. This section is relevant if you are integrating Business Availability Center with Service Center 6.2.6 or 6.2.1 or Service Manager 7.01, 7.02, or 7.10. The following notes are addendums to the HP ServiceCenter Integration - Workflow topic and HP ServiceCenter Monitor User Interface topic described in the System Availability Management guide. Addendum to workflow Step 1: After following the procedure to load the .unl file, verify that the clocks table has the values described below. If the values do not match, edit the clocks table in ServiceCenter/Service Manager so that the values are the same as in the below table. Field Caption Type events[start] start DateTimeType events[stop] stop DateTimeType name name StringType Key.char clockId StringType sysmodtime sysmodtime DateTimeType Type type StringType Key.numeric clockKey DecimalType Addendum to workflow Step 3d (Create the Jar File-Step 4): The step states that when integrating with Service Manager 7.01, the URL must point to the sc62server wsdl that is running on Service Manager 7.01. The exact URL syntax to the sc62server wsdls for 7.01, 7.02, or 7.10 is as follows: clocks.wsdl.url=http://<SM host>:<SM port>/sc62server/PWS/Clocks?wsdl prob.wsdl.url=http://<SM host>:<SM port>/sc62server/PWS/IncidentManagement?wsdl When integrating with Service Manager 6.2.6, the exact URL syntax to the sc62server wsdl is as follows: clocks.wsdl.url=http://<SM host>:<SM port>/sc61server/PWS/Clocks?wsdl prob.wsdl.url=http://<SM host>:<SM port>/sc61server/PWS/IncidentManagement?wsdl Addendum to HP ServiceCenter Monitor User Interface section, HP ServiceCenter Web Service Endpoint GUI element description: The URL syntax when integrating with Service Manager 7.01 is: <protocol>://<SM host>:<SM port>/sc62server/PWS/. The URL syntax when integrating with ServiceCenter 6.2.6 is: <protocol>://<SM host>:<SM port>/sc61server/PWS/. The Includes CMDB relationship should be used only for SiteScope CIs and its usage is deprecated for any other CI types. It is strongly recommended to replace such relationships with Depends On relationships. Caution should be exercised when performing such replacements due to the RECURSIVE_DELETE qualifier of the Includes relationship. This means that deletion of the relationship causes automatic deletion of the target CI of the relationship from the CMDB. Note that all remaining instances of this relationship that are unrelated to SiteScope CIs will be automatically replaced by Depends On in future versions of Business Availability Center. The Direct Links URLs (which are documented in the Platform Administration guide) that contain the string newReport.do will not work in Internet Explorer 6 browsers (but will work in IE7). Workaround: Replace newReport.do with popupAction.do in the URL. Returned ability to associate an executable command with a CI type, which is then available from the CI context menu. Real User Monitor Session Replay now works with Java 1.6 Runtime Environment (plug-in). The issue of the Problem Isolation feature in Business Availability Center for SAP not showing any results has been fixed. For details on this functionality, see ProblemIsolation_for_SAP.pdf, located in the Download area. 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, in IT Universe Manager, click the Rebuild View button in the CI Selector pane. (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 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 related to removing or moving a group of users in the User Management page 1601419886 BAC_PlatformAdmin Fixed issue of users not being able to open CMDB UI when a user is associated with more then one group 1601350738 BAC_PlatformAdmin Fixed issue of event-based alerts upgrade not occurring in two-server installation 1601642044 Bac_BasicTopaz Fixed issue of Trend report not showing data for past year 42869 BAC_AppCore Fixed issue in IDM-SSO of self-server request http://localhost:8080/XXX being filtered by BAC SSO filter 203626 BAC_PlatformAdmin Added support in LDAP authentication for login with email instead of uid 202990 BAC_PlatformAdmin Fixed issue of published Trend report (by Links) leading to the last previewed Trend report 1601775290 BAC_Applications Fixed LDAP performance issue when retrieving LDAP groups per a specific LDAP user when using dynamic groups 203303 BAC_PlatformAdmin Fixed issue of RUM Servers by Page Summary Report failing after upgrade 3602560367 BAC_EUM Fixed issue of automatic user creation with LDAP authentication 203849 BAC_PlatformAdmin Fixed issue of drilldown from System Availability Management to SiteScope failing when request too large 3602559753 BAC_SiteScope Fixed issue of sporadic appearances of 'Internal system error' messages in Dashboard Top View 44202 BAC_Dashboard Fixed issue of Send Email function on Report Manager page not working in Japanese locale 44381 BAC_AppCore Fixed issue of exception thrown when editing alert with complex dominant alerts hierarchy 3602998493 BAC_Alerts Fixed issue of event alert group-by data (for example, Transaction Name) missing from alert actions 1600385781 BAC_Alerts Internal bug fixes Updated Components The following updated components are included with Business Availability Center 7.51: Real User Monitor Probe 7.51 Build 7.5.1.24 (Linux)  For instructions on upgrading the Real User Monitor probe, see separate Upgrade_RUM.pdf located in the Download area. Improved Probe performance Improved SSL traffic handling Real User Monitor Engine 7.51 Build 11 (Windows) For instructions on upgrading the Real User Monitor engine, see separate Upgrade_RUM.pdf located in the Download area. Added support for WebSphere Portal Fixed issue of text pattern of type "not containing" not working in some cases Business Process Monitor 7.51 Build 1039 (Windows, Solaris) To install Business Process Monitor, first uninstall the existing Business Process Monitor via Add/Remove Programs (Windows) or BPM_DIR\_uninst\uninstall (Solaris). Then run HPBPM_v7.51_win.exe (Windows) or HPBPM_v7.51_solv4.bin (Solaris). HP Business Process Monitor 7.51 contains security enhancements to the BPM Web console.  Discovery Probe 7.51 Build 46 (Windows) To install the Discovery Probe, first uninstall the existing Discovery Probe via Start > Programs > UCMDB or HP DDM > Uninstall UCMDB Discovery Probe or Uninstall HP DDM Probe. Then run HPDiscoveryProbe_v7.51_ win32.exe. Bug fixes  Updated HP Business Availability Center Support Matrixes This section describes updated matrix sections for various environments and components supported by HP Business Availability Center. Only specific updates for 7.51 are shown. √=supported, X=not supported Business Availability Center Component Support Matrixes Supported Environments Component Brand Version Comments HP Business Availability Center Servers - Operating Systems Windows Additional supported environment: Windows Server 2003 R2 32-Bit Enterprise Edition, Service Pack 2   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.51 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.51 (VuGen 9.1) √ (Recommended) √ √ √ √ √ √ 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.5 √ √ X X X X X QTP 9.1/2 √ √ √ √ (BPM 6.5) X X X QTP 9.0 √ √ √ √ √ (Recommended) √ (BPM 6.1) √ Real User Monitor Support Matrix Compatibility Matrix HP Business Availability Center 7.51 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.51 √ √ X X X X X Real User Monitor Probe 7.51 √ √ X X X X X 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 X Real User Monitor Probe 7.0 X X √ X X X X Real User Monitor Engine 6.5 X X X √ √ (Recommended, together with Real User Monitor Probe 6.5) X X Real User Monitor Probe 6.5 X X X √ √ (Recommended, together with Real User Monitor Engine 6.5) X X Real User Monitor Engine 6.2 X X X X √ X X Real User Monitor Probe 6.2 X 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 √ X Real User Monitor Probe 6.1 X X X X X √ X 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 - 2009 Hewlett-Packard Development Company, L.P. 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 2009 Hewlett-Packard Development Company, L.P.