This topic provides information about mapping BMC Server Automation data to BMC Atrium CMDB.

Transferring data from BMC Server Automation to BMC Atrium CMDB involves two steps. The first is installing the BMC BladeLogic Atrium Integration which creates the jobs on the BMC Server Automation Application Server, tables, and views on BMC Decision Support for Server Automation, and jobs on the AI console. The next step involves mapping the BMC Atrium CMDB Domain attribute of the

To map the Domain attribute to the DNS_DOMAIN_NAME property:

1. Navigate to the following directory on the computer where BMC BladeLogic Atrium Integration is installed: BL2AIInstallationDirectory\DBScripts\sqlserver.
2. Copy the blatrium_customization.sql to the computer where SQL Server Client is installed and go to step 4.
3. Run the following command: sqlcmd -S <BDSSAwarehousecompName> -d <BSARA_DW_DB> -U <BSARA_DW> -P <sa> -i blatrium_customization.sql.
4. On the BMC BladeLogic Atrium Integration computer, in the BL2AIInstallationDirectory, open the customizationProperties.txt file with a text editor and update the file with the BMC AR server details.
5. From the command prompt, navigate to the following directory: BL2AIInstallationDirectory\BMCBL2AtriumInstallJVM\bin.
6. Run the following command: java -jar "BL2AIInstallationDirectory\BLAUpdateFieldMapping.jar" "BL2AIInstallationDirectory\customizationProperties.txt".
   For example: java -jar "C:\Program Files (x86)\BMC Software\BL2AI\BLAUpdateFieldMapping.jar" "c:\Program Files (x86)\BMC Software\BL2AI\customizationProperties.txt"

   This command generates output similar to the following:

   true
   arServer Name :: vm-w23-cc01
   arServerPort:: 0
   arUser:: Demo
   arPassword:: sa
   INFO  31-05 17:23:19,330 - Trying to load configuration arsys_api.xml
   WARN  31-05 17:23:19,370 - Could not load optional configuration arsys_api.xml
   INFO  31-05 17:23:19,502 - Trying to load configuration default.xml
   INFO  31-05 17:23:19,516 - jrpcMode: true
   INFO  31-05 17:23:19,520 - jniLoadMode: 1
   INFO  31-05 17:23:19,521 - apiRecordingMode: 0
   INFO  31-05 17:23:19,521 - useConnectionPooling: true
   INFO  31-05 17:23:19,522 - maxProxiesPerServer: 80
   INFO  31-05 17:23:19,522 - idleConnectionsPerServer: 5
   INFO  31-05 17:23:19,523 - connectionTimeout: 0
   INFO  31-05 17:23:19,523 - connectionLifespan: 0
   INFO  31-05 17:23:19,524 - timeUnit: MINUTES
   INFO  31-05 17:23:19,524 - minimumSupportedServerRpcVersion: 12
   INFO  31-05 17:23:19,525 - connectionMaxRetries: 1
   INFO  31-05 17:23:19,525 - timeLagBetweenRetriesMillSec: 100
   INFO  31-05 17:23:19,526 - stringizeFieldAssignments: false
   INFO  31-05 17:23:19,526 - stringizeSetIfQualification: false
   INFO  31-05 17:23:19,526 - useLegacyQualParser: false
   INFO  31-05 17:23:19,527 - useLegacyAssignParser: false
   INFO  31-05 17:23:19,527 - useLegacyQualFormatter: false
   INFO  31-05 17:23:19,528 - useLegacyAssignFormatter: false
   INFO  31-05 17:23:19,531 - APITIMEOUT from system property : null
   INFO  31-05 17:23:19,578 - APITIMEOUT from Environment : null
   INFO  31-05 17:23:19,578 - AROVERLAYGROUPS from system property : null
   INFO  31-05 17:23:19,579 - AROVERLAYGROUPS from Environment : null
   INFO  31-05 17:23:22,269 - fipsProviderJsafeJCE installed = false
   INFO  31-05 17:23:23,579 - set timer period 60000 milliSec (00:01:00)
   INFO  31-05 17:23:23,622 - Connects to vm-w23-cc01 through com.bmc.arsys.api.ProxyJRpc@177600e
   INFO  31-05 17:23:23,648 - WIIntegHandler(arg[1]) Init Started
   INFO  31-05 17:23:23,649 - WIIntegHandler Connecting to AR Server Form NGIE:Config
   INFO  31-05 17:23:23,663 - WIIntegHandler Connecting to Repository Database
   INFO  31-05 17:23:23,664 - WIIntegHandler.getKettleInitialized Started
   INFO  31-05 17:23:24,023 - Using "C:\Users\ADMINI~1\AppData\Local\Temp\vfs_cache" as temporary files store.
   INFO  31-05 17:23:24,181 - WIIntegHandler.getKettleInitialized JobEntryLoader Initialized
   INFO  31-05 17:23:24,365 - WIIntegHandler Initialize Completed
   INFO  31-05 17:23:24,371 - Reading pentaho configuration from UDM:Config
   INFO  31-05 17:23:24,541 - DevtoProdExportRepository : connectRep : Repository Connection Sucessfull : PDIREPO_vm-w23-cc01_0
   INFO  31-05 17:23:25,295 - transName : BL_PULL_COMPUTERSYSTEM_BL_PULL_COMPUTERSYSTEM
   INFO  31-05 17:23:25,296 - oRepDir.getName() : BL2ATRIUM_REPO
   INFO  31-05 17:23:25,306 - existingId : 000000000000190
   INFO  31-05 17:23:25,320 - strIntegrationName : BL2ATRIUM_REPO
   INFO  31-05 17:23:25,321 - tmetaKTR.getRepositoryDirectory().getName() : BL2ATRIUM_REPO
   INFO  31-05 17:23:25,380 - Connects to vm-w23-cc01 through com.bmc.arsys.api.ProxyJRpc@1167c35
   INFO  31-05 17:23:25,394 - Trying to load configuration arsys_api.xml
   WARN  31-05 17:23:25,396 - Could not load optional configuration arsys_api.xml
   INFO  31-05 17:23:25,397 - Trying to load configuration default.xml
   INFO  31-05 17:23:27,196 - Start Time : 1370001205322 : End Time : 1370001207196 : Difference : 1874
   Updated field mapping successfully...

7. Log on to Atrium Integrator Spoon.
8. From the Tools menu, choose Database > Clear Cache.
9. Restart the AR service.

To verify that the mapping is done correctly

1. Log on to Atrium Integrator Spoon.
2. From the Tools menu, choose Repository > Explore.
3. In the right pane, double-click the BL2ATRIUM_REPO repository.
4. In the right pane, double-click the BL_PULL_COMPUTERSYSTEM_BL_PULL_COMPUTERSYSTEM transformation.
5. In the transformation, right-click the icon for CMDBOutput and choose Edit step.
6. In the CMDBOutput dialog box, in the Update fields section, verify that the Domain class attribute is mapped to DNS_DOMAIN_NAME.