Preparing BMC Atrium CMDB for synchronization

 

You can integrate BMC Atrium Discovery with the currently supported versions of BMC Atrium CMDB, which are 8.1, 8.0, 7.6.04, and 7.6.03. If you are on a version of BMC Atrium CMDB earlier than 7.6.03, you must complete some additional tasks before you can synchronize data with those versions.

Prerequisites

Before you can synchronize data to BMC Atrium CMDB, you must complete the following tasks corresponding to your version of CMDB in the given order:

BMC Atrium CMDB version

Task

Description

Only in versions earlier than 7.6.03

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.

All versions of CMDB

Create the BMC.ADDM dataset

The BMC.ADDM dataset must be manually created in the CMDB before a synchronization is attempted.

All versions of CMDB

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.

All versions of CMDB

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.

Only in versions earlier than 7.6 patch 001 or 7.5 patch 004

Modify the reconciliation rules

The standard reconciliation rules must be modified before running the first reconciliation from BMC.ADDM to BMC.ASSET.

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. For more information, see the following documentation corresponding to your product version:

Applying the ADDM integration extensions

This section is applicable only to CMDB versions earlier than 7.6.03.

BMC Atrium CMDB and BMC Atrium Discovery Integration extensions are supplied as a zipped archive of XML files called extension-423-ADDMIntegration.zip and extension-703-800-Mainframe.zip. You can obtain these from the CMDB Sync page in the BMC Atrium Discovery user interface. The CMDB Sync page is described here. The extensions are required only for versions of BMC Atrium CMDB prior to 7.6.03.

The ADDM Integration extension adds an attribute ADDMIntegrationId) to the BMC_BaseElement class that is used to store a key that ensures the correct CIs in the CMDB are updated when data in BMC Atrium Discovery is updated. The Mainframe extension adds Mainframe-specific classes and relationships. It is only required if you are discovering mainframe systems.

The XML extension files should be extracted from the zipped archive and saved to your local file system.

To apply the integration extension

The extension is applied using the BMC Atrium Extension Loader. The Extension Loader is part of the BMC Atrium Configuration Management Database Maintenance Tool, which is installed with BMC Atrium Configuration Management Database.

Due to a defect in BMC Atrium CMDB, you must run the BMC Atrium Configuration Management Database Maintenance Tool as the same NT user that installed the CMDB. Otherwise, you will get a critical failure related to authentication and the rik.exe executable not being found.

  1. Depending on your environment, perform the following steps to access the Extension Loader:
    • On Windows
      • Atrium CMDB 7.5
        • From <BMC_install_directory>\BMC Software\AtriumCore\<server>\atriumcore, double-click AtriumCoreMaintenanceTool.cmd.
      • Atrium CMDB 7.6
        • From <BMC_install_directory>\BMC Software\AtriumCore\atriumcore, double-click AtriumCoreMaintenanceTool.cmd.
    • On UNIX
      • Navigate to your installation directory and run ./AtriumCoreMaintenanceTool.sh.
  2. Click the Configuration tab.
  3. Select the Run Extensions.
  4. Click Browse to locate and select the extension data file ExtensionLoader.xml that you extracted from the extension-423-ADDMIntegration.zip file.
  5. Click Next.
  6. Provide the following BMC Remedy AR System information, and click Next.
    • User Name: Specify an Administrator user name.
    • Password: Type the password for the Administrator user name.
    • Port Number: If you specified a port number when installing the AR System server, type that number in this field. If the server uses a portmapper to automatically select a port to use, leave this field to the default "0".
    • AR Server Host Name: Type the AR System server on which you want to install the extensions.
      It is recommended that you install the BMC Atrium Discovery extensions on the AR System server which has the administration operations enabled. The configurations on the AR System Group Operation Ranking form determine whether administration operations are enabled on the servers or not. In some cases, these configurations might either not be correctly picked up by the server, or might not be available on the AR System configuration file (ar.cfg) of the server. In such cases, you must:
      • Verify the settings on the AR System Group Operation Ranking form to determine which servers are enabled for administrator operations.
      • Verify the AR System configuration file (ar.cfg) on the corresponding servers to have the correct settings for Disable-Admin-Ops and Server-Group-Member.
      • Restart the servers and verify that the one which support administrator operations is accessible through BMC Remedy Developer Studio.
      • Verify that the host name specified during installation resolves to the correct server, and does not go through a load balancer, or gets routed to a server where administrator operations are disabled.
  7. Click Run.
    An installation summary indicates if the generation succeeded or failed, including a brief reason for the failure, such as "The structure of the XML is not proper. Please ensure tags are closed properly."
  8. For a failure, click View Log to find details.
    1. In the atriumcore_configuration_log.txt window, you can sort by Severity.
    2. Look for SEVERE messages highlighted in red.
    3. Select a message to display the details at the bottom of the window.
  9. To return to the initial generation view, click Done.

