Error: Invalid spaceKey on retrieving a related space config.

Importing data from BMC BladeLogic Client Automation

You can import data from BMC BladeLogic Client Automation into BMC Remedyforce CMDB 2.0 by using the Pentaho Data Integration tool only if the Microsoft SQL Server data source is used in BMC BladeLogic Client Automation. The Pentaho package for importing data from BMC BladeLogic Client Automation is available on the BMC Communities website. 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.

The following topics provide information about importing data from BMC BladeLogic Client Automation into BMC Remedyforce CMDB:

Note

For information about the BMC BladeLogic Client Automation versions that BMC Remedyforce supports, see Supported browsers, mobile devices, and integrations.

Before you begin

Before importing data from BMC BladeLogic Client Automation, you must meet the following requirements:

To import data from BMC BladeLogic Client Automation

  1. To launch the Pentaho Data Integration tool, perform the following actions:

    1. Navigate to the location where you downloaded and unzipped the Pentaho Data Integration tool.

    2. Navigate to the data-integration folder and double-click the Spoon.bat file.

  2. In Pentaho Spoon, select File > Open, navigate to the folder where you downloaded the Pentaho package, and open the appropriate KJB file.
    For example, to import LAN Endpoint CIs into BMC Remedyforce CMDB, open the TransferBBCALANEndPointInfotoCMDB.kjb file in the LANEndpoints folder.
  3. In the KJB file, right-click the Update BE table with BBCA <CI type name> information step, select Open referenced object, and then select Transformation.

  4. Enter the information required to access the BMC BladeLogic Client Automation database.

     Click here to see the detailed steps.
    1. In the KTR file, double-click the BBCA Input step.
    2. Next to the Connection list, click Edit.
    3. In the Database Connection window, enter the host name, database name, user name, and password.
      The host name is the name of the computer where the BMC BladeLogic Client Automation database is installed.

      Note

      If you have configured Windows authentication on the BMC BladeLogic Client Automation database, user name and password are not required.

    4. (Optional) To verify the connection, click Test.
    5. To save your changes and close the window, click OK.
  5. Enter the information required to access your Salesforce organization.

     Click here to see the detailed steps.
    1. Double-click the Upsert into class <CI type name> step.
    2. In the Salesforce Upsert window that opens, enter your Salesforce organization user name and password.
      BMC recommends that you do not change the default API version in the Salesforce Webservice URL.
    3. (Optional) To verify the connection, click Test connection and then click OK.
    4. To save your changes and close the window, click OK.
    5. Double-click the Salesforce Input[CMDB_Class] step and in the Salesforce Input window, repeat step 5b to step 5d.

    Important

    If you have enabled the setting to access your Salesforce organization from limited IP addresses, you must append the security token to your Salesforce organization password.

    For example, if the password for your Salesforce organization is mypassword and your security token is XXXXXXXXX, specify mypasswordXXXXXXXXX in the Password fields.

  6. (Optional) Update the predefined mapping between the BMC BladeLogic Client Automation fields and Remedyforce CMDB.

     Click here to see the detailed steps.
    1. Double-click the Upsert into class <CI type name> step.
    2. In the Salesforce Upsert window, click Edit Mapping.
    3. In the Enter Mapping window, update mappings for fields based on your requirements.
      For information about updating the out-of-the-box mapping, see Field mapping in CMDB 2.0.
    4. To save your settings and close the Enter Mapping window, click OK.

    5. To save your changes and close the Salesforce Upsert window, click OK.
  7. To save the KTR and KJB files, click Save .
  8. In the TransferLDAPInfo.kjb file, click Run this job .
  9. Perform one of the following actions based on the Pentaho version that you are using:

    Pentaho versionAction
    6.1In the Run Options window, click Run.
    5.4In the Execute a job window, click Launch.

    Transformation status is depicted by using the following icons:

    • — Complete
    •   — Running
    • — Unsuccessful
  10. (Optional) To view logs, in the Execution results section, click the Logging tab.
    All errors are displayed in red.

User scenarios for importing data from BMC BladeLogic Client Automation

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 pre-configured, 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. 

John Doe, a BMC Remedyforce administrator, helps David to import details of the laptops provided to the team members of ABC project from BMC BladeLogic Client Automation to BMC Remedyforce CMDB. 

Data to be importedSteps to follow
  • Operating System
  • Processor
  • Person
  • LAN Endpoint
  1. Run the \CombinedJobs\TransferAdvancedBBCAInfotoCMDB.kjb file.
  2. Go to Remedyforce CMDB and verify whether the entries are correct in the Relationships Editor of the following classes:
    • Operating System
    • Processor
    • Person
    • LAN Endpoint
Operating system details of the laptops
  1. Run the \ComputerSystem\TransferBBCAComputerSystemInfotoCMDB.kjb file.
  2. Run the \OS\TransferBBCAOSInfotoCMDB.kjb file.
  3. Go to Remedyforce CMDB and open the Operating System class.
  4. Verify whether the entries are correct in the Relationships section in the Instance Editor of the Operating System class.
