Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

This section describes the considerations and steps to migrate a service model from an environment that does not employ BMC Atrium CMDB, to an environment that does employ BMC Atrium CMDB.

Migrating from non Atrium CMDB SIM to BMC Atrium CMDB SIM

When you have implemented service impact management without the BMC Atrium CMDB product and now want to use the BMC Atrium CMDB to store and manage service components and their relationships, you can migrate service model data to BMC Atrium CMDB by using the sim2cmdb tool. The sim2cmdb tool facilitates the migration of a non BMC Atrium CMDB service impact management implementation to a solution where BMC Atrium CMDB stores and manages service components and their relationships. The sim2cmdb tool populates the BMC Atrium CMDB with service model data from Infrastructure Management.

Service impact management without the BMC Atrium CMDB product means that you have created component instances and relationships directly in Infrastructure Management by using Direct Feed (through Product Short, mposter CLI command, or rules) or by using Direct Publish (a BAROC source file and the pposter CLI command) or that you are using a third-party database for service model data.

Migrating SIM data that originates from a third-party source

If you have a third-party repository for your service model, you do not have to use the sim2cmdb tool to copy it into the BMC Atrium CMDB. It is probably more efficient to import this data into the BMC Atrium CMDB directly from the third-party repository than to use the data in the cell as the interface between these two repositories. After the initial model is imported into the BMC Atrium CMDB, BMC recommends that you make further changes to the model directly in the BMC Atrium CMDB. sim2cmdb is intended as an upgrade tool to be used when the main repository of service impact management data is actually the cell; it is not a way to keep a third-part repository in sync with the BMC Atrium CMDB.