hp business availability center 8

HP Business Availability Center 8.01

ReadmeSoftware 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

Installation Prerequisites

Installation

Uninstallation

Version Content and Limitations

Updated Components

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

Setup.exe (Windows installation)

Setup.bin (Solaris installation)

Component setup files

New: Real User Monitor Probe 8.01 (Linux)

New: Real User Monitor Engine 8.01 (Windows)

New: Discovery Probe 8.01 (Windows)

New: TransactionVision 8.01 components

New: Business Process Insight Server 8.01

New: Diagnostics 8.01 components (see Diagnostics readme for details)

Note: You need to separately download new component setup files.

Documentation files

whatsnew.html

readme801.html (includes 8.00 Readme)

reissue of complete Business Availability Center documentation set

Additional files

tzupdater.jar - file needed for Daylight Savings Time definition update

Installation Prerequisites

Business Availability Center 8.01 must be installed on top of Business Availability Center 8.00.

Installation

HP Business Availability Center 8.01 http://bac.itsolution.biz/releasenotes/bac/readme801.html

1 of 35 5/28/2012 12:37 AM

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.

If you are installing Business Availability Center 8.01 on top of 8.00 and are working with an external UCMDB architecture,

you must perform the following procedure to deploy the 8.01 BAC packages to the UCMDB server, as they are notdeployed automatically to the external UCMDB server during the installation: After installing 8.01 (BAC and UCMDB) rerunthe Server and Database Configuration utility and reconnect to existing BAC schemas and external UCMDB server. During

this process the BAC packages are deployed to the UCMDB server. For details on running the Server and DatabaseConfiguration utility, see the HP Business Availability Center Deployment Guide.

The tzupdater.jar file included with Business Availability Center 8.01 is the same as the one included with BusinessAvailability 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 DSTdefinitions.

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 forusing the tzupdater.jar file on Business Process Monitor instances, see the HP BusinessAvailability 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 usingJMX 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: 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


2 of 35 5/28/2012 12:37 AM

Center install directory>\logs\topaz_all.ejb.log

Perform the below workaround before starting the upgrade process to enable writing to theupgradeFramework.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. 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 thechanges 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 jobshould be run in full replication mode. For details on running diff and full replication, see the Replication Jobs

Tab section in the Model Management guide.

Service Desk adapter: Perform the following procedures to make sure you do not lose your existing Service

Desk adapter configuration information during the upgrade process:

Before upgrading to 8.01: Back up the <HP Business Availability Center Data Processing

Server root directory>\fcmdb\Codebase\ServiceDeskAdapter\serviceDeskConfiguration.xml

file.

After installation of 8.01: Copy the backed up file back to its original location.

Proprietary adapter configured in Generic DB Adapter default folder: If you created a proprietary adapter

in the default Generic DB Adapter folder, you must perform the following procedures to make sure you do not

lose your existing Generic DB Adapter configuration information during the upgrade process.

Before upgrading to 8.01: Back up the <HP Business Availability Center Data Processing Server

root directory>\fcmdb\Codebase\GenericDBAdapter\META-INF directory.

After installation of 8.01: Copy the backed up directory back to its original location.

Proprietary adapters based on Generic DB Adapter (when upgrading from HP Business Availability

Center 7.5.1 or 7.52 to 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.


3 of 35 5/28/2012 12:37 AM

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 prefixedby the corresponding CI type name. For example, if one of the reconciliation rulesis multinode[host] expression[host.host_hostname or ip.ip_address]end1_type[host] end2_type[ip] link_type[contained], then ip.ipaddressshould 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 instructionsbelow.

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.


4 of 35 5/28/2012 12:37 AM

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.

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 Databaseis 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 HPBusiness Availability Center, he is automatically created as HP Business Availability Center usertestuser, who can be assigned permissions in the HP Business Availability Center User Managementinterface. If you then login to HP Business Availability Center as Testuser, the LDAP Active Directoryserver 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 notidentify this user as testuser (because the Oracle Database is case sensitive), the user Testuser istreated 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 notavailable. While there may be enough correlation information--based on either standard technologycontext or customer specific business data--to triage the events and limit the matching event candidatesto a minimum set, additional factors need to be considered to complete the correlation process and resultin one-to-one event relationship.

One such factor is event time stamps. In certain situations, TransactionVision can correlate specific eventcandidates by considering the respective event execution time. One example: two events A and Brepresenting EJB X and Y method calls respectively are reported to TransactionVision, with EJB X methodinvoking 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 thatby truncating the respective event time stamps to a precision consistent with the expected latency, thetwo events would have the same truncated timestamp, and this can in turn be considered as a matchingkey in a lookup key based correlation algorithm.

TransactionVision provides a correlation component that supports this type of time based correlationenhancement. One can consider this as a correlation algorithm based on a mix of time andpayload/technology specific data keys. Contact HP Software Support for more information about usingthis 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 underanother user/group on the same host. Therefore the Business Availability Center nanny process does not have permissionto execute the TransactionVision components.

Workaround: Change the user/group of the /opt/HP/TransactionVision directory to the same as thatbeing 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 BusinessAvailability Center installation directory). Alternatively, you can grant write permissions for allusers/groups to the TransactionVision directory by using the command: chmod -R a+w /opt/HP


5 of 35 5/28/2012 12:37 AM

