Installation and troubleshooting Manual
Running the installer
Note: The installer will not work against BAO 7.7 and later versions. Supported BAO versions include
7.6.x
If you are working with BAO 7.7 follow the manual steps listed below.
1. Go to the link https://communities.bmc.com/docs/DOC-31037
2. If you are running the installer on windows download the windows installer else download the
linux installer.
3. Extract the installer in a directory on local machine.
4. To launch the installer on windows execute setup.exe. On linux launch the installer by running
the following command – sh setup.bin
5. After you accept the license agreement a prerequisites screen will come.
6. Read all the prerequisites very carefully.
7. On next screen provide “BMC Atrium Orchestrator Inputs.”
a. AO Repository Server – Ip address or hostname of AO repository server
b. AO Repository Server Username – AO repository server username with administrator
permissions
c. AO Repository Server Password - AO repository server password with administrator
permissions
d. AO Repository Server Protocol – If AO repository is running on HTTPS specify “https”
else specify “http”
e. AO Repository Server Port – Port on which AO repository server is running.
8. Click “Next”. On next screen provide “BSA Server Automation Inputs”
a. BSA Server - BSA server ip address or hostname
b. BSA Server Username – BSA server username with BLAdmin permissions
c. BSA Server Password - BSA server password with BLAdmin permissions
d. BSA Server SRP Connection Profile – BSA Server connection profile of type “SRP”
corresponding to username and password provided above. This profile should exist on
BSA server.
e. Remote BLCLI Location Path – Path to the bin directory where BLCLI and NSH
executables are present
f. Create Installer Job? – Select this check box if agent installer job should be created as
part of the installer
g. RSCD Agent Bundle Folder Fully Qualified Path - Fully qualified group path where RSCD
agent bundle exists. This field is required only if agent installer job creation is required.
h. RSCD Agent Bundle Name – RSCD agent bundle name. This field is required only if agent
installer job creation is required.
9. When you click on “Next” installer will proceed with uploading AO adapters and modules. Once
this is done an install summary screen is shown. Read the notes on the screen very carefully and
follow the steps mentioned.
10. Once this is done click “Next” and installer will then continue to install BSA artifacts.
Step by step instructions for manual installation
Manual setup includes the following steps
1. Uploading AO artifacts (adapters and modules)
2. Enabling/Activating adapters and modules and configuring the same
3. Configuring BSA
Uploading AO artifacts
AO Modules Required
1. ADDM_BSA_Integration
2. AMP-AD-BMC-Remedy-ARS
3. AutoPilot-AD-Utilities
4. AutoPilot-OA-Common_Utilities
5. AutoPilot-OA-Incident_Management
6. BMC_BladeLogic-AD-Operations_Manager
AO Adapters Required
1. ARS Adapter
2. HTTP Adapter
3. Bladelogic Adapter
4. File Adapter(Optional)
Steps to configure AO
1. Open AO Grid Manager
2. Go to “Repository Manager”
3. Click on “Upload”
4.
5.
6.
7.
Select the “aroar” or “roar” to be uploaded and then finish.
Follow the above procedure to upload all the modules and adapters.
Enable all the adapters listed in section 2 with appropriate adapter configurations.
To enable a particular adapter say “Http Adapter”, go to “Manage -> Adapters”.
8. Select the appropriate adapter type from the left panel and click “Add to Grid”
9. Click on “Configure”
10. On the screen that comes up provide the required details for adapter configuration and save the
configuration.
11. Go to “Manage -> Peers”. Select the peer on which adapter needs to be enabled and click on
“Edit” sign.
12. Click on “Enable” and select the one or more adapter(s) to be enabled from the list and click
“OK”
13. Activate all the modules listed in section 1.
14. To activate a module go to “Manage -> Modules”
15. In the left panel select the module to be activated and click on “Activate”.
16. Follow the above procedure to activate all the required modules.
Updating AutoPilot-OA-Incident_Management Module Configuration
1. Once the “AutoPilot-OA-Incident_Management” module is activated click on the activated
module.
2. This will bring up “Edit Module Configuration” screen.
3. Expand to Configuration -> BMC_AR_System -> Adapter.
4. Click on “Adapter” and enter the name with which ARS Remedy adapter is enabled on grid.
Steps to configure BSA
1. Connect to “Server Automation Console” using BSA credentials
2. Launch “Unified Agent Installer” to create RSCD agent installer
3. Follow the wizard to complete the RSCD agent installer creation. Refer to
https://docs.bmc.com/docs/display/public/bsa83/Running+the+Unified+Agent+Installer for
detailed information on working with Unified Agent Installer.
4. Next step would be to create a workflow Job.
5. Click on “Add” to add an AO configuration. Specify the required details.
6. Click on “Workflow Job Configuration”.
7. Select the AO module whose workflows will be invoked by BSA workflow job. In our case it will
be “ADDM_BSA_Integration”
8. Under “Jobs” create a new workflow job as shown below.
9. Follow the wizard and select the workflow that needs to be called by this workflow job. In this
case it will be “Enroll Servers In BSA”. Also provide other required details.
Workflow Job “Enroll Servers In BSA” Input Parameters Description
Parameter Name
Parameter Description
ADDM Server
ADDM Server Connection Port
ADDM Server Discovery Encoded
Password
ADDM Server Discovery Username
ADDM Using Secure Connection
Add Servers To BSA
Agent Installer Job Group Path
Agent Installer Name
BSA Adapter Name
Create Helpdesk Ticket
Discovery Timestamp
Hostname Exclude List
HTTP Adapter Name
Install RSCD Agent
Operating System Exclude List
Subnet Exclude List
ADDM server ip address or hostname
ADDM server http/https connection port.
Default values – 80 for http
443 for https
ADDM server password for username used to perform
discovery. The password is specified in encoded format.
For example – If the password is Disc123# then it should
be specified as Disc123%23 in input.
ADDM server username used to perform discovery.
If ADDM uses secure connection specify this value as
“true” else “false”
If ADDM servers should be added to BSA during
workflow job execution specify this value as “true” else
“false”
Fully qualified group path in BSA containing the Agent
installer job. For example, if the agent installer job is
present in “Jobs -> Installers” group then it should be
specified as “/Installers”
Name of the agent installer job.
Name with which Bladelogic adapter is enabled on AO
grid.
If ITSM helpdesk ticket should be created for all failed
RSCD agent installations during workflow job execution
specify this value as “true” else “false”
Date specified in yyyy-mm-dd format. During job
execution only servers discovered by ADDM after this
date will be retrieved. For example – for all servers
discovered after 24 February 2014 it should be specified
as 2014-02-24
Comma separated list of hostname to be excluded from
discovery. For example – to exclude all server hostnames
which contain “esxi” or “corporate” in their name it
should be specified as – esxi,corporate.
Name with which HTTP adapter is enabled on AO grid.
If RSCD agent should be installed on all the servers
added to BSA during workflow job execution specify this
value as “true” else “false”
Comma separated list of operating system types to be
excluded from discovery. For example – to exclude all
rhel and solaris servers it should be specified as –
rhel,solaris
Comma separated list of subnets to be excluded from
discovery. All the servers which are present in these
Workflow Job Group Path
Workflow Job Name
subnets will be excluded from discovery. For example –
to exclude all servers which are present in
192.168.9.0/24 and 10.129.48.0/20 it should be
specified as – 192.168.9.0/24,10.129.48.0/20
Fully qualified group path in BSA containing the
workflow jobs. For example, if the workflow installer job
is present in “Jobs -> ADDM-BSA-Integration-Jobs” group
then it should be specified as “/ADDM-BSA-IntegrationJobs”
Name of the workflow job. By default it should be “Get
Discovered Servers”
Custom Server Properties
Following custom server properties need to be created for “Server” class.
1. DISCOVERED_SERVER – Type:Boolean, Default value:false
2. AGENT_INSTALL_ATTEMPT - Type:Boolean, Default value:false
3. HELPDESK_TICKET_CREATED - Type:Integer, Default value:0
Steps to create custom properties
1. Connect to BSA server using BSA console
2. Open “Property Dictionary” view
3. Under “Built-In Property Classes” go to “Server” class and click on + sign.
4. In “Name” field type in the property name say “DISCOVERED_SERVER”
5. In “Type” provide the appropriate type. In this case it would be Boolean
6. Provide the default value as applicable. In this case it would be “false”.
Troubleshooting
1. Execution status of BSA workflow job created earlier is “failed”. Execution logs contain the
following error - An unknown error occurred in AO. If needed, please refer to the AO logs or
AO Administrator for more information, AO Process Status is: 'COMPENSATED'
Troubleshooting – Scan AO “processes.log” for errors similar to one belowno peer with a running instance of HTTPAdapter found
If similar error exists in log that means one of the required adapters is not enabled on the AO
CDP/LAP/AP peer. Enabling the missing adapters should resolve the issue.