This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Importing data to BMC Atrium CMDB

Populating BMC Atrium Configuration Management Database (BMC Atrium CMDB) includes activities such as importing and filtering data and verifying that each data import is successful. To import data into BMC Atrium CMDB, complete the following procedures:

StepInstruction
Review

Review the source and target system and list of CI and relationships to be migrated.

Migrate

Migrate the CIs and relationships from the production/non-production dataset of the Source system to the non-production (sandbox) dataset of target system.

  • If you are migrating a CI Relationship, you must migrate the Instance ID of the CI and its relationship.
  • If CI/Relationship is associated with an application (for example, ITSM/SRM), you must migrate the Reconciliation ID of both the CI and its relationship

Validate

 Perform post-migration validation.

Reconcile

Reconcile the migrated dataset to the production dataset of the target system.

Recommendations

As you prepare to migrate data from existing sources to BMC Atrium CMDB, consider these recommendations:

  • Examine your data to make sure that data exists in each category of your current classification scheme that is being mapped to a class in BMC Atrium CMDB. Do not waste resources attempting to migrate something that does not exist.
  • Freeze your current classification scheme a few weeks prior to the migration.
  • Test the migration with a representative subset of all the classes you plan to use. For example, import 1,000 computer systems and 1,000 application systems.
  • When testing, verify both that the contents of several configuration items (CIs) were migrated correctly and that the correct number of CIs were migrated for each class.
  • For better performance, take advantage of the multithreaded nature of the BMC Remedy AR System server when loading your initial data into BMC Atrium CMDB. Either use a multithreaded process on your loading application or split the data into pieces that can be loaded by separate instances of your application.
  • If your loading application will do any searching, create indexes on the fields it searches.
  • An easy way to load data from many sources is to create BMC Remedy AR System view forms or vendor forms that point to those sources. You can then use workflow, such as an escalation, to transfer the data from those forms to the BMC Atrium CMDB forms.
  • When importing data from a source such as a spreadsheet or comma-separated value file, you can use a regular BMC Remedy AR System form as an intermediate storage location. This enables you to use qualifications and workflow to verify that the data made it into the BMC Remedy AR System, normalize the text in your data, and route it to the appropriate BMC Atrium CMDB class.
  • If your source data does not include relationships or includes them only as foreign keys on CI records, your loading application should analyze the data and create relationships between appropriate CIs in BMC Atrium CMDB.
  • Your loading application is responsible for normalizing text in the data you bring into BMC Atrium CMDB, such as enforcing capitalization and delimiting rules. Data that has not been normalized is much harder to reconcile.
Was this page helpful? Yes No Submitting... Thank you

Comments