/TransactionVision, but this alternative would open up read/write access for the TransactionVisioninstallation 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 messagingmiddleware provider and the SonicMQ Broker is not configured with security.

Work Around : To avoid this problem, enable security in the SonicMQ Broker by requiringauthentication. 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 theProgress SonicMQ Deployment Guide. This manual is available on any host on which the Analyzer isinstalled; 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 couldnot 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

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 theoption to continue with the installation. The Process Repository database details will need to be entered manually but theinstallation 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, i.e. <hostname>\

<instance>, to specify the database. Workaround: During installation of BPI, identify the host and specific port that

the named instance is running on and then enter the following during 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 Serverport) 1433, discover that the fred instance is running on port 1244 and use:

MS SQL Server hostname: fred

MS SQL Server port: 1244

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 withlanguages such as Hungarian, German, or French. In these cases, the user is able to see the number in the correct formatin 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


6 of 35 5/28/2012 12:37 AM

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 worksproperly.

HP Business Availability Center bug fixes - see table below for details:

Description SR/E-Sar

Number

Area

Fixed issue of required libraries for Windows authentication via datadirect driver in 64-bit servers which were missing from setup

3603596158 BAC_Platform

Fixed problem of Scheduled Reports being sent prematurely after editand after resume

3604680525 BAC_Platform

Fixed issue of user being able to define CI alerts and create newrecipients without permissions on first login

1602875529 BAC_PlatformAdmin

Added default role setting for automatically created users 1603050342 BAC_PlatformAdmin

Fixed issue of access URL in alert engine not working for follow-up alerts 207458 BAC_Platform

Fixed problem of Dashboard Top View slow performance 3604202581 BAC_Dashboard

Fixed out of memory problem 206576 BAC_SLM

Added record of actions to the audit log in System AvailabilityManagement Admin

46705 BAC_SAM

Fixed issue of Scheduled Reports that contain old EUM reports displayingthe word "profile" and the X-axis labels (dates) in the server locale

48057 BAC_EUM

Added to BLE ability to filter out events not needed for EMS Integration 3603829487 BAC_DataEntry

Fixed issue of user with view permissions being able to create arelationship between two CIs

1602875529 BAC_MAM

Fixed issue of user with view permissions on a specific view being able togenerate reports for other views

1602875529 BAC_MAM

HP Universal CMDB bug fixes - see table below for details:

Description Area

Fixed issue of SAP Solution Manager pattern failing DDM

Fixed issue with dbadapter of failure to retrieve link layout Federation

Fixed issue of reports not being sorted under System Report Application

Fixed issue of sort function in System Report not working properly Application

Fixed issue of System Reports generated in CSV not conforming to the CSV standardused in 6.6 and earlier

Application

Fixed user permissions issues, including allowing access to all views in Asset Reportsand enabling user with no permissions to create relationships in ITU

Application

Fixed issue of null pointer exception error while running correlation with logsset to info or higher

Topology

Internal bug fixes

Updated Components


7 of 35 5/28/2012 12:37 AM

The following updated components are included with Business Availability Center 8.01:

Real User Monitor Probe 8.01 Build 8.01.014 (Linux)

For instructions on upgrading the Real User Monitor probe, see the Upgrade Components chapter in the HP Business Availability

Center Deployment Guide.

The issue of only being able to start the Real User Monitor probe as the root user has been fixed and you are

now able to start the probe as another user.

Real User Monitor Engine 8.01 Build 13 (Windows)

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 RealUser 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 > TrafficDiscovery) 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 UserMonitor 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), thenuninstall 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.

Bug fixes

TransactionVision - all TransactionVision components, except for the NonStop TMF, i5/OS WMQ Agent, and z/OS DSSLR

components, have been updated with bug fixes.

For installation instructions, see the TransactionVision Deployment Guide.

Business Process Insight - the BPI 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.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.

Compatibility

Matrix

HP Business

Availability

Center 8.01

HP Business

Availability

Center 8.00

HP Business

Availability

Center 7.51

HP Business

Availability

Center 7.50

HP Business

Availability

Center 7.0

BPM 7.52(VuGen 9.1)

√(Recommended)

√(Recommended)

√ √ √

BPM 7.51(VuGen 9.1)

√ √ √(Recommended)

√ √

BPM 7.50(VuGen 9.1)

√ √ √ √(Recommended)

√

BPM 7.0(VuGen 9.0)

√ √ √ √ √(Recommended)


8 of 35 5/28/2012 12:37 AM

QTP SAP R/37.31

√ √ √ √ √

QTP 9.5 √ √ √ √ X

QTP 9.1/2 √ √ √ √ √

QTP 9.0 √ √ √ √ √

SiteScope Support Matrix

Compatibility

Matrix

HP Business

Availability Center

8.01

HP Business

Availability Center

8.00

HP Business

Availability Center

7.50

HP Business

Availability

Center 7.0

SiteScope 10.00 √ (Recommended) √ (Recommended) √ √

SiteScope 9.5 √ √ √ (Recommended) √

SiteScope 9.0,9.01

√ √ √ √

SiteScope 8.x √ √ √ √

SiteScope 9.01 recommended with BAC 7.01, SiteScope 9.0 recommended with BAC 7.0, SiteScope 8.5 recommended

with BAC 6.5

SiteScope/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.

1.

System Availability Management Administration which refers to configuring SiteScope in System Availability

