BMC Atrium CMDB SCCM Adapter Guide

Note

You must first install the MSSQL JDBC driver to use the BMC Atrium CMDB SCCM Adapter.

About BMC Atrium CMDB SCCM Adapter

Introduction

Starting from BMC CMDB 9.0, BMC provides an SCCM adapter for Microsoft SCCM which you can use to retrieve, transform and import data from Microsoft SCCM into the BMC CMDB. This imported Microsoft SCCM discovered data can then be used by end-to-end ITIL Asset and Incident and Change management processes in the BMC Remedy IT Service Management Suite after you have merged your source data to the Asset Dataset.

The SCCM adapter is an Atrium Integrator based solution that provides a starting point for the SCCM integration and is intended to be modified and customized to suit your requirements.

As a best practice, BMC recommends that the data should be represented in the source dataset 'as is' from the source and then manipulated using normalization to meet your expectations. After normalization is done, reconciliation with data in other datasets should be performed before the data is merged into the production dataset. If this process is not done correctly, the AI jobs barely make data transformations.

The SCCM adapter officially supports SCCM 2007 and SCCM 2012, but it can be customized to connect and read data from any later versions SCCM DB.

When using this adapter for other SCCM releases, verify to know if the SCCM Database structure has changed, and if it has changed, you must modify the Database Tables and/or Views for some of the transformations. Contact the SCCM support person in your company who can help you with further steps.

This topic covers the following details about BMC Atrium CMDB SCCM Adapter:

Value Proposition

Integrating BMC Atrium CMDB with SCCM using the SCCM adapter provides the following business values to the customers:

Saves cost and speeds time to value.
Eliminates errors by prepackaging the following best practices:
- Provides a complete integration package including Reconciliation Engine / Normalization Engine rules.
- Offers end to end scenario for loading data to BMC Atrium CMDB from Microsoft SCCM.

For more details on integrating BMC Atrium CMDB with Microsoft SCCM, see the following video:

Salient Features of SCCM Adapter

The SCCM adapter which can be leveraged by both BMC Remedy ITSM suite and BMC Remedy OnDemand, provides the following features:

Imports both configuration items (CIs) and relationship data from Microsoft SCCM.
Includes pre-defined mappings between SCCM tables and CMDB classes/relationships.
- Mappings are configurable
- Supports both ‘full’ and ‘delta’ update.
- Includes default reconciliation and normalization jobs.
- Provides modification/extension capabilities for out-of-the-box mappings for custom attributes/classes.
- Supports compatibility with the latest version of Remedy (9.0 or later)

Supported Versions

Versions 9.0.00 and later of BMC Atrium CMDB.

Audience

Users with access to supported versions of SCCM and BMC Atrium CMDB.

Enhancements to 9.1

For BMC Atrium CMDB 9.1 release, BMC focused on the following two improvements:

Installer framework
SCCM 2012 Mappings

In addition, many other fixes like error handling cases, junk connection clean-up, log file path correction, and customer defect fixes are part of the enhancements.

Installer framework improvements

Moved to a common BMC install framework.
Enabled Java8 support.
Removed Extension Loader Dependency.
Moved to RIKJ.

Improvements in SCCM 2012 Mappings

Added mapping for SerialNumber in transformation for BMC_ComputerSystem.
Slipped and stored the comma separated IP Address stored in SCCM view to an appropriate BMC_IPEndpoint Class.
Removed SCCMIntegration_LocalFileSystem transformation from job, as there is no appropriate table/view in SCCM 2012.
Removed owner Information lookup from SCCMIntegration_VirtualSystemEnabler due to structure of SCCM 2012 database.
Changed source view for BMC_LANEndpoint to v_GS_NETWORK_ADAPTER as it is the right view for this class.

SCCM Adapter Installation

Prerequisites

Install the following applications before using the integration package:

Microsoft SCCM Application
- Microsoft SCCM 2007 OR Microsoft 2012
BMC Applications
- BMC Remedy AR System 9.0 or later
- BMC Atrium CMDB 9.0 or later
- BMC Atrium Integrator 9.0 of later

Installing SCCM adapter using the installer

The BMC Atrium CMDB – SCCM integration package comprises the following installer components:

New Dataset for Microsoft SCCM
Atrium Integrator Jobs
- Initial load/Update Job
- Delete Job
- 16 transformations
- Reconciliation Job
- Normalization Job
  - CMDB Extension (creating attribute for SCCM integration ID). This is necessary for mapping the integration ID with the source system.