For more information about BMC Atrium CMDB extensions, see the documentation for the corresponding version:

Additional Information

If you are having difficulty applying the extension you might like to try the resolution covered in this thread on the BMC Communities site.

 

Creating the BMC.ADDM dataset

Creating a BMC.ADDM dataset provides a dataset into which BMC Atrium Discovery is exported before being taken into the BMC Atrium CMDB. You create the dataset using the BMC Atrium CMDB Reconciliation console. It is recommended that you create the BMC.ADDM dataset on the primary AR System server.

Warning

The dataset you are creating is intended to receive data from only one BMC Atrium Discovery appliance. If your deployment architecture requires that several scanners or consolidator synchronize to the same CMDB, then you must create a separate dataset for each. For example, BMC.ADDM1, BMC.ADDM2, and associated reconciliation jobs.

  1. You can create a dataset from one of two places in the console. Either:
    • From the Identify activity, click Add Dataset Identification Group Association,
      and then click Create Dataset.
    • From the Mid Tier, Open Atrium Core Console -> Applications -> Reconciliation console, click "Create Dataset" option.
  2. Complete the following fields:

    Field

    Description

    Name

    The name for the dataset. Usually set to BMC.ADDM.

    ID

    The system identifier for the dataset. This must match the ID used in the configuration within BMC Atrium Discovery. The default is BMC.ADDM.

    Accessibility

    Set to "Writable".

    DatasetType

    Set to "Regular".

  3. Click Save.

For more information, see the documentation for the corresponding version:

Creating the Identification, Merge and Purge Job

BMC Atrium Discovery exports its data to a staging dataset in BMC Atrium CMDB. The content of this dataset should then be reconciled into the BMC.ASSET dataset. To accomplish this, a new Job must be added in the BMC Atrium CMDB Reconciliation Console. It is recommended that you create the Identification, Merge and Purge Job on the primary AR System server.

To add the Identification, Merge and Purge Job

  1. From the Mid Tier, Open Atrium Core Console > Applications > Reconciliation Application.
  2. Select the Create Standard Identification and Merge Job Icon
  3. Give the Job a meaningful name (for example, "BMC ADDM - Identification, Merge and Purge").
  4. Set the Source Dataset to be "BMC.ADDM".
  5. After the Job is Created, Select "BMC ADDM - Identification, Merge and Purge" job.
  6. Click the "Edit Job" icon.
  7. From the 'Job Editor' window, in the 'Activities' pane, select the 'New' tab.
  8. In the 'New Activity' pane, select Type as 'Purge', Sequence as '700' and provide 'Name' as BMC ADDM - Identification, Merge and Purge.
  9. In the Datasets option below, select Datasets as BMC.ADDM.
  10. Click 'Done'.
  11. Click 'Save' in the 'Job Editor'.

The best practice is to create a precedence group that specifies a precedence for the BMC.ADDM dataset. The value depends on your relative preference for data populated by BMC Atrium Discovery and other data providers to the CMDB. For more information about how precedence groups are configured for version 7.6.00 or later, see the documentation for the corresponding version:

Checking 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. To do this:

  1. Access the Home page from BMC Remedy User or a browser.
  2. Access the Application Administration Console.
  3. Go to the Custom Configuration page.
  4. From Foundation, select Products / Operational Catalogs.
  5. Select Trusted Datasets for Product Catalog and click Open.
  6. Select the BMC.ADDM dataset for Dataset Name and save the record.

Modifying the Reconciliation Rules

This section is applicable only to CMDB versions earlier than 7.5 patch 004 and 7.6 patch 001.

