Moving your CMDB customizations to a new target system

Before you begin

• Download the CMDB utilities.
  To download the utilities, see Working with CMDB utilities in BMC Helix CMDB documentation.

• Make sure that in your source system, all the classes and attributes that you want to migrate were created or modified by using CMDB Explorer in the Atrium Core Console.
  If you have created the classes or attributes manually in the Class form or Attribute form, the classes and attributes are not detected by the migration tools.
   

To migrate customizations by using the Workflow Migration utility

Workflow Migration utility migrates the foundation data, including groups, roles, CMDB, AR System object overlays, and the synchronization of newly added classes or attributes to Asset forms. The utility provides end-to-end automation of entire migration and auto-reconciliation of AR System objects including CMDB class and attribute changes. 
The Workflow Migration utility creates a working directory. The working directory contains several folders such as CMDB, Customizations, and Recon. In these folders, you can find the xml, definitions, and arx files. Use the files to verify the migration.

For information about the Workflow Migration utility, see Migrating customized objects to a new target system in BMC Helix Innovation Suite documentation.

To migrate CMDB customizations, run the workflow migration utility with the parameters stp1, stp2, stp3, and stp8 separately by using the following steps:

1. Perform the following steps to migrate roles and groups:
   1. Run the Workflow Migration utility by using the parameter stp1.
      Workflow migration utility initially exports and deletes all the groups and roles from the target system. It migrates all the groups and roles from the source system to target system. Then, it imports all the groups and roles exported from the target system.
      
   2. In the source system, on the Group and Role form, note down the total count.
      

   3. Migrate roles and groups data, by using the -stp 1 -sngl false parameters in the Workflow Migration utility.
      Example command:
      

      java -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -jar migratecustomizations-21.30.00-SNAPSHOT.jar -hsrc <sourceServer>  -usrc <Source Server login name> -pwdsrc <Source Server password> -psrc <port> -hdest targetServer -udest <Destination server login name>  -pwddest <Destination server password> -pdest <Destination server Port> -o  <path of the working directory> -op migrate -stp 1 -sngl false 
   4. In the working directory, in the logs folder, in the MigrateCustomizations.log file, review the data migration logs and check for any errors.

   5. Validate the migration of group and roles by comparing the total number of groups and roles in the source and target systems. 

      Important

      If out-of-the-box data is added to the target system, the total number of groups and roles in the source and target systems might differ. In this case, verify the specific groups and roles data.

      The following image shows an example working directory and log files:
      

      File	Description
      AllSourceGroups.arx	Contains the list of all the groups exported from the source system.
      AllSourceGroups.log	Contains logs of the import process. Review this file for any errors.
      Groups.arx	Contains the list of all the groups exported from the target system.
      Groups.log	Contains logs of the export process. Review this file for any errors.
      MigrateCustomizations.log	Contains the consolidated logs.

   6. For any failed records, find the root cause of the failure, fix the errors, and then import the groups and roles by using the Data Import Tool.
2. Perform the following steps to migrate the CMDB classes and attributes.
   

   1. Run the Workflow Migration utility by using the -stp 2 -sngl false parameter.
      Example command:
      

      java -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -jar migratecustomizations-21.30.00-SNAPSHOT.jar -hsrc sourceServer  -usrc tester -pwdsrc tester -psrc 0 -hdest targetServer -udest tester -pwddest tester -pdest 0 -o WorkingDirectory -op migrate -stp 2 -sngl false 

      The utility captures snapshots of the source and target CMDB classes and attributes, compares the classes and attributes, and captures the changes to be migrated to the target system.

   2. In the working directory, review the MigrateCustomizations.log file for any errors. 