Management Administration.

2.

The following table contains compatibility information regarding the above aspects and the various combinations of SiteScope andBusiness Availability Center releases.

1 = Data logging support

2 = System Availability Management support

SiteScope Version Business Availability Center Version

8.00, 8.01 7.50 7.0x

SiteScope 10.0 1, 2 1, 2 1, 2

SiteScope 9.5, 9.51 1, 2 1, 2 1, 2

SiteScope 9.0, 9.01, 9.02 1, 2 1, 2 1, 2

SiteScope 8.8 8.7, 8.6, 8.5 1 1 1

Real User Monitor Support Matrix

Compatibility

Matrix

HP Business

Availability

Center 8.01

HP Business

Availability

Center 8.00

HP Business

Availability

Center 7.51

HP Business

Availability

Center 7.50

HP Business

Availability

Center 7.0

Real UserMonitor Engine8.01

√ √ X X X

Real UserMonitor Probe

√ √ X X X


9 of 35 5/28/2012 12:37 AM

8.01


√ √ X X X

Real UserMonitor Probe8.00

√ √ X X X


X X √ √ X


X X √ √ X


X X √ √ X


X X √ √ X


X X X X √


X X X X √

Note: Real User Monitor 7.01 (probe and engine) works only with Business Availability Center 7.01.

DDM Discovery Probe Support Matrix

Compatibility

Matrix

HP Business

Availability Center

8.01

HP Business

Availability Center

8.00

HP Business

Availability Center

7.50

HP Business

Availability Center

7.0

Discovery Probe8.01

√ X X X

Discovery Probe8.00

X √ X X

Discovery Probe7.50

X X √ X

Discovery Probe7.0

X X X √

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


10 of 35 5/28/2012 12:37 AM

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

Integration

Matrix

Integration

Type

HP Business

Availability Center

8.01

HP Business

Availability Center

8.00

HP Business

Availability Center

7.50

HP Business

Availability Center

7.00

Service Manager

7.10

IncidentSubmission

√ √ X X

Problem

Isolation

√ X X X

EMS

(Dashboard,SLM)

√ (SiteScope 10.00) √ X X

Service Manager

7.02

Incident

Submission

√ √ √ X

Problem

Isolation

√ √ √ X

EMS(Dashboard,

SLM)

√ (SiteScope 10.00) √ (SiteScope 10.00) √ (SiteScope 10.00) √ (SiteScope 10.00)

Service Manager

7.01

Incident

Submission

√ √ √ X

ProblemIsolation

X X X X

EMS(Dashboard,SLM)


ServiceCenter

6.26

IncidentSubmission

√ √ √ X

ProblemIsolation

√ √ √ X

EMS

(Dashboard,SLM)



11 of 35 5/28/2012 12:37 AM

Note: For integration with Service Manager to function properly, additional setup is required in both Business Availability Center andService Manager. See the Business Availability Center documentation for details.

HP Business Availability Center 8.00

ReadmeSoftware version: 8.00 / January 2009

This file provides information about HP Business Availability Center 8.00.

Documentation

What's New

System Requirements

Notes and Limitations

Multilingual Support

HP Business Availability Center Support Matrixes

Support

Legal Notices

Documentation

The first page of this release notes document contains the following identifying information:

Version number, which indicates the software version.

Publish date, which changes each time the document is updated.

To check for recent updates or to verify that you are using the most recent edition, visit the following URL:

http://h20230.www2.hp.com/selfsolve/manuals

This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to:

http://h20229.www2.hp.com/passport-registration.html

Or click the New users - please register link on the HP Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales

representative for details.

Note: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat

Reader, go to the following URL: www.adobe.com

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


12 of 35 5/28/2012 12:37 AM

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 toa single application and then permits you to access other supported applications configured in the original application'sgroup. 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 notApache. 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 whenrunning 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 AvailabilityCenter 8.0x.

Favorite filters created for CI Status Alert and SLA Status Alert reports in previous versions are not upgraded and will notwork 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 manuallyremove business processes and related CIs (steps and all BPI monitors) from the CMDB that were created by BPI 2.20 onBusiness 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 businessprocesses created either manually or by BPI on a Business Availability Center 6.x (from 6.8) or 7.0. system should beremoved, 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 avertical 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 newversion. 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://<HPBusiness Availability Center GATEWAY server>/axis2/*

The following issue is relevant if you are performing an upgrade in staging mode in an HP Business Availability Centerenvironment in which HP Diagnostics is integrated and you want to register a different Diagnostics server to the stagedBusiness 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 theproduction environment. Instead, change the Diagnostics server host registration directly in the Business Availability Centermanagement 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 beable 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)


13 of 35 5/28/2012 12:37 AM

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 TQLnames 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:

Locate the service=CMDB Business View Enrichment Services JMX and invoke the

removeEnrichment() method for each enrichment that has a missing TQL.

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 atopological 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 releaseand 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 linkswere created by adapters or DNode.

The Topology Map portlet has been discontinued, and is no longer available from Dashboard or My BSM. To view atopological 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 changesthe 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. ThePNR 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


14 of 35 5/28/2012 12:37 AM

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 changefrom 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 DSTtime 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 ProcessMonitor 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 CIsthat 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 CIis 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 tothe location name of a Business Process Monitor for which SLAs are defined. Also, configure the Business ProcessMonitor 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 becausenesting 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 forthe 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 arethe 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) configuredin 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 atimeout. 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 whencreating 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


