Importing data from BMC Atrium Discovery

The following topics provide information about importing data from BMC Atrium Discovery and Dependency Mapping (BMC Atrium Discovery) into BMC Remedyforce CMDB by using the Pentaho Data Integration tool:

For information about how configuration items (CIs) are imported and relationships are created in CMDB 2.0, see Overview of how data is imported into BMC Remedyforce.

Pentaho packages on BMC Communities

The Pentaho packages for importing data from BMC Atrium Discovery are provided on the BMC Communities website. The following table helps you to decide which package to download:

Package to download	Details
https://communities.bmc.com/docs/DOC-28434	Imports CIs from BMC Atrium Discovery and then creates relationships between the imported CIs in BMC Remedyforce CMDB based on the Assembly ID field.
https://communities.bmc.com/docs/DOC-33777	Imports CIs and relationships of Computer System CIs with IPEndpoint, LANEndpoint, OperatingSystem, Processor, and Software Server CIs from BMC Atrium Discovery. This package also sets the HasImpact field value of the relationship records imported in BMC Remedyforce CMDB to Yes.

KJB files in the Pentaho packages

Each Pentaho package includes different job (KJB) files for importing different types of configuration items (CIs), such as computer systems and LAN endpoints. 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. For more information about the KJB files, see Overview of Pentaho packages.

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

KTR files in the Pentaho packages

All job (KJB) files for importing data from specific CI types contain a series of transformations that are run in a sequence. Each transformation maps to a KTR file that is available, along with the KJB file, in the folder for each CI type. The following table provides information about the KTR files and the corresponding transformations that the KJB file for each CI type contains:

For example, the ComputerSystem folder contains the following KTR files:

• CreateInitialTimeStampedFileForADDM(CS).ktr
• TransferADDM(CS)InfoToCMDB.ktr
• StoreADDM(CS)Timestamp.ktr

The following table provides information about the steps that are included in the TransferADDM<CIType>InfoToCMDB.ktr file (Update staging table with ADDM <CI type name> information or Update BE Table With ADDM <CI type name> Information transformation). The Pentaho package runs these steps to transfer data from BMC Atrium Discovery into BMC Remedyforce CMDB. You can view these steps only when you open the KTR file in the Pentaho Data Integration tool.

Before you begin

 Before you can import data from BMC Atrium Discovery, you must perform the following tasks:

• Install Java Runtime Environment (JRE).
• Download the Pentaho Data Integration tool.
• Create the KETTLE_HOME variable to store the location of the Kitchen.bat file. 
• Register at the BMC Communities website.

• Download the appropriate Pentaho package. For more information, see Pentaho packages on BMC Communities. 
  BMC recommends that you download the job files in the folder in which you have unzipped the Pentaho Data Integration tool.

  Note

  If you have already downloaded the Pentaho packages and you also want to import IPv6 records of BMC_IPEndPoint CI types, BMC recommends that you download the latest transformation files from the IPEndpoint folder. 

To import data from BMC Atrium Discovery

1. From the \<PentahoInstallerFolder>\data-integration folder, make a backup copy of the Kitchen.bat file.

2. In the folder that you downloaded from the BMC Communities page, double-click the Common folder, copy the Kitchen.bat file, and paste it into the \<PentahoInstallerFolder>\data-integration folder.
3. To launch the Pentaho Data Integration tool, in the \<PentahoInstallerFolder>\data-integration folder, double-click the Spoon.bat file, and open the appropriate KJB file.
   For example, the TransferADDMLANEndpointInfotoCMDB.kjb file in the LANEndpoint folder.

4. To open the required KTR file, right-click the Update BE Table With ADDM <CI type name> information step, select Open referenced object, and then select Transformation.

5. In the KTR file, double-click the Create CSV URL step.
6. In the script, provide your BMC Atrium Discovery server access details:
   1. Replace <Enter HostName> with the BMC Atrium Discovery server name or the primary IP address of BMC Atrium Discovery.
   2. Replace <Enter UserName> with the BMC Atrium Discovery user name.
      Ensure that you enter the user name and password of a BMC Atrium Discovery system administrator. 
   3. Replace <Enter Password> with the BMC Atrium Discovery password.
   
7. (Optional) To import a fixed number of rows of data, perform the following actions:
   1. Right-click the ADDM input step, and select Edit Step.
   2. In the Text file input window, click the Content tab.
   3. In the Limit field, enter the number of rows that you want to import.
      Enter one additional row value, because one less row is fetched. For example, to fetch 100 rows, enter 101.
   4. Click OK.