3. Validate the CMDB classes and attributes migration by running the Workflow Migration utility with -stp 3 -sngl false parameter.
   Example command:
   

   java -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -jar migratecustomizations-21.30.00-SNAPSHOT.jar -hsrc sourceServer  -usrc tester -pwdsrc tester -psrc 0 -hdest targetServer -udest tester -pwddest tester -pdest 0 -o WorkingDirectory -op migrate -stp 3 -sngl false 

   This command compares source and destination systems to check that all the classes and attributes are created properly.

4. Review the MigrateCustomizations.log file for any errors, fix the issues, and then import or create the attributes on the target system by using the Atrium Core Console.

5. Synchronize the Asset Sync UI utility with the Asset forms by running the Workflow Migration utility with -stp 8 -sngl false parameter.
   Example command:
   

   java -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -jar migratecustomizations-21.30.00-SNAPSHOT.jar -hsrc sourceServer  -usrc tester -pwdsrc tester -psrc 0 -hdest targetServer -udest tester -pwddest tester -pdest 0 -o WorkingDirectory -op migrate -stp 8 -sngl false 

   This command initiates the Asset Sync UI utility to synchronize the class and attribute changes to all the Asset forms. For more information about Asset Sync UI utility, see Modifying CMDB classes and synchronizing the data with ITSM applications in BMC Helix CMDB documentation.

To migrate customizations by using Deployment Management Console

Migrating customizations by using the Deployment Management Console involves the following steps:

1. Export the customizations from the source system.
2. Import the customizations to the target system.

For information about the Deployment Management console, see Defining and deploying data and object packages in BMC Helix Innovation Suite documentation.

To export the customizations by using the Deployment Management Console

1. Log in to Mid Tier as an administrator.
2. Select AR System Administration > AR System Deployment Management Console.

3. On the AR System Deployment Management Console page, click Create.The following image shows an example: 

   

4. Specify the details such as package name, version, and description.
5. From the Content Type drop down list, select CMDB.
6. Add the custom and out-of-the-box classes and attributes.
   From the CMDB Object Type drop down list, select one of the following options:
   1. To add a class, select Add Class, click Add.
   2. On the CMDBObject Search Dialog box, select the class name and click Add.
      The following image shows an example:
      
      
      When you select a class, the class with all the attributes are selected for export. You can create a single package for all classes and attributes.
      For example, to migrate data for one tenant at a time, you can create a package for tenant 1, then create another package for tenant 2, and so on.

1. 
   
   1. To add an attribute, select Add Attribute, click Add.
   2. On the CMDBObject Search Dialog box, select the attribute name, and click Add.
      The following image shows an example:
      

1. Click Save.
   A package is created and a package creation message is displayed.
2. Navigate to the Deployment Management Console.
3. To build the package, click Build. 
   After the package is built successfully, the build status changes to Ready for Export.
   The following image shows an example:
   

1. Click Export.
   A ZIP file is downloaded to your local system.  

To import the customizations by using Deployment Management Console

1.  Log in to the target system.

1. Select AR System Administration > AR System Deployment Management Console.

2. On the AR System Deployment Management Console page, click Import.The following image shows an example:

   

3. After the import is complete, click Deploy.
   The package is deployed and the status is changed to Deployed.

1. To check for any errors in import, in the Manage Package menu, click View. 

1. Perform the following steps to run the Asset UI Sync utility.
   1. Check if you have any overlays on the source on the Asset forms.
   2. After you import CMDB class and attribute changes to the target system, check all imported custom CMDB classes and attributes for which UI Asset forms exist in the source system.

1. 
   
   1. To generate UI Asset forms for the imported classes, run the Asset UI Sync utility.
      Asset UI Sync utility uses merge functionality to synchronize class or attribute definitions to the Asset forms.

1. 
   

   1. Verify the changes by using Developer Studio or Mid Tier.
      For information about the Asset UI Sync utility, see Modifying CMDB classes and synchronizing the data with ITSM applications in BMC Helix CMDB documentation.

Where to go from here

Migrating-Remedy-on-premises-to-BMC-Helix-Service-Management-on-premises