Prerequisites for importing data to BMC Remedyforce
The following table describes the configurations that you must perform before importing data into BMC Remedyforce.
Description or procedure
Registering at the BMC Communities website
You must register at the BMC Communities website to download the job files that are uploaded for you to use for importing data from various data sources.
Installing the JRE
You must install the Oracle Java Runtime Environment (JRE) to run the Pentaho Data Integration tool. You must perform the following steps to install the JRE on a Windows computer.
For Pentaho 6.1, the supported JRE versions are Oracle Java 7 and 8.
Downloading the Pentaho Data Integration tool
The Pentaho Data Integration tool is an open source integration tool that can be used to import data from various data sources to BMC Remedyforce. For more information about using the Pentaho Data Integration tool, see http://wiki.pentaho.com/display/EAI/Spoon+User+Guide.
Note: To enable you to use the Pentaho Data Integration tool, you must have the latest version of Java installed on your computer.
|Connecting to Windows authenticated MS SQL server|
To enable communication between Pentaho Data Integration tool and Windows authenticated Microsoft SQL server, you must connect both.
Note: By default, SCCM 2007 is installed in Windows authenticated mode. You must configure the steps mentioned in this section to enable communication between Pentaho Data Integration tool and SCCM 2007.
|Configuring BMC Remedyforce to retain the original Instance Name value of CIs imported from an external source||All|
While importing data from an external source, BMC Remedyforce generates a dateTimeStamp and appends it to the Instance Name value of each CI. The dateTimeStamp ensures that CIs imported to BMC Remedyforce CMDB are unique. However, you can choose not to append the dateTimeStamp to the Instance Name values of CIs by configuring the Staging_SkipInstanceIDSuffix custom setting value. This custom setting is not available by default; you must create it and set its value to True.
Important: If you configure Staging_SkipInstanceIDSuffix custom setting to True, and the Instance Name values of CIs being imported from an external source to BMC Remedyforce CMDB are not unique, the import job does not complete successfully.
|Creating the KETTLE_HOME environment variable||All|
You must first create KETTLE_HOME environment variable to store the location of the Kitchen.bat file. The Kitchen.bat file is available in the \pdi-ce-4.x.0-stable\data-integration or \pdi-ce-5.0.1.A-stable\data-integration folder.
|Adding the MySQL connector file||Dell KACE|
You need the mysql-connector-java-5.1.23-bin.jar file to establish a connection between Dell KACE Pentaho packages and the Dell KACE server. This file is provided in the Dell KACE package that is available on the BMC Communities website.
To add the mysql-connector-java-5.1.23-bin.jar file
Pentaho packages for CMDB 1.0 and 2.0
Pentaho packages for CMDB 1.0 and 2.0 are different. The following table lists the folder names that are used for the packages on the BMC Communities website.
Folder name for CMDB 1.0
Folder name for CMDB 2.0
BMC Atrium Discovery
ADDM 9.0 CMDB 2.0
BMC BladeLogic Client Automation
BBCA CMDB 2.0
DELL KACE CMDB 2.0
BMC FootPrints Asset Core
FootPrints Asset Core Integration Package
FootPrints Asset Core Integration Package CMDB 2.0
System Center Configuration Manager
SCCM CMDB 2.0
BMC Atrium Configuration Management Database (BMC Atrium CMDB)
|BMC Client Management||None||BMC Client Management Web Services Integration Package|
Use the appropriate package depending upon the CMDB version that you are using. For information about versions of CMDB, see BMC Remedyforce CMDB architecture.