Mercury Business Availability Center 6.1 Readme

This file provides the following information about Mercury Business Availability Center 6.1:

Additional Reading

Mercury Business Availability Center 6.1 Limitations and Release Notes

Backward Compatibility

Support Matrixes

Additional Reading

For details on deploying, upgrading, and getting started with Mercury Business Availability Center, refer to the documents located in the Deployment_Documentation directory on the Mercury Business Availability Center Setup CD-ROM.

For complete information on deploying, administering, and using Mercury Business Availability Center, refer to the Mercury Business Availability Center Documentation Library, available from the following locations:

  • Documentation\doc_lib directory on the Mercury Business Availability Center Documentation and Utilities CD-ROM
  • Mercury Business Availability Center Help menu, available after installation
  • Mercury Customer Support Web site

For details on recommended reading before Mercury Business Availability Center deployment, refer to Getting Started with Mercury Business Availability Center.

For details on system requirements for Mercury Business Availability Center server installation and on the ports used by Mercury Business Availability Center, refer to Deploying Servers. For details on system requirements for other Mercury Business Availability Center components, refer to the appropriate section in the Documentation Library.

For information on new Mercury Business Availability Center features, refer to the What's New in Mercury Business Availability Center 6.1 document, available from the Mercury Business Availability Center Help menu after server installation, and from the Documentation\ whatsnew directory on the Mercury Business Availability Center Documentation and Utilities CD-ROM.

NOTE: Check the Mercury Customer Support Web site on a regular basis for posted updates to the Documentation Library. To ensure that the most updated Documentation Library is always available from within Mercury Business Availability Center, enable the Web-based Documentation Library feature. For details, refer to Getting Started with Mercury Business Availability Center.

Mercury Business Availability Center 6.1 Limitations and Release Notes

General

Server Deployment and Maintenance

Mercury Business Availability Center Upgrade

Business Process Monitor

SiteScope

Client Monitor

Real User Monitor

Platform Administration

CMDB Administration

Monitor Administration

Service Level Management

Dashboard

Reports and Reporting Framework

Documentation Library

I18N

General

  • Tomcat sometimes (rarely and randomly) fails to retrieve JSPs or tags due to a stream closed exception. In such cases, a stream closed error message will be displayed when attempting to work with Mercury Business Availability Center 6.1. The situation resolves itself within a short period of time (up to a few minutes).
  • If the password used to access Mercury Business Availability Center includes an exclamation point (!), you cannot access any functionality related to the Script Repository, including the Script Repository itself and working with transaction monitors in Monitor Administration.
  • Workaround: Change the password you use to access Mercury Business Availability Center.

Server Deployment and Maintenance

  • For assistance with capacity planning for your Mercury Business Availability Center installation, contact your Mercury representative.
  • The LDAP database on the Centers Server requires manual intervention for failover.
  • You cannot install Mercury Business Availability Center 6.1 to a machine on which any component of Mercury Diagnostics is installed.

Mercury Business Availability Center Upgrade

  • Mercury Business Availability Center 6.1 supports upgrade from the following versions: Topaz 4.5 FP2; Mercury Business Availability Center 5.0, 5.0 FP1, 5.1 SP1 and 6.0. There is no upgrade for Real User Monitor.
  • If you are upgrading the HP Systems Insight Manager (SIM) source adapter to Mercury Business Availability Center 6.1, some machine and device items that do not have an IPAddress property may not pass the upgrade. If you receive a warning on this, you should rollback the upgrade, define the IPAddress property for each relevant item in the previous version, and run the upgrade again.
  • Empty Mercury Business Availability 5.x Dashboard views are not upgraded to Mercury Business Availability Center 6.1. If required, create a new view directly in Mercury Business Availability Center 6.1.
  • Changes to the default values of the Must and Weight parameters for Business Profile transactions in Mercury Business Availability Center 5.x Dashboard views are not upgraded to Mercury Business Availability Center 6.1. Redefine the values in the upgraded Mercury Business Availability 6.1 view.
  • A 5.x Dashboard view that includes a dynamic element twice, once as a root item and once as a non root (child) item, will be upgraded to Mercury Business Availability Center 6.1, but the upgraded root item (CI) is not displayed in the Mercury Business Availability 6.1 instance view. Only the upgraded non root CI is displayed.
  • If a default Mercury Business Availability Center 5.x dimension is deleted, it is still upgraded to a Mercury Business Availability Center 6.1 KPI. If required, delete the KPI manually from Mercury Business Availability Center 6.1.
  • The manual data upgrade procedure can occasionally lose its session, causing it to complete without upgrading the configuration data. In such a case, the entities listed on the Manual Data Upgrade page will still be shown as not having been upgraded. Refresh the Manual Data Upgrade page and repeat the upgrade procedure.
  • The Service Level Management upgrade process sets all SLAs to a daily aggregation (that is, a daily tracking period). If you are upgrading many SLAs, it is not recommended to change this granularity to the hourly tracking period for all SLAs whose start dates fall in the past three month period. Changing the tracking period could cause the SLM aggregation table to become inflated (that is, to increase to more than one hundred million rows).
  • Avoid changing the tracking period, but if it is necessary, use one of the following:

    • Set the SLAs start date to occur after the upgrade process has finished recalculating the SLAs.
    • Create additional partitions with the Partition Manager for the historical data (you may need to consult with Mercury Customer Support).
  • The first occurrence of a version 6.1 upgraded event can be earlier than the first occurrence of the same 5.1 event. For example, if the SLA in version 5.1 has a start limit date of 1/1/05 3:00 AM and an offset of 2:00 AM, in version 6.1 the first occurrence is at 1/1/05 at 2:00 AM. This is because the upgrade process concatenates the start limit date and time and the event's time offset to one value. To change the start time of the event, after the upgrade process, edit the SLA.
  • Following custom report upgrade, verify that all Service Level Management components in custom reports have successfully upgraded. If any components have failed to upgrade, you must delete them, otherwise scheduled reports that include these custom reports cannot be sent.
  • Real User Monitor items included in Mercury Business Availability Center 5.x Dashboard views are not upgraded to Mercury Business Availability Center 6.1. Mercury Business Availability Center 6.1 includes a new RUM model and you must add the required RUM Configuration Items (CIs) to the upgraded views.

Business Process Monitor

  • In order to enable Business Process Monitor to use NTLM authentication for communication with Mercury Business Availability Center or via a proxy server, you must open the <Business Process Monitor root directory>\config\sconn.cfg file for editing and make sure that under each Site# section (where NTLM authentication is required), one or both of the following parameters are set to 1, as required:

