If you plan to use the integration between BMC Atrium Discovery 8.3 and Atrium CMDB, there are some pre-requisites and known issues and limitations that you need to be aware of.

Interaction of BMC Atrium Discovery 8.3 with other BMC data providers BMC Atrium Discovery 8.3 can co-exist with other BMC data providers. In order to prevent duplicated Configuration items (CIs) in the BMC Atrium CMDB Asset dataset BMC recommends that the following minimum product versions when using other data providers in addition to BMC Atrium Discovery. BMC Atrium CMDB 7.6.04 – no patches required. BMC Atrium CMDB 7.6.03 – no patches required. BMC Atrium CMDB 7.6 - recommended Patch 001 and Hot Fix for defect SW00355736. BMC Atrium CMDB 7.5 - recommended Patch 004 and Hot Fix for defect SW00355736. BladeLogic - recommended BladeLogic Server Automation 8.0 SP2 and Hot fixes for SW00355142 and QM001646701. See below for details. BMC Performance Manager (BPM) and BMC Performance Assurance (BPA) – recommended BMC Performance Manager Portal 2.7.00.040. See below for details. BMC BladeLogic Client Automation (BBCA) - recommended BMC BladeLogic Client Automation 8.1.01. See below for details. If you are using BBCA please be aware that there are two known issues that are fixed in BMC BladeLogic Client Automation 8.1.01 . Please see the table below for exact details.

Supported versions of BMC Atrium CMDB

Integrations with the following versions of Atrium CMDB are supported:

• BMC Atrium CMDB 7.6.04 – no patches required.
• BMC Atrium CMDB 7.6.03 – no patches required.
• BMC Atrium CMDB 7.6 – recommended Patch 001 and Hot Fix for defect SW00355736. (Available Now)
• BMC Atrium CMDB 7.5 – recommended Patch 004 and Hot Fix for defect SW00355736. (Available now)

BMC Atrium CMDB

Prerequisites for CMDB synchronization

Before you can synchronize data to BMC Atrium CMDB, you must satisfy the following prerequisites:

1. Extend the CMDB - In order to tightly integrate the two models, it is necessary to store a BMC Atrium Discovery-specific identifier on the corresponding BMC Classes in BMC Atrium CMDB. Additional mainframe-specific classes and relationships are required if you are discovering mainframe systems. The identifier and the mainframe classes and relationships are only present in the default CMDB data model after CMDB version 7.6.03. Versions prior to 7.6.03 require the ADDM Integration Extension and the mainframe discovery extensions.
2. Create the BMC.ADDM dataset - the BMC.ADDM dataset must be manually created in the CMDB before a synchronization is attempted.
3. Create the Job to merge the BMC.ADDM dataset with BMC.ASSET - After the BMC.ADDM dataset has been created, you must then create the job to reconcile it with the BMC.ASSET dataset.
4. Check the BMC.ADDM dataset configuration - When using ITSM 7.0 with a backwards compatibility patch, you also need to ensure that the BMC.ADDM dataset is trusted.

An additional step is required if your Atrium CMDB instance is earlier than: 7.5 patch 004 7.6 patch 001 See Modifying the Reconciliation Rules for more details

After you have performed these steps, you can start synchronizing BMC Atrium Discovery data to BMC Atrium CMDB.

Performance considerations

To obtain the maximum synchronization performance when using CMDB synchronization with BMC Atrium Discovery version 8.2.03 and later, you should consider tuning the database which BMC Atrium CMDB (or BMC Remedy AR System) is using. See the "BMC Remedy AR System Server 7.6 Performance Tuning for Business Service Management" White Paper for more information.

The following sections in the White Paper are particularly relevant:

• Tuning an Oracle server (page 37).
• Best practices for tuning Oracle database servers (page 44).
• Tuning a SQL Server database (page 47).
• Best practices for tuning SQL Server database servers (page 49).

Supported previous versions of Discovery

New installations of BMC Atrium Discovery 8.3 are compatible with the following, previous versions of discovery products:

• BMC Atrium Discovery: 7.5
• BMC Foundation Discovery: 1.6 (upgrade to version 7.5)
• BMC Topology Discovery: 1.6 (upgrade to version 7.5)
• BMC Discovery for zOS: 1.6 (upgrade to version 7.5)

If you are migrating data from prior versions to version 8.3, you must ensure that you have upgraded any prior versions of your Discovery products to BMC Atrium Discovery 7.5.01.03. For more information on migrating your existing data to BMC Atrium CMDB, see Migrating from version 7.5 to 8.3.

Co-existence with other data providers

The following issues exist in other BMC Products that can lead to duplicate CIs in the Atrium CMDB ASSET dataset when reconciling with BMC Atrium Discovery.

All dates mentioned regarding future releases are subject to change. Fixes which are available as hot fixes will be rolled into future patches, so check the latest patch release notes for the defect number to see if the hot fix is already included.

• BladeLogic – recommended BladeLogic Server Automation 8.0 SP2 and Hot fixes for SW00355142 and QM001646701. See below for details.
• BPM/BPA – recommended BMC Performance Manager Portal 2.7.00.040. See below for details.
• BBCA – recommended BMC BladeLogic Client Automation 8.1.01. See below for details.

BladeLogic

BPM/BPA

BBCA