Importing data from BMC Atrium CMDB (Deprecated)

You can import configuration items (CIs) and relationships from BMC Atrium Configuration Management Database (BMC Atrium CMDB) into BMC Remedyforce CMDB 2.0 by using Atrium Integrator with a customized Pentaho package. The Pentaho package is available on the BMC Communities website.

The following topics provide information about importing data from BMC Atrium CMDB into BMC Remedyforce CMDB:

• • Before you begin
  • To import CIs from BMC Atrium CMDB
  • To import relationships from BMC Atrium CMDB
  • To schedule import jobs from the Atrium Integrator Console
  • KJB and KTR files for importing data from BMC Atrium CMDB
  • Related topics

Before you begin

 Before you can import data from BMC Atrium CMDB into BMC Remedyforce CMDB, you must perform the following tasks:

• Install Java Runtime Environment (JRE).
• Register at the BMC Communities website.
• Create a Log Files folder at the root level of the drive on which the BMC Remedy Action Request System (BMC Remedy AR System) server is installed.
  For example, if you have installed the BMC Remedy AR System server on the C: drive, create a C:\Log Files folder.
• Download the Pentaho package from the BMC Communities website (https://communities.bmc.com/docs/DOC-28437).
  The files in the Pentaho package are customized to be used in Atrium Integrator. For information about the KJB (job) and KTR (transformation) files that are included in the Pentaho package, see KJB and KTR files for importing data from BMC Atrium CMDB.

To import CIs from BMC Atrium CMDB

1. Log on to BMC Remedy AR System and access the Atrium Integrator Console.
2. To launch the Atrium Integrator Spoon, click .
3. To create a new folder in Atrium Integrator to store your KTR and KJB files, perform the following actions:
   1. Go to Tools > Repository > Explore.
   2. Right-click the window, and select New Folder.
   3. Enter a name for the folder in which you want to save the KTR and KJB files that you have downloaded from the BMC Communities website, and click OK.
      For example, create a folder called Remedyforce.
4. To save the KTR and KJB files in the folder, perform the following actions for each file:
   1. Click File > Open URL and browse to the folder in which you have saved the job files that you downloaded from the BMC Communities website.
   2. Open the KJB and KTR files for the required CI type, such as computer system.
   3. Click File > Save As.
   4. In the Directory field, click .
   5. Click OK.
5. In the KJB file, double-click the AtriumtoCMDB_<CI type> step.
   For example, double-click the AtriumtoCMDB_ComputerSystem step.
6. In the Job entry details for this transformation window, in the Specify by name and directory option, click , and select the KTR for the opened KJB file from the folder that you have created.
   For example, Remedyforce > AtriumToCMDB_ComputerSystem.ktr.
7. Click File > Open, and open the required KTR file.

8. In the KTR file, enter the information to access BMC Remedy AR System, the SQL server that BMC Atrium CMDB uses, and your Salesforce organization.

   Click here to see the detailed steps.
9. To save the KTR and KJB files, click .
10. Navigate back to the Atrium Integrator Console.
11. Select the job that you have set up, and click . 
    While the data is being imported, the following log files are generated:
    
    • Job-level logs: Created in the Atrium Integrator Console.
    • Success, process, and error logs: Created as CSV files in the Log Files folder that you created before importing CIs from BMC Atrium CMDB. For more information, see Before you begin.
      The failure log is created only if an error occurs in inserting a record in BMC Remedyforce. The delta_value log stores the time stamp of the last time you imported data. Rejected logs are also created if records with blank unique identifier values exist.
      For the imported records, the Source field is set to Atrium. You can use the Source field to generate reports and also when you enable and configure reconciliation.

To import relationships from BMC Atrium CMDB

Before importing relationships from BMC Atrium CMDB, perform all the actions listed in Before you begin and import all the CIs from BMC Atrium CMDB.

1. Log on to BMC Atrium Action Request System and access Atrium Integrator Console.
2. To launch the Atrium Integrator Spoon, click .
3. To save the KTR and KJB files in the folder on Atrium Integrator, perform the following actions for each file:
   1. Click File > Open URL and browse to the folder in which you have saved the job files that you downloaded from the BMC Communities website.
   2. Open the AtriumtoCMDB_BaseRelationship.kjb and AtriumtoCMDB_BaseRelationship.ktr files.
   3. Click File > Save As.
   4. In the Directory field, click .
   5. Click OK.
4. In the KJB file, double-click the AtriumtoCMDB_BaseRelationship step.
5. In the Job entry details for this transformation window, in the Specify by name and directory option, click , and select the AtriumtoCMDB_BaseRelationship.ktr from the folder where you have saved the KTR file.
6. Click File > Open, and open the AtriumtoCMDB_BaseRelationship.ktr file.

7. In the AtriumtoCMDB_BaseRelationship.ktr KTR file, enter the information to access BMC Remedy AR System, the SQL server that BMC Atrium CMDB uses, and your Salesforce organization.

   Click here to see the detailed steps.

8. If you have created custom relationships in the database used by BMC Atrium CMDB, perform additional actions.

   Click here to see the detailed steps.

   1. In Salesforce, navigate to Setup > Create > Objects.
   2. In the Label column, click Base Relationship.
   3. In the Custom Fields & Relationships section, click Type.
   4. On the Base Relationship Custom Field Type page, in the Picklist Values section, click New.
   5. Enter the name of the BMC Atrium CMDB custom relationship, and click Save.
   6. Repeat step 8d and step 8e for all custom relationships that you are importing.
   7. Navigate to the Atrium Integrator Spoon.
   8. In the AtriumtoCMDB_BaseRelationship.ktr file, double-click the Read Response Variable step.
   9. Copy and paste the last "else if" statement.
      For example, else if(endsWith(ClassIdUpper,"BMC_SETTINGOF")){TypeScript="Setting Of";}
   10. Replace the first class string with the class ID of the custom relationship and the second text string with the value that you have added in the Type field, and save the step.
       For example, say that you are importing the mobile custom relationship type from BMC Atrium CMDB and in the Type field, you have added the Atrium Mobile value. In the Read Response Variable step, replace the text strings with the following text:
       
       else if(endsWith(ClassIdUpper,"MOBILE")){TypeScript="Atrium Mobile";}
       Ensure that the first text string is in uppercase. In this statement, ClassIdUpper is the name of the custom relationship in BMC Atrium CMDB, and TypeScript is the value that you have entered in the Type field.
   11. Repeat step 8i and step 8j for all custom relationships that you are importing.
9. To save the KTR and KJB files, click .
10. Navigate back to the Atrium Integrator Console.
11. Select the job that you have set up, and click .
    While the data is being imported, the following log files are populated:
    • Job-level logs: Created in the Atrium Integrator Console.
    • Success, process, and error logs: Created as CSV files in the Log Files folder that you created before importing CIs from BMC Atrium CMDB. For more information, see Before you begin.
      The error log is created only if an error occurs in inserting a record in BMC Remedyforce. The delta_value log stores the time stamp of the last time you imported data. Rejected logs are also created if records with blank unique identifier values exist.

To schedule import jobs from the Atrium Integrator Console

1. Go to the Atrium Integrator Console.
2. Save the combined job KJB files in the Atrium Integrator folder in which you saved the KJB and KTR files for CIs and relationships.
3. In the KJB and KTR files for all the CIs, provide the information required to access the BMC Remedy AR System, SQL database used by BMC Remedy AR System and your Salesforce organization.
    For more information, see To import CIs from BMC Atrium CMDB and To import relationships from BMC Atrium CMDB.
4. Schedule the jobs (the combined job KJB files) in the following sequence:
   • AtriumToCMDBComputerSystem&Hardware
   • AtriumToCMDBComputerSystem&SoftwareServer
   • AtriumtoCMDB_BaseRelationship

KJB and KTR files for importing data from BMC Atrium CMDB

The Pentaho package contains job (KJB) and transformation (KTR) files that are created in the Pentaho Data Integration tool. The KJB files (jobs) and KTR files (transformations) store metadata in XML format. A KJB file contains a series of transformations that are run in a sequence. A KTR file contains a single transformation. The KJB (job) files retrieve data from external sources into BMC Remedyforce CMDB.

For information about the KJB and KTR files in the Pentaho package for BMC Atrium CMDB, see KJB files in the Pentaho package and KTR files in the Pentaho package.

KJB files in the Pentaho package

The Pentaho package includes different KJB (job) files for importing different types of CIs, such as computer systems and LAN endpoints, from BMC Atrium CMDB. These job files are bundled with related files and provided to you in folders. The folder names correspond to CI types in BMC Remedyforce CMDB.

The following table provides information about the job files that you must run to import specific CI types to BMC Remedyforce CMDB:

KTR files in the Pentaho package

Each KJB file (job file) that is provided for importing data from BMC Atrium CMDB contains the following steps:

• Start
• AtriumToCMDB_<CI type>

The AtriumToCMDB_<CI type>.ktr file (AtriumToCMDB_<CI type> step) contains the following steps to import data from BMC Atrium CMDB.

Related topics

Overview of how is data imported in BMC Remedyforce

Applying-models-while-importing-CIs-and-assets

Troubleshooting-common-issues-when-importing-data

Known-and-corrected-issues-for-Pentaho-packages