Section
Parameter
Description
Default Value
Site#
UseNTLMAuth
Determines whether to use NTLM authentication when communicating with Mercury Business Availability Center. If authentication parameters are defined and this parameter is set to 1, NTLM authentication is used. If this parameter is missing, or set to any value other than 1, basic authentication is used.
0
Site#
UseNTLMProxyAuth
Determines whether to use NTLM authentication when communicating with proxy. If authentication parameters are defined for proxy and this parameter is set to 1, NTLM authentication is used. If this parameter is missing, or set to any value other than 1, basic authentication is used.
0

  • Business Process Monitor does not support WebTrace on Windows XP SP2 platforms. On Windows XP SP2 platforms, traceroute (UDP based WebTrace) is supported. (WebTrace is supported for Windows 2000 or 2003, and Windows XP without SP2.)
  • Do not create a Dynamic Node Factory CI that includes Business Process Monitor transactions; otherwise, if Business Process Monitor transactions are included in the Dynamic Node Factory, two CIs are created in the CMDB for each transaction - one from the adapter, and one from the Dynamic Node Factory.
  • Business Process Monitor registers with Mercury Business Availability Center using http://<Mercury Business Availability Center Core Server name>/topaz, and not with MercuryAM at the end of the URL. You must use this format when creating instances for Business Process Monitor.
  • Large scripts (larger than 10 MB) cannot be uploaded to the database.
  • When running a page component breakdown (from End User Management or Business Process Monitor), the target URL is limited to 144 characters.
  • For Business Process Monitor 6.1 working with QuickTest Professional 9.0, the following additional environments are supported for running QuickTest Professional scripts:
  • QuickTest Professional Web Services Add-in
  • QuickTest Professional Stingray Add-in
  • QuickTest Professional VisualAge Smalltalk Add-in
  • QuickTest Professional PeopleSoft Add-in
  • In the online help accessed from Business Process Monitor 6.1, it states that you should not set the whole Business Process Monitor to run as a specific user, if you plan to run QuickTest Professional scripts. This information is out-of-date - you can set the whole Business Process Monitor to run as a specific user in this case.

SiteScope

  • The SiteScope High availability version is located in the "SiteScopeHA" directory, as follows:
    • Windows version - Windows Components CD-ROM Disc 2
    • Solaris version - Solaris Components CD-ROM Disc 2
    • Linux version - Linux Components CD-ROM

Client Monitor

  • During the Client Monitor uninstall process, any open Web browser windows close automatically.

Real User Monitor

  • Limited persistency between engine restarts:
    • All the data that is currently being processed will be lost.
    • Data that was not yet read from the Real User Monitor probe or data that was processed but not yet sent to Mercury Business Availability Center will not be lost.
  • If the engine crashes, some data may be retransmitted (status is saved every 30 seconds).
  • In case of database connectivity problems on engine startup, the engine may fail to start.
  • Session start time is reported as the end time of the first page in the session.
  • The URL is truncated on events that occur on pages with URLs that contains more the 100 characters.
  • There is no support for session correlation by HTTP headers other than the cookie header. This may cause problems with session correlation for LoadRunner transactions (there is a workaround available in LoadRunner).
  • A server or client IP will not be resolved to a host name the first time the engine encounters it.

Platform Administration

  • When building an event-based alert trigger for a Business Process Monitor or Client Monitor alert, you cannot define multiple triggers.
  • Alert dependencies defined for alerts on Mercury Diagnostics data do not expire even if a time limit is specified.
  • A user who has been granted the permissions role of a Client Monitor Profile Administrator can access Business Process Monitor scripts while in the Script Repository. The same is true for users with Business Process Profile Administrator permissions and Client Monitor scripts.
  • If a script has been added to transaction monitors belonging to more than one profile, and the script is not in the Script Repository, the error message to add the script to the Script Repository appears under each profile. This occurs even after the script has been added to the Script Repository from one of the profiles. You cannot add the script from a second profile because the script cannot be added to the repository more than once.
  • Workaround:

    • Edit a transaction monitor containing the missing script and add the script back to the Script Repository using the link in the error message.
    • For the other profiles, delete the transaction monitors that contain the same missing script.
    • Add the transaction monitors back to the profiles using the existing script from the Script Repository.
    • If the password used to access Mercury Business Availability Center includes an exclamation point (!), you cannot access any functionality related to the Script Repository, including the Script Repository itself and working with transaction monitors in Monitor Administration.
    • Workaround: Change the password you use to access Mercury Business Availability Center.

CMDB Administration

  • If you have a large number of CIs in the Monitors View (over the 50,000 limit), then, when you access the view, it may be empty. In this case, you should use one of the following workarounds:
    • Work instead with the End User Monitors View or the System Monitors View (which together contain all CIs that are in the Monitors View).
    • In View Manager, create new pattern views that define TQLs only for specific monitoring areas. For example, you can create a different pattern view for each SiteScope, by adding conditions to the TQL node definitions.
  • Note the following regarding permissions for CMDB Administration and for service views (defined in Permissions Management):
    • Users must have role Superuser or Administrator in order to have any access to CMDB Administration.
    • Superusers have full viewing and editing rights for all CMDB Administration and for all views.
    • Administrators can only see/edit views (in CMDB Administration and in Dashboard/Dashboard Administration) for which they have specifically been granted permissions.
    • Administrators cannot edit, create, or delete source adapters in CMDB Administration Source Manager.
  • In Discovery Manager, you can view a selected discovery pattern in XML format and make manual changes to the XML file if required. For example, if you want to discover all data pertaining to WebSphere servers but want to change the port number that is used to access the WebSphere servers, you can change this manually in the Pattern Editor. The Configuration files tab in the Pattern Editor contains all the XML files for the selected discovery pattern. To manually edit the XML files of a selected discovery pattern: 
    1. In the Module Manager tab, select the Advanced View dialog box.
    2. Right-click the discovery pattern you want to edit and select Edit Pattern to open the Pattern Editor dialog box.
    3. Click the Source View tab and then click the Configuration files tab at the bottom.
    4. Either double-click the XML file you want to edit or select it and click the Edit button to open the script editor.
    5. Make the required changes.
    6. Click OK to save the changes you have made.
  • When editing a pattern view in View Manager, some relationships that are using complex cardinality conditions cannot be deleted. If this is the case, after deleting the relationships in the view, when you try and save your changes you receive a message that the TQL cannot be saved - you must then cancel the edit operation.
  • 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.
  • When editing the SiteScope source adapter in Source Manager, if you select the Include machines option, then the hierarchy in the Monitors View and System Monitors View (as shown in View Explorer) includes CIs for the monitored machines.
    However, for each appearance of a SiteScope target machine in the view, the child CIs for the machine include all monitors monitoring that machine.
  • This means that:

    • monitor CIs may be duplicated, appearing under multiple instances of a SiteScope target CI.
    • monitor CIs may appear below SiteScope groups to which they do not belong.
  • Do not create a Dynamic Node Factory CI that includes Business Process Monitor transactions; otherwise, if Business Process Monitor transactions are included in the Dynamic Node Factory, two CIs are created in the CMDB for each transaction - one from the adapter, and one from the Dynamic Node Factory.
  • When editing an adapter template in Source Manager, if you add a KPI definition to any CI template, the KPI is attached to all CIs generated by that template, but does not propagate up to the parents of the generated CIs.
  • CITs that have the root_container attribute defined as a key attribute in CI Type Manager, cannot be added to the CMDB through the XML File source adapter.

