Prerequisites for the BMC Server Automation adapter

The following requirements must be met before you use the adapter:

• BMC Server Automation Console and NSH must be installed on the peer where the adapter is enabled—CDP, AP, or LAP if you use Secure Remote Password (SRP) or AD/Kerberos authentication.
• If the BMC Server Automation server is running on Windows, the peer service must be running with administrative rights or as a standard user.
• The user profile running the peer service should have read and execute rights on the installation folder for BladeLogic Server Automation Console and NSH.
• To communicate with the BMC Server Automation server using an NSH script, you must run the blcred cred -acquire command in the script itself.
• You must configure the adapter to work with the BladeLogic single sign-on (SSO) feature.
• If the BladeLogic client is installed on the computer after the installation of TrueSight Orchestration, you must restart the peer before enabling the adapter.
• For using the Active Directory/Kerberos authentication mechanism, you must configure Active Directory and the Kerberos protocol on the peer where the adapter is enabled.
• For executing Jython commands using the adapter, you must install Jython on the peer where the adapter is enabled.

Additionally, if you want to use the adapter with the BladeLogic Web Services interface, you must enable web services on the BladeLogic Application Server.

For more information about BLCLI commands, on the BladeLogic Console, navigate to Start > Programs > BMC Software > BladeLogic Server Automation Suite > BLCLI Help.

To enable web services

1. On the Application Server, start the blasadmin utility and type the following command:
   set AppServer enableWebServices true
2. Restart the application server.