Importing data from Microsoft System Center Configuration Manager
You can import data from System Center Configuration Manager (SCCM) into the BMC Remedyforce configuration management database (CMDB) by using the Pentaho Data Integration tool.
The following topics are provided:
Before you begin
Before importing data from SCCM, you must meet the following requirements:
- Install JRE
- Download the Pentaho Data Integration tool
- Register at the BMC Communities website
- Configure Windows authentication to enable communication between the Pentaho Data Integration tool and SCCM
For more information about these procedures, see Prerequisites for importing data to BMC Remedyforce.
KJB and KTR files for importing data from SCCM
In Pentaho, metadata is stored in XML format in the file system as KTR (transformations) or KJB files (jobs). For more information about the Pentaho packages applicable to Remedyforce CMDB 2.0, see Pentaho packages to import data into CMDB 2.0.
A KTR file contains a single transformation. The KTR files that are provided to you include the following transformations for all the CI types:
Reads the saved time stamp.
An SQL query that fetches information from SCCM based on the stored time stamp.
Transform SCCM variables
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.
Accepts the access details of the Salesforce organization to fetch the BMC Remedyforce CMDB classes details.
Stores the rows that are imported successfully.
Stores the rows that are not imported, error code, error description, and error fields.
A job file contains a series of transformations. A KJB file that is provided to you includes the following steps:
|Check If Delta Time stamp 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 executed; otherwise, the Update staging table with SCCM <CI type name> information or Update BE Table With SCCM <CI type name> information step.|
|Create the initial time stamp file||Creates the time stamp file to record the time of import. This step is executed only if you are importing for the first time or you have deleted the existing time stamp file.|
|Update BE Table With SCCM <CI type name > Information||Transfers data from SCCM to the |
|Store the current timestamp|
If the importing of data is successful, the time stamp file is updated with the current time of import. For example, the ComputerSystem job file (TransferSCCMinfotoCMDB.kjb) contains the following transformation KTR files:
In CMDB 2.0, the data is saved in the CMDB directly.
List of KJB files for importing data from SCCM
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.
|Folder name (CI Type)||Description||Job file|
|Computer System||Transfers information about the |
BMC_ComputerSystem CI type
|OS||Transfers information about the |
BMC_OperatingSystem CI type
|Processor||Transfers information about the |
BMC_Processor CI type
|IPEndPoints||Transfers information about the |
BMC_IPEndPoint CI type
|LANEndPoints||Transfers information about the |
BMC_LANEndpoint CI type
Transfers information about the
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.
There are two job files in the folder. The TransferAdvancedSCCMinfotoCMDB.kjb job file transfers information related to the BMC_ComputerSystem, BMC_OperatingSystem, BMC_Processor, BMC_IPEndPoint, and BMC_LANEndpoint CI types. The TransferComputerSystemAnd
To import data from SCCM by using Pentaho packages
Before importing data from SCCM, perform all of the actions in Before you begin.
To download the job files from the BMC Communities page, click https://communities.bmc.com/docs/DOC-28432.
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, BMC recommends that you use packages for CMDB 2.0 for faster imports.
BMC recommends that you download the job files in the folder in which you have unzipped the Pentaho Data Integration tool.
Do not change the folder structure because doing so can interfere with the running of the batch files provided in the CombinedJobs folder.
- To launch the Pentaho Data Integration tool, in the \<PentahoInstallerFolder>\data-integration folder, double-click the Spoon.bat file, and open the required KJB file.
To open the KTR file, right-click the Update BE table with SCCM <CI type name> information step, select Open referenced object, and then select Transformation.
- To enter the information required to access SCCM, perform the following actions:
- In the KTR file, double-click the SCCM Input step.
- Next to the Connection list, click Edit.
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 SCCM database is installed.
If you have configured Windows authentication on the SCCM database, user name and password are not required.
- (Optional) To verify the connection between the SCCM server and the Pentaho Data Integration tool, click Test.
- Click OK.
- To enter the information required to access your Salesforce organization, perform the following actions:
- Double-click the Upsert into class <CI type name> step.
- In the Salesforce Upsert window, enter your Salesforce organization user name and password.
(Optional) To update the predefined mapping between the SCCM fields and the BMC Remedyforce CMDB, click Edit Mapping.
For more information about mapping in Remedyforce CMDB 2.0, see Field mapping in CMDB 2.0.
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 API version> to before the retirement date.
If you are running the Pentaho package in a Sandbox environment, modify the Salesforce Webservice URL from API version> to in the updated Pentaho transformation. For more information, see Salesforce API Endpoint Retirement.
- (Optional) To test the connection, click Test connection.
- Click OK.
- To provide Salesforce log on details in the Salesforce Input[CMDB_Class] step, perform the following steps:
- Double-click Salesforce Input[CMDB_Class].
- In the Connection section, enter the Salesforce organization access details.
- (Optional) To test the connection, click Test connection.
- Click OK.
- (Optional) If you are importing data from an unidentified network, to enable communication between Salesforce and the Pentaho Data Integration tool, perform the following actions:
In Salesforce, navigate to Setup > Reset My Security Token.
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.
- Click Reset Security Token.
An email message is sent to your email address stored in Salesforce.
- 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, then you must enter mypasswordXXXXXXXXX in the Password field.
- To save the KJB and KTR files, click .
- In the KJB file, click .
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:
- — Complete
- — Running
- — Unsuccessful
(Optional) To view logs, in the Execution results section, click the Logging tab.
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.
In the folder that you downloaded from the BMC Communities page, double-click the sub-folders one by one, copy all the KTR and KJB files from the ComputerSystem, IPEndPoints, LANEndPoints, OS, Processor, and SoftwareServer folders and paste the files in the SCCM folder.
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, or software server.
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 SCCM
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 the ABC project from SCCM to BMC Remedyforce CMDB.
|Data to be imported||Steps to follow|
|Operating system details of the laptops|
|Processor details of the laptops|
|Software server details of the laptops|