Monitor Administration

  • When attaching a SiteScope to Monitor Administration, you can enter either an IP address or a DNS name into the Host Name field to identify the SiteScope machine. If you entered an IP address and that SiteScope is synchronized, the value of the Host Name field becomes the DNS name as it is stored in the database. You can edit the SiteScope object and change it back to an IP address.
  • There are three new monitors in SiteScope version 8.1.2. These are the UDDI Monitor, the Oracle 10G Monitor, and the NetScout Monitor. These monitors can report data to Mercury Business Availability Center version 6.1 but cannot be managed in Monitor Administration. If a SiteScope containing these monitors is attached to Monitor Administration for configuration purposes, you cannot edit these monitors, copy/paste their configurations, or perform a Global Replace on the monitors' fields.
  • If the password used to access Mercury Business Availability Center includes an exclamation point (!), you cannot access any functionality related to the Script Repository, including the Script Repository itself and working with transaction monitors in Monitor Administration.
  • Workaround: Change the password you use to access Mercury Business Availability Center.

  • If you are working with Log File Monitors in SiteScope version 7.9.5.x and managing the SiteScope in Monitor Administration, you see a Log File Encoding property that is not available in that version of SiteScope. Entering or editing a value in this field or changing it while performing a Global Replace has no impact on the monitor because the SiteScope does not recognize that field. It was added to later versions of SiteScope.
  • Copying items within the monitor tree from a SiteScope object running on SiteScope version 8.0 or higher to another SiteScope object running on a previous version of SiteScope may cause unexpected errors.
  • Copying items within the monitor tree from a SiteScope object running on one operating system (for example, Windows) to another SiteScope object running on a different operating system (for example, Linux) is not supported.
  • Pasting a container into another container in the monitor tree is not supported.
  • Monitor Administration does not support Dynamic Update preferences for SiteScope. Dynamic Update preferences are supported only when working in a standalone SiteScope. If you work with Dynamic Update preferences, you can add a SiteScope to Monitor Administration for reporting purposes only but do not import configurations when adding the SiteScope.
  • If a SiteScope has been detached from Monitor Administration and unregistered from Mercury Business Availability Center, it is possible to add another SiteScope to Monitor Administration with the same host name. If a second SiteScope has been added with the same host name, it is highly recommended to work only with the new SiteScope and not reattach the old SiteScope. Only one SiteScope profile can report data to Mercury Business Availability Center from a SiteScope server and working with the old SiteScope may cause unexpected errors.
  • If you use a very long string for the name field when adding a SiteScope to Monitor Administration, your browser may get stuck.
  • If you work with a SiteScope using the https network protocol, you can add the SiteScope to Monitor Administration for reporting purposes only. Do not import configurations when adding the SiteScope.
  • SiteScope cannot report data to a Mercury Business Availability Center whose user name or password uses Japanese characters.
  • If there is a change in the way that a SiteScope monitor reports to Mercury Business Availability Center (that is, the monitor changes from status-based to measurement-based-or vice versa-in the Mercury BAC Logging section), historical data cannot be recalculated. To recalculate the historical data, schedule the recalculation task to start exactly at the time that this monitor logging option was changed.

Service Level Management

  • During SLA creation or editing, the Define KPIs page may not display CIs that were added in the previous Select CIs page. To update the display, click the Refresh button in the View Explorer pane.
  • When defining custom report properties for a Service Level Management report in the Custom Report Manager, you can ignore the time period fields as custom reports are always calculated per component.
  • In Service Level Management, you cannot attach more than one PNR KPI (defined in Dashboard) to a configuration item.
  • If the KPI Definition window has not been closed by clicking the OK or Cancel button, Service Level Management does not display the correct objectives for a KPI on the next occasion that the window is accessed.
  • If the location name is changed for a Business Process Monitor after the associated CI has been added to an SLA, the CI is no longer included in the SLA's calculations and the CI's descendants are not displayed in the SLA hierarchy. Furthermore, Service Level Management cannot recalculate the SLA. To prevent this occurring, avoid making changes to the location name of a Business Process Monitor for which SLAs are defined. Also, configure the Business Process Monitor source (in the Source Manager) to use the "Regular" hierarchy structure and not "Transaction/Location."
  • In the SLA Wizard (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 descendant of itself in the original definition in the CMDB. This is because nesting is meaningless in the SLA calculation (Service Level Management cannot calculate a CI using the CI result as a value). If you add such a CI to an SLA, Service Level Management truncates the CI at the point at which the CI appears for the second time in the SLA hierarchy. However, you can add the same CI to an SLA more than once if the CI does not include a descendant of itself. In this case, Service Level Management calculates the CI once only, so the objectives are the same no matter where the CI appears in the SLA hierarchy.
  • A renamed SLA appears under its previous name in some Service Level Management reports and in the SLA Wizard.
  • 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.

Dashboard

  • The Configuration Item Status Alerts engine does not support:
    • upgrading old alerts
    • follow-up of alerts
    • editing notification templates (a notification template is used to format the message that is sent when an alert occurs). Only pre-defined templates are supported.
  • Microsoft MSN Virtual Earth, used with Dashboard Geographical Map, does not support translation into languages other than English. If you want to work in a different language, you can use the maps applet for the Geographical Map supplied with Mercury Business Availability Center; however, this option is not recommended because of the limitations of the maps applet.
  • In the Business Rules Repository, when editing a parameter for a rule, note that changing the value in the Name box actually changes the value of the reference key for the parameter. The reference key is used for the rule calculation in the Business Logic Engine, so changing this value may cause the calculation to fail. The display name for the parameter cannot be edited.
  • In Mercury Business Availability Center 5.1, you could set geographical location (used in the Dashboard Geographical Map) per host, so that the specified location was automatically defined for all items originating from that source. In Mercury Business Availability Center 6.1, geographical location can only be defined individually for each CI (in IT Universe).
  • The Dashboard Geographical Map uses new presentation technology (MSN Virtual Earth) that requires connection to the Internet. If no connection is available, you can switch to the previous applet technology (in this case if the map does not load properly, check that you do not have more than one JRE installed -- you should have only JRE version 1.4.2_08 or later installed).
  • The PNR KPI in Dashboard does not have persistency in case of failure of the Data Processing Server or a system restart. The PNR KPI shows status initialized until the SLA is recalculated, then the PNR value is updated.
  • For Mercury Business Availability Center pages that require applets, the View Explorer right-click menu may not be fully displayed, and you may not be able to access the submenus. This is the case, for example, in the Dashboard Top View and Topology Map tabs. To view the full menu and access the submenus, you can move the pane divider to the right, or move to the Console tab.
  • Mercury Dashboard Ticker cannot be connected to an SSL environment.

Reports and Reporting Framework

  • If a time interval includes the hours when daylight saving time (DST) moves the clock backwards or forwards, Service Level Management reports for the same night ignore one hour. For example, the Fall DST changes the clock from 1:59 AM to 1:00 AM. For a time interval that runs from 22:00 PM to 02:00 AM, Service Level Management calculates the time interval from 22:00 PM to 01:00 AM).
  • You cannot open a report in PDF format if Mercury Business Availability Center has been configured to support basic authentication. To view reports in PDF format, disable basic authentication.
  • Reports in graph format that have been mailed as a PDF attachment can be viewed with Acrobat Reader 7.0 only.
  • Daylight savings time is not supported by scheduled reports.
  • The SiteScope Cross-Performance report, when added to a custom report and sent by e-mail as a scheduled report (with a weekly or longer time period), displays the data on a different time scale than when the same report is viewed directly in the System Availability Management application.
  • The Alert Count over Time report displays incorrect colors in the severity legend.
  • When working in the Cross-Performance Reports page in System Availability Management, if you are running a SiteScope Log File monitor that is monitoring a different machine, then you should select in the Servers list the SiteScope machine running the monitors, and not the monitored machine (the target machine where the log file or database is located).

