Mercury Business Availability Center 6.4 Readme

New customers should install Mercury Business Availability Center 6.1, then install the Mercury Business Availability Center 6.2 add-on, and then install the Mercury Business Availability Center 6.4 add-on.

Mercury Business Availability Center 6.4 includes the content of Mercury Business Availability Center 6.3, so 6.4 can be installed directly on top of 6.2 (it is not necessary to install 6.3).

For upgrade from 4.5.x or 5.1.x, contact Mercury Customer Support.

Mercury Business Availability Center 6.4 Installation

Installation Procedure

Stop the Mercury Business Availability Center service on all servers and confirm the service is stopped.

Stop the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers.

Run the Mercury Business Availability Center 6.4 setup program on all server machines.

When the installation is complete, restart the machine, if requested during installation.

Restart the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers.

Run the Connect to Database tool (Start > Program > Mercury Business Availability Center > Administration > Connect to Database).

Select the database server you use (Oracle Server/MS SQL Server), choose the "Connect to an existing management schema" option, and fill in the database connection parameters. (For details on using the Connect to Database tool, see the Deploying Servers guide.)

Restart the Mercury Business Availability Center service on all servers.

Installation Procedure for Shared CMDB Environment

The following procedure should be performed when Mercury Business Availability Center shares the Mercury Universal CMDB with Mercury Application Mapping. The procedure differs, depending on whether the shared environment already exists (that is, in version 6.2 or 6.3) or is being set up in this version (6.4).

When the shared CMDB environment already exists from previous versions (6.2 or 6.3):

Stop all servers (for both Mercury Business Availability Center and Mercury Application Mapping).

Install Mercury Business Availability Center 6.4 according to the instructions in this readme.

Copy cmdb_shared.jar (part of 6.4) on all servers (Core, Data Processing, Centers) to the following locations:

Core Server: <Mercury_home>\LIB

Data Processing Server: <Mercury_home>\LIB

Centers Server: <Mercury_home>\LIB and <Mercury_home>\AppServer\webapps\site.war\static\mamJars\cmdb

Restart all servers.

When the shared CMDB environment does not exist from previous versions and a new shared CMDB is being installed:

Install Mercury Business Availability Center 6.4 according to the instructions in this readme.

Install Mercury Application Mapping version 6.2 according to the instructions in the Mercury Application Mapping Installation Guide for version 6.2.

Perform the shared CMDB installation on the Mercury Business Availability Center machine. During this installation, you enter details about the Mercury Business Availability Center version 6.4 installation

Copy cmdb_shared.jar (part of 6.4) on all servers (Core, Data Processing, Centers) to the following locations:

Core Server: <Mercury_home>\LIB

Data Processing Server: <Mercury_home>\LIB

Centers Server: <Mercury_home>\LIB and <Mercury_home>\AppServer\webapps\site.war\static\mamJars\cmdb

Mercury Business Availability Center 6.4 Uninstallation

Stop the Mercury 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.

Uninstall Mercury Business Availability Center 6.4 from Start > Settings > Control Panel > Add/Remove Programs. On Windows 2003 Server make sure to check the Show Updates check box in order to display the patch information.

When the uninstall process is complete, restart the machine if requested.

Restart the Web server process (IIS Admin Service for IIS; Apache service for Apache) on all servers.

Restart the Mercury Business Availability Center service on all servers.

Note: When uninstalling Mercury Business Availability Center 6.4 and rolling back to Mercury Business Availability Center 6.2/6.3, make sure to uninstall the 6.4 data collectors as well, and to reinstall the 6.2/6.3 data collectors.

Mercury Business Availability Center 6.4 Content

Bug fixes:

