Verifying the BMC Atrium Orchestrator installation
After installing BMC Atrium Orchestrator, perform the following verification tasks.
To review the BMC Atrium Orchestrator installation log files
- If you just completed installing BMC Atrium Orchestrator and the installer prompts you to view the installation log, click View Log and skip to step 3.
- If you already exited the installation host, perform the following steps:
- Log on to the BMC Atrium Orchestrator host computer.
Locate the installation directory for your operating system.
Location of installation log files
Default installation log location
Red Hat Linux
Open the log file that corresponds to the installation type, as shown in the following table:
Installation log file names
Installation log file name
Platform and all components included in the installation
Includes installation information for the Access Manager, repository, configuration distribution peer (CDP), and all optional components such as secondary peers
BMC Atrium Orchestrator Development Studio
Includes the installation information for BMC Atrium Orchestrator Development Studio
BMC Atrium Orchestrator content
Includes all installed content: adapters, modules, and run books
When you use the content installation program to install a predefined workflow for a BMC solution, the log files are created in <installationFolder>\import-logs.
Search the log files to verify that they contain no SEVERE error messages.
The BAO_install_log.txt log file contains the following known SEVERE error message. You can disregard this message because it does not cause any issues with the installation.
* (Windows) The Windows service name is defined on this system ,Detail=AO-CDP * (Linux) Could not run command because target file does not exist
Scroll to the end of the file to locate the success message.
If no error messages were reported, the installation was successful and you can skip the rest of the procedures in this topic.
- For all error, (including SEVERE) messages, perform the following procedures:
- If a SEVERE error message was reported, additionally perform the steps documented in the Resolving product installation issues on target hosts topic.
To verify that the BMC Atrium Orchestrator services are running
From a BMC Atrium Orchestrator server host:
- (Windows) Verify that the following services are running:
- BMC Atrium Orchestrator Access Manager and Repository
- BMC Atrium Orchestrator Configuration Distribution Peer
- (Linux) Verify that the following processes are running:
If either of these processes is not running, you can attempt to start them by using one of the following commands:
To verify that BMC Atrium Orchestrator Grid Manager starts
- In a web browser, launch Grid Manager by using the following format to type the URL:
- <hostnameOrIpAddress> is the IP address or host name used to install the CDP.
<webServerPort> is the port value entered during the installation. The default port is 28080.
The Access Manager logon page is displayed.
Log on to Grid Manager.
You can use the following default credentials to start Grid Manager:
- On the Status tab, verify that Grid CDP1 appears with the green, "Fully Running" status.
With BMC Cloud Lifecycle Management installer, you can enable ARSAdapter, BladeLogic, and NetAppActor adapters. If you enabled other adapters, they should also appear on the Status tab.
If any of your enabled adapters do not appear in this list, you can check the following log files for errors:
To manually configure adapters
If you did not configure adapters as part of the BMC Atrium Orchestrator post-install configuration steps, perform the following steps:
- Log into your BMC Atrium Orchestrator installation using the following link:
The Grid Manager screen is displayed.
- Go to Manage > Adapters.
- Select the following adapters:
- Click Add to Grid.
The adapter will now be added to the grid.
Click Configure in the Name column for each of the above adapters and provide the required information as listed in table:
Parameter and value
Additional configuration steps
Name: ARS Adapter
Target: BMC Remedy AR System ITSM Suite Server host
Name: BladeLogic Adapter
Initial command: nsh
Executable directory: C:\Program Files\BMC Software\BladeLogic\NSH\bin
Script directory: C:\Program Files\BMC Software\BladeLogic\NSH\scripts
Script executable: nsh
Jython executable: bljython
Authentication mechanism: SRP
SRP User Name: BLAdmin
SRP Password: <password specified during BBSA AppServer and Console install for BLAdmin>
Default User Role: BLAdmins
Install Certificate: yes
Install Certificate Prompt: ?[yes|no]:
To add the profile to the BBSA Appserver, perform the following steps:
- On the BMC Atrium Orchestrator host, navigate to the NSH folder.
- Run the following command:
cd /opt/bmc/bladelogic/8.1/NSH/bin/blcred authprofile -add -profile testProfile -host <BBSA hostname>:10840 -type srp -username BLAdmin -password <BLAdmin password>
Name: NetApp Adapter
Target: Enter the target hostname / IPAddress
- Go to Manage > Peers.
- Select the required Peer, for example CDP1 and click Edit selected Peer (Pencil icon) on the right.
- Click Enable and select the available adapters.
- Click OK and wait for a few minutes.
- Click the Status tab on the top of the screen.Select the GRID link on the top of the table, as shown in the screenshot below.
For each of the adapters listed in the table a green button should be displayed, indicating that the adapters are running.