Documentation Library

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

I18N

  • When inserting non-English characters in the OpenAPI Query Builder, gibberish appears in the Preview pane. Do not use non-English names in the input fields of the OpenAPI Query Builder.
  • Assigning scripts with names that include French characters to a Business Process Monitor profile fails. Do not use French characters in script names.
  • The Page Component Breakdown report does not support URLs that include multibyte characters.
  • When defining alerts, recipients' names must be in English characters.
  • During alert definition, when editing the command line required to run an executable file (accessed from the Alerts Actions tab), Japanese characters are incorrectly displayed.
  • Not all environments were tested for I18N environments. The following environments were tested: Mercury Business Availability Center running on Windows 2000/Windows 2003 using either Oracle Server or MS SQL Server database.
  • When installing Mercury Business Availability Center 6.1 on a machine that includes a French version of IIS, the installation fails if the IIS default site name includes special French characters. Before installing Business Availability Center 6.1 on a French machine, carry out the following steps on the machine:
    • Select Start > Programs > Administrative Tools > Internet Services Manager.
      In the Tree pane of the Internet Information Services window, click the active IIS instance (that is, the default Web site).
    • Right-click the site name with the special French characters and select Properties.
    • In the Properties window, select the Web Site tab and in the Description field, enter the name Site Web par default.
    • Click OK
    • Restart the machine

Backward Compatibility

Dashboard Configuration

Dashboard Application

Service Level Management Configuration

Service Level Management Reports

Real Time Service Level Management

Siebel

EMS

Business Process Monitor

Real User Monitor

Analytics

Auto Correlation (ARCA)

Platform

Dashboard Configuration

  • No direct upgrade from Topaz 4.5 FP2
  • Dashboard has no direct upgrade from Topaz 4.5 FP2 to Mercury Business Availability Center 6.1. Dashboard must first be upgraded to Business Availability Center 5.x. For instructions, contact Mercury Customer Support.

  • User-defined properties of CI will be deleted
  • In CDM 5.0 the user could add any property to the CDM item. In Mercury Business Availability Center 6.1 it will be defined by the CMDB schema, so there might be properties the user added in 5.0 which will not appear in 6.1.

  • Uniqueness of CI can cause unification of CI and objectives
  • The uniqueness of CMDB items in the CMDB is determined according to a predefined set of properties, where each class has its own unique set of properties. In CDM 5.0 however, two elements with exactly the same property values are considered to be different elements. Customers who had different objectives (thresholds) for the same entity in different views, will have only a single objective per entity. This means you cannot set a CI with different objectives in different views since it is considered to be the same CI.

  • Weights are moved from the KPI to the relation level
  • In Mercury Business Availability Center 5.0, weights were properties of the KPI, meaning elements e1 in CDM 5.0 could have two KPIs d1 & d2 with different weights w1 & w2. In Mercury Business Availability Center 6.1, the weights are not kept as properties on the KPI, but are kept as a property in the relation between two elements.

  • Custom rules need to be updated
  • Custom rules will need to be updated since there are API changes, to connect to the model. The logic written in the rules will not change.

  • DNode created items are deleted
  • When moving from Mercury Business Availability Center 5.1 to Mercury Business Availability Center 6.1, all items that were created by a DNode will be lost. Dnodes will start to be rebuilt from samples that arrive to the new system.

  • DB adapter has been removed
  • DB adapter has been removed from the sources since it is not in use.

Dashboard Application

  • Customers tab removed
  • The Customers tab is removed from Dashboard since it is not in use. The context menu item "Show Customer Impact" is removed as well. The user will be able to see customer items in all other tabs.

  • No split screen
  • The user will not be able to see Business Console, Geographical Map and Top View in the same tab. The Top View and Geographical Map will have their own tab and the user can navigate between them without losing context.

  • Limit for the number of items in Top View
  • In Mercury Business Availability Center 6.1 there is a limitation on the maximum number of items that can be shown in the Top View (configurable).

  • No breadcrumbs in Dashboard
  • Breadcrumb navigation is removed since it is being replaced by the tree navigation.

  • Cannot save topology filters in Events tab
  • You cannot save a filter on the topology of the items in the view. However, you can still save a filter on the status of the items in the view.

  • No paging in Events tab
  • No paging is available in the Events tab. The number of events shown in this tab is limited to a value defined in the infrastructure settings.

  • Cannot filter KPIs by applicable Dashboard tab.
  • The KPIs can be filtered by view or by user role (Operations/Business).