15 of 35 5/28/2012 12:37 AM

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 thecorresponding 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 anerror 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 inthe target SiteScope. This is because the monitor tree in the new SiteScope user interface refreshes by default fiveseconds 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 (byselecting 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 youadd 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, eventhough 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 runningagain. 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 changedaccordingly. 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.

FIXED IN 8.01: 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 HPBusiness Availability Center using http:// in this case would produce "mixed mode content" errors on each page.

FIXED IN 8.01: 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" toset 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.


16 of 35 5/28/2012 12:37 AM

FIXED IN 8.01: 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 definitionsare 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 topdashboard view. Re-syncing the CMDB does not fix this problem since CMDB updates only affect business transactionclasses 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 theCMDB 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 IMSsensor 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 toinvoke the TransactionVision IMS sensor (SLMYIOE0).

Starting with z/OS version 1.9, the default setting for system parmlib DIAGnn member statement VSMALLOWUSERKEYCSA 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 parametervalue 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


17 of 35 5/28/2012 12:37 AM

Note that the WebLogic domain name is usually the directory containing your server.

3. Restart your WebLogic server.

FIXED IN 8.01: The nanny utility information in Appendix A of the TransactionVision Deployment Guide is incorrect. The

syntax and options should be:

Syntax

nanny -s <hostname> -p <port> <cmd>

Options

Option Description

-s <hostname> Hostname of the host where the Analyzer is installed. It defaults to localhost.

-p <port> Port of the nanny server. It defaults to 11020.

<cmd> One of the following commands:disableService <servicename>enableService <servicename>getServiceInfo <servicename>isServiceRunning <servicename>listAllDisabledServicesNameslistAllServicesNameslistDeadServicesNameslistLiveServicesNameslistServiceInfolitStartingServicesNamesrestartService <servicename>retrieveNannyManagerHTMLAdapterPortshowStackTrace <servicename>startAllServicesstartService <servicename>stopAllServicesstopService <servicename>where <servicename> is one of the following:tv_as - TransactionVision UI/Job Server Tomcat Web Servicetv_message_broker - TransactionVision SonicMQ Message Brokertv_domain_manager - TransactionVision SonicMQ Domain Managertv_analyzer - TransactionVision Analyzer

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 ormove 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 HealthDashboard.

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


18 of 35 5/28/2012 12:37 AM

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 correctJava 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 cando one of the following:

Navigate to the Component Topology Analysis page, and click on the link in the message bar at the top of the

browser to download the Java Applet plugin.

Manually install the Java JRE from Sun's web site.

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.

FIXED IN 8.01: 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 insystem model.

If your TransactionVision deployment environment consists of 7.5 Java Agents only, we recommend that theCMDB Population and CMDB Update jobs be stopped.

If your TransactionVision deployment environment consists of both release 7.50 Java Agents and 8.00 JavaAgents 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 entitiescorresponding 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 leftrunning, 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 Analyzerconfiguration 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.

FIXED IN 8.01: 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.

FIXED IN 8.01: 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 ensurethat 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 Centerdoes not resolve the problem. In these cases, the problem can be resolved by restarting theTransactionVision UI/Job Server using nanny restartService tv_as. For more information about thenanny utility, see Appendix A in the TransactionVision Deployment Guide.

Business Process Insight Server


19 of 35 5/28/2012 12:37 AM

Business Process Insight Not Receiving Events from TransactionVision

If you start Business Process Insight while TransactionVision's JMS Event Queue services for sendingevents to BPI are unavailable, or if the JMS Event Queue services become unavailable once BPI hasstarted, the OVBPIJmsEventHandler Service stops. To solve this problem, you need to configure theWindows Service for the OVBPIJmsEventHandler Service under Control Panel > AdministrativeTools > Services. You should configure the service in the same way as is described for adapter WindowsServices in the Integration Training Guide - Business Events, by selecting the Recovery option and settingeach 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 BPI Modeler and you see unexpected images displayed next tothe deployed Business Process definition name, you are likely to be experiencing a problem with theversion of the Java Virtual Machine that you are using. The problem is specifically with JRE version1.5_16.

To resolve the problem, use a version of the JRE that is earlier than version 1.5_16, or a later version, ifthere is one available.

Modifying Servlet Engine files

If you intend to modify the Servlet Engine (Tomcat) configuration files, you need to be aware thatchanges made directly to the Servlet Engine files are overwritten by BPI configuration files. Refer to theupgrading 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 Oracledatabase. It can be any string, but you cannot leave the field blank; if you do, you receive an error whenaccessing 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 withinthe BPI Administration Console and as a Windows Service. The Servlet Engine service is actually in theprocesses of starting, but is taking a long time, possibly due to other applications causing delay; forexample, the database can take a long time to start when it is very full.

If you think that you are experiencing this problem:

Click the Start button for the Servlet Engine from the Status screen on the Administration Console.

Click the Stop button for the Servlet Engine as soon as it is enabled.

Your Servlet Engine services are now synchronized and the Servlet Engine is not started.

Restart the Servlet Engine as normal.

Unable to contact RMI Registry during component startup

If you receive an error message indicating that the BPI Server is unable to contact the RMI Registry onport 44,000, this is likely to be due to a port number clash.

The BPI RMI Registry uses port 44,000, and if another application or service is temporarily using thisport, then the RMI Registry cannot start. To resolve this problem, you can:

wait and attempt to restart the BPI components again

use the BPI Administration Console to modify the port number for the RMI

Select the Port Numbers tab from the BPI Server Administration Console to change the RMIRegistry port number from 44,000. If you change the value for the port number, you need tomake 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 changesare made to the progression rules. In this case, the BPI Modeler should detect that theprogression rules are referencing a different Data definition, but it does not and as a result, noprocess instances are created.


20 of 35 5/28/2012 12:37 AM

To resolve this problem, use the Export and Import options within the BPI Modeler to make acopy of a Process definition. Use the option to rename the definitions (not overwrite them).

Refer to Using Business Process Insight 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 BPI Modeler, be aware that the Oracle Serverdoes 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 areadvised to use a single blank space (" "), and not an empty string ("").

The Accelerator and openadaptor

The HP Business Process Insight Accelerator for SAP Applications uses the openadaptor framework. If youinstall the Accelerator on a different machine to the one where the BPI Server is installed, theAccelerator 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 feature of the openadaptor frameworkthat are not provided as part of the Accelerator installation, you need to copy the complete openadaptorframework from the BPI machine to the machine where the Accelerator is installed.

The openadaptor framework is located at the following location on the BPI 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 BPIModeler, it is possible that you are attempting to import a Process definition with a name that containscharacters 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 containcharacters only from the character set of the system locale where the BPI Modeler is running. Thecontent of the file can contain any characters, but the file name is limited by the character set of theWindows system that is reading or writing the file. In the case of the zip archive files for exporting andimporting processes, the zip archive file name is based on the Process definition name. Therefore, if youwant to export a Process definition, you have to consider where you will be importing the file. If you planto move the file across locales, you are advised to use only ASCII characters for the Process definitionname 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 theProcess definitions.

Changing the Locale of a System Where BPI is Installed

If you modify the locale for a system where the BPI Server is installed, you might find that you cannotstart the BPI Administration Console when you reboot your system. The Administration Console alsoreturns an error indicating that it cannot find the main class and that the program will exit.

This can happen in cases where BPI is installed into a directory, which is named using locale-specificcharacters. If the locale for the system is then changed, it is not always possible for the directory and filenames to be readable using the character set of the new locale.

If you have changed the locale of the system where BPI is installed and you are experiencing thisproblem, you need to:

revert to the original locale and continue to use BPI.

revert to the original locale, uninstall BPI, configure the new locale, and then reinstall BPI into a new directory.

Running the BPI Installation on Turkish Locale Causes Exception Error

If you attempt to run the BPI Installation procedure using a Turkish locale, the installer does not presentthe installation screens correctly and, as a result, you cannot answer the installation questions. This is aproblem related to the InstallAnywhere software and details of the problem can be found at the followingURL:

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 UnitedStates 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 BPI installation, theinstallation fails with a Database Setup error. The error indicates that Oracle is unable to create thedatabase instance or a database table.


21 of 35 5/28/2012 12:37 AM

If the BPI installer reports a Database Setup Error, and you have used non-ASCII characters for the nameof the database data directory, you need to reinstall (overinstall) BPI into the same location, this timeusing 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 withdatabase checkpoint I/O requests, you are experiencing a known problem with SQL Server 2005. Theproblem 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 tomake sure that you have installed Service Pack 2. Microsoft also recommends that you use the -k3startup parameter to limit the I/O requests generated by the checkpoint process. Refer the defect textprovided 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 BPI uninstaller stops responding, you need to complete thefollowing 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 BPI Server, delete the BPI files under the BPI 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 touninstall, 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 describedin the following step.

If the registry file contains entries in addition to those for BPI, edit the file to removethe following entries:

The product elements for BPI. Make sure the element references the directory where the files arelocated that you want to uninstall.

The components elements for BPI. Make sure the component element references the directorywhere 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 BPI:

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 BPI. Inthis 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 entercustomer 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 andsave the script in HP Virtual User Generator version 9.10 or later, and reattach the script to the profile. Scripts recordedwith HP Virtual User Generator version 8.10 FP3 and earlier are not supported and you must record the script again using

HP Virtual User Generator version 9.10 or later.

Business Availability Center for SAP

The data received from the SiteScope SAP CCMS Alert monitor is not displayed in Dashboard and Service LevelManagement SAP Systems views when working with HP Business Availability Center for SAP application.

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


22 of 35 5/28/2012 12:37 AM

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 theWorst Child rule).

