Onboarding BMC Atrium Orchestrator
This topic describes a process for onboarding a connector for BMC Atrium Orchestrator (BAO). The process requires you to download and run a small program on your premises. Running as a service, the on-premise program is the connector that enables communication between SecOps Response and a BAO configuration distribution peer (CDP) server.
After onboarding is complete, you can set up job approval and change tracking for operator actions by integrating SecOps Response and BMC BladeLogic Server Automation with BMC Remedy ITSM and BAO.
- When using BMC Atrium Orchestrator, SecOps Response only supports Continuous Compliance for Servers. SecOps Response does not supports BMC Change Automation 2.0, the successor to Continuous Compliance for Servers.
- BMC Atrium Orchestrator must be running version 7.9 or later.
The following sections in this topic describe how to onboard the BAO connector.
Before you begin
To set up a connector for BAO:
- Confirm that a system connector for BMC BladeLogic Server Automation has already been onboarded.
- Confirm that the server running the BAO connector meets the following minimum requirements:
Configuration Required Value(s) Operating System(s)
- Red Hat Enterprise Linux 7
- Microsoft Windows 2012 R2
CPUs 4 Available memory 8 GB Disk space
20 GB free space
Java Runtime Environment (JRE) 1.8 Communication requirements
- HTTPS outbound connection to Internet
- Access to the TrueSight Orchestration configuration distribution peer (CDP) server
When onboarding connectors, a single machine cannot host more than one connector of the same type. For example, if you have onboarded a connector for BAO on a host, you cannot successfully onboard another BAO connector on the same machine.
To onboard a BAO connector
- Log on to SecOps Response as a SecOps Response administrator with your registered credentials.
- Click Add Connector.
The Choose Connectors page opens. It lets you choose the connectors that interact with SecOps Response.
You cannot add a connector for BAO without first adding a system connector for BMC Server Automation.
- On the Choose Connectors page, select BMC Atrium Orchestrator.
- Click Download.
The Download page opens. It presents the set of the connectors you have chosen.
- Download the connector by clicking on
The connector is downloaded locally.next to BMC Atrium Orchestrator.zip.
Before installing the connector, ensure that Java 1.8 or later is running on the local environment.
To check which version of Java is installed, use a command line and enter the following:
- Using any standard compression tool, extract the BMC Atrium Orchestrator.zip file to the location where you want to install the connector.
- Depending on the operating system, take one of the following actions:
(Windows) Perform the following steps:
Using a command line, cd to the location of the extracted ZIP file contents.
Install the connector by entering the command:
Start the connector by entering the command: ao
To stop the connector, enter the command: ao
(Linux) Perform the following steps as the root user or using
Cd to the location of the extracted ZIP file contents.
Grant execute permissions to the
install.shfile by entering the command:
chmod +x install.sh
Install the connector by running the command:
- Grant execute permissions to the
connector.shfile by entering the command:
chmod +x connector.sh
Start the connector by entering the command:
systemctl start ao-connectorTo stop the connector, enter the command:
systemctl stop ao-connector
You may also want to run the command
systemctl enable ao
-connector, which instructs the connector to start on reboot.
- Using the onboarding interface, click Configure.
The Configure page asks for information needed to set up a connection to a connector. The information requested depends on which connector you are configuring.
Provide the following information for the BAO connector.
If you have access to the BSA Application Server, you can obtain most of the following information by going to Configuration > Integration Configuration > AO Configuration.
Option Description AO Connection String
IP address or fully-qualified host name of the BMC Atrium Orchestrator configuration distribution peer (CDP) server. The host name should be in the format https://<hostname>.
AO Port Port number used to connect to the BMC Atrium Orchestrator CDP. AO User Name Name of the BMC Atrium Orchestrator user required to log on to the CDP. This user must be associated with the ADMIN role in BMC Atrium Orchestrator. AO Password BMC Atrium Orchestrator password for the specified user. AO Grid Name
Name defined for the BMC Atrium Orchestrator grid.
A grid is a logical collection of servers, called peers, where the BMC Atrium Orchestrator Platform is installed. The peers on the grid communicate with each other and work as a group. They communicate concurrently to every other peer in the group, and can detect which peers are running and the load on those peers.
Where to go next
Set up job approval and change tracking for operator actions in SecOps Response.