Service Level Management Configuration

  • Upgrade from Topaz 4.5 FP2 is done in two stages
  • The first stage upgrades the SLM module to Business Availability Center 5.0 FP1 and cannot be rolled back. The second stage upgrades the SLM module to Business Availability Center 6.1.

  • One logic for all time intervals
  • The logic for an objective is across time intervals (for example, the performance metric cannot be average for 24x7 and percentile for business hours).

  • Reports are based on aggregated data instead of raw data
  • This has the following implications:

    • When defining retroactive downtime, the user is required to recalculate the data.
    • Recalculation can be done only for the previous three months.
    • Changes to the SLA configuration/time intervals take affect only from the moment of the change (unless the data is recalculated).
    • Only calendar time periods are calculated (hour, day, week, month, quarter, and year). The minimum time period granularity is one hour (for example, there is no single value for the past three days).
    • The up-to-date reports are updated at midnight.
  • Business Process Monitor filter options removed
  • You cannot filter Business Process Monitor transactions by multiple locations automatically (you can add a new item with dedicated selectors in IT Universe manually and then use it). Business Process Monitor transactions by group are also not filtered automatically (it is not modeled; you can add a new item with dedicated selectors in IT Universe manually and then use it).

  • Remove support for several downtime definition options:
    • Downtime by specific location-profile no longer supported.
    • No support for group downtimes.
    • No support for "All SLAs" downtime (meaning you cannot define in a single definition stating that all SLAs and their content are in downtime).
  • Logic related changes:
    • There is no custom (UDX) event frequency logic.
    • There is no ability to import thresholds from Monitor Administration to the performance KPI in Service Level Management.
    • There is no ability to import the trimming conditions as defined in Monitor Administration.

Service Level Management Reports

  • Service Level Management scheduled reports are not upgraded/supported
  • There is no support for previous Service Level Management scheduled reports (they will not be upgraded).

    In 5.x a special support/mechanism for Service Level Management scheduled reports existed in a dedicated tab. This support no longer exists in 6.1. To define Service Level Management scheduled reports you use the regular scheduled reports mechanism (based on custom reports).

  • Changes in Service Level Management report customization
  • There is no ability to define a header and footer for a Service Level Management report (can be done as part of a custom report). In addition report customizations are per report and not per SLA.

  • Report format changes
  • The following reports have a different format in 6.1: Executive Scorecard, Availability Snapshot, Performance Snapshot, Availability Over Time vs. SLA, and Availability by Location/Group.

  • Reports do not contain active filters
  • There are no active filters in the reports.

Real Time Service Level Management

  • There is no Service Level Management tab in Dashboard.
  • There is no Service Level Management tab that contains historic and real-time data side by side.

    Instead, in the Reports tab the user can view the SLAs Summary report that contains Service Level Management historical data; the PNR has been moved to the Business Console tab.

  • PNR in Dashboard has at least one hour delay
  • The PNR displayed in Dashboard is delayed by at least one hour (in some cases, up to two hours).

Siebel

  • The Siebel module is not part of 6.1 (it will be available in 6.2).

EMS

  • Cease support for Auto Correlation on EMS data
  • The old ems_type samples are no longer sent. Monitors that use main.config no longer work.

  • Tivoli Event and Metrics monitor changes
    • Tivoli Metrics monitor is no longer a browsable monitor since the measurements selection is done in the Tivoli agent. This means that the Get Counters property is no longer relevant.
    • Tivoli monitor (Event and Metrics) thresholds have been changed.
  • BMC event integration requires BMC agent activation
  • To have BMC event integration, you must install and activate another BMC agent on the SiteScope machine (and not just install it). There is no longer support for the new add-on and old SiteScope (pre-8.0), but there is support for the old add-on and new SiteScope.

  • Error log location change
  • The error log in SiteScope is located in <SiteScope_Home>\logs\EmsMonitors.log instead of in errors.log (as of SiteScope 8.0).

Business Process Monitor

  • New LoadRunner replay can cause different results and settings
  • The upgrade of the LoadRunner replay engine can result in compatibility issues. In previous replay upgrades, script runs show different transaction response times, default setting changes, and so forth.

  • New QuickTest Professional replay can cause different results and settings
  • The release of QuickTest Professional 8.2 could potentially cause the same issues as the new LoadRunner replay.

  • Business Process Monitor adapter brings default topology that cannot be changed
  • Business Process Monitor adapter has two optional topologies: the default is the profile and its transactions, the second also includes a location breakdown of the transactions. The option to retrieve a geographical location topology no longer exists.

  • Upload of scripts is done through Script Repository and not directly to profile
  • Script Repository is used instead of uploading scripts directly to the profiles. This is also relevant for Client Monitor.

Real User Monitor

  • No upgrade to Mercury Business Availability Center 6.1. Upgrade will be part of a service pack on top of 6.1.
  • Transactions are calculated by session
  • Transaction steps must occur in the same session.

  • The engine reports slowest pages instead of slowest components
  • The smallest component in Real User Monitor 6.1 is page and not component like in previous versions.

  • Slowest pages and slowest end users do not need to exceed a predefined threshold to be reported
  • Business Critical Pages (BCP) definition changes
    • BCP matching is done at the application level and cannot be defined on the engine level
    • BCP matching for POST and GET parameter is always order insensitive
    • Secondary components (such as GIFs) cannot be defined as BCP
    • Missing components are not matched against BCP definitions, which prevents defining them as ignored missing components
    • POST and GET parameters that are known as session identifiers are not ignored on BCP matching (only their value is ignored)
  • No auto-discovery of application servers
  • Application server-specific URL handling is disabled by default. Special application server handling can be set by changing the file: <RUM HOME>\conf\resolver\AppServer.xml

Analytics

  • Analytics documentation has been removed from Documentation Library, and can be obtained via Mercury Customer Support.

Auto Correlation (ARCA)

  • Auto Correlation is not part of 6.1. It is removed from the interface and documentation, and will not be included in any subsequent releases.

Platform

  • Aggregation delay is set to 1 hour by default, for all types of data.
  • Remove support for bucket aggregation
  • In 5.x, bucket aggregation is turned off by default (the algorithm is not accurate enough and it causes severe performance issues in the system). In 6.1 the legacy aggregator has been replaced. For these reasons, bucket aggregation is no longer supported in 6.1.

  • Legacy data engine works only on aggregated data
  • Previously, the legacy data engine checked whether aggregation had been calculated before deciding to use raw or aggregated data. Now, the engine assumes that aggregation has been done. In the past, if the aggregator did not work properly, reports would still contain data (although they would take longer to run, since the data engine used raw data). Now, however, reports are empty.

  • Event Reporter Web Service (HTTP Client) is not supported
  • Web Services API (HTTP Client) is no longer supported. Use the new SiteScope EMS Web Service Monitor instead.