HP SiteScope

Refer to the SiteScope release notes for all SiteScope limitations.

Adapters and Views

In Source Manager, if you perform an adapter synchronization that does not finish before the adapter's scheduled

synchronization, the adapter will no longer synchronize automatically. To solve this issue, disable the problematic adapterand 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 defaultvalue.

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 thecontents 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 higherversions, but never used the Diagnostics integration, you may have a missing property in the Sessions table of the BusinessAvailability 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):

Check the management database/schema SESSIONS table:

SELECT * FROM SESSIONS

WHERE SESSION_NAME='J2EE_For_Default Client'

If there is a result, go to last step.

If there is no result, insert a new record to the SESSIONS table:

Run the query:

SELECT * FROM SESSIONS

WHERE SESSION_NAME like 'Unassigned%' AND SESSION_TYPE_ID=5

Insert a new record with the same value as the result record of the sql statement. Note that youhave to insert the record with a new SESSION_ID.

Update the new record of step 3 or the found record from step 2 with the following statement:

UPDATE SESSIONS

SET SESSION_NAME='J2EE_For_Default Client',

SESSION_ACTION=1,


23 of 35 5/28/2012 12:37 AM

SESSION_TYPE_ID=10,

SESSION_AGR_POLICY_ID=12,

SESSION_PRIM_TIME_DIFF=120

