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:
Note
For information about the BMC Atrium CMDB versions that BMC Remedyforce supports, see Supported browsers, mobile devices, and integrations.
Before you can import data from BMC Atrium CMDB into BMC Remedyforce CMDB, you must perform the following tasks:
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.
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.
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.
If you have created custom relationships in the database used by BMC Atrium CMDB, perform additional actions.
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.
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:
Folder name (CI Type) | Job file | Job description |
---|---|---|
Application | AtriumToCMDB_Application.kjb | Transfers information about the |
ApplicationService | AtriumToCMDB_Application Service.kjb | Transfers information about the |
BusinessService | AtriumToCMDB_Business Service.kjb | Transfers information about the |
Cluster | AtriumToCMDB_Cluster.kjb | Transfers information about the |
ComputerSystem | AtriumToCMDB_Computer System.kjb | Transfers information about the |
Concrete Collection | AtriumToCMDB_Concrete Collection.kjb | Transfers information about the |
Database | AtriumToCMDB_Database.kjb | Transfers information about the |
IPConnectivitySubnet | AtriumToCMDB_IPConnectivity Subnet.kjb | Transfers information about the |
IPEndPoint | AtriumToCMDB_IPEndPoint.kjb | Transfers information about the |
LANEndPoint | AtriumToCMDB_LANEndPoint.kjb | Transfers information about the |
NetworkPort | AtriumToCMDB_NetworkPort.kjb | Transfers information about the |
Offering | AtriumToCMDB_Offering.kjb | Transfers information about the |
OperatingSystem | AtriumToCMDB_Operating System.kjb | Transfers information about the |
Printer | AtriumToCMDB_Printer.kjb | Transfers information about the |
Processor | AtriumToCMDB_Processor.kjb | Transfers information about the |
Product | AtriumToCMDB_Product.kjb | Transfers information about the |
Rack | AtriumToCMDB_Rack.kjb | Transfers information about the |
SoftwareServer | AtriumToCMDB_Software Server.kjb | Transfers information about the |
VirtualSystemEnabler | AtriumToCMDB_VirtualSystem Enabler.kjb | Transfers information about the |
Combined Packages |
|
|
BaseRelationship | AtriumToCMDB_Base Relationship.kjb | Transfers information about relationships in BMC Atrium CMDB. |
Each KJB file (job file) that is provided for importing data from BMC Atrium CMDB contains the following steps:
The AtriumToCMDB_<CI type>.ktr file (AtriumToCMDB_<CI type> step) contains the following steps to import data from BMC Atrium CMDB.
Step | Description |
---|---|
ARInput | Gets time stamp for this package and saves it in the NGIE:Delta form of the BMC Remedy AR System server. |
Table Source | Fetches information from the Microsoft SQL server that is used by BMC Remedy AR System about CIs that are modified after the time displayed in the stored time stamp. When you import data for the first time, all CIs are imported. |
Read Response Variable | Facilitates JavaScript transformations, such as appending or trimming field values. For example, in the BMC Remedy AR System, the value of the Mark As Deleted field is stored as a boolean value (0 or 1); whereas in BMC Remedyforce, the value of the field is stored as True or False. In this step, 0 or 1 is changed to True or False. |
Salesforce Input[CMDB_Class] | Accepts the Salesforce organization access details to fetch the details of the BMC Remedyforce CMDB classes. |
Get CMDB Class ID | Fetches the class ID of the BMC Remedyforce CMDB class for the source record. For example, if the source is a computer system record, it fetches the class ID of the BMC_ComputerSystem class from the BMC Remedyforce CMDB. |
Unique Identify Filter | Removes all records that have a blank unique identifier field and saves the records in a CSV file that is defined in the rejected records as a reference log. |
Salesforce Upsert | Accepts the Salesforce organization access details where you want to save the imported data. This step also displays field mapping between BMC Remedyforce and BMC Atrium CMDB fields. |
Success logging | Stores the rows that are imported successfully. |
Error logging | Stores the error code, error description, error fields, and field values for the rows that are not imported successfully. |
Identify last row in a stream | Fetches the last record from the successfully imported records (sorted by the date they were modified). |
AROutput | Saves the modified date of the record fetched in the Identify last row in a record stream step into the NGIE:Delta form record that correspond to the running KTR. |
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