Importing data from BMC BladeLogic Client Automation
You can import data from BMC BladeLogic Client Automation into BMC Remedyforce CMDB by using the Pentaho Data Integration tool only if Microsoft SQL Server data source is used in BMC BladeLogic Client Automation. The following topics are provided: Before importing data from BMC BladeLogic Client Automation, you must meet the following requirements: For more information about these procedures, see Prerequisites for importing data to BMC Remedyforce. In Pentaho, metadata is stored in XML format in the file system as KTR (transformations) or KJB files (jobs). A job file contains a series of transformations. A KJB file that is provided to you includes the following steps: The KTR files contain mapping of the fields in BMC BladeLogic Client Automation to the fields in the Remedyforce CMDB. In CMDB 2.0, the imported data is saved in CMDB directly. Different job files are provided for different jobs. These job files are bundled with related files and provided to you in folders. The following table provides the names of the folders and the description of the jobs for which the job files in these folders are used. Before importing data from BMC BladeLogic Client Automation, perform all of the actions in Before you begin. To download the job files from the BMC Communities website, click https://communities.bmc.com/docs/DOC-28435. BMC recommends that you download the job files in the folder in which you have unzipped the Pentaho Data Integration tool. In the Database Connection window, enter the host name, database name, user name, and password. (Optional) To update the predefined mapping between the BMC BladeLogic Client Automation fields and the Remedyforce CMDB, click Edit Mapping. Perform one of the following actions based on the Pentaho version that you are using: Pentaho version Action 6.1 In the Run Options window, click Run. 5.4 In the Execute a job window, click Launch. Transformation status is depicted by using the following icons: David is a member of the Infrastructure team for Downtown Bank, responsible for managing the laptops for ABC project. Before you begin
KJB and KTR files for importing data from BMC BladeLogic Client Automation
A KTR file contains a single transformation. The KTR files that are provided to you include the following transformations for all the CI types:List of KJB files for importing data from BMC BladeLogic Client Automation
To import data from BMC BladeLogic Client Automation by using Pentaho packages
The host name is the name of the computer where the BMC BladeLogic Client Automation database is installed.
For more information about mapping, see Overview of how CIs are imported in CMDB 2.0.
An email message is sent to your email address stored in Salesforce.
For example, if your password is mypassword and your security token is XXXXXXXXX, then you must enter mypasswordXXXXXXXXX in the Password field..
.
— Complete
— Running
— Unsuccessful
All errors are displayed in red.
The relationship between the Computer System as a source and the Software Server as a destination is not displayed in the Configuration Items Explorer because the Configuration Items Explorer can display only a limited number of relationships (due to platform limitations). Displaying Computer System and Software Server relationships might hide other important relationships between the Computer System and other CIs.
The BMCServiceDesk_AssemblyId_c field is required to create a relationship between the computer system and various CIs. The source is the computer system and the destination can be operating system, processor, IP End Points, LAN End Points, software server, or Person.
For example, the value of the BMCServiceDesk_AssemblyId_c field is 1 for a computer system record and a processor record has a Assembly ID value as 1, a relationship is automatically created between the computer system (source) and processor (destination).User scenarios for importing data from BMC BladeLogic Client Automation
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.
Overview of how is data imported in BMC Remedyforce
Importing-data-to-custom-attributes