Support Matrixes

This section contains the following matrixes:

Supported Environments

Mercury Business Availability Center Component Support Matrix

SiteScope/Mercury Business Availability Center Compatibility Matrix

Security Matrix

Business Process Monitor Protocol Support Matrix

Mercury Diagnostics Support Matrixes

Supported Environments

The following table enables you to compare supported environments.

Component
Brand
Version
Comments
Mercury Business Availability Center Servers - Operating Systems
Windows
Windows 2000 Server/Advanced Server (SP4),
Windows 2003 Standard/Enterprise Server (SP1)
 
Database
Oracle Server
9i, 10g
Oracle 10.2.0.1 is the recommended environment for use with Mercury Business Availability Center. Oracle 9.2.0.6 is a supported environment.
Oracle is supported over Solaris OS (8, 9, 10); Solaris OS environments are 64-bit only; recommended Oracle environments are 32-bit only.
Oracle Client
9, 10
Oracle 10.2.0.1 is the recommended environment for use with Mercury Business Availability Center.
Oracle 9.2.0.6 is a supported environment.
SQL Server
2000 Enterprise (SP4)
Recommended on Windows 2003 Standard/Enterprise Server (SP1)
Supported on Windows 2000 Server/Advanced Server (SP4)
Web Browsers
IE
6, 6 SP1
 
Web Servers
IIS
5, 6
 
Apache
2.0.49
 
Business Process Monitor - Operating Systems
Windows
Windows 2000 Server/Advanced Server (SP4)
WebTrace functionality is not available on Windows XP SP2 because Microsoft has disabled low level socket access as part of the Windows XP SP2 security lockdown.
Windows 2000 Professional (SP4)
Windows XP Professional SP1, SP2
Windows 2003 Standard/Enterprise editions (SP1)
Solaris
Sun Solaris 9 + latest recommended patch cluster
 
Linux
Linux Red Hat 9.0
 
SiteScope - Operating Systems
Windows
Windows 2000 Server/Advanced Server (SP4)
 
Windows 2000 Professional (SP4)
Windows 2003 Standard/Enterprise editions (SP1)
Solaris
Sun Solaris 9, 10 - both with latest recommended patch cluster
Linux
Linux Red Hat 8, 9.0
Linux Red Hat Advanced Server 3, 4
Client Monitor - Operating Systems
Windows
Windows 2000 Server/Advanced Server (SP4)
 
Windows 2000 Professional (SP4)
Windows XP Professional SP1, SP2
Windows 98 SE
Siebel KIT does not run on Windows 98
Solaris
Not supported
 
Linux
Not supported
 
Real User Monitor Probe - Operating Systems
Windows
Not supported
 
Solaris
Not supported
Linux
Linux Red Hat Enterprise 4.0 (RHEL4)
Real User Monitor Engine - Operating Systems
Windows
Windows 2000 Server/Advanced Server (SP4)
 
Windows 2003 Standard/Enterprise editions (SP1)
Solaris
8, 9, 10
For Solaris OS, Solaris 8 and 10 are the recommended environments
Note: From BAC 6.2, the Real User Monitor engine will only be supported on a Windows operating system.
Linux
Not supported
 
Discovery Probe - Operating Systems
Windows
Windows 2000 Server/Advanced Server (SP4)
 
Windows 2003 Standard/Enterprise editions (SP1)
 
Solaris
Not supported
 
Linux
Not supported
 

Mercury Business Availability Center Component Support Matrix

The following table enables you to compare component support for the current and previous Mercury Business Availability Center and Topaz versions (√=supported; X=not supported).

Note that the table is divided into two. The first part lists:

  • Mercury Business Availability Center 6.1
  • Mercury Business Availability Center 6.0
  • Mercury Business Availability Center 5.1 SP1 and 5.0 FP1
  • Mercury Business Availability Center 5.0

The second part lists:

  • Topaz Managed Services 4.5 FP2
  • Topaz 4.5 FP2
  • Topaz 4.5 FP1
  • Topaz 4.5 GA