WHERE SESSION_ID=<<the new id>>

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 theupgrade is complete. This is because the upgrade process overrides custom changes made to out-of-the-box content. Fordetails, 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 Modelingsection 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 thechanges 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 loseyour existing Generic DB Adapter configuration information during the upgrade process.

Before upgrading to 8.00: Back up the <HP Business Availability Center Data Processing

Server root directory>\fcmdb\CodeBase\GenericDBAdapter\META-INF directory.

After installation of 8.00: Copy the backed up directory back to its original location.

Discovery and Dependency Mapping

J2EE Discovery Wizard might not be able to import large JAR files (>30MB). You may need to copy such files manually tothe proper location in the Discovery probe's installation folder.

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 visiblein the collapsed view tree until you expand the relevant branch of the tree. Workaround: Once you expand the relevantbranch, 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 ApplyOver 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 whenrunning 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


24 of 35 5/28/2012 12:37 AM

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 arenot 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 therecalculation 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, thisversion 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 willenable the UCMDB application to use an additional 192MB of memory, which will help it perform much better. Afteraccepting 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 beable 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

If you experience a JavaScript error when opening the HP Business Availability Center Documentation Library online helpsystem, disable the "Show Exception Dialog Box" in the Java Console and open the help again.

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 CenterGateway 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 inBusiness 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 differentlanguages 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 isusing 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

Component Brand Version Comments


25 of 35 5/28/2012 12:37 AM

HP BusinessAvailability CenterServers - OperatingSystems

Windows Windows 2003Standard/Enterprise Server(SP1, SP2)Windows Server 2003Enterprise x64 Edition SP2Windows Server 2003 R232-Bit Enterprise Edition,Service Pack 2

Solaris Solaris 9, 10

Web Browsers IE 6.07.0

FireFox 2.0 Note that FireFox does not support all HPBusiness Availability Center functions.Support is limited to:

Dashboard application

EUM reports

SLM reports

SAM Admin

Web Servers IIS 6

Apache 2.2.6

Sun JavaSystem WebServer

6.1 SP 5

Business ProcessMonitor - OperatingSystems

Windows Windows XP ProfessionalSP1, SP2

WebTrace functionality is not available onWindows XP SP2 because Microsoft hasdisabled low level socket access as part ofthe Windows XP SP2 security lockdown.

Windows 2003Standard/Enterpriseeditions (SP1, SP2)

Solaris Sun Solaris 9 + latestrecommended patch cluster,Solaris 10

SiteScope -Operating Systems

Windows Windows 2003Standard/Enterpriseeditions (SP1, SP2)Windows 2003 Server R2SP1

Solaris Sun Solaris 9, 10 - bothwith latest recommendedpatch cluster

Linux Linux Red Hat ES\AS 3, 4 Removed support for: Linux RH 9.0

Real User MonitorProbe - OperatingSystems

Windows Not supported

Solaris Not supported

Linux Red Hat Enterprise Linuxversion 5.x (RHEL5), 4.x(RHEL4)

Real User MonitorEngine - OperatingSystems

Windows Windows 2003Standard/Enterpriseeditions (SP1, SP2)


26 of 35 5/28/2012 12:37 AM

Discovery Probe -Operating Systems

Windows Windows 2003Standard/Enterpriseeditions (SP1, SP2)

Note: System health is based on SiteScope - please see SiteScope supported operating systems.

Database Support Matrixes

Hardware Requirements

Deployment Size Number of Processors Physical Memory

Standard 1 dual core Minimum: 2G RAM

Recommended: 4G RAM

Large 2 dual core or 1 quad core Minimum: 4G RAM

Recommended: 8G RAM

For information on sizing criteria, see the HP Business Availability Center Database Guide.

Software Requirements - Oracle Server

Support

Level

Database Release Operating System

Version BIT

Set

Certified Oracle 10.2.0.3 Enterprise Edition plus latest criticalpatches

64 BIT Linux Enterprise Edition

Oracle 10.2.0.3 RAC Enterprise Edition plus latest critical

patches


Oracle 10.2.0.4 Enterprise Edition plus latest critical

patches


Oracle 10.2.0.3 Enterprise Edition plus latest criticalpatches

64 BIT Solaris 10

Supported Oracle 9.2.0.8 Enterprise Edition plus latest criticalpatches



patches

32 BIT Windows 2003 Enterprise Edition Service

Pack 2


patches

64 BIT AIX 5L

Oracle 10.2.0.3 Enterprise Edition plus latest criticalpatches

64 BIT HP-UX 11.31


27 of 35 5/28/2012 12:37 AM

Oracle 10.2.0.4 RAC Enterprise Edition plus latest criticalpatches


Note: It is strongly recommended to apply the latest critical Oracle patches per your operating system. For details, consult theOracle documentation.