Real User Monitor page configuration should enable "HTTP OR HTTPS" as an option. (eSAR# 25643)

Fixed: Page Component Breakdown data is incomplete for data older than 24 hours. (SR# 1-449092202, eSAR# 26158)

LRDT implementation over database instead of BUS. (SR# 1B-1IIIM5) See below for more information.

Fixed: Cannot see VuGen download in Mercury Business Availability Center Downloads page although it was installed. (SR# 1-21YZTP)

Fixed: Poor Real User Monitor aggregation performance.

Fixed: PDF format Real User Monitor offline scheduled report does not display data in table format. (SR# 1-433486285)

Fixed: Default time ranges in Service Level Management reports are not correct. (SR# 1-442989683)

Add thresholds to the objectives cell for percentile KPIs. (SR# 1-451144883)

Fixed: Scheduling engine does not start. (eSAR# 27085)

Fixed: Limit event occurrence cannot be unchecked. (SR# 177088)

Fixed: Availability is showing above 100%. (eSAR# 25995)

Allow MyBAC to be accessed using different URLs. (eSAR# 26851)

Fixed: BLE sends "test_sample" that is not registered in the MetaData and causes errors in Dispatcher. (SR# 1-219GJ9)

Fixed: Memory leak in Mercury Business Availability Center caused by SiteScope registration. (eSAR# 26862)

MMS HTTPS user creation behind proxy. (eSAR# 25156)

Internal bugs fixes

6.3 content: See readme63.html for details.

New LRDT monitor implementation:

Mercury Business Availability Center 6.4 includes a new implementation of the LRDT (last reported data time) monitor. This monitor extracts the last reported data time of Business Process Monitor, Client Monitor, and SiteScope data collectors, and its result is displayed in SiteScope. The new LRDT monitor solves one of the causes of Mercury Business Availability Center BUS failure. By default, the old LRDT monitor is operational. To switch to the new implementation (recommended), follow the steps below:

Disable the old LRDT monitor:

Open the Mercury Business Availability Center JMX console: http://<server_name>:8080/jmx-console

In the Topaz section, click service=LastReportedDataTime.

Invoke the Stop method.

Configure Mercury Business Availability Center to work with the new LRDT monitor:

Run the following query against the Mercury Business Availability Center management database:

MS SQL Server:

insert into SYSTEM (SYS_NAME,SYS_VALUE) values('LRDTProviderType', 'LRDTSQLImplementation')

ORACLE Server:

insert into "SYSTEM" ("SYS_NAME", "SYS_VALUE") values ('LRDTProviderType', 'LRDTSQLImplementation')

Restart Mercury Business Availability Center.

Configure the timeframe:

By default, the LRDT monitor searches for last reported data within the last 24 hours.

This timeframe can be expanded/narrowed, since it affects the monitor performance - considering the customer's database and its performance. The change can be done by the following procedure:

Add a key to the SYSTEM table:

MS SQL Server:

insert into SYSTEM (SYS_NAME,SYS_VALUE) values('LRDT_TIMEFRAME', <value in seconds>)

ORACLE Server:

insert into "SYSTEM" ("SYS_NAME", "SYS_VALUE") values ('LRDT_TIMEFRAME', <value in seconds>)

Restart Mercury Business Availability Center.

Updated Components

The following updated components are included with Mercury Business Availability Center 6.4:

Client Monitor (Build 170)

The regular expression mechanism was improved to support backslash within a regular expression.

Business Process Monitor (Build 799)

Fixed a bug in the coloring of Siebel transactions in cases where profile ID is greater than 32767.

Real User Monitor probe (v6.4 B2)

Improved performance of full snapshot mode.

Real User Monitor engine (v6.4.0.0 Build 11)

URLs in Real User Monitor were not coupled with protocol (HTTP or HTTPS). Now it can be configured as HTTP* which means it will capture HTTP and HTTPS.
Note that you cannot define an application URL using wildcard for the port as you do in the page definitions. You will need to define two separate URLs, one for each protocol, with the corresponding port to allow RUM monitoring for such applications.

FIXED: When monitoring an environment with many distinct users, the performance of Real User Monitor was reduced

FIXED: The first user name is shown in the session analyzer instead of the last one. This caused the username to be wrong when the user entered wrong username.

Improved connection recovery for the Real User Monitor repository.

Note: Newer versions of the Real User Monitor Engine and probe might be released after Mercury Business Availability Center 6.4. Contact Mercury Customer Support to check whether there are newer versions of these components available for installation.

Real User Monitor Probe Installation

Follow the instructions in the rum_probe_readme.txt file included with Mercury Business Availability Center 6.4. Note that the file is called MercuryBeatboxSetup_linux.bin.

Real User Monitor Engine Installation

Follow the instructions exactly as described below to continue working with your existing Real User Monitor database and engine configuration:

When uninstalling Real User Monitor 6.2:

Make sure the during uninstall both "Mercury Real User Monitor Core Engine" and "Mercury Real User Monitor Database Engine" features are marked for removal.

When prompted whether to delete files remaining in the Mercury Real User Monitor directory, choose NO to keep the configuration.

When installing Real User Monitor 6.4, use the same installation type you used when installing Real User Monitor 6.2 (Typical/Custom).

If you chose the Custom installation type, it is recommended that you install the same products that you installed when originally installing Real User Monitor 6.2.

When prompt whether to create a new schema or connect to the existing schema, choose to connect to the existing schema.

When installation finishes, restart the engine.

Installation for Other Components (Business Process Monitor/Client Monitor)

Stop the component.

Uninstall the previous version.

Install the new version.

Other Notes

If burning Solaris or Linux components onto a CD-ROM for installation purposes, make sure to select a non-Joliet ISO setting.

If burning Mercury Business Availability Center 6.4 files onto a CD-ROM, keep in mind that the complete release will not fit onto one CD-ROM. Divide the files between two CD-ROMs according to your requirements.

When navigating to Mercury Business Availability Center 6.4 pages for the first time after installation, the pages may take some time to load due to .jsp compilation.