HP Business Availability Center 8.02 Readme
for the Windows and Solaris operating systems
Software version: 8.02
Publication date: June 2009
This file provides information about HP Business Availability Center 8.02, 8.01, and 8.00 (for 8.01 information, click here; for 8.00 information, click here).
Business Availability Center 8.02 Files
Separation of Discovery and Dependency Mapping (DDM) Content into Content Packs
Version Content and Limitations
Universal CMDB Content and Limitations
Updated HP Business Availability Center Support Matrixes
Business Availability Center 8.02 Files
Business Availability Center 8.02 includes the following files:
Business Availability Center 8.02 setup file
Component setup files
- New: Real User Monitor Probe 8.02 (Windows 2003, Linux)
- New: Real User Monitor Engine 8.02 (Windows)
- New: Business Process Monitor 8.02 (Windows, Solaris)
- New: Virtual User Generator 9.50 (Windows)
- New: Discovery Probe 8.02 (Windows)
- New: Business Process Insight Server 8.02
- New: Diagnostics 8.02 components (see Diagnostics readme for details)
Note: You need to separately download new component setup files.
Documentation files
Additional files
Installation Prerequisites
Business Availability Center 8.02 must be installed on top of Business Availability Center 8.01. Customers who do not yet have 8.01 installed must install it on top of Business Availability Center 8.00. For details on Business Availability Center 8.01, click here.
Note: The requirement to install Business Availability Center 8.01 as a prerequisite is due to the separation of updated Discovery and Dependency Mapping content into separate content packs. For details, see the next section.
Separation of Discovery and Dependency Mapping (DDM) Content into Content Packs
Discovery and Dependency Mapping (DDM) content packs include new and updated packages needed for activating DDM jobs. The packs also include documentation of the procedures for running the DDM jobs.
The Business Availability Center 8.01 release contained software changes to support the separation of service pack releases from DDM content pack releases. Thus, Business Availability Center 8.01 is a prerequisite to enabling the separation of service pack versus content pack installation.
As a result of the separation of service pack from content pack, starting from Business Availability Center 8.01, customers can choose whether to update their DDM content via content pack release regardless of which service pack release is installed.
Note: DDM Content Pack 1 is built into Business Availability Center 8.01 (there is no separate Content Pack 1 installation).
Note: DDM Content Pack 2 is not supported by Business Availability Center (it is not possible to install Content Pack 2 on top of Business Availability Center).
Installation
Read all information in this Installation section and the 8.01 installation section before starting the installation. If you are installing 8.01, directly followed by 8.02, you do not need to repeat the pre-installation procedures (file backups or log setting modifications) listed in the 8.01 installation section before installing 8.02. Further, you should perform all the post-installation procedures mentioned in the 8.01 installation section after installing 8.02.
- If you have Business Availability Center 8.01 installed, stop Business Availability Center on all servers and make sure it is stopped before installing the service pack. Install the 8.02 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. After installing 8.02 on all servers, restart Business Availability Center on all servers.
- Note: If Business Availability Center is running on a Windows 64-bit operating system with at least 16 GB of RAM, after installing 8.02 but before starting Business Availability Center, you must run the database configuration utility on all servers and reconnect to the existing databases.
- Note: If you are planning to install a DDM content pack, do not restart Business Availability Center until after the content pack is installed.
- If you have Business Availability Center 8.00 installed, stop Business Availability Center on all servers and make sure it is stopped before installing the service pack. Install the 8.01 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. Then install the 8.02 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. After installing 8.02 on all servers, restart Business Availability Center on all servers.
- Note: If Business Availability Center is running on a Windows 64-bit operating system with at least 16 GB of RAM, after installing 8.02 but before starting Business Availability Center, you must run the database configuration utility on all servers and reconnect to the existing databases.
- Note: If you are planning to install a DDM content pack, do not restart Business Availability Center until after the content pack is installed.
- If you do not yet have Business Availability Center 8.00 or 8.01 installed, install 8.00 according to the instructions in the HP Business Availability Center 8.02 Deployment Guide (this is a more updated version of the 8.00/8.01 Deployment Guide). After installing 8.00, do not run the database configuration process or start Business Availability Center until after relevant service packs are installed. After installing Business Availability Center 8.00, install 8.01, and then 8.02 on every Business Availability Center server as per instructions above. After 8.02 is installed, run the database configuration utility or upgrade wizard (depending on whether you are installing 8.x as a new installation or whether you are upgrading from an earlier Business Availability Center version) as per instructions in the Deployment Guide.
- The following note is relevant if you are upgrading from Business Availability Center 7.x: As a result of the upgrade process from Business Availability Center 7.x to HP Business Availability Center 8.00, the results displayed in some views may differ from the results displayed before the upgrade. You can use the Upgrade Information Tool to create a log file listing all such views and the problems in each view. The tool should be run on Business Availability Center 7.x before the upgrade. It details the changes to be anticipated during the upgrade process. The tool is not relevant for versions of Business Availability Center other than 7.x. The tool and instructions for its use are located in the <Business Availability Center 8.02 setup package root directory>\CMDB_Upgrade_Info_Tool directory.
- The following note is relevant if you are working with an external UCMDB architecture and are upgrading to Business Availability Center 8.02 and HP Universal CMDB 8.02 from 7.x or earlier versions: As described in the HP Universal CMDB Deployment Guide, during the HP Universal CMDB upgrade to 8.x, you are directed to perform a procedure that involves invoking a JMX that converts instance views into perspective-based views. If you were already working with an external UCMDB architecture prior to the upgrade, during the Business Availability Center upgrade, all instance views are automatically converted into perspective-based views. As such, it is not necessary to run this procedure again during the HP Universal CMDB upgrade. Doing so can result in corrupted views.
- If you are installing Business Availability Center 8.02 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 8.02 on the Business Availability Center machines and HP Universal CMDB 8.02 on the external UCMDB machine.
- Open the file < Business Availability Center 8.02 setup package root directory>\updated_bac_packages\updated_bac_packages.txt to view a list of the updated packages. The file contains two lists: updated packages from 8.00 to 8.01 (relevant if you have not previously deployed updated 8.01 packages to the external UCMDB server) and updated packages from 8.01 to 8.02.
- 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.
- If relevant, after installation is complete run the Daylight Savings Time update procedure using the updated tzupdater.jar file included with Business Availability Center 8.02. This provides your system with the latest DST definitions. Note that the tzupdater.jar file included with Business Availability Center 8.02 only includes time zone updates for the following countries: Mauritius, Argentina, Cuba, Morocco, Tunisia, Syria, Jordan, Pakistan, Egypt
- 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 HP Business Availability Center 8.02 Deployment Guide.
- Upgrade Limitation: If you have disabled Lightweight Single Sign-On in HP Business Availability Center 7.5x and then upgrade to HP Business Availability Center 8.0x, login to HP Business Availability Center fails. To enable login, you must set the SSO Mode to Disabled in the HP Business Availability Center SSO JMX Console (Topaz:SSO) after upgrading. To do so:
- Access the HP Business Availability Center SSO JMX Console by navigating to the following URL (log in using JMX credentials): http://<Gateway Server>:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=Topaz%3Aservice%3DSSO, where <Gateway Server> is the name of the machine on which HP Business Availability Center Gateway Server is running.
- In the setSingleSignOnMode() MBean, type Disabled in the ParamValue box and click Invoke.
- Upgrade Limitation: During the upgrade to 8.02, 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.
- Upgrade Limitation: If you are upgrading from a 7.0x or 7.5x version of Business Availability Center and are accessing via reverse proxy, you may not be able to log into Business Availability Center. Workaround:
- Install 8.00, 8.01, 8.02, 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.
- Upgrade Limitation: After 8.02 installation, files with the extensions .bff, .xmit, and .savf will not be available for download from the Downloads page in Platform Administration until the IIS is restarted on the Gateway Server.
- If you are upgrading from Business Availability Center 7.5x to 8.02, you may need to manually synchronize certain KPI assignments (for example, if you added KPI assignments in the previous version). If you do not perform manual synchronization on the relevant assignments, existing CIs may have wrong KPIs. You can ascertain whether you need to perform manual synchronization by checking the log files after upgrade. You can use one of the following files, located on the Business Availability Center Data Processing Server:
- HPBAC/log/upgrade/upgrade.wizard.log
- HPBAC/log/EJBContainer/kes.upgrade.log (this is a more detailed log file)
The following message is displayed for the relevant assignments in the upgrade.wizard.log file (a similar message is displayed in the kes.upgrade.log file):
"NOTE: Assignment name=[<assignment name>] id=[<assignment ID>] description=[<assignment description>] of Bundle name=[<assignment bundle name>] was added to new persistency. Please consider a manual synchronization for this assignment."
If you decide that manual synchronization is required, perform the synchronization in the Dashboard Administration KPI Assignments tab.
- Upgrade Note: If you use Problem Isolation On-Demand Monitors and have upgraded from HP Business Availability Center version 8.00 or 8.01 to version 8.02, you must reconnect to the management database. For details on setting database parameters, refer to the HP Business Availability Center Deployment Guide.
- 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, 7.53, 8.00, or 8.01), it is recommended to perform a diff replication on your current system prior to upgrading to 8.02. This will prevent losing data for removal during the full synch. Then, after upgrading to 8.02, 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:
- 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.
- Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.5.1 or 7.52 to 8.02): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter.
- Upgrade HP Business Availability Center from HP Business Availability Center 7.5.1 or 7.52 to 8.00, then to 8.01, and finally to 8.02.
- 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 8.02): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter.
- Upgrade HP Business Availability Center from HP Business Availability Center 7.0x or 7.50 to 8.00, then to 8.01, and finally to 8.02 (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.
- Upgrade Note: This note pertains to reconciliation rules in UCMDB. During the upgrade procedure from a previous version, and once the server is up, you should activate the RemoveMultipleProcesses enrichment rule. Once Calculate TQL Result Count returns zero results, you can deactivate the rule. For details on activating enrichment rules, see the Rule General Attributes Page section in the Enrichment Manager chapter of the Model Management guide.
- Upgrade Note: This note is relevant if you are upgrading SiteScope from a pre-10.00 version 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 HP Business Availability Center 8.02 Deployment Guide.
- To roll back an installation of Business Availability Center 8.02 to Business Availability Center 8.00 or 8.01, follow the instructions below.
- Stop the HP Business Availability Center service on all servers and confirm they are stopped.
- Stop the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers.
- From Control Panel, select Add/Remove Programs > Change or Remove Programs > HP Business Availability Center 8.02. On Windows 2003 Server, select the Show Updates option to ensure that version 8.02 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 8.01 limitations and 8.00 limitations below. Removed limitations are marked with prefix FIXED IN 8.02.
- 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.
- Dashboard: In Dashboard, the OK threshold value for the Availability and Performance KPIs is set as >=100% for Application Sessions CIs. As a result, if availability or performance is any lower than 100%, OK status is immediately breached. In BAC 8.02, the threshold was corrected to >=90%. Important: This fix is only relevant for new BAC installations (installing 8.00, 8.01, and then 8.02). If you are upgrading to BAC 8.02 from an existing 7.5.x/8.x installation, a manual workaround is required. Contact HP Software Support for details.
- Dashboard: If you are upgrading to BAC 8.02 from an existing 8.x installation, the Downtime PNR status image is not available. Workaround: Enter the following URL to perform a manual invocation of the Clean Repositories service: http://<GATEWAY_SERVER>:8080/jmx-console/HtmlAdaptor?action=invokeOpByName&name=Topaz%3Aservice%3Drepositories_manager&methodName=cleanRepositoryTypeDBAndCache&argType=java.lang.String&arg0=0&argType=java.lang.String&arg1=dimensions
- Service Manager/Service Center Integration: If you are integrating with HP ServiceCenter 6.2.6, note the below corrections to the Service Manager Monitor topics in the System Availability Management documentation. These corrections are also available in the System Availability Management Guide in PDF format (SystemAvailabilityManagement.pdf) that is located on the HP Software Manuals site (details here):
- Correction to HP Service Manager Monitor User Interface section, HP Service Manager Web Service Endpoint GUI element description: The URL syntax when integrating with ServiceCenter 6.2.6 is: <protocol>://<SM host>:<SM port>/sc61server/PWS/
- Correction to the HP Service Manager Integration Workflow topic, Create the JAR File section, fourth step, description of 6.2.6 URL syntax:
clocks.wsdl.url=http://<SM host>:<SM port>/sc61server/PWS/Clocks?wsdl
prob.wsdl.url=http://<SM host>:<SM port>/sc61server/PWS/IncidentManagement?wsdl
- Diagnostics Integration: In BAC 8.00, a Location selector was added to the Diagnostics Application KPI. However, the Diagnostics sample does not have a Location parameter, so the KPI is always grey. In BAC 8.02, the Location selector was removed from the Diagnostics Application KPI. As a result, even when working in transaction by location mode, the Application status is calculated according to all locations. Important: This fix is only relevant for new BAC installations (installing 8.00, 8.01, and then 8.02). If you are upgrading to BAC 8.02 from an existing 7.5.x/8.x installation, a manual workaround is required. Contact HP Software Support for details.
- TransactionVision: Exception errors may occur when executing the Export BPI Definitions command. If a BPI action is modified in the Transaction Definition Editor, be sure that no required parameters are removed. If they are, an exception error will occur when the Export BPI Definitions command is executed.
- TransactionVision: Java Agent installation and Setup Module response files generated with version 8.00 cannot be used to perform a silent installation of the 8.01 or 8.02 version of the Java Agent installation and Setup Module. Response files generated with 8.01 will work with 8.02 and later releases.
- TransactionVision: After upgrading TransactionVision from 7.50 to 8.0x, there is no flow map showing in Aggregate Topology or Instance Topology reports. Workaround: After you perform an upgrade install of TransactionVision Analyzer from 7.50 to 8.0x, add the following lines into the <TVISION_HOME>/config/services/Beans.xml file (right before the </BeanFramework> line):
<Module name="TxnUpdateCtx" type="Context">
<!-- This context contains beans that perform transaction updates -->
<!-- Only one bean in the context is called (based on its type) -->
<Module class="com.bristol.tvision.services.analysis.txnupdate.RUMTxnUpdateBean" type="Bean">
<Attribute name="type" value="RUM"/>
</Module>
</Module><Module name="com.bristol.tvision.services.analysis.transactiontopology.TransactionTopologyBeanCtx" type="Context">
<Module class="com.bristol.tvision.services.analysis.transactiontopology.TransactionTopologyWMQBean" type="Bean"/>
<Module class="com.bristol.tvision.services.analysis.transactiontopology.TransactionTopologyJMSBean" type="Bean"/>
<Module class="com.bristol.tvision.services.analysis.transactiontopology.TransactionTopologyServletBean" type="Bean"/>
<Module class="com.bristol.tvision.services.analysis.transactiontopology.TransactionTopologyEJBBean" type="Bean"/>
<Module class="com.bristol.tvision.services.analysis.transactiontopology.TransactionTopologyJDBCBean" type="Bean"/>
</Module>- Business Process Insight/TransactionVision Integration: Business Process Insight-TransactionVision integration is not compatible between patch releases.
If you integrate Business Process Insight 8.0x with TransactionVision 8.0x where the minor versions of Business Process Insight and TransactionVision do not match, and you get an error message that the client version does not match the server version when exporting definitions to Business Process Insight, use the following workaround.
Workaround: To make TransactionVision and Business Process Insight compatible, stop the TransactionVision UI/Job server, copy the following file from the Business Process Insight server machine to the TransactionVision UI/Job Server machine and start the TransactionVision UI/Job server after copying the file.
- Business Process Insight: With Business Availability Center 8.02, if you launch the BPI modeler (from the BPI > Admin > Modeler application), navigate to the Process Editor tab for any process step, and launch the CI Selector, the Business Availability Center user interface displays an error message such as, "An internal error has occurred." Workaround: Select the Site Map menu in the Business Availability Center user interface to restore the Business Availability Center user interface to its normal behavior--the errors are no longer encountered. Contact HP Software Support for details on when a fix to this issue will be available.
- Business Process Insight: Implemented a way to link sub-processes to parent processes.
A minimal solution has been implemented for the 8.02 release, which will be released in the contrib directory of the installed Business Process Insight server. See the readme.htm file in the contrib directory for instructions.
- Business Process Insight: The Process Simulator is a contributed component that is a test tool for Business Process Insight, which is placed in the contrib directory of the installed BPI server. For details on using the Process Simulator, see the HP Business Process Insight Using the HP BPI Flow Simulator guide (flowsim.pdf), also located in the contrib directory.
- Business Process Insight: If you specify a Business Availability Center user name other than admin during the Business Process Insight installation it may incorrectly report: The supplied user name or password is invalid. You may also see this error if the Business Availability Center admin password has been changed from the default.
Workaround: Choose the continue option to complete the installation. The Process Repository database details need to be entered manually but the installation should complete successfully and Business Process Insight should operate without problems as long as the name and password that you entered are valid credentials for the Business Availability Center server.
- Business Process Insight: The processing and display of Business Process Insight monitor instance values is only done to a precision of 6 or 7 digits, and not to the precision of 15 digits used for process values. This can mean that large integer values may not show their exact value. For example, $123,000,000 could show as $123,000,064.
- Business Process Insight: Business Process Insight Landing pages are not displaying monitor values and statistics to double precision.
- Business Process Insight: Business Process Insight instance pages fail when first accessed in a multi-domain LWSSO configuration.
Workaround: Access the Process Repository Explorer under the Business Process Insight Admin area in Business Availability Center (Admin->Business Process Insight->Process Repository Explorer). After doing this, the process instance pages can be accessed normally.
- Business Process Insight: If you integrate Business Process Insight 8.0x with Business Availability Center 8.0x where the minor versions of Business Availability Center and Business Process Insight do not match, and when launching the Business Process Insight Modeler you get an error message that the Modeler version does not match the repository version, use the following workaround.
Workaround: To make Business Availability Center and Business Process Insight compatible, stop the Business Availability Center Gateway servers, copy the following files from the Business Process Insight server machine to the Business Availability Center Gateway machines and start the Business Availability Center Gateway server after copying the files.
- Location of files on Business Process Insight server:
<BPI-install-dir>\nonOV\jakarta-tomcat-5.0.19\webapps\hpbpi-bpd\WEB-INF\lib\bia-flowviewer.jar
<BPI-install-dir>\msg\bia\model_repository.properties
- Destination on Business Availability Center Gateway server:
<BAC-install-dir>\AppServer\webapps\bpi.war\WEB-INF\lib\bia-flowviewer.jar
<BAC-install-dir>\AppServer\webapps\bpi.war\jsps\bpi\admin\modeler\lib\bia-flowviewer.jar
<BAC-install-dir>\AppServer\resources\model_repository.properties
<BAC-install-dir>\conf\bpi_process_repository\model_repository.properties
- HP Business Availability Center bug fixes - see table below for details:
UCMDB Version Content and Limitations
Universal CMDB
- 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, refer to the "CI Lifecycle and Aging Mechanism" chapter in the Model Management guide.
- The UML Tool now enables the export of documentation about the CITs and their attributes in the class model. The tool can export to files with the XMI format.
Federation and Replication
- Get full layout plug-in. The Generic Database Adapter default implementation now includes a get full layout plug-in in full synchronization, for replication. For more information, refer to the "Generic Database Adapter" chapter in the Model Management guide.
- Using Inline SQL Statements Instead of Table Names. For details on this functionality, refer to the "Generic Database Adapter" chapter in the Model Management guide.
Security Manager
- You can now grant permissions to users for the following general actions:
- CI Search. Grants permissions to users to access the CI Selector search option. Only users with these permissions can search for CIs.
- Get Related. Grants permissions to users to view data of related CIs. Only users with these permissions can view related CIs.
- Data Modifier. Grants permissions to users to change CIs in ITU. Only users with these permissions or users with edit rights on a view (as currently) can modify data. Furthermore, users with these permissions can delete CIs from the CI Instances grid.
- Users can access View Manager and Modeling Studio only if they are given permissions to do so.
- A user without any permissions or roles is no longer able to log in to Business Availability Center.
- Security Roles
- Security Upgrade
- You do not need to perform any special steps to upgrade security from version 8.00 and 8.01 to 8.02.
- All roles are granted rights for the Get Related and CI Search actions.
- All roles are granted access rights to View Manager and the Modeling Studio.
- After you upgrade to version 8.02, users can continue working as usual. All current permissions are maintained.
- Security Fixes:
Discovery and Dependency Mapping
- Discovery Analyzer. For details on using the DDM Analyzer, refer to the Discovery and Dependency Mapping guide.
- Discovery Analyzer. To prevent an error being thrown during the tool run, before using the Analyzer, verify that the following line exists in the DiscoveryProbe.properties file:
# Fix used to run DiscoveryAnalyzer from Eclipse (should be true if running from eclipse else should be false)
appilog.agent.local.discoveryAnalyzerFromEclipse = trueIntegration Documentation
Defect Fixes
Updated Components
The following updated components are included with Business Availability Center 8.02 (they must be downloaded separately from the software patches download site):
- Real User Monitor Probe 8.02 (Windows 2003, Linux)
For instructions on upgrading the Real User Monitor probe, see the Upgrade Components chapter in the HP Business Availability Center Deployment Guide.
- Real User Monitor Engine 8.02 (Windows)
For instructions on upgrading the Real User Monitor engine, see the Upgrade Components chapter in the HP Business Availability Center Deployment Guide.
- Business Process Monitor 8.02 (Windows, Solaris)
For instructions on installing/upgrading Business Process Monitor, see the Business Process Monitor Administration Guide.
Note: To take advantage of all the functionality provided by Business Process Monitor 8.02, you must install VuGen 9.50 as well as the VuGen 9.50 Patch for BPM, HPVUGen9.5PatchForBPM.exe (restart VuGen after applying the patch). Both are available from the software patches download site.
- Virtual User Generator (VuGen) 9.50 (Windows)
To install VuGen, double-click VUGen.exe and follow the on-screen instructions. After installing VuGen, install the HPVUGen9.5PatchForBPM.exe, which contains a critical fix required for creating SOA Scripts.
- Discovery Probe 8.02 (Windows)
To install the Discovery Probe, first stop any existing Discovery Probe instances (if you have a previous version running), then uninstall the existing Discovery Probe via Start > Programs > UCMDB or HP DDM > Uninstall UCMDB Discovery Probe or Uninstall HP DDM Probe. Then, run HPDiscoveryProbe_v802_win32.exe. Finally, start the 8.02 Discovery Probe.
- Business Process Insight - the Business Process Insight Server has been updated with bug fixes.
For installation instructions, see the Business Process Insight Deployment Guide.
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 8.02 are shown.
√=supported, X=not supported
Supported Environments
Business Availability Center Component Support Matrixes
Business Process Monitor − Business Availability Center Support Matrix
For each BPM version, the latest supported VuGen version is mentioned. All previous versions of VuGen are supported as well.
Business Process Monitor/QuickTest Professional (QTP) Support Matrix
SiteScope Support Matrix
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
Real User Monitor Support Matrix
Note: Real User Monitor 7.01 (probe and engine) works only with Business Availability Center 7.01.
DDM Discovery Probe Support Matrix
Note: Discovery Probe 7.51 works only with Business Availability Center 7.51.Discovery Probe 7.01 works only with Business Availability Center 7.01.
Business Availability Center/Diagnostics Integration Matrix
(*) Note: Business Availability Center for SOA not supported
Business Availability Center/Service Manager & ServiceCenter Integration Matrix
Note: For integration with Service Manager to function properly, additional setup is required in both Business Availability Center and Service Manager. See the Business Availability Center documentation for details.
Business Availability Center/HP Operations Manager Integration Matrix
HP Business Availability Center 8.01
Readme
Software version: 8.01 / March 2009
This file provides information about HP Business Availability Center 8.01 and 8.00 (for 8.00 information, click here).
Business Availability Center 8.01 Files
Version Content and Limitations
Updated HP Business Availability Center Support Matrixes
Business Availability Center 8.01 Files
Business Availability Center 8.01 includes the following files:
Business Availability Center 8.01 setup file
Component setup files
Note: You need to separately download new component setup files.
Documentation files
Additional files
Installation Prerequisites
Business Availability Center 8.01 must be installed on top of Business Availability Center 8.00.
Installation
- If you have Business Availability Center 8.00 installed, stop Business Availability Center on all servers and make sure it is stopped before installing the service pack. Install the 8.01 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 8.00 installed, install it according to the instructions in the HP Business Availability Center 8.01 Deployment Guide (this is a more updated version of the 8.00 Deployment Guide). After installing 8.00, do not run the database configuration process or start Business Availability Center until after 8.01 is installed. Then install Business Availability Center 8.01 on every Business Availability Center server as per above instructions. After 8.01 is installed, run the database configuration utility or upgrade wizard (depending on whether you are installing 8.x as a new installation or whether you are upgrading from an earlier Business Availability Center version) as per instructions in the Deployment Guide.
- If you are installing Business Availability Center 8.01 on top of 8.00 and are working with an external UCMDB architecture, you must manually deploy the 8.01 BAC packages to the UCMDB server. For details, click here.
- The tzupdater.jar file included with Business Availability Center 8.01 is the same as the one included with Business Availability Center 8.00. If you did not run the Daylight Savings Time update procedure using the tzupdater.jar file during 8.00 installation, perform the below procedure after 8.01 installation is complete to update your system with the latest DST definitions.
- Copy the tzupdater.jar file to the <HP Business Availability Center root directory>\bin directory.
- Stop HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Disable Business Availability Center).
- Open a Command Prompt window (DOS shell) and change the directory to <HP Business Availability Center root directory>\bin.
- Run the following command to set JAVA_HOME: set JAVA_HOME=%TOPAZ_HOME%\jre
- Run the following command to install the patch: %JAVA_HOME%\bin\java -jar tzupdater.jar -u -bc
- Start HP Business Availability Center (Start > Programs > HP Business Availability Center > Administration > Enable Business Availability Center).
For additional details on updating Daylight Savings Time definitions, including the procedure for using the tzupdater.jar file on Business Process Monitor instances, see the HP Business Availability Center 8.01 Deployment Guide.
- Upgrade Limitation: If you have disabled Lightweight Single Sign-On in HP Business Availability Center 7.5x and then upgrade to HP Business Availability Center 8.0x, login to HP Business Availability Center fails. To enable login, you must set the SSO Mode to Disabled in the HP Business Availability Center SSO JMX Console (Topaz:SSO) after upgrading. To do so:
- Access the HP Business Availability Center SSO JMX Console by navigating to the following URL (log in using JMX credentials): http://<Gateway Server>:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=Topaz%3Aservice%3DSSO, where <Gateway Server> is the name of the machine on which HP Business Availability Center Gateway Server is running.
- In the setSingleSignOnMode() MBean, type Disabled in the ParamValue box and click Invoke.
- FIXED IN 8.02: Upgrade Limitation: Upgrade wizard fails to start on Gateway Server running on a Solaris OS due to the following error:
(root@mysolaris) HPBAC/bin>./upgrade_wizard_run.sh
upgrade wizard run
Failed to determine server type.
./upgrade_wizard_run.sh: cannot return when not in function
Workaround: Edit <HP Business Availability Center Gateway Server root directory>\conf\TopazSetup.ini and under the [INSTALLED_SERVERS] section add the following lines:
Core_Server=1
Centers_Server=1
For example:
[INSTALLED_SERVERS]
Gateway=1
Core_Server=1
Centers_Server=1
- Upgrade Limitation: During the upgrade to 8.01, 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.
- Upgrade Limitation: After 8.01 installation, files with the extensions .bff, .xmit, and .savf will not be available for download from the Downloads page in Platform Administration until the IIS is restarted on the Gateway Server.
- Upgrade Note: If you use Problem Isolation On-Demand Monitors and have upgraded from HP Business Availability Center version 8.00 to version 8.01, you must reconnect to the management database. If you are installing 8.02 directly after 8.01, perform reconnect after installing 8.02. For details on setting database parameters, refer to the HP Business Availability Center Deployment Guide.
- 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, 7.53, or 8.00), it is recommended to perform a diff replication on your current system prior to upgrading to 8.01. This will prevent losing data for removal during the full synch. Then, after upgrading to 8.01, 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:
- 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.
- Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability Center 7.5.1 or 7.52 to 8.01): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter.
- Upgrade HP Business Availability Center from HP Business Availability Center 7.5.1 or 7.52 to 8.00, then to 8.01.
- 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 8.01): If you created proprietary adapters based on the Generic DB Adapter, you must perform the below procedure for each such adapter.
- Upgrade HP Business Availability Center from HP Business Availability Center 7.0x or 7.50 to 8.00, then to 8.01 (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.
- Upgrade Note: This note pertains to reconciliation rules in UCMDB. During the upgrade procedure from a previous version, and once the server is up, you should activate the RemoveMultipleProcesses enrichment rule. Once Calculate TQL Result Count returns zero results, you can deactivate the rule. For details on activating enrichment rules, see the Rule General Attributes Page section in the Enrichment Manager chapter of the Model Management guide.
- Upgrade Note: This note is relevant if you are upgrading SiteScope from a pre-10.00 version 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 HP Business Availability Center 8.01 Deployment Guide.
- To roll back an installation of Business Availability Center 8.01 to Business Availability Center 8.00, 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 8.01. On Windows 2003 Server, select the Show Updates option to ensure that version 8.01 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 8.00 limitations below. Removed limitations are marked with prefix FIXED IN 8.01 or FIXED IN 8.02.
- 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.
- Authentication: When HP Business Availability Center is installed with an Oracle Database and User Synchronization enabled with an LDAP Active Directory server, ensure that you login to HP Business Availability Center with the correct-case UID (uppercase or lowercase), as configured on the LDAP server. This is because while the Oracle Database is case-sensitive, the LDAP Active Directory is not case sensitive, and logging in with an incorrect case UID can create undesirable results.
For example, if a user called testuser exists on the LDAP Active Directory server and logs into HP Business Availability Center, he is automatically created as HP Business Availability Center user testuser, who can be assigned permissions in the HP Business Availability Center User Management interface. If you then login to HP Business Availability Center as Testuser, the LDAP Active Directory server sends an acknowledgement that the user exists (because Active Directory is not case sensitive) and he is allowed entry to HP Business Availability Center. However, since the Oracle Database does not identify this user as testuser (because the Oracle Database is case sensitive), the user Testuser is treated as a new user, without the permissions that were assigned to testuser.
- Universal CMDB: When selecting First Service View in Universal CMDB View Manager, the following error is displayed: "Selected Configuration Item could not be loaded." Workaround: Go to JMX Console > UCMDB > Service=Views Services and invoke upgradeOldInstanceView() with parameters CustomerID=1 and bacViewName=First Service View.
- SiteScope: In SiteScope, Solution Templates can only be deployed from the template tree.
- TransactionVision: Custom correlation based on lookup key and time range match up available:
In the area of event correlation, there are certain scenarios where perfect correlation data is not available. While there may be enough correlation information--based on either standard technology context or customer specific business data--to triage the events and limit the matching event candidates to a minimum set, additional factors need to be considered to complete the correlation process and result in one-to-one event relationship.
One such factor is event time stamps. In certain situations, TransactionVision can correlate specific event candidates by considering the respective event execution time. One example: two events A and B representing EJB X and Y method calls respectively are reported to TransactionVision, with EJB X method invoking the EJB Y method. In this case TransactionVision can reasonably assume that the two events' exit timestamps are very close based on the call latency nature. Thus TransactionVision can deduce that by truncating the respective event time stamps to a precision consistent with the expected latency, the two events would have the same truncated timestamp, and this can in turn be considered as a matching key in a lookup key based correlation algorithm.
TransactionVision provides a correlation component that supports this type of time based correlation enhancement. One can consider this as a correlation algorithm based on a mix of time and payload/technology specific data keys. Contact HP Software Support for more information about using this component.
- TransactionVision: Java Agent installation and Setup Module response files generated with version 8.00 cannot be used to perform a silent installation of the 8.01 Java Agent. Generate new response files to be used with the 8.01 version.
- TransactionVision: On Solaris hosts, the TransactionVision Analyzer or UI/Job Server may fail to start upon installation. This occurs when either of these components is installed by a root user and Business Availability Center was started under another user/group on the same host. Therefore the Business Availability Center nanny process does not have permission to execute the TransactionVision components.
Workaround: Change the user/group of the /opt/HP/TransactionVision directory to the same as that being used by Business Availability Center by using the following commands: chown -R <bacuser> /opt/HP/TransactionVision and chgrp -R <bacgroup> /opt/HP/TransactionVision (where <bacuser> and <bacgroup> are the user/group of the Business Availability Center installation directory). Alternatively, you can grant write permissions for all users/groups to the TransactionVision directory by using the command: chmod -R a+w /opt/HP/TransactionVision, but this alternative would open up read/write access for the TransactionVision installation files to all users and may pose a security risk.
- TransactionVision: Out-of-memory errors can occur in a .NET application being monitored. This occurs when the .NET Agent is configured in "TV" mode to send events to the TransactionVision Analyzer using SonicMQ as the messaging middleware provider and the SonicMQ Broker is not configured with security.
Work Around : To avoid this problem, enable security in the SonicMQ Broker by requiring authentication. Specify the user id\password credentials in the <sensor_install_dir>/etc/probe_config.xml file. Information about implementing security in SonicMQ Broker is described in the Progress SonicMQ Deployment Guide. This manual is available on any host on which the Analyzer is installed; see <analyzer_install_directory>\Sonic\Docs7.5\books\mq.deploy.pdf.
- TransactionVision: Errors can occur when upgrading a release 5.0.0, 7.50, or 8.00 Analyzer with custom beans to 8.0x. The errors that occur are as follows:
TransactionVision Error(FrameworkInitError): Failed to initialize Analyzer framework.
TransactionVision Error(CouldNotLoadBeanClass): Bean class 'XXXXX' specified in beans config file could not be loaded. Please see error log for details.
- Workaround for 5.0.0 or 7.50 upgrade: On Windows, copy the value of the service_additional_classpath property from <TVISION_HOME>\config\services\Analyzer.properties and add the following line to the <TVISION_HOME>\bin\SetupEnv.bat file:
set ANALYZER_ADDITIONAL_CLASSPATH=<service_additional_classpath_value>
In addition, add the following line to the SetupEnv.bat file:
set CLASSPATH=%CLASSPATH%;%ANALYZER_ADDITIONAL_CLASSPATH%
On UNIX, copy and paste the similar entry from the backup SetupEnv.sh file to the new one, and export the updated CLASSPATH.
- Workaround for 8.0x upgrade: On Windows, copy the "set ANALYZER_ADDITIONAL_CLASSPATH=...." line from the saved <TVISION_HOME>\bin\SetupEnv.bat.bak file, and paste it in the migrated <TVISION_HOME>\bin\SetupEnv.bat file. In addition, add the following line to the SetupEnv.bat file:
set CLASSPATH=%CLASSPATH%;%ANALYZER_ADDITIONAL_CLASSPATH%
On UNIX, copy and paste the similar entry from the backup SetupEnv.sh file to the new one, and export the updated CLASSPATH.
- TransactionVision: A WebSphere MQ Agent monitoring WebSphere MQ 7.0 using the API Exit Sensor may collect undesired MQ Explorer events and fill up the event queue.
Workaround: Add the following lines to the end of the <TVISION_HOME>/exit_sensor.deny file:
*\WebSphere MQ\java\jre\bin\javaw
*/mqm/java/jre/bin/javaw- FIXED IN 8.02: Business Process Insight: Incorrect backlogs result when monitor instances complete before they start.
- FIXED IN 8.02: Business Process Insight: In Business Availability Center versions 8.00 and 8.01, sometimes the annotations on the Business Availability Center Dashboard flow map tab's process diagram read No Data even though the data samples were being sent to Business Availability Center from Business Process Insight.
Workaround: Edit the \HPBAC\conf\settings\bpiSettings.xml infrastructure settings file and change the setting with the name attribute: settings.bpi.profile.sample.multiple to have a displayInUI attribute value of true and a value attribute value of 10. Restart Business Availability Center once these changes have been made. After Business Availability Center has been restarted the Multiple of sample periods queried property can be modified in the Business Process Insight Infrastructure Settings Profile Database Data Sample Retrieval Settings section.
- Business Process Insight: If you specify a Business Availability Center username other than admin during the BPI installation it may incorrectly report "The supplied user name or password is invalid." You may also see this error if the Business Availability Center admin password has been changed from the default. If you see this, you should choose the option to continue with the installation. The Process Repository database details will need to be entered manually but the installation should complete successfully and BPI should operate without problems as long as the name and password that you entered are valid credentials for the Business Availability Center server.
- Business Process Insight: Business Process Insight cannot use MS SQL named instances, such as <hostname>\<instance>, to specify the database.
Workaround: During the installation of Business Process Insight, identify the host and specific port on which the named instance is running and enter the following during the Business Process Insight installation:
MS SQL Server hostname: enter the host
MS SQL Server port: enter the specific instance port number
For example: Instead of entering (for MS SQL Server hostname) myhost\fred and (for MS SQL Server port) 1433, you find that the fred instance is running on port 1244 and use:
MS SQL Server hostname: myHost
MS SQL Server port: 1244
Alternatively, you can use forward slashes (/) when specifying the named instance. For example, instead of entering (for MS SQL Server hostname) myhost\fred you can use:
MS SQL Server hostname: myHost/fred
MS SQL Server port: 1244
- FIXED IN 8.02: 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.
- I18n: When using a language that reads right to left (for example Arabic or Hebrew), exporting a report to PDF format does not work properly. The letters appear backwards in the PDF. Viewing the report in Business Availability Center works properly.
- HP Business Availability Center bug fixes - see table below for details:
Updated Components
The following updated components are included with Business Availability Center 8.01:
For instructions on upgrading the Real User Monitor probe, see the Upgrade Components chapter in the HP Business Availability Center Deployment Guide.
For instructions on upgrading the Real User Monitor engine, see the Upgrade Components chapter in the HP Business Availability Center Deployment Guide.
- Real User Monitor now supports monitoring of Oracle applications that use the Oracle NCA protocol over HTTP. (Note: Oracle applications that use the Oracle NCA protocol on a direct connection are not monitored.)
- 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).
- The issue of not being able to start Web traffic discovery (Real User Monitor Web console > Tools > Traffic Discovery) when the Real User Monitor Web console is configured for SSL has been fixed.
- 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.
- Discovery Probe 8.01 (Windows)
To install the Discovery Probe, first stop any existing Discovery Probe instances (if you have a previous version running), then uninstall the existing Discovery Probe via Start > Programs > UCMDB or HP DDM > Uninstall UCMDB Discovery Probe or Uninstall HP DDM Probe. Then, run HPDiscoveryProbe_v80_sp_win32.exe. Finally, start the 8.01 Discovery Probe.
For installation instructions, see the TransactionVision Deployment Guide.
For installation instructions, see the Business Process Insight Deployment Guide.
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 8.01 are shown.
√=supported, X=not supported
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.
SiteScope Support Matrix
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
Real User Monitor Support Matrix
Note: Real User Monitor 7.01 (probe and engine) works only with Business Availability Center 7.01.
DDM Discovery Probe Support Matrix
Note: Discovery Probe 7.51 works only with Business Availability Center 7.51.Discovery Probe 7.01 works only with Business Availability Center 7.01.
Business Availability Center/Diagnostics Integration Matrix
Integration Matrix
HP Diagnostics 8.01
HP Diagnostics 8.00
HP Diagnostics 7.50
HP Diagnostics 7.0
BAC 8.01
√
√
√
X
BAC 8.00
√
√
√
X
BAC 7.50
√
√
√
X
BAC 7.0
√*
√*
√*
√
(*) Note: Business Availability Center for SOA not supported
Business Availability Center/ServiceCenter/Service Manager Integration Matrix
Note: For integration with Service Manager to function properly, additional setup is required in both Business Availability Center and Service Manager. See the Business Availability Center documentation for details.
HP Business Availability Center 8.00
Readme
Software version: 8.00 / January 2009
This file provides information about HP Business Availability Center 8.00.
HP Business Availability Center Support Matrixes
Documentation Updates
The first page of this release notes document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals
To retrieve a document, select the:
1. Product name.2. Version list.3. Operating System.4. Preferred Language.5. Document title.6. Click Open or Download.You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.
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
General, Deployment, and Upgrade
- See the upgrade notes in this section for important upgrade information regarding Universal CMDB (UCMDB).
- Upgrading to version 8.00 on a Solaris operating system is not yet supported and will be delivered after the general release of 8.00. Contact HP software support for details on when this will be available.
- 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.
- If you are using Solaris version 9.0, run HP Business Availability Center using the Sun Java System Web Server and not Apache. You may encounter problems running HP Business Availability Center on Solaris version 9.0 with Apache. (The Apache web server installed during HP Business Availability Center server installation has been adapted for use when running on Solaris version 10.0.)
- After upgrading from HP Business Availability Center 7.5x to HP Business Availability Center 8.0x, any Favorite Filters for Trend Reports configured in HP Business Availability Center 7.5x cannot be viewed in HP Business Availability Center 8.0x. Once you have completed the upgrade, you must recreate your Trend Report Favorite Filters in HP Business Availability Center 8.0x.
- Favorite filters created for CI Status Alert and SLA Status Alert reports in previous versions are not upgraded and will not work in Business Availability Center 8.0. You must recreate the favorite filters.
- If you cleared any of the Include in View and Include in CI Status options for the KPIs of an instance view in Dashboard > Admin > KPIs > KPI Selection, before upgrading to 8.00, any customization of the Zoom feature in Dashboard > Admin > Geographical Map is not upgraded, the Zoom feature is reset, and the Include in View and Include in CI Status options are reset to be selected for all KPIs in the instance view. You must clear the appropriate Include in View and Include in CI Status options for the KPIs in the view and customize the Geographical Map Zoom feature for the view after the upgrade.
- If the BPI Modeler fails to deploy business processes and reports CMDB synchronization error you may need to manually remove business processes and related CIs (steps and all BPI monitors) from the CMDB that were created by BPI 2.20 on Business Availability Center 6.x (from 6.8) or 7.0. Business Availability Center 8.00 (and Business Availability Center 7.5x) do not support upgrade of business processes created in the CMDB either manually or by BPI 2.20. Any business processes created either manually or by BPI on a Business Availability Center 6.x (from 6.8) or 7.0. system should be removed, and the Business.zip UCMDB package redeployed, before business processes can be deployed on Business Availability Center 8.00 from the BPI Modeler.
- When viewing Business Availability Center in Internet Explorer 7.0, it is recommended to disable the address bar to avoid a vertical scroll bar appearing on some pages. To disable the address bar in Internet Explorer 7.0, select Tools > Internet Options > Security tab > Internet icon > Custom Level and enable the Allow websites to open windows without address or status bars option.
- An Internet Explorer exception error message is thrown inside Business Availability Center pages (usually on login page), indicating Operation aborted. To resolve this issue, remove the Skype add-ons on your system. For further details, see http://support.microsoft.com/default.aspx/kb/927917
- After performing an upgrade, the tooltips of cloned and overridden KPIs are not updated with the colors used in the new version. The new colors can be applied by cloning or overriding the KPI again, and redefining the custom KPI's fields.
- The following configuration is required if a SOAP adapter is used for replication via reverse proxy into a secure (hardened) HP Business Availability Center server architecture:
Requests for /axis2/* on the Reverse Proxy Server should be served by the following URL: http://<HP Business Availability Center GATEWAY server>/axis2/*
- 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: WAITING FOR ANSWER FROM YISRAEL
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 8.00 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.
- FIXED IN 8.01: If while running the upgrade wizard, the step for upgrading the CMDB fails, this could be due to invalid business view enrichments. Perform the following procedure in the JMX console to determine whether there are invalid enrichments and to remove them from the CMDB.
- Open the JMX console on the Data Processing Server machine (http://<Data Processing Server name>:8080/jmx-console/).
- Locate the service=CMDB Dal Services JMX and invoke the getCmdbVersion() method. If the version of the BusinessViewEnrichmentsUpgrader.PackageManager upgrader is 8.0.0.0, skip the rest of this procedure as this is not the reason for the failure in the upgrade wizard. Refer to the HP Business Availability Center Deployment Guide for troubleshooting upgrade CMDB issues. If the version is not 8.0.0.0 or blank, continue with the procedure.
- Locate the service=CMDB Business View Enrichment Services JMX and invoke the retrieveAllEnrichmentNames() method. Save the results.
- Locate the service=MAM Views Services JMX and invoke the getAllViewsNamesWithTqlNames() method. Search for views with the same names as the business view enrichments saved in step 3 and retrieve their TQL names from the result.
- Locate the service=CMDB Tql Services JMX and invoke the retrieveTqlNames() method. Search for the TQL names retrieved in step 4.
- If there are TQLs missing, the corresponding business view enrichments are invalid and must be removed. Remove the invalid business view enrichments as follows:
- Restart the Data Processing Server machine.
My BSM
- The Topology Map portlet has been discontinued, and is no longer available from Dashboard or My BSM. To view a topological perspective of CIs, select Applications > Universal CMDB > Topology View.
- 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. For example Dashboard portlets have their own height parameter in filter settings.
- When viewing EMS events in My BSM, the Clear Event option on the context menu does not work. If required, clear the event from Dashboard.
- In My BSM, 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
- Business Availability Center 8.00 includes Dashboard Ticker 7.50. Dashboard Ticker 7.50 is compatible with Business Availability Center 8.00. Dashboard Ticker is being discontinued as of the next major Business Availability Center release and is being replaced by the Dashboard Widget, already available in Business Availability Center 8.00.
- Some KPIs that should not be propagated to parent CIs are automatically propagated for CIs in hierarchies whose links were created by adapters or DNode.
- The Topology Map portlet has been discontinued, and is no longer available from Dashboard or My BSM. To view a topological perspective of CIs, select Applications > Universal CMDB > Topology View.
- 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.
- FIXED IN 8.01: All HP Business Availability Center perspectives include all KPIs (including non-relevant KPIs). The problem can be seen, for example, when creating a model that includes end-user CIs and SiteScope CIs. You then generate a view from the model by applying the End User Monitors perspective; the view displays End User CIs without the SiteScope CIs. In Dashboard, the view displays all the KPIs of the end user CIs as well as those of the SiteScope CIs. Workaround: Access the view in Dashboard > Admin and exclude the non-relevant KPIs from the relevant views.
- 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
- Business Availability Center 8.00 is being released with Business Process Monitor 7.52.
- 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 TCP-based WebTrace (default) 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.
- When Business Availability Center is working with SSL and requires client-side certificate, Real User Monitor session replay will not work
System Availability Management
- If a SiteScope is restarted while being accessed in System Availability Management Administration, you may receive an error and have to renavigate to the SiteScope to properly access the SiteScope server.
- If you are copying from a SiteScope version 10.00 to another SiteScope version 10.00 using the copy/paste functionality in System Availability Management Administration, there may be a delay of up to a minute until the pasted object appears in the target SiteScope. This is because the monitor tree in the new SiteScope user interface refreshes by default five seconds after a paste operation completes. If the paste operation takes longer than 5 seconds, it will miss this automatic refresh and the pasted objects appear only after the regularly scheduled refresh (by default 60 seconds).
- When creating a Technology Integration monitor for integrating measurements into HP Business Availability Center (by selecting Measurements as the Sample type in the Field Mapping area of the monitor properties), SiteScope reports system topology data for the monitor to HP Business Availability Center. This is the standard host topology SiteScope reports to HP Business Availability Center. This cannot be changed by adding a script in the Topology Settings area. If you add a topology script, the script will fail.
- 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.
TransactionVision
- The TransactionVision Analyzer is installed under /opt/HP/TransactionVision on Solaris and RedHat Enterprise Linux, and under /usr/lpp/HP/TransactionVision on AIX. While it is not possible to change the installation path, it is possible to create soft-links to ensure that the product files are placed on a drive or partition with available space. Under normal circumstances, customers may create a soft-link from /opt/HP/TransactionVision or /usr/lpp/HP/TransactionVision to a new location prior to running the tvinstall_800_unix.sh installation script. However, due to a limitation in the SonicMQ installation with respect to soft-links, the SonicMQ files must be installed under the default /opt/HP/TransactionVision/Sonic or /usr/lpp/HP/TransactionVision/Sonic directory. If space is a concern, customers may still create soft-links for other higher capacity directories (such as jre, jre64, java, docs, and logs) under the TransactionVision installation directory.
- On AIX systems, after the Java Agent installation, the following message will appear:
The Installation Wizard has successfully installed HP Diagnostics/TransactionVision Agent for Java. Choose next to continue the wizard.
However, on some systems, the following warning is also generated: o null.
In this case, the installation has succeeded and the message can be ignored.
- If your HP TransactionVision UI URL setting is configured using https:// in HP Business Availability Center Infrastructure Settings Manager, you must also access HP Business Availability Center using https://. Logging into HP Business Availability Center using http:// in this case would produce "mixed mode content" errors on each page.
- When starting HP Business Availability Center on Solaris systems using the "run_topaz start" command, "Bad String" errors may be seen if the LANG environment variable is not set properly. These errors can be eliminated by setting LANG to the proper locale prior to starting BAC. For example, run the command "export LANG=en_US.UTF-8" to set LANG for U.S. English.
- FIXED IN 8.01: Basic Authentication is not supported when using a TransactionVision UI/Job Server with a BAC Gateway server.
- TransactionVision does not currently support IDM-SSO environments.
- If transaction class definitions are imported from a TransactionDefinition.xml file that does not have a dbschema tag defined, they will have an invalid schema assignment. In this case, classes need to be manually assigned to specific schemas in the TransactionVision Transaction Definition. This applies to the upgrade scenario as well. If class definitions are migrated from an earlier version of TransactionVision, make sure to manually assign those classes to one or more of your project schemas.
- FIXED IN 8.01: If the TransactionVision UI/Job Server is switched to point to a different Business Availability Center server or one that had its CMDB re-initialized, applications may not be associated with their respective transactions in the top dashboard view. Re-syncing the CMDB does not fix this problem since CMDB updates only affect business transaction classes and not system model information. One solution is to drop and re-create the project schema. Another solution is to stop the TransactionVision UI/Job Server and execute the following SQL after logging into the TransactionVision database:
update <project_name>.SYS_MDL_OBJECT set CMDB_ID=null
update project_name>.SYS_MDL_OBJECT_RELATION set CMDB_ID=null;
commit;
After executing these SQL commands, restart the TransactionVision UI/Job Server and ensure that the CMDB population job is running.
- FIXED IN 8.01: In this TransactionVision release, SiteScope Configuration Item status is not shown in the Aggregated Topology Flowmap.
- Customers who plan to enable the TransactionVision IMS sensor on z/OS should ensure that they are not already using the IMS OTMA Input/Output exit (DFSYIOE0) for some other non-TransactionVision purpose before proceeding with the IMS sensor configuration. If DFSYIOE0 is already being used for customer internal purposes or by another vendor product, please contact TransactionVision customer support for detailed instructions on how to modify DFSYIOE0 source code to invoke the TransactionVision IMS sensor (SLMYIOE0).
- Starting with z/OS version 1.9, the default setting for system parmlib DIAGnn member statement VSM ALLOWUSERKEYCSA has changed to "NO." This parameter disallows User Key CSA storage for security reasons. In order for TransactionVision 8.00 Sensors to execute successfully under z/OS, the VSM ALLOWUSERKEYCSA parameter value must be set to "YES."
- When using the Diagnostics/TransactionVision Agent to monitor WebLogic on Linux, the following error may be seen due to a problem with the version of the JVM shipped with that version of WebLogic, which causes the server to not start:
<Dec 3, 2008 5:41:17 PM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.t3.srvr.SubsystemRequest.action(SubsystemRequest.java:79)
at weblogic.t3.srvr.SubsystemRequest.start(SubsystemRequest.java:51)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:372)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)
To work around this problem, the following steps should be performed:
1. Edit the all-in-one-rule.xml file under the directory MercuryDiagnostics/JavaAgent/TransactionVisionAgent/config/sensor/instrumentDef and remove the following section:
<ClassName name="weblogic.management.configuration.DomainMBeanImpl">
<Action name="ForwardMethodCall">
<SensorFlagName name="com.bristol.tvision.sensor.CheckSensor.servletSensorInstalled"/>
<SensorClass name="com.bristol.tvision.sensor.servlet.ServletSensor"/>
<SensorMethodPrefix name="DomainMBeanImpl_"/>
<MethodSignature name="void setName(java.lang.String)"/>
</Action>
</ClassName>
2.Edit the TV.properties file under MercuryDiagnostics/JavaAgent/DiagnosticsAgent/etc directory to add the following at the end of the tvProperties line.
; com.hp.j2ee.domain.name=your_weblogic_domain_name
Note that the WebLogic domain name is usually the directory containing your server.
3. Restart your WebLogic server.
Syntax
nanny -s <hostname> -p <port> <cmd>
Options
- FIXED IN 8.01: The Aggregated Topology page may incorrectly show a blank table. Click the Generate button to populate this page correctly.
- FIXED IN 8.01: Tooltips may flicker in the Flowmap, Aggregated Topology, and Instance Topology. This occurs if the tooltip is too close to the bottom of the screen. If you experience this, you can either slowly move the cursor off the tooltip or move the line or icon higher up in the topology so that the tooltip is not touching the bottom of the screen. This is a known bug with Sun's JRE. See Sun's Java bug report for more information: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6308296.
- FIXED IN 8.01: System Health monitors TransactionVision components such as the Analyzer, SonicMQ Domain Manager, SonicMQ Message Broker, and UI/Job Server. On UNIX, System Health does not correctly monitor the SonicMQ Domain Manager. This results in a bad status being shown for SonicMQ Domain Manager process in the System Health Dashboard.
To fix this problem, perform the following steps:
- Stop the nanny on the Analyzer host using the command:
<TVISION_HOME>/bin/run_topaz stop.- Edit the file: <TVISION_HOME>/conf/supervisor/nanny/SonicMQDomainManager.nanny and replace the following line:
procName=SonicMQDomainManager
with the line:
procName=SonicMQDM- Start the nanny on the Analyzer host using the command: <TVISION_HOME>/bin/run_topaz start.
To verify the fix, click the Analyzer node in the System Health Dashboard and observe the green status of the SonicMQ Domain Manager process.
- FIXED IN 8.01: Appendix B of the TransactionVision Deployment Guide is incomplete; the following configuration files are supported at this release and should be included in the appendix:
- License.properties: The <TVISION_HOME>/config/license/License.properties file specifies the TransactionVision license code supplied by HP.
- Performance.properties: The <TVISION_HOME>/config/services/Performance.properties file contains the following settings for performance logging:
- performance. Specifies whether performance logging is on or off. The default is off.
- count_interval. Specifies the number of events after which performance data is logged. The default is 500.
- detail. Specifies whether to generate detailed performance and statistics logs. The default is off.
- start_at. Defines how many events have to get processed before the performance logging will start. The default is 500.
- get_queuedepth. Specifies whether to retrieve the current event queue depth for each log interval. The default is off.
- The flow map will not load for the Aggregated Topology, Instance Topology or Dashboard if you do not have the correct Java JRE installed - you must have JRE 1.5.x or above. Instead of the flow map, a red X icon displays. To fix this, you can do one of the following:
- FIXED IN 8.01: The Search function has been removed from the Active Filters dialog for both the Aggregated Topology and Instance Topology pages, since it was not functioning properly.
- Release 7.50 Java Agents do not collect the data required by the CMDB Population and CMDB Update jobs when used with the 8.00 Analyzer and UI/Job Server. In this case, the UI /Job Server logs contain messages such as:
TransactionVision Error (SystemModelMissingCIAttributes: Data required to populate CI not present in system model.
- If your TransactionVision deployment environment consists of 7.5 Java Agents only, we recommend that the CMDB Population and CMDB Update jobs be stopped.
- If your TransactionVision deployment environment consists of both release 7.50 Java Agents and 8.00 Java Agents reporting to the 8.00 Analyzer and UI/Job Server, the CMDB Population and CMDB Update jobs can continue to run and the above error message can be ignored. In this case, only the infrastructure entities corresponding to the 8.00 Agents are reported to the uCMDB.
- After reinstalling the TransactionVision UI/Job Server on Solaris, a tomcat process from the previous installation is left running, causing the TransactionVision menus in Business Availability Center to be disabled. To resolve the problem, use "ps | grep Tomcat" to find the problem process, then kill it.
- When upgrading a TransactionVision Analyzer from a previous version, the migration automatically updates the Analyzer configuration files to use the new standard port for the Analyzer, 21100. However, the Analyzer definition in the Business Availability Center is not updated accordingly and must be done manually. Access the Admin > TransactionVision > Administration > Analyzers > Update Analyzer page, and for any affected analyzer update the port to 21100.
- Corrections and additional instructions for importing the Trade Demo Sample Events can be found in the <TVISION_HOME>\samples\readme.txt file which is included with the TransactionVision Analyzer installation package. Please refer to this file prior to importing the sample events.
- The Delete button is mistakenly enabled in the Communication Link Templates page. If a user is editing one of the default communication link templates they can unintentionally delete the edited communication link template. Workaround: Rerun TVisionSetupInfo.bat/.sh located in the <TVISION_HOME>\bin directory to re-create the deleted communication link template.
- TransactionVision data is always saved to the default profile database in HP Business Availability Center.
- If connection to the TransactionVision database is lost, the following message is displayed:
"TransactionVision Error: The connection to the TransactionVision database has been lost. Please ensure that the database is accessible, and then re-login to BAC again."
In some cases, making sure the database is accessible and re-logging into Business Availability Center does not resolve the problem. In these cases, the problem can be resolved by restarting the TransactionVision UI/Job Server using nanny restartService tv_as. For more information about the nanny utility, see Appendix A in the TransactionVision Deployment Guide.
Business Process Insight Server
- FIXED IN 8.01: When viewing individual process instance data in Business Process Insight, links to TranactionVision may fail.
Previously, when viewing a TransactionVision-driven process from within the Business Process Insight application inside Business Availability Center, if you selected the Health Page, clicked to drill down to a list of process instances, selected an individual instance and selected to view the data for the instance, a link to TransactionVision reports appeared. However, if you attempted to get to the report by clicking on the link, it failed with HTTP 404 errors, or nothing opened.
This issue has been fixed by changing the mechanism of how the Business Process Insight drill down pages link to the TransactionVision reporting pages.
- Business Process Insight is not receiving events from TransactionVision.
If you start Business Process Insight while TransactionVision's JMS Event Queue services for sending events to Business Process Insight are unavailable, or if the JMS Event Queue services become unavailable once Business Process Insight has started, the OVBPIJmsEventHandler Service stops. To solve this problem, you need to configure the Windows Service for the OVBPIJmsEventHandler Service under Control Panel > Administrative Tools > Services. You should configure the service in the same way as is described for adapter Windows Services in the Integration Training Guide - Business Events, by selecting the Recovery option and setting each of the First, Second and Subsequent Failures to the value of Restart the Service.
- Unexpected images displayed within Modeler when deploying a business process.
If you deploy a Business Process using the Business Process Insight Modeler and you see unexpected images displayed next to the deployed Business Process definition name, you are likely to be experiencing a problem with the version of the Java Virtual Machine that you are using. The problem is specifically with JRE version 1.5_16.
To resolve the problem, use a version of the JRE that is earlier than version 1.5_16, or a later version, if there is one available.
- Modifying Servlet Engine files.
If you intend to modify the Servlet Engine (Tomcat) configuration files, you need to be aware that changes made directly to the Servlet Engine files are overwritten by Business Process Insight configuration files. Refer to the upgrading chapter of the Business Process Insight Deployment Guide for more details.
- Missing Business Process Insight Infrastructure settings.
If you see an error indicating that one or more Business Process Insight Infrastructure settings is missing, make sure that you have specified a value for the Microsoft SQL Server database name:
Instance Database Settings: Database Name.
You need to provide a value for this setting even if you are configuring the settings for an Oracle database. It can be any string, but you cannot leave the field blank; if you do, you receive an error when accessing the Business Process Insight Application pages.
- Servlet Engine appears not to start following a system restart.
Very occasionally, following a system restart, the Servlet Engine appears not to have started, both within the Business Process Insight Administration Console and as a Windows Service. The Servlet Engine service is actually in the processes of starting, but is taking a long time, possibly due to other applications causing delay; for example, the database can take a long time to start when it is very full.
If you think that you are experiencing this problem:
- Unable to contact RMI Registry during component startup.
If you receive an error message indicating that the Business Process Insight Server is unable to contact the RMI Registry on port 44,000, this is likely to be due to a port number clash.
The Business Process Insight RMI Registry uses port 44,000, and if another application or service is temporarily using this port, then the RMI Registry cannot start. To resolve this problem, you can:
- wait and attempt to restart the Business Process Insight components again.
- use the Business Process Insight Administration Console to modify the port number for the RMI.
Select the Port Numbers tab from the Business Process Insight Server Administration Console to change the RMI Registry port number from 44,000. If you change the value for the port number, you need to make sure that any other configuration affected by this change is also modified, for example, the Business Process Insight Infrastructure settings.
- Process fails to progress when common data and event definitions are derived from a single process
The following scenario results in a Process definition that cannot be progressed:
- Create and deploy two Process definitions, each linked to the same Data definition.
- Separate the Processes completely by creating a new Data definition with identical properties to the first Data definition.
One of the Process definitions is now linked to the newly created Data definition and no changes are made to the progression rules. In this case, the Business Process Insight Modeler should detect that the progression rules are referencing a different Data definition, but it does not and as a result, no process instances are created.
To resolve this problem, use the Export and Import options within the Business Process Insight Modeler to make a copy of a Process definition. Use the option to rename the definitions (not overwrite them).
See "Modeler Management Tasks" in the Using Business Process Insight guide for details of making copies of your Process definitions.
- Empty string values and null string value evaluation within Oracle.
When entering property values for subscriptions within the Business Process Insight Modeler, be aware that the Oracle Server does not distinguish between a zero-length string, and a string with a value that has not been assigned (null string). This means that if you want to test a zero length string within a subscription, you are advised to use a single blank space (" "), and not an empty string ("").
- The Accelerator and openadaptor framework.
The HP Business Process Insight Accelerator for SAP Applications uses the openadaptor framework. If you install the Accelerator on a different machine to the one where the Business Process Insight Server is installed, the Accelerator installs only the subset of the openadaptor files that it needs to operate.
If you want to extend the capabilities of the Accelerator and use a feature of the openadaptor framework that are not provided as part of the Accelerator installation, you need to copy the complete openadaptor framework from the Business Process Insight machine to the machine where the Accelerator is installed.
The openadaptor framework is located at the following location on the Business Process Insight Server machine:
bpi-install-dir\nonOV\openadaptor
- Error in Modeler when attempting to import a Process definition.
If you see an error message similar to the following when importing a Process definition into the Business Process Insight Modeler, it is possible that you are attempting to import a Process definition with a name that contains characters that are locale-specific:
The file proc-defn-name.zip is not a valid import file. Please see the log file for more information.
where proc-defn-name is the filename, based on the Process definition name.
There are restrictions in the use of locale-specific character sets, whereby a .zip file name can contain characters only from the character set of the system locale where the Business Process Insight Modeler is running. The content of the file can contain any characters, but the file name is limited by the character set of the Windows system that is reading or writing the file. In the case of the zip archive files for exporting and importing processes, the zip archive file name is based on the Process definition name. Therefore, if you want to export a Process definition, you have to consider where you will be importing the file. If you plan to move the file across locales, you are advised to use only ASCII characters for the Process definition name to ensure the file can be read on any configured locale.
This problem can also occur if you change the locale of the Windows system where you have created the Process definitions.
- Changing the Locale of a system where Business Process Insight is installed.
If you modify the locale for a system where the Business Process Insight Server is installed, you might find that you cannot start the Business Process Insight Administration Console when you reboot your system. The Administration Console also returns an error indicating that it cannot find the main class and that the program will exit.
This can happen in cases where Business Process Insight is installed into a directory, which is named using locale-specific characters. If the locale for the system is then changed, it is not always possible for the directory and file names to be readable using the character set of the new locale.
If you have changed the locale of the system where Business Process Insight is installed and you are experiencing this problem, you need to:
- Running the Business Process Insight installation on Turkish Locale causes an exception error.
If you attempt to run the Business Process Insight Installation procedure using a Turkish locale, the installer does not present the installation screens correctly and, as a result, you cannot answer the installation questions. This is a problem related to the InstallAnywhere software and details of the problem can be found at the following URL:
http://support.installshield.com/kb/view.asp?articleid=Q110959
In order to complete the installation successfully, you need to temporarily set the locale to a United States locale. When you have completed the installation, you can reset the locale to Turkish.
- Do not use non-ASCII characters for the Oracle database data directory.
If you enter non-ASCII characters for the Oracle database data directory during the Business Process Insight installation, the installation fails with a Database Setup error. The error indicates that Oracle is unable to create the database instance or a database table.
If the Business Process Insight installer reports a Database Setup Error, and you have used non-ASCII characters for the name of the database data directory, you need to reinstall (overinstall) Business Process Insight into the same location, this time using a database data directory name that contains only ASCII characters.
- Microsoft SQL Server 2005 and excessive checkpoint process I/O.
If you are using Microsoft SQL Server 2005 and you are aware that you are having problems with database checkpoint I/O requests, you are experiencing a known problem with SQL Server 2005. The problem has been fixed by Microsoft and has the following Microsoft defect number: 50000708.
Microsoft provided a solution for this problem in their Service Pack 2 for SQL Server 2005. You need to make sure that you have installed Service Pack 2. Microsoft also recommends that you use the -k3 startup parameter to limit the I/O requests generated by the checkpoint process. Refer the defect text provided by Microsoft, or the Microsoft documentation for details of using startup parameters.
- InstallAnywhere uninstaller stops responding.
Many errors encountered when the InstallAnywhere uninstaller is running, for example, a missing JVM, causes the uninstaller to stop responding, or hang.
If you experience a problem where the Business Process Insight uninstaller stops responding, you need to complete the following tasks according to what you have installed:
- Stop the uninstaller process, which is still running on your system. For example, on a Windows system use the Task Manager.
- If you are removing a Business Process Insight Server, delete the Business Process Insight files under the Business Process Insight installation directory.
- Modify the Zerog Global Registry (an InstallAnywhere file):
- Open the registry file, which is usually located in c:\Program Files\Zero G Registry\.com.zerog.registry.xml. Note that on Windows the registry file is located in a hidden directory, so you might have to configure your system to display hidden directories and files.
If the registry file contains only entries for the product that you are attempting to uninstall, you can rename the file. However, if there are multiple product installations, or multiple instances of one product installation, you need to edit the file as described in the following step.
If the registry file contains entries in addition to those for Business Process Insight, edit the file to remove the following entries:
- The product elements for Business Process Insight. Make sure the element references the directory where the files are located that you want to uninstall.
- The components elements for Business Process Insight. Make sure the component element references the directory where the files are located that you want to uninstall.
- Restrictions when using Autopass.
The following are restrictions that you need to be aware of when using Autopass with Business Process Insight:
- Autopass is a separate product and has its own requirements with respect to local language support. It is possible that versions of Autopass are available in languages that differ from the languages supported by Business Process Insight. In this case, you might see a mixture of US English and local language for each of the products.
- Autopass does not support the use of non-ASCII characters in entry fields; for example, you cannot enter customer details using non-ASCII characters. Refer to the Autopass product information for more details.
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
Business Availability Center for Siebel
- The Siebel Cross Performance report requires Internet Explorer 7.0 to display correctly. If you want to view this report when using Business Availability Center for Siebel, use Internet Explorer 7.0.
- If you attach the Siebel KPI to a CI in a non-Siebel view, the propagation propagates the Siebel KPI with the wrong rule, and the KPI displays a No data status. Workaround: Edit the Siebel KPI and attach the required rule (for example the Worst Child rule).
HP SiteScope
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.
- 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 OM (formerly HP OVO) monitor can be created on the same port using the Copy function, resulting in duplicate OM 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.
- If you ever used a version of Business Availability Center prior to 5.x, subsequently performed multiple upgrades to higher versions, but never used the Diagnostics integration, you may have a missing property in the Sessions table of the Business Availability Center database that prevents the integration between HP Business Availability 8.00 and Diagnostics 8.00.
Workaround (not relevant for Software-as-a-Service customers):
SELECT * FROM SESSIONSWHERE SESSION_NAME like 'Unassigned%' AND SESSION_TYPE_ID=5
Universal CMDB
General, Installation, and Upgrade
- When upgrading from previous version, you must export configuration changes made to out-of-the-box content (TQLs, views, CI types, Jython Scripts, discovery jobs, and so forth) of UCMDB packages and reapply the changers after the upgrade is complete. This is because the upgrade process overrides custom changes made to out-of-the-box content. For details, see the HP Universal CMDB Deployment Guide.
- After upgrading to 8.00, the CIs of types Database and J2EE (termed WebSphere in the documentation) Server are removed from all instance views, SLAs, and alerts that include the CIs of those types. For details, see the Impact Modeling section in the "Component and Data Upgrade and Limitations" chapter in the HP Business Availability Center Deployment Guide.
- After upgrading to 8.00, check the log file: <HP Business Availability Center root directory>\mam_lib\_reports\customer_[id]\UpgradeInfoReport.txt to view all the CIs that are deleted.
- If an upgraded instance view contains a host (without any monitor), and the host is connected to a software element (that is connected to a monitor), after the upgrade the Host CI appears in Show hidden CIs list in Modeling Studio. This is relevant if the software element is not of the type Database or J2ee server. Workaround: Remove Host CIs from Show hidden CIs list.
- 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 <Business Availability Center 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.
- Proprietary adapter configured in Generic DB Adapter default folder: If you created 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.
Discovery and Dependency Mapping
Modeling and Application
- When working in the Model Editor in Modeling Studio, the Find feature only works for CIs that are visible in the expanded model/view. Workaround: Make sure the model is expanded before using the Find feature.
- The Find feature in the CI Selector (in IT Universe Manager and Modeling Studio) does not work for CIs that are not visible in the collapsed view tree until you expand the relevant branch of the tree. Workaround: Once you expand the relevant branch, the Find feature works, even if the branch is collapsed again. If you navigate away from the view and return to it, you need to expand the branch again for the Find feature to work.
- In Modeling Studio, when the Location Based Monitors perspective is selected as the perspective for a view, the Apply Over Model Hierarchy option is selected by default, which results in the inclusion of business process step CIs in the view. Clear the Apply Over Model Hierarchy check box to remove these CIs from the view.
- Changing an integration TQL can result in data loss. To avoid data loss:
- Before making changes to a TQL, run diff replication. This step is needed to avoid losing removed data when running a full replication (the next step).
- After making changes to a TQL, run full replication. This step is needed to retrieve all the data for a second time, to differentiate between new data (that must be retrieved) and existing data (that does not need to be retrieved).
- 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.)
- UCMDB 8.00 uses an applet that is run by a JRE. The supported JRE versions are 6u4 and later (6u10 recommended, this version is included on the UCMDB server itself for local network download).
- To optimize the user experience in UCMDB 8.00, 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 selection.
- If you run get result count over a TQL with an invisible multiple data store element, the count for the element will not include the CMDB objects satisfying the query for that element. If you have a view based on such a TQL, you will not be able to run discovery based on this view (via IT Universe Manager > View Browser > Show Discovery Status and Changes of View) if the view's result contains data only from the CMDB in the multiple data store node, and no objects in the view's other nodes.
- Exporting data from UI components such as tables and trees is not supported for Asian languages.
Reports
- FIXED IN 8.01: Running Asset reports on template-based views is not supported.
- The results of scheduled Gold Master and Topology reports (known as System reports in 6.x) that were generated in HP Universal CMDB 6.x cannot be viewed in HP Universal CMDB 8.00.
- 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
Multilingual Support
- If you use a CJK language in your browser, you must ensure that the Gateway server machine running HP Business Availability Center has East Asian languages installed. On the machine on which the HP Business Availability Center Gateway server is installed, you must select Control Panel > Regional & Language Options > Languages > Install files for East Asian languages.
- In CJK languages, when browser locale and Windows system locale are not set to the same language, navigation pane in Business Availability Center documentation library displays gibberish in Search and Favorites tabs. Workaround: Ensure that browser locale and Windows system locale are both set to the same language.
- 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.
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
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
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
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.
Business Process Monitor 7.52 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.
Business Process Monitor Changes
SiteScope Support Matrix
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.
- 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
Real User Monitor Support Matrix
Note: Real User Monitor 7.01 (probe and engine) works only with Business Availability Center 7.01.
DDM Discovery Probe Support Matrix
Note: Discovery Probe 7.51 works only with Business Availability Center 7.51.Discovery Probe 7.01 works only with Business Availability Center 7.01.
Security Matrix
Business Availability Center for SAP Component Support Matrix
SAP Version Limitations SAP R/3 4.6SAP R/3 4.7 None ERP 2004 (ECC 5.0)ERP 2005 (ECC 6.0) The following reports are not supported:Business Availability Center for Siebel Component Support Matrix
Business Process Insight (BPI) Support Notes
Note the following limitations when deploying BPI:
TransactionVision Integration Notes
When running TransactionVision components together with Business Availability Center and/or Business Process Insight and/or Diagnostics, all software versions must be the same - for example if running TransactionVision from Business Availability Center 8.0, installed TransactionVision components must be version 8.0, Business Process Insight (if installed) must be 8.0, and Diagnostics (if installed) must be 8.0.
Business Availability Center/Diagnostics Integration Matrix
Integration Matrix
HP Diagnostics 8.00
HP Diagnostics 7.50
HP Diagnostics 7.0
BAC 8.00
√
√
√ (*)
BAC 7.50
√
√
√ (*)
BAC 7.0
√
√
√
(*) Note: Business Availability Center for SOA not supported
Business Availability Center 8.00/ServiceCenter/Service Manager Integration Matrix
Note: For integration with Service Manager to function properly, additional setup is required in both Business Availability Center and Service Manager. See the Business Availability Center documentation for details.
HP Software Support
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:
- Search for knowledge documents of interest
- Submit and track progress on support cases
- Submit enhancement requests online
- Download software patches
- Manage a support contract
- Look up HP support contacts
- Review information about available services
- Enter discussions with other software customers
- Research and register for software training
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
To register for an HP Passport ID, go to: HP Passport Registration.
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.
For information about third-party license agreements, see the Third_Party_Agreements directory on the product installation media.
Trademark Notices
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.
If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.