For information on Oracle Client software requirements, see the HP Business Availability Center Database Guide.

Software Requirements - Microsoft SQL Server

Support

Level

Database Release Operating System Microsoft Data Access

Components (MDAC)

Certified Version BIT

Set

Service

Pack

Microsoft SQL Server2005 Enterprise Edition

32BIT

ServicePack 2

Windows 2003 EnterpriseEdition Service Pack 2

2.8 SP1 Refresh (installedautomatically during server

installation)

Microsoft SQL Server2005 Enterprise Edition

64BIT

ServicePack 2

Windows 2003 EnterpriseEdition Service Pack 2

Supported Microsoft SQL Server

2000 Enterprise Edition

32

BIT

Service

Pack 4

Windows 2000 Enterprise

Edition Service Pack 2

2.5; 2.52; 2.61; 2.62;

2.7 SP1 Refresh

Business Availability Center Component Support Matrixes

Business Process Monitor Support Matrix

For each BPM version, the latest supported VuGen version is mentioned. All previous versions of VuGen are supported as well.

Compatibility

Matrix

HP Business

Availability Center

8.00

HP Business

Availability Center

7.51

HP Business

Availability Center

7.50

HP Business

Availability Center

7.0

BPM 7.52(VuGen 9.1)

√ (Recommended) √ √ √

BPM 7.51(VuGen 9.1)

√ √ (Recommended) √ √

BPM 7.50(VuGen 9.1)

√ √ √ (Recommended) √

BPM 7.0 (VuGen9.0)

√ √ √ √ (Recommended)

QTP SAP R/37.31

√ √ √ √

QTP 9.5 √ √ √ X

QTP 9.1/2 √ √ √ √

QTP 9.0 √ √ √ √

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.


28 of 35 5/28/2012 12:37 AM

* Indicates new protocols that were added in 7.0.

** Indicates new protocols that were added in 7.50.

Protocol Windows Solaris

.NET * √ X

AJAX * √ √ (ActiveX is not supported)

C VUser √ √

Citrix 1.8 √ X

COM/DCOM √ X

CORBA-java √ X

DB2 CLI √ X

DNS √ X

EJB √ X

Flex ** √ X

FTP √ X

IMAP √ X

I-mode √ X

Informix √ X

Jacada √ X

JAVA Record\Replay * √ X

Java VUser √ X

JavaScript VUser √ X

JMS * √ X

LDAP √ X

MSSQL Server √ X

Multi protocol Web √ √

ODBC √ X

Oracle (2-tier) √ X

Oracle NCA √ X

PeopleSoft - 8 √ √

POP 3 √ X

RDP * √ X

Real √ X

RMI-java √ X

SAP Click and Script * √ √

SAP GUI √ X

SAP Web √ √

Siebel - Web √ √

Siebel DB2 CLI √ X


29 of 35 5/28/2012 12:37 AM

Siebel MSSQL √ X

Siebel Oracle √ √

SMTP √ X

SOAP √ X

Sybase CtLib √ X

Sybase DBlib √ X

Terminal Emulation [RTE] √ X

Tuxedo 6 √ X

Tuxedo 7 √ X

VB VUser √ X

Voice XML √ X

WAP √ √

Web [HTTP/HTML] √ √

Web Click and Script √ √

Windows sockets √ X

Business Process Monitor Changes

Business Process

Monitor Version

Changes

7.52 Fix to the Citrix protocol replay mechanism, which improves the way the color quality andresolution are set during a Citrix session. This is essential to certain applications that haveresolution and color depth limitations.

7.51 Fixes for security vulnerabilities pertaining to cross-site scripting attacks

7.50 Compatible with LoadRunner 9.1.Support QTP 9.5Support Business Availability Center for SOA solution.

7.0 Compatible with LoadRunner 9.0.

Starting from BPM 7.50, QTP 9.5 is supported with the following new protocol: Power Builder Add-in

Supported protocols via QTP add-ins:

Web

QuickTest Professional Oracle Add-in (Web-based & Java-based Oracle applications)

QuickTest Professional Add-in for SAP Solutions (Windows-based & Web-based SAP solutions)

QuickTest Professional Siebel Add-in

QuickTest Professional Web Services Add-in

QuickTest Professional PeopleSoft Add-in

QuickTest Professional Java Add-in

QuickTest Professional .NET Add-in

QuickTest Professional Terminal Emulator Add-in

QuickTest Professional Stingray Add-in

QuickTest Professional VisualAge Smalltalk Add-in


30 of 35 5/28/2012 12:37 AM

SiteScope Support Matrix

Compatibility

Matrix

HP Business Availability

Center 8.00


Center 7.50


Center 7.0

SiteScope 10.00 √ (Recommended) √ √

SiteScope 9.5 √ √ (Recommended) √

SiteScope 9.0,9.01

√ √ √

SiteScope 8.x √ √ √

SiteScope 9.01 recommended with BAC 7.01, SiteScope 9.0 recommended with BAC 7.0, SiteScope 8.5 recommendedwith BAC 6.5

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.

1.

System Availability Management Administration which refers to configuring SiteScope in System Availability

Management Administration.

2.

The following table contains compatibility information regarding the above aspects and the various combinations of SiteScope andBusiness Availability Center releases.

1 = Data logging support

2 = System Availability Management support

SiteScope Version Business Availability Center Version

8.00 7.50 7.0x