8. To provide your Salesforce organization access details, perform the following actions:
   1. Double-click the Upsert into class <CI type name> step.
   2. In the Salesforce Upsert window, enter your Salesforce organization user name and password.

   3. (Optional) To update the predefined mapping between the BMC Atrium Discovery fields and Remedyforce CMDB, click Edit Mapping.
      For more information about mapping, see Overview of how CIs are imported in CMDB 2.0.

      Note

      Starting from January 1, 2016, Salesforce is retiring www.salesforce.com as an API endpoint. To avoid connectivity issues (HTTP Status 404 error), update your Pentaho transformations that connect to https://www.salesforce.com/services/Soap/u/<API version> to https://login.salesforce.com/services/Soap/u/35.0 before the retirement date.
      If you are running the Pentaho package in a Sandbox environment, modify the Salesforce Webservice URL from https://test.salesforce.com/services/Soap/u/<API version> to https://test.salesforce.com/services/Soap/u/35.0 in the updated Pentaho transformation. For more information, see Salesforce API Endpoint Retirement.

   4. (Optional) To verify the connection, click Test connection.
   5. Click OK.
9. (For CMDB 2.0 only) Enter the information required to access your Salesforce organization:
   1. Double-click Salesforce Input[CMDB_Class].
   2. In the Connection section, enter the Salesforce organization access details.
   3. (Optional) To test the connection, click Test connection.
   4. Click OK.
10. (For importing CIs and relationships in CMDB 2.0 only) Enter the information required to access your Salesforce organization:
    1. Double-click the Salesforce Input [BaseRelationship] step.
    2. In the Connection section, enter the Salesforce organization access details.
    3. (Optional) To test the connection, click Test connection.
    4. Click OK.
    5. Double-click the Salesforce Input [BaseElement] step.
    6. In the Connection section, enter the Salesforce organization access details.
    7. (Optional) To test the connection, click Test connection.
    8. Click OK.
    9. Double-click the Upsert into BaseRelationship step.
    10. In the Connection section, enter the Salesforce organization access details.
    11. (Optional) To test the connection, click Test connection.
    12. Click OK.
11. (Optional) If you have enabled the setting to access your Salesforce organization from limited IP addresses, to enable communication between Salesforce and the Pentaho Data Integration tool, perform the following actions:

    1. In Salesforce, navigate to Setup > Reset My Security Token.

       Note

       If you have enabled the improved Setup user interface in your Salesforce organization, navigate to My Settings > Personal > Reset My Security Token. For more information, see http://help.salesforce.com/apex/HTViewHelpDoc?id=admin_setup_improved.htm&language=en_US.

    2. Click Reset Security Token.
       An email message is sent to your email address stored in Salesforce.
    3. In the Password field of the Upsert into class <CI type name> step, append the security token to the password.
       For example, if your password is mypassword and your security token is XXXXXXXXX, enter mypasswordXXXXXXXXX in the Password field.
12. To save the KTR and KJB files, click .
13. Close the Pentaho Data Integration tool.

14. From the folder of the CI type for which you are importing data, double-click the .bat file provided in the folder.
    For example, if you are importing data for Computer System, open the SchedulingComputerSystem.bat file.

    Important

    You must use the .bat file to avoid any errors while importing.

    
    The relationships between the computer system as a source and the product or software server as a destination are not shown in the Configuration Items Explorer, which can show only a limited number of relationships (due to limitations of the Salesforce platform). Displaying relationships between a computer system and product or software server might hide other important relationships between the computer system and other CIs.

User scenario for importing data from BMC Atrium Discovery

David is a member of the Infrastructure team for Downtown Bank, responsible for managing the laptops for ABC project. He signs up for BMC Remedyforce and expects to use the preconfigured, ITIL based incident and problem management processes for managing CIs. Also, David wants to use the CMDB to represent the physical, logical, and conceptual items and to track the relationships between the different CIs. 

Charlotte, a BMC Remedyforce administrator, helps David to import details about ABC team member laptops from BMC Atrium Discovery to BMC Remedyforce CMDB. Charlotte imports the laptop data into BMC Remedyforce CMDB by running multiple jobs from the Pentaho package in the following sequence:

1. To import the operating system, processor, IP EndPoint, and LAN Endpoint data, Charlotte navigates to the CombinedJobs folder and runs the TransferAdvancedADDMinfotoCMDB.bat file.
   After running the job, she opens the Operating System, Processor, IP EndPoint, and LAN Endpoint classes in the Instance Editor and verifies that the entries are correct on the Relationships tab.
2. To import the laptop OS details, Charlotte navigates to the ComputerSystem folder and runs the SchedulingComputerSystem.bat file. Next, Charlotte navigates to the OperatingSystem folder and runs the SchedulingOperatingSystem.bat file. 
   After running the jobs, she opens the Operating System class in the Instance Editor and verifies that the entries are correct on the Relationships tab.
3. To import the laptop software-server details, Charlotte navigates to the CombinedJobs folder and runs the TransferComputerSystemAndSoftwareADDMinfotoCMDB.bat file.
   After running the job, she opens the Software Server class in the Instance Editor and verifies that the entries are correct on the Relationships tab.

Related topics

Importing data to custom attributes

Scheduling jobs to import data

Troubleshooting common issues with importing data