Note

 

This documentation supports the 20.15.01 version of BMC Remedyforce.

To view the latest version, select the version from the Product version menu.

Importing data from BMC Atrium Discovery

Note

Starting with the 20.18.01 release, Remedyforce has replaced the older BMC Discovery integration, which required Pentaho, with an improved (API-based, no Pentaho required) integration . This improved integration offers many enhancements including additional classes, relationships and synchronization. It is recommended that you move to the new integration to take advantage of the many new features. To learn more about the differences between the old (Pentaho) integration and the new (API-based) integration, please refer to the Remedyforce and BMC Discovery FAQ documentation.

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 1.0 and 2.0, see Overview of how data is imported into BMC Remedyforce.

Supported versions

The Pentaho packages for importing data from BMC Atrium Discovery support the following versions:

  • BMC Atrium Discovery 9.0, 9.0.2, 10.0, and 10.1
  • BMC Remedyforce CMDB 1.0 and 2.0
  • Pentaho Data Integration Tool 4.4 and 5.0.1

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, based on your version of BMC Atrium Discovery and BMC Remedyforce CMDB:

BMC Atrium Discovery versionBMC Remedyforce CMDB versionPackage to downloadDetails
  • 9.0
  • 9.0.2
  • 10.0
  • 10.1

1.0

https://communities.bmc.com/docs/DOC-21741

Imports configuration items (CIs) from BMC Atrium Discovery and then creates relationships between the imported CIs in BMC Remedyforce CMDB based on the Assembly ID field.
2.0 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.

Best practice

If you have upgraded to CMDB 2.0 and you were using CMDB 1.0 packages, you can continue using the CMDB 1.0 packages. However, for faster imports, BMC recommends that you use CMDB 2.0 packages

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:

Folder name (CI type)Job fileJob description
ComputerSystemTransferADDM(CS)Infoto
CMDB.kjb
Transfers information about the
BMC_ComputerSystem
CI type
OperatingSystemTransferADDM(OS)Infoto
CMDB.kjb
Transfers information about the BMC_OperatingSystem CI type
ProcessorTransferADDM(CPU)Infoto
CMDB.kjb
Transfers information about the BMC_Processor CI type
IPEndpointTransferADDMIPEndpoint
InfotoCMDB.kjb
Transfers information about the BMC_IPEndPoint CI type (both IPv4 and IPv6)
LANEndpointTransferADDMLANEndpoint
InfotoCMDB.kjb
Transfers information about the BMC_LANEndpoint CI type
SoftwareServerTransferADDMSoftwareServer
InfotoCMDB.kjb

Transfers information about the BMC_SoftwareServer CI type.

Note: Depending on the organization size, running the Software Server job transfers large amounts of data to the Salesforce organization, which might lead to the organization storage limit being exceeded.

CombinedJobs
  • TransferAdvancedADDMinfoto
    CMDB.bat
  • TransferComputerSystemAnd
    SoftwareADDMinfotoCMDB.bat
  • TransferAdvancedADDMinfotoCMDB.bat
    This file transfers information related to the BMC_ComputerSystem, BMC_OperatingSystem, BMC_Processor, BMC_IPEndPoint, and BMC_LANEndpoint CI types.
  • TransferComputerSystemAndSoftware
    ADDMinfotoCMDB.bat

    This file transfers information related to the BMC_ComputerSystem and BMC_SoftwareServer 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:

KTR fileTransformation in the KJB file

Description

NoneCheck if Delta timestamp File existsThe Pentaho package utilizes a time stamp file to determine which records were added or modified since the last time the job was run. This step is used for incremental import. If a time stamp file does not exist, the Create the initial timestamp file step is run; otherwise, the Update staging table with ADDM <CI type name> information or Update BE Table With ADDM <CI type name> Information step is run.
CreateInitialTimeStamped
FileForADDM<CIType>.ktr

Create the initial Timestamp file

Records the time of import. This transformation runs only if you are importing for the first time or you have deleted the existing time stamp file.
TransferADDM<CIType>
InfoToCMDB.ktr

Update staging table with ADDM <CI type name>information
(Available only in Pentaho packages for CMDB 1.0)

Transfers data from BMC Atrium Discovery to BMC Remedyforce CMDB 1.0 by using a staging table.

Update BE Table With ADDM <CI type name> Information
(Available only in Pentaho packages for CMDB 2.0)

Transfers data from BMC Atrium Discovery to the Base Element object of BMC Remedyforce CMDB 2.0.
StoreADDM<CIType>Time
stamp.ktr

Store the current timestamp

If the data import is successful, the time of import is saved.
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.

Step

Description