SiteScope 10.0 1, 2 1, 2 1, 2

SiteScope 9.5, 9.51 1, 2 1, 2 1, 2

SiteScope 9.0, 9.01, 9.02 1, 2 1, 2 1, 2

SiteScope 8.8 8.7, 8.6, 8.5 1 1 1

Real User Monitor Support Matrix

Compatibility

Matrix

HP Business

Availability Center

8.00

HP Business

Availability Center

7.51

HP Business

Availability Center

7.50

HP Business

Availability Center

7.0

Real User MonitorEngine 8.00

√ X X X

Real User MonitorProbe 8.00

√ X X X


X √ √ X


X √ √ X


X √ √ X


31 of 35 5/28/2012 12:37 AM


X √ √ X


X X X √


X X X √

Note: Real User Monitor 7.01 (probe and engine) works only with Business Availability Center 7.01.

DDM Discovery Probe Support Matrix

Compatibility

Matrix


Center 8.00


Center 7.50


Center 7.0

Discovery Probe8.00

√ X X

Discovery Probe7.50

X √ X

Discovery Probe7.0

X X √

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

Section Component Name Fix/Patch Target

HP Business Availability Centerservers operating system

Windows 2003 Standard/Enterprise Server

SP2 and all Microsoft security patches thatwere released through February 2008.

Sun Solaris 9, 10 All recommended patch clusters

HP Business Availability CenterWeb servers

MS IIS 6 (Windows 2003) All Microsoft security patches that werereleased through February 2008.

Apache 2.2.6

Sun Java System WebServer 6.1

SP5

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:

Show Impacting SAP Transports

Show SAP Transport Impact

SAP Transaction Changes

SAP Transport Changes

Business Availability Center for Siebel Component Support Matrix


32 of 35 5/28/2012 12:37 AM

Siebel

Version

Solaris Operating System

Version for Siebel Servers

Windows Operating System

Version for Siebel Servers

Other Operating System

Version (on the Siebel

Servers)

Siebel 7.5.3 Solaris 5.9

SARM on mixedenvironment notsupported

Windows 2000

Siebel 7.7 Solaris 9 Windows 2000

Siebel 7.8(to work withSARM youmust useSARMAnalyzerversion 7.7)

Solaris 9 Windows 2000

Siebel 8.0 Solaris 10 Windows 2003Enterprise Edition

Windows 2003Datacenter edition

IBM AIX 5L version5.3

HP-UX 11i V2

Red Hat EnterpriseLinux 4

Oracle EnterpriseLinux 4

Novell SUSE LinuxEnterprise Server 9

Business Process Insight (BPI) Support Notes

Note the following limitations when deploying BPI:

BPI is only available on the Windows platform (that is, the BPI Server only runs under the Windows OS)

BPI requires either a Microsoft SQL 2005 or Oracle database (it will not work with a Microsoft SQL 2000 database)

TransactionVision Integration Notes

When running TransactionVision components together with Business Availability Center and/or Business Process Insight and/orDiagnostics, 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 (ifinstalled) 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


33 of 35 5/28/2012 12:37 AM

Matrix

Integration Matrix Integration Type HP Business Availability

Center 8.00


Center 7.50


Center 7.00

Service Manager

7.02

IncidentSubmission

√ √ X

Problem Isolation √ √ X

EMS (Dashboard,

SLM)

√ (SiteScope 10.00) √ (SiteScope 10.00) √ (SiteScope 10.00)

Service Manager

7.01

IncidentSubmission

√ √ X

Problem Isolation X X X

EMS (Dashboard,SLM)


ServiceCenter

6.26

IncidentSubmission

√ √ X

Problem Isolation √ √ X

EMS (Dashboard,SLM)


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.

Support

You can visit the HP Software Support Web site at:

http://www.hp.com/go/hpsoftwaresupport

This web site provides contact information and details about the products, services, and support that HP Software offers.

HP Software online software support provides customer self-solve capabilities. It provides a fast and efficient way to accessinteractive technical support tools needed to manage your business. As a valued support customer, you can benefit by using thesupport site to:

Search for knowledge documents of interest

Submit and track support cases and enhancement requests

Download software patches

Manage support contracts

Look up HP support contacts

Review information about available services

Enter into discussions with other software customers

Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support

contract. To find more information about support access levels, go to the following URL:

http://h20230.www2.hp.com/new_access_levels.jsp

To register for an HP Passport ID, go to:


34 of 35 5/28/2012 12:37 AM

http://h20229.www2.hp.com/passport-registration.html

Legal Notices

© Copyright 2005 - 2009 Mercury Interactive (Israel) Ltd.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and

12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensedto 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 andservices. 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.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Intel®, Pentium®, and Intel® Xeon™ are trademarks of Intel Corporation in the U.S. and other countries.

Java™ is a US trademark of Sun Microsystems, Inc.

Microsoft®, Windows®, Windows NT®, and Windows® XP are U.S registered trademarks of Microsoft Corporation.

Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.

Unix® is a registered trademark of The Open Group.

© Copyright 2009 Mercury Interactive (Israel) Ltd.


35 of 35 5/28/2012 12:37 AM

hp business availability center 8

Documents

fcmdb codebase genericdbadapter meta

fcmdb codebase genericdbadapter

latest critical patches

business availability center

hp passport id

generic db adapter

business process insight

service level management