BMC Atrium CMDB version 7.5 patch 004 and version 7.6 patch 001 contain changes to the standard reconciliation rules that are required for successful reconciliation of the BMC.ADDM dataset with the BMC.ASSET dataset.

If you are using an earlier version of BMC Atrium CMDB then the standard reconciliation rules need to be modified before running the first reconciliation from BMC.ADDM to BMC.ASSET.

These are described in the following table:

Class

Rule

Attribute

Replace

BMC_Application

Execution Order 110

Qualification*

Replace
'ApplicationType' != $\NULL$ AND 'ApplicationType' = $ApplicationType$
with
'Name' != $\NULL$ AND 'Name' = $Name$

BMC_SoftwareServer

Execution Order 110

Qualification*

Replace
'SoftwareServerType' != $\NULL$ AND 'SoftwareServerType' = $SoftwareServerType$
with
'Name' != $\NULL$ AND 'Name' = $Name$

BMC_ConnectivitySegment

Execution Order 110

Qualification*

Replace
'ConnectivityType' != $\NULL$ AND 'ConnectivityType' = $ConnectivityType$
with
'Name' != $\NULL$ AND 'Name' = $Name$

How to Modify the Reconciliation Rules in BMC Atrium CMDB version 7.5 and 7.6

  1. From the Mid Tier, Open Atrium Core Console > Applications > Reconciliation Application, and click Standard Rules Editor.
  2. Select the 'Application Type' attribute for the BMC_Application class. Drill down to the 'Application Type' attribute and change it to 'Name'.
  3. Similarly, Select Attribute 'Connectivity Type' for BMC_ConnectivitySegment class. Drill down to the 'Connectivity Type'attribute and change it to 'Name'.
  4. Select the 'SoftwareServerType' attribute for the BMC_SoftwareServer class.
  5. Drill down to the 'SoftwareServerType' attribute and change it to 'Name'.
  6. Click Save.

How to add a Reconciliation Rule for BMC_OperatingSystem

  1. From the Mid Tier, open the Atrium Core Console and navigate to Applications > Reconciliation Application, and then click Standard Rules Editor.
  2. Click the 'Add Rule' Icon on the top-right side of the Standard Rules Editor.
  3. Select Namespace* as BMC.CORE, Class* as BMC_OperatingSystem, Attribute* as "ClassId", and Priority* as "3".
  4. Save the rule.

For more information about modifying reconciliation rules, see the documentation for the corresponding version:

Preparing synchronization to another CMDB

There might be occasions where you have already synchronized data to a CMDB, and you want to push data to a different CMDB. For example, if you are migrating from a development to a production environment for your CMDB, you might want to populate your new CMDB with fresh inventory data, independent of previous experiments you might have performed in the development instance. To synchronize the data to the new CMDB, perform the following steps using continuous CMDB synchronization.

  1. Stop any discovery runs (you can do this by putting the appliance into Maintenance mode).
  2. Stop continuous synchronization (wait for it to finish processing the queue).
  3. Change your configuration to the new CMDB dataset (see Prerequisites).
  4. From the CMDB Sync > Configuration tab, click Test Connectionto the new CMDB dataset.

    Note

    Ensure that the connection is successful before proceeding.

  5. From the Infrastructure > Hosts page, send one or two hosts to the CMDB, and select Actions > Sync with CMDB.
  6. Start continuous synchronization.
  7. Take the appliance out of maintenance mode and restart your discovery runs.

The data is inserted into the new CMDB dataset as your Discovery jobs are executed. BMC Atrium Discovery detects that the data does not exist, and then inserts the data.

Synchronizing data from multiple BMC providers to the CMDB

When multiple BMC providers synchronize data to the CMDB (such as BMC Atrium Discovery, BladeLogic, and BBCA), there is the possibility that BMC_OperatingSystem instances may not be merged during reconciliation.

BMC Atrium Discovery is an agentless discovery tool and, as such, it might retrieve slightly different information than an agent-based product (for example, "SunOS" or "Solaris" for the same server). To eliminate this problem, you can add a fallback reconciliation rule based on ClassId for BMC_OperatingSystem.

Was this page helpful? Yes No Submitting... Thank you

Comments