To install SCCM Adapter

Note

The SCCM Adapter does not support the following:

In-place upgrade.

You must manually uninstall and remove the previous SCCM Adapter version before installing another or a newer version.

Windows authentication on CentOS and Linux.

You must use SQL Server Authentication to run SCCM Adapter on Linux and CentOS.

Download the SCCM installer files from the following location:
ftp://ftp.bmc.com/pub/BSM/AtriumCore/9.1/Integrations/SCCM/
Unzip the SCCM installer files.
Run:
For Windows - setup.exe
For UNIX - setup.bin
In the Copyright panel, select a language, and click OK.
In the Welcome panel, click Next.
Accept the license agreement, and click Next.
Enter the database settings, and click Next.
Enter details of the server where BMC Remedy AR System is installed, and click Next.
Click Install.
View the Installation Summary and click Done.
You can view a log file of the installation in the following folder:
<USERPROFILE>/AppData/Local/Temp/sccmcmdintegration_install_log.txt

Installing SCCM adapter using silent installation

Use the following options file and make the necessary modifications to the file before running the silent installation.

Note

To edit the options.txt file, remove the comment (#) markers. In UNIX environments, ensure that no Ctrl+M characters appear in the options.txt file.


################################################################################
# Options File
#
# Product Name: BMC SCCM-CMDB Integration
# Product Version: 9.1.00
#
# To invoke the installer in silent mode with an options file:
#   setup -i silent -DOPTIONS_FILE=Options.txt
################################################################################
################################################################################
# Available Features
#
# add a line to the options file
#    -A featureName
# 
#
# --featureSCCMCMDBIntegration
#  
#
################################################################################
#-A featureSCCMCMDBIntegration
################################################################################
# Product Install Location
#
# The install location of the product. Specify a valid directory into which the
# product should be installed.
#
# Default value if not set:
#   - %ProgramFiles%\\BMC Software\\SCCMCMDBIntegration (Windows)
#   - /opt/bmc/SCCMCMDBIntegration (UNIX)
################################################################################
#-P installLocation=C:/Program Files/BMC Software/SCCMCMDBIntegration
#-J SCCM_CMDB_HOME=C:/Program Files/BMC Software/SCCMCMDBIntegration
#-J SQL_SERVER_NAME_IP=<SQL Server Host Name>
#-J SQL_SYSADMIN_USER=<SQL Server Admin User Name>
#-J SQL_SYSADMIN_PASSWORD=<SQL Server Admin Password>
#-J SQL_DATABASE_NAME=<SQL Server Database Name>
#-J SQL_DATABASE_PORT=<SQL Server Port Number>
################################################################################
# Authentication Properties
#for Windows Authentication:
#BMC_SQLSERVER_WINDOWSAUTH_OR_SQLAUTH=WINDOWSAUTH
#
#for SQL Authentication:
#BMC_SQLSERVER_WINDOWSAUTH_OR_SQLAUTH=SQLAUTH 
################################################################################
#-J BMC_SQLSERVER_WINDOWSAUTH_OR_SQLAUTH=<SQLAUTH/WINDOWSAUTH>
#-J BMC_AR_USER=<AR System Admin User>
#-J BMC_AR_PASSWORD=<AR System User Password>
#-J BMC_AR_PORT=<AR server Port>
#-J BMC_AR_SERVER_NAME=<AR server name>

Run the installer with the -i silent option.
- (Windows) setup.exe -i silent -DOPTIONS_FILE=<path_to_txt_file_with_installation_options>
- (UNIX) sh setup.bin -i silent -DOPTIONS_FILE=<path_to_txt_file_with_installation_options>

Uninstalling SCCM adapter

Navigate to <SCCMCMDBIntegration_HOME/UninstallBMCSCCMCMDBIntegration>.
Launch the uninstaller.
Complete the uninstallation steps to remove the file structure of SCCM adapter.
Open the Pentaho Spoon client and remove the SCCM package directory.
Remove the guid (OI-BS005056B5170DoDpHUQF4OR#gJngB1D) from the share application property form (SHARE:Application_Properties).
Remove the SCCMIMPORT_NE job from Normalization Jobs (BMC Atrium Core Console > Advanced > Normalization).
Remove the SCCM Identification and Merge RE job from Reconciliation Jobs (BMC Atrium Core Console > Advanced > Reconciliation).
(Optional) Remove the following attributes from the BMC_BaseElement class using Class manager Console or CMDB driver.

- SMSParentID
- SMSCheckViewName
- SMSChildID
  
  Important
  
  Removing the attributes may result in data loss.

Additional Resources

Microsoft has provided an Installation and Configuration guide for SCCM. Install and configure SCCM as per the guides provided. These documents are available at the following location: http://technet.microsoft.com/en-us/evalcenter/bb736730.aspx.

SCCM Adapter Maintenance Tool

The Maintenance Tool provides a common tool to access diagnostics and utilities that are useful when troubleshooting SCCM related issues. You can use the Maintenance Tool to collect diagnostic information, open and view log files, or search logs to identify issues. The SCCM Adapter Maintenance Tool also gives you access to installation and uninstallation logs.

Working with SCCM jobs

The user can work with the BMC Atrium CMDB – SCCM integration package using the following components.

Atrium Integrator Integration Package

BMC Atrium Core includes Atrium Integrator (AI), an Extract, Transform, and Load (ETL) based integration engine.

• Provides an easy-to-understand, wizard-based UI.

• Comprises Out of the box templates which encompass best practices.

• Provides a wide berth of integration technologies such as single tool standardization.

• Comprises a scalable data-warehousing proven architecture.

For the classes provided in the List of Transformations section, a transformation is created to import the class as well as the relationships. Relationships could be done in the same transformation or in a different one based on the design decision. The transformation (AI job/transformation) has both delta and initial load capabilities .In addition to the transformations, a total of 17*2=34 AI child jobs will be created. There is also a delete transformation per class.

A single top level job is designed to call the lower level child jobs that deal with individual classes/relationships. The user interacts only with top level job which is used to monitor and manage the transformation through the Atrium User Interface (AUI) for AI.

SCCM Import Job

The SCCM Import job is responsible for loading data from the SCCM database to CMDB, The job pushes both new data and changes to existing data to CMDB.

The following image provides an illustration of a SCCM Import Job.

SCCM Delete Job

The SCCM Delete job is responsible for setting the MarkedAsDeleted attribute to “Yes” in CMDB for data which no longer exists in the SCCM database.

The following image provides an illustration of a SCCM Delete Job.

Normalization Engine Integration Package

After SCCM – CMDB integration is completed, a Normalization job, along with rules, is automatically configured for the SCCM import dataset. The Normalization Engine job runs in a Continuous mode.

Reconciliation Engine Integration Package

After SCCM – CMDB integration is completed, a standard Identification and Merge job, along with its rules, is automatically configured for SCCM import dataset. The Reconciliation Engine job runs in a Continuous mode.

From 9.0 version and onwards, the following configurations are also available:

Purge activity is added to the job.
Reconciliation engine processes only normalized CIs. However, it is not mandatory and that option can be disabled.

Troubleshooting the SCCM Adapter

After installing Microsoft System Center Configuration Manager (SCCM), the user might encounter the following issues:

Incorrect location of error log file

If you have installed SCCM, the user may not be able to locate the error log file. All error log files related to Atrium Integrator jobs are saved in ngie/bin folder. Hence, the user must make sure that the error logging plugin has the correct file location.

Perform the steps given below to update the file location:

In the Pentaho Integration console, open the Error Logging plugin.
In the Filename box, update the error log file location to include ngie/bin folder.
Click OK.

Failure when running Normalization Engine jobs

SCCM installer is shipped with Atrium Integrator, Normalization Engine, and Reconciliation Engine jobs. Normalization Engine jobs might fail to run after the Atrium Integrator jobs. In such a case, make sure that each transformation that SCCM has discovered has data mapped to Category / Type / Item / ManufactureName / Model. It is mandatory to have the data in this format in order to normalize that instances that Atrium Integrator creates.

List of Transformations

The following table lists the transformations available with SCCM.

CMDB Class

SCCM Transformation

SCCM 2007

SCCM 2012

Details

BMC_

CDROMDrive

SCCMIntegration_

CDRomDrive

v_GS_

CDROM

v_GS_

CDROM

BMC_

ComputerSystem

SCCMIntegration_

ComputerSystem

v_GS_

COMPUTER_

SYSTEM

v_GS_

COMPUTER_

SYSTEM

BMC_

DiskDrive

SCCMIntegration_

Diskdrive

v_GS_

DISK

v_GS_

DISK

BMC_

IPEndpoint

SCCMIntegration_

IPEndPoint

v_GS_

NETWORK_

ADAPTER_

CONFIGUR

v_GS_

NETWORK_

ADAPTER_

CONFIGUR

BMC_

LANEndpoint

SCCMIntegration_

LANEndPoint

v_GS_

DEVICE_

NETWORK

v_GS_

NETWORK_

ADAPTER

BMC_

LocalFileSystem

SCCMIntegration_

LocalFileSystem

v_GS_DEVICE_

FILESYSTEM

Not Applicable

Disabled

for

SCCM

2012

as there

is no

clear

mapping

table

BMC_

LogicalDisk

SCCMIntegration_

LogicalDisk

v_GS_LOGICAL_

DISK

v_GS_LOGICAL_

DISK

BMC_

Memory

SCCMIntegration_

Memory

v_GS_X86_

PC_

MEMORY

v_GS_X86_

PC_

MEMORY

BMC_

Monitor

SCCMIntegration_

Monitor

v_GS_

DESKTOP_

MONITOR

v_GS_

DESKTOP_

MONITOR

BMC_

NetworkPort

SCCMIntegration_

Networkport

v_GS_

NETWORK_

ADAPTER

v_GS_

NETWORK_

ADAPTER

BMC_

OperatingSystem

SCCMIntegration_

OperatingSystem

v_GS_

OPERATING_

SYSTEM

v_GS_

OPERATING_

SYSTEM

BMC_

Patch

SCCMIntegration_

Patch

v_GS_

PATCHSTATE

Not Applicable

Disabled

for

SCCM

2012

as there

is no

clear

mapping

table

BMC_

Processor

SCCMIntegration_

Processor

v_GS_

PROCESSOR

v_GS_

PROCESSOR

BMC_

Product

SCCMIntegration_

Software_Product

v_GS_

SoftwareProduct

v_GS_

SoftwareProduct

BMC_
TapeDrive

SCCMIntegration_

TapeDrive

v_GS_TAPE_

DRIVE

v_GS_TAPE_

DRIVE

BMC_

VirtualSystemEnabler

SCCMIntegration_

VirtualSystemEnabler

v_GS_

VIRTUAL_

APPLICATION_

PACK

v_GS_

VIRTUAL_

APPLICATION_

PACK

BMC_

CDROMDrive

Delete_SCCM_

CDRomDrive

BMC_

ComputerSystem

Delete_SCCM_

ComputerSystem

BMC_

DiskDrive

Delete_SCCM_

DiskDrive

BMC_

IPEndpoint

Delete_SCCM_

IPEndPoint

BMC_

LANEndpoint

Delete_SCCM_

LanEndPoint

BMC_

LocalFileSystem

Delete_SCCM_

LocalFileSystem

Disabled

for

SCCM

2012

as there

is no

clear

mapping

table

BMC_

LogicalDisk

Delete_SCCM_

LogicalDisk

BMC_

Memory

Delete_SCCM_

Memory

BMC_

Monitor

Delete_SCCM_

Monitor

BMC_

NetworkPort

Delete_SCCM_

Networkport

BMC_

OperatingSystem

Delete_SCCM_

OperatingSystem

BMC_

Patch

Delete_SCCM_

Patch

Disabled

for

SCCM

2012

as there

is no

clear

mapping

table

BMC_

Processor

Delete_SCCM_

Processor

BMC_

Product

Delete_SCCM_

Product

BMC_

TapeDrive

Delete_SCCM_

TapeDrive

BMC_

VirtualSystemEnabler

Delete_SCCM_

VirtualSystemEnabler

Field	What it means
Machine Name or IP Address	The IP of the server where Microsoft SCCM is installed.
Database Name	instance\databaseName or databaseName This depends on how MS SCCM database is installed.
Administrator User	Database administrator user
Password	Database administrator password

BMC Atrium CMDB SCCM Adapter Guide

About BMC Atrium CMDB SCCM Adapter

Introduction

Value Proposition

Salient Features of SCCM Adapter

Supported Versions

Audience

Enhancements to 9.1

Installer framework improvements

Improvements in SCCM 2012 Mappings

SCCM Adapter Installation

Prerequisites

Installing SCCM adapter using the installer

To install SCCM Adapter

Installing SCCM adapter using silent installation

Uninstalling SCCM adapter

Additional Resources

SCCM Adapter Maintenance Tool

Working with SCCM jobs

Atrium Integrator Integration Package

SCCM Import Job

SCCM Delete Job

Normalization Engine Integration Package

Reconciliation Engine Integration Package

Troubleshooting the SCCM Adapter

Incorrect location of error log file

Failure when running Normalization Engine jobs

List of Transformations

Comments