Processor details of the laptops
  1. Run the \ComputerSystem\TransferBBCAComputerSystemInfotoCMDB.kjb file.
  2. Run the \Processor\TransferBBCAProcessorInfotoCMDB.kjb file.
  3. Go to Remedyforce CMDB and open the Processor class.
  4. Verify whether the entries are correct in the Relationships Editor of the Processor class.
Software server details of the laptops
  1. Run the \CombinedJobs\TransferComputerSystemAndSoftwareBBCAInfotoCMDB.kjb file.
  2. Go to Remedyforce CMDB and open the Software Server class.
  3. Verify whether the entries are correct in the Relationships Editor of the Software Server class.

KJB and KTR files for importing data from BMC BladeLogic Client Automation

The Pentaho packages contain 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 packages for BMC BladeLogic Client Automation, 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 BladeLogic Client Automation. 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 fileDescription

Computer
System

TransferBBCAComputer
SystemInfotoCMDB.kjb

Transfers information about the
BMC_ComputerSystem CI type.

OSTransferBBCAOSInfoto
CMDB.kjb

Transfers information about the
BMC_OperatingSystem CI type.

Processor

TransferBBCAProcessorInfoto
CMDB.kjb

Transfers information about the
BMC_Processor CI type.

IPEndPoints

TransferBBCAIPEndPointInfoto
CMDB.kjb

Transfers information about the
BMC_IPEndPoint CI type.

LANEndPoints

TransferBBCALANEndPoint
Infoto
CMDB.kjb

Transfers information about the
BMC_LANEndpoint CI type.

Software Server

TransferBBCASoftwareServer
Infoto
CMDB.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 exceeding the organization storage limit.

Person

TransferBBCAPerson
InfotoCMDB.kjb

Transfers information about BMC_Person CI type.

Combined Jobs
  • TransferAdvancedBBCA
    InfotoCMDB.kjb
  • TransferComputerSystemAnd
    SoftwareBBCAInfotoCMDB.kjb
  • TransferAdvancedBBCAInfotoCMDB.kjb
    This job file transfers information related to the BMC_ComputerSystem, BMC_OperatingSystem, BMC_Processor, BMC_IPEndPoint, and BMC_LANEndpoint CI types.
  • TransferComputerSystemAnd
    SoftwareBBCAInfotoCMDB.kjb

    This job file transfers information related to the BMC_ComputerSystem and BMC_SoftwareServer CI types.

KTR files in the Pentaho package

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 KTR files contain mapping of the fields in BMC BladeLogic Client Automation to the fields in the Remedyforce CMDB.

The following table provides information about the KTR files and the corresponding transformations that the KJB file for each CI type contains:

KTR fileTransformation or step in the KJB fileDescription
NoneCheck If Delta Timestamp File Exists

Checks if any time stamp file exists.

The 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 BE Table With BBCA <CI type name> information step.

CreateInitialTimeStampedFileFor<CIType>.ktrCreate the initial time stamp file

Creates the time stamp file to record the time of import.

This step is run only if you are importing for the first time or you have deleted the existing time stamp file.

TransferBBCA<CIType>InfotoCMDB.ktrUpdate BE Table With BBCA <CI type name > informationTransfers data from BMC BladeLogic Client Automation to the Base Element object of BMC Remedyforce CMDB.
Store<CIType>Timestamp.ktrStore the current timestamp

If the data is successfully imported, the time stamp file is updated with the current time of import

For example, the LAN Endpoint job file (TransferBBCALANEndPointInfotoCMDB.kjb) contains the CreateInitialTimeStampedFileForLANEndPoint.ktr, TransferBBCALANEndPointInfotoCMDB.ktr, and StoreLANEndPointTimestamp.ktr files.

The following table provides information about the steps that are included in the TransferBBCA<CIType>InfotoCMDB.ktr file (Update BE Table With BBCA <CI type name> information transformation). The Pentaho package runs these steps to transfer data from BMC BladeLogic Client Automation 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.

BBCA input

An SQL query that fetches information from BMC BladeLogic Client Automation based on the stored time stamp.

Transform BBCA variables

Facilitates JavaScript transformations, such as appending or trimming fields.

Upsert into class <CI type name >

Accepts the destination of the data, the credentials for the Salesforce organization where you want to save the imported data.

Salesforce Input[CMDB_Class]

Accepts the access details of the Salesforce organization to fetch the BMC Remedyforce CMDB classes details.

Success rows

Stores the rows that are imported successfully.

Failure rows

Stores the rows that are not imported, error code, error description, and error fields.

Related topics

Applying models while importing CIs and assets

Scheduling jobs to import data

Troubleshooting common issues when importing data

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

Comments