Compatibility Matrix
Mercury Business Availability Center 6.1
Mercury Business Availability Center 6.0
Mercury Business Availability Center 5.1 SP1 and 5.0 FP1
Mercury Business Availability Center 5.0
BPM 6.1
√
√
√ (only 5.1 SP1 was tested)
Not tested
BPM 6.0
√
√
√ (5.1 SP1 has NTLM enabled by default. This should be included in the instance definition.)
√
BPM 5.1
√
√
√
√
BPM 4.5.2 GA b264
√
√
√
√
BPM 4.5 GA b1166
Not tested
Not tested
√ (Not Siebel)
√ (Not Siebel)
BPM 4.2 GA
Not tested
Not tested
√ (Not Siebel)
√ (Not Siebel)
QTP SAP R/3 7.31
Not tested
Not tested
X
X
QTP 9.0
√ (BPM 6.1)
Not tested
Not tested
Not tested
QTP 8.2
√ (BPM 6.0)
√ (BPM 6.0)
√ (BPM 6.0)
√ (BPM 6.0)
QTP 8.0
Not tested
Not tested
√
√
QTP 6.5
Not tested
Not tested
X
X
QTP 6.0
Not tested
Not tested
X
X
SiteScope 8.1.2
√
Not tested
√ (BAC 5.1 SP1 needs a patch to work with SiteScope 8. To obtain this patch, contact Mercury Customer Support.
Not tested
SiteScope 8.1.1
Not tested
√
√ (BAC 5.1 SP1 needs a patch to work with SiteScope 8. To obtain this patch, contact Mercury Customer Support.
Not tested
SiteScope 8.0 SP2
Not tested
√
√ (BAC 5.1 SP1 needs a patch to work with SiteScope 8.0. To obtain this patch, contact Mercury Customer Support.
Not tested
SiteScope 7.9.5.0
√
√
√
√ (Not Monitor Administration)
SiteScope 7.9.1.0
Not tested
Not tested
√ (Not Monitor Administration)
√
SiteScope 7.9
Not tested
Not tested
√
√
SiteScope 7.8.1.3
Not tested
Not tested
√
√
SiteScope 7.8.1.2 b145
Not tested
Not tested
√
√
SiteScope 7.8.1.0 b109
Not tested
Not tested
√
√
SiteScope 7.8.0.1 b900
Not tested
Not tested
X
X
Real User Monitor 6.1 (Engine and Probe)
√
√ (BAC 6.0 needs a patch to work with Real User Monitor 6.1. To obtain this patch, contact Mercury Customer Support)
X
X
Client Monitor 6.1
√
Not tested
Not tested
Not tested
Client Monitor 6.0
Not tested
√
√
√ (No Client Monitor Recorder - old scripts must be converted.)
Client Monitor 5.0 FP1
√
√
√
√ (No Client Monitor Recorder - old scripts must be converted.)
Client Monitor 5.0
Not tested
√
√
√
Client Monitor 4.5.2
Not tested
Not tested
√
√
Client Monitor 4.5
Not tested
Not tested
√
√

Compatibility Matrix
Topaz Managed Services 4.5 FP2
Topaz 4.5 FP2
Topaz 4.5 FP1
Topaz 4.5 GA
BPM 6.1
Not tested
Not tested
Not tested
Not tested
BPM 6.0
√
√
Not tested
Not tested
BPM 5.1
√
√
√ Needs TMC patch
√ Needs TMC patch
BPM 4.5.2 GA b264
√
√
√ Needs TMC patch
√ Needs TMC patch
BPM 4.5 GA b1166
√
√
√
√
BPM 4.2 GA
√
√
√
√
QTP SAP R/3 7.31
√
√
√
Not tested
QTP 9.0
Not tested
Not tested
Not tested
Not tested
QTP 8.2
Not tested
√ (BPM 6.0)
Not tested
Not tested
QTP 8.0
X
X
X
X
QTP 6.5
√
√
X
Not tested
QTP 6.0
X
X
√
√
SiteScope 8.1.2
Not tested
Not tested
Not tested
Not tested
SiteScope 8.1.1
Not tested
Not tested
Not tested
Not tested
SiteScope 8.0 SP2
Not tested
Not tested
Not tested
Not tested
SiteScope 7.9.5.0
√ (Not Monitor Administration)
√ (Not Monitor Administration)
Not tested
X
SiteScope 7.9.1.0
√ (Not Monitor Administration)
√ (Not Monitor Administration)
Not tested
X
SiteScope 7.9
√
√
X
X
SiteScope 7.8.1.3
√
√
√
X
SiteScope 7.8.1.2 b145
√
√
√
X
SiteScope 7.8.1.0 b109
√
√
√
√
SiteScope 7.8.0.1 b900
Not tested
Not tested
√
√
Real User Monitor 6.1 (Engine and Probe)
X
X
X
X
Client Monitor 6.1
Not tested
Not tested
Not tested
Not tested
Client Monitor 6.0
Not tested
Not tested
Not tested
Not tested
Client Monitor 5.0 FP1
Not tested
√
Not tested
Not tested
Client Monitor 5.0
√
√
√
√
Client Monitor 4.5.2
√
√
√
Not tested
Client Monitor 4.5
√
√
√
√

SiteScope/Mercury Business Availability Center Compatibility Matrix

There are two main aspects of compatibility between SiteScope and Mercury Business Availability Center. The first is data logging which is the process of logging data collected by SiteScope to Mercury Business Availability Center for the purposes of real-time status, reporting, Service Level Management, and so forth. The second aspect of compatibility is Monitor Administration which refers to configuring SiteScope (including deploying monitors) from within Mercury Business Availability Center. The following table contains compatibility information regarding these two aspects and the various combinations of SiteScope and Topaz/Mercury Business Availability Center releases.

1 = Data logging support

2 = Monitor Administration support

 
Mercury Business Availability Center 6.1
Mercury Business Availability Center 6.0
Mercury Business Availability Center 5.1
Mercury Business Availability Center 5.0
Topaz 4.5SP1-4.5SP3
SiteScope 8.1.2
1,2
1,2
1,2
1
1
SiteScope 8.1.1
1,2
1,2
1,2
1
1
SiteScope 8.0.0.2 (8.0 SP2)
1,2
1,2
1,2
1
1
SiteScope 8.0., 8.0 SP1 (see notes)
1
1
1,2
1
1
SiteScope 7.9.5.x
1,2
1,2
1,2
1
1
SiteScope 7.9.1.0
1
1
1
1,2
1
SiteScope 7.9.0.0
1
1
1
1
1
SiteScope 7.8.1.0, 7.8.1.2
   
1
1
1

NOTES:

  • New SiteScope 8.0 monitors (UNIX Resources, Windows Services State, and XML Metrics) are not supported in Mercury Business Availability Center 5.1 Monitor Administration but can be configured by detaching SiteScope, configuring the monitors, and reattaching.  These new monitors will be added to Mercury Business Availability Center 6.0/6.1 Monitor Administration.
  • Support for configuring reports in BAC 5.1 Monitor Administration with SiteScope 8.0 requires a patch for BAC 5.1.
  • SiteScope 8.1.2 is the recommended version for Mercury Business Availability Center 6.1.

Security Matrix

Section
Component Name
Fix/Patch Target
Mercury Business Availability Center servers operating system
Windows 2000 server/Advanced Server
SP4 and all MS security patches that were released up to November 1, 2005.
Windows 2003 standard /enterprise additions)
SP1 and all MS security patches that were released up to November 1, 2005.
Mercury Business Availability Center Web servers
MS IIS 5/6 (Windows 2000/2003)
All MS security patches that were released up to November 1, 2005.
Apache 2.0.49
 

Business Process Monitor Protocol Support Matrix

The following table describes the supported protocols for each platform on which you can install Business Process Monitor (√=supported; X=not supported).

Protocol
Windows
Solaris
Linux
Citrix 1.8
√
X
X
Oracle NCA
√
√
X
PeopleSoft - 8
√
√
√
SAP Web
√
√
√
SAP GUI
√
X
X
Siebel DB2 CLI
√
X
X
Siebel Oracle
√
√
X
Siebel MSSQL
√
X
X
Siebel - Web
√
√
√
Terminal Emulation [RTE]
√
X
X
Tuxedo 6
√
X
X
Tuxedo 7
√
X
X
VB VUser
√
X
X
WAP
√
√
X
Web [HTTP/HTML]
√
√
√
POP 3
√
X
X
SMTP
√
X
X
Java VUser
√
X
X
DB2 CLI
√
X
X
DNS
√
X
X
FTP
√
X
X
IMAP
√
X
X
JavaScript VUser
√
X
X
LDAP
√
X
X
MSSQL Server
√
X
X
Multi protocol Web
√
√
√
ODBC
√
X
X
Oracle (2-tier)
√
X
X
Real
√
X
X
Windows sockets
√
X
X
C VUser
√
√
√
SOAP
√
X
X
Sybase CtLib
√
X
X
Sybase DBlib
√
X
X
COM/DCOM
√
X
X
CORBA-java
√
X
X
EJB
√
X
X
RMI-java
√
X
X
I-mode
√
X
X
Jacada
√
X
X
Voice XML
√
X
X
Informix
√
X
X

Mercury Diagnostics Support Matrixes

This section contains the following matrixes:

Application Server Support

Operating Systems Support

Portal Server Support

Diagnostics Server Support

Diagnostics Lifecycle Probe Support

Virtual Machine Support

E2E Transaction Tracing (RMI only) Support

Browser Support

Oracle 11i Diagnostics

SAP NetWeaver Diagnostics D4.0

Application Server Support

Application servers and support tier for Diagnostics probes:

Application Server
Versions
BEA WebLogic
6.0, 6.1, 7.0SP1-6, 8.1SP1-4, 9.0
IBM WebSphere
3.5, 4.x, 5.1, 6.0
JBoss
3.0.x, 3.2.x, 4.x
Microsoft .NET
1.1, 2.0
Oracle
9iAS, 9.0.2, 9.0.3, 10g(9.0.4), 10g (10.1.2-J2EE 1.3 compliant)
JServ
1.x (For Oracle apps)
SAP Web AS
6.20, 6.40
Sun Java Enterprise System
7.0, 8.1 (check adoption)
Apache Tomcat
4.1, 5.x
ATG Dynamo
5.6.1
Borland ES
5.2.1
Fujitsu Interstage (Japan)
v6.0
Fujitsu Interstage (Japan)
v7
Macromedia JRun
4.x
Sun ONE
6.0, 6.5
TMaxSoft JEUS (Korea)
 

Operating Systems Support

Operating systems and support tier for Diagnostics Probes:

Operating System
Version
HP-UX
11.x 32 bit
HP-UX
11.x 64 bit
IBM AIX
5.x
IBM zOS
1.3 (31 bit platform)
RedHat Linux
v3, v4
Sun Solaris
8, 9, 10
SuSe Linux
8.x, 9.x
Microsoft Windows
2000 SP3-SP4, 2003 SP1
Debian Linux
3.x
HP-UX
10.x
IBM AIX
4.x
IBM zOS
1.4, 1.5, 1.6 (64 bit z-series only 10-15% adoption)
Microsoft Windows
XP

Portal Server Support

The following table lists support for portal servers:

Portal
Version
BEA WebLogic Portal
8.1SP3
SAP Enterprise Portal
6.0 SP2
IBM WebSphere
5.1

Diagnostics Server Support

The following table lists guidelines for hardware requirements for a Diagnostics server. These are tested guidelines but customers' needs may differ based on various factors such as load, network, and so forth.

Platform
Item
Up to 10 Probes
Up to 20 Probes
Up to 50 Probes
Windows
CPU
1x 1.5 GHz
1x 2 GHz
2x 2.4 GHz
Windows
Memory 1
1 GB
2 GB
4 GB
Solaris
CPU
1x Ultrasparc 2
2x Ultrasparc 2
2x Ultrasparc 3
Solaris
RAM
1 GB
2 GB
4 GB
1This is the amount of RAM required on the machine running the Diagnostics Server.

Diagnostics Lifecycle Probe Support

The following table shows tested guidelines for probe requirements. However, customers' needs may differ based on various factors such as load, network, and so forth. Probe tuning is considered advanced configuration and should not be performed without proper training.

Platform
Item
Minimum
J2EE
-Xmx
Recommend an additional 60 MB
J2EE
Disk
200 MB
.NET
Memory
TBD
.NET
Disk
50 MB

Virtual Machine Support

The following table lists the virtual machines that Diagnostics Probe supports.

Platform
Item
BEA JRockit
1.4.2, 1.5
HP JVM
1.3.x
IBM JVM
1.2.2, 1.3.1
Microsoft .NET CLR
1.1, 2.0
Sun JVM
1.2.2, 1.3
Sun JVM
1.4, 1.5

E2E Transaction Tracing (RMI only) Support

The following table lists the supported level for cross RMI tracing. The following combinations have been tested and certified. Since RMI Correlation requires specific support per application server type, if your system includes other JVMs or application server combinations, RMI Correlation may not work. In this case, you should contact the Diagnostics subject experts in Mercury Customer Support.

Application Server
Virtual Machine
Versions
WebLogic 8.1 SP3 to WebLogic 8.1 SP3
Sun JVM and BEA JRockit
Sun JRE 1.4.2
JRockit 1.4.2
WebSphere 5.1 to WebSphere 5.1
IBM JVM
IBM JVM 1.3.1
Tomcat 4.1 to WebLogic 8.1 SP3
Sun JVM and BEA JRockit
Sun JRE 1.4.2
JRockit 1.4.2

Browser Support

Browser
Versions
Support Tier
Microsoft IE
6 SP1
1
Firefox
1.0.6, 1.5 (Beta1)
1

Oracle 11i Diagnostics

The new Oracle 11i Diagnostics v4.0 is based on Diagnostics 4.0 (D4), which is intended for Application Management only, available with the Mercury Business Availability Center integration.

Oracle Application Server
Versions
9iAS Release 1
1.0.2.2
9iAS Release 2
9.0.3
10g
9.0.4
10g Release 2
10.1.2.0.0
10g Release 2 Standard One
10.1.2.0.1
10g Release 2 (patched)
10.1.2.0.2
9iAS Release 1
1.0.2.2

Oracle Application Versions
Details
Oracle 11i E-business Suite 11.5.8 (GA Build)
App Server 9iAS Release 1 , version 1.0.2.2
Client:
Standalone mode: where OC4J uses HTTP protocol with a direct web connection
Embedded mode: where Apache JServ (with mod_ob4j) is embedded within App Server as the web listener. Jserv version 1.x
Oracle 11i E-business Suite 11.5.7
 
Oracle 11i E-business Suite 11.5.9
 

SAP NetWeaver Diagnostics D4.0

The new SAP NetWeaver Diagnostics v4.0 is based on Diagnostics 4.0 (D4), which is intended for Application Management only, available with the Mercury Business Availability Center integration.

Note: The versions of SAP R/3 listed here refer to deployment scenarios where SAP Enterprise Portal and SAP Web AS are connected to the SAP R/3 backend (for cross-tier transaction breakdown features).

Platform
Versions
SAP Enterprise Portal
6.0 SP2
SAP Web Application Server
6.20, 6.40
SAP R/3 4.0B
4.0B
SAP R/3 4.5B
4.5B
SAP R/3 4.6B
4.6B BASIS 4.6B
SAP R/3 4.6C
4.6C BASIS 4.6C
SAP R/3 4.7 (Enterprise)
4.7E BASIS 6.20
ECC (ERP 2004)
BASIS 6.4



Copyright 2006 Mercury Interactive Corporation