Delta timestamp

Reads the saved time stamp.

Create CSV URL

Creates a URL to query BMC Atrium Discovery to fetch data for the corresponding CI type and accepts the credentials for the BMC Atrium Discovery server.

ADDM input

Uses the URL that is created to query BMC Atrium Discovery and lists the fields that are queried.

Transform ADDM variables

Facilitates JavaScript transformations such as appending or trimming fields.

Salesforce Input[CMDB_Class]
(Available only in Pentaho packages for CMDB 2.0)
Fetches details of the BMC Remedyforce CMDB class from your Salesforce organization and accepts the credentials for the Salesforce organization.

Get Class Name
(Available only in Pentaho packages for CMDB 2.0)

Changes the BMC Remedyforce CMDB class name into uppercase characters to compare it with the class name that is fetched from BMC Atrium Discovery.
Get CMDB Class Id
(Available only in Pentaho packages for CMDB 2.0)
Maps data imported from BMC Atrium Discovery to the appropriate CI class in BMC Remedyforce CMDB.
SortSorts the records that are imported from BMC Atrium Discovery.
Unique rowsChecks that imported records are unique so that duplicate records are not created in BMC Remedyforce CMDB  

Upsert into class <CI type name>

Stores the imported data into the specified CI class and accepts the credentials for the Salesforce organization in which you want to save the imported data.

Success rows

Stores the rows that are imported successfully.

Failure rows

Stores the rows that are not imported along with error code, error descriptions, and error fields.

The following steps in this transformation are available only in the Pentaho package to import CIs and relationships into CMDB 2.0. Also, these steps are available in all jobs in the package, other than the job to import Computer System CIs (TransferADDM(CS)InfotoCMDB.kjb).

Salesforce Input [Base Relationship]Fetches details of the Base Relationship class in BMC Remedyforce CMDB from your Salesforce organization and accepts the credentials for the Salesforce organization.
Stream lookup for <CI type name>Checks if the Base Relationship class stores any relationships with the specified CI type as the destination.
Salesforce Input [BaseElement]Fetches details of the Base Element class in BMC Remedyforce CMDB from your Salesforce organization and accepts the credentials for the Salesforce organization.
Stream lookup for ComputerSystemIdentifies the computer system CIs that are the source of the relationships with the specified CI type.   
Filter rowsIdentifies and filters relationships that already exist in BMC Remedyforce CMDB so that duplicate relationships are not created.
Duplicate BaseRelationshipRecords the relationships that already exist in BMC Remedyforce CMDB.

Upsert into Base Relationships
(Available only in the Pentaho package to import CIs and relationships into CMDB 2.0)

Stores the relationship records in the BMC_BaseRelationship class and accepts the credentials for the Salesforce organization in which you want to store the relationship records that are imported.

This step also sets the HasImpact field value of all relationship records imported in the BMC_BaseRelationship class to Yes.

Base Relationship Upsert Failure RowsStores the rows that are not imported, error code, error descriptions, and error fields.
Base Relationship Upsert Success Rows

Stores the rows that are imported successfully.


Before you begin

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

To import data from BMC Atrium Discovery

  1. From the \pdi-ce-4.x.0-stable\data-integration or \pdi-ce-5.0.1.A-stable\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 \pdi-ce-4.x.0-stable\data-integration or pdi-ce-5.0.1.A-stable\data-integration folder.
  3. To launch the Pentaho Data Integration tool, in the \pdi-ce-4.x.0-stable\data-integration or pdi-ce-5.0.1.A-stable\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, perform one of the following actions based on the CMDB and Pentaho version that you are using:

    CMDB versionPentaho versionAction
    1.04.4Right-click the Update staging table with ADDM <CI type name> information step, and select Open transformation.
    5.0.1Right-click the Update staging table with ADDM <CI type name> information step, select Open referenced object, and then select Transformation.
    2.04.4Right-click the Update BE Table With ADDM <CI type name> Information step, and select Open transformation.
    5.0.1Right-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.
    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 1.0.

      Note

      If you are using an earlier version of the Pentaho data integration tool (for example, Pentaho 4.1 or 4.2), you must change the Salesforce Webservice URL to https://www.salesforce.com/services/Soap/u/20.0.

    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.

Mary, a BMC Remedyforce administrator, helps David to import details about ABC team member laptops from BMC Atrium Discovery to BMC Remedyforce CMDB. Mary 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, Mary 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, Mary navigates to the ComputerSystem folder and runs the SchedulingComputerSystem.bat file. Next, Mary 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, Mary 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 issues with importing data

Was this page helpful? Yes No Submitting... Thank you

Comments