Setting up Atrium CMDB Import Job in BladeLogic. Atrium can be used to model the relationship between Business Services and Computer Systems
In this example diagram, there are 3 servers (devops-jee-dev, devops-jee-prod, devops-jee-new) and 2 business services (devops-db and devops-web).
Business Services can contain one or more servers, and Servers can be in more than on Business Service.
The end goal is that BladeLogic can see the Business Services as Smart Groups that can be used as deployment targets.
The documentation for setting up this import is in https://docs.bmc.com/docs/display/public/bbas83/Configuring+BMC+BladeLogic+Atrium+Integratio n+after+installation (also attached)
The integration is just one way (from Atrium CMDB to BladeLogic), so the sections covering the export of data from BladeLogic to Atrium CMDB can be ignored.
Network requirements for integration The BladeLogic application server needs to be able to connect to the Server TCP/IP port for the Atrium instance.
This can be found on the AR System Administration Console, “Ports and Queues” tab. The attached screenshot shows that the port is 46262.
BladeLogic Configuration Steps 1. Enable atrium integration as documented: https://docs.bmc.com/docs/display/public/bbas83/Enabling+BMC+BladeLogic+Atrium+Integ ration
2. Follow the steps described in the following section: https://docs.bmc.com/docs/display/public/bbas83/Transferring+business+service+data+fro m+BMC+Atrium+CMDB+to+BMC+Server+Automation
3. Create a Server property called BUSINESS_SERVICES of type String (If it doesn’t already exist) BladeLogic settings used for testing
In this case, we selected Company = “Calbro Services” in order to select the right group of servers. Mainframes were removed from the possible Computer System classes.
The relationship selected was the BMC_Dependency relationship, and the BladeLogic property shown was the default BUSINESS_SERVICES Atrium CMDB setup For my testing, I used Atrium Core Explorer to create computer system and business services entries, and then tie them up together with dependencies. The layout looked like this:
For testing on site, it may be worth creating a new Dataset to ensure that any changes made don’t interfere with the Production dataset.
For each computer system, click Edit, and make sure that Primary Capability is set to “Server” There is an attribute called CDMachineID which needs to be set for each server. This should be verified for each server, by navigating to
CDMachineID is at the bottom: This attribute should be checked, and then saved.
Performing the Atrium Import job. In BladeLogic, create a new Atrium Import Job. There are no targets specified for this job.
Once executed, then it will have updated the BUSINESS_SERVICE property for all servers found in Atrium.
The highlighted part of the image shows the servers that have been updated with information from Atrium. The properties for the devops servers in BladeLogic will be set as follows:
Server Name Value for BUSINESS_SERVICES property devops-jee-new devops-db devops-jee-prod devops-db,devops-web devops-jee-dev devops-web In order to use these properties, smart groups should be created. The smart group will use the CONTAINS clause as the BUSINESS_SERVICES property can contain one or more comma separated values.
The Smart Group for devops-db would be BUSINESS_SERVICES contains “devops-db”, and the smart group for devops-web would be BUSINESS_SERVICES contains “devops-web”