Child pages
    • Enabling BMC Atrium Orchestrator to run commands
    Skip to end of metadata
    Go to start of metadata

    This topic provides instructions on enabling BMC Atrium Orchestrator to run commands on a BMC Atrium Discovery appliance. You can do this by installing the BMC Atrium Orchestrator Lightweight Activity Peer (LAP) 7.7.01 on the BMC Atrium Discovery appliance.

    This is intended for executing long running operations, for example:

    To install BMC Atrium Orchestrator Lightweight Activity Peer

    Executing the graphical installer does not work as it requires X which is not available on a BMC Atrium Discovery appliance. Rather, you must perform a silent install. A silent install relies on a file containing all of the installation options that would normally be set using the GUI install. See the LAP installation worksheet for more information.

    The installation consists of the following major steps:

    To create an installation options file

    Copy the following sample file into a text editor and edit the options to suit your environment. The fields are described in the BMC Atrium Orchestrator silent installation documentation.

       -P installLocation=/usr/local/bmc/BAO/LAP
       -J AO_INSTALL_TYPE=install_new
       -J AO_ENVIRONMENT_NAME=BAO Environment
       -J AO_GRID_NAME=MyGrid
       -J AO_GRID_TYPE=dev
       -J AO_REPOSITORY_PORT=28080
       -J AO_SECURITY_ACTIVE=false
       -J AO_WEBSERVER_PORT=38080
       -J AO_PEER_COMM_PORT=61719

    Save this file onto the BMC Atrium Discovery appliance file system, for example, /usr/tideway/tmp/optionsFile.

    To install BMC Atrium Orchestrator Lightweight Activity Peer

    To proceed with the install, create the install directory as root and change its ownership to the tideway user:

    1. Log in to the appliance command line as the tideway user.
    2. Run screen. Enter: 
      [tideway@localhost ~]$ screen
    3. Become the root user. Enter:
      [tideway@localhost ~]$ su 
      [root@localhost tideway]#
    4. Create the installation directory and change its ownership to the tideway user. Enter:
      [root@localhost tideway]# mkdir /usr/local/bmc
      [root@localhost tideway]# chown tideway:tideway /usr/local/bmc
      [root@localhost tideway]# exit
      [tideway@localhost tideway]$
    5. Open port 61721, or whichever port you intend to use for LAP communications. Use a text editor to add the following entries to the firewall configuration file /etc/sysconfig/iptables.
      :in_TIDEWAY_bao - [0:0]
      -A in_TIDEWAY -j in_TIDEWAY_bao
      -A in_TIDEWAY_bao -p tcp -m tcp --sport 1024:65535 --dport 61721 -m state --state NEW,ESTABLISHED -j ACCEPT
    6. Switch back to the tideway user:
      [root@localhost tideway]# exit
      [tideway@localhost tideway]$ 
    7. Unset the Tomcat environment variables. Enter:
      [tideway@localhost tideway]$ unset CATALINA_BASE CATALINA_HOME
    8. Run the installer in silent mode as the tideway user, passing it the options file:
      [tideway@localhost tideway]$ sh -i silent -DOPTIONS_FILE="/usr/tideway/tmp/optionsFile"
      Initializing blind certificate trust...
      Composing URL from components: protocol=https,, port=38080, file=baocdp/ws/install
      Composed URL: []
      Creating config fetcher from []
      Composing URL from components: protocol=https,, port=38080, file=baocdp
      Composed URL: []
      Composing URL from components: protocol=https,, port=38080, file=baocdp/ws/install
      Composed URL: []
      Creating config fetcher from []
      Apr 11, 2014 5:03:59 PM
      WARNING: LOG EVENT {Description=[Certificate stored in file <temp.cer>]}
      Apr 11, 2014 5:04:01 PM
      WARNING: LOG EVENT {Description=[Certificate was added to keystore]}
      [tideway@localhost tideway]$
    9. Check that you have the following java process running for the LAP:
      /usr/local/bmc/BAO/LAP/jvm/bin/java -Djava.util.logging.config.file...

    Configure LAP to run on boot

    To configure LAP to run at boot time, use a text editor to edit the BMC Atrium Orchestrator start up file.

    1. Edit /usr/local/bmc/BAO/LAP/bin/ and set RUN_AS_USER=tideway
    2. Remove the "-" from all of the "su -" commands in that file. This prevents the superuser inheriting the tideway user's environment variables. For example, the tideway user's Tomcat environment variables refer to the BMC Atrium Discovery Tomcat instance.
    3. Become the root user. Enter:
      [tideway@localhost ~]$ su 
      [root@localhost tideway]#
    4. Create a symlink to the BAO startup script from the system startup scripts directory. Enter:
      [root@localhost tideway]# ln -s /usr/local/bmc/BAO/LAP/bin/ /etc/init.d/bao_lap
      [root@localhost tideway]# chkconfig bao_lap on
      [root@localhost tideway]# chkconfig |grep bao_lap

       bao_lap         0:off   1:off   2:on    3:on    4:on    5:on    6:off
      [root@localhost tideway]# 

    Timeout of long running processes

    Long running processes have been observed to timeout with the following message: "A request was sent to a remote peer and a response was not received prior to the specified timeout". The following workaround prevents this occurring.

    1. Create an XML file called tuning-config.xml using the following code:
                      <!-- timeout in milliseconds. 36000000 is 10 hours -->
                      <!-- must exceed the longest expected execution time of a process -->
    2. Copy the tuning-config.xmlfile to the following locations:
      • On the BMC Atrium Discovery appliance -- /usr/local/bmc/BAO/LAP/config/
      • On the BMC Atrium Orchestrator CDP host -- C:\Program Files\BMC Software\BAO\CDP\config\ or /opt/bmc/BAO/CDP/config
      • On the machine running the Dev Studio GUI (if required)  -- C:\Program Files\BMC Software\BAO\Studio\config\

    Known issue with current BMC Atrium Discovery versions

    The firewall changes must be applied again if BMC Atrium Discovery is upgraded.

    • No labels


    1. Hi Duncan Tweed,


      I noticed that this page was recently updated to remove the following example usage of AO integration:


      Run a discovery and wait for completion


      This is something that we're currently looking to explore, but am now wondering if this is possible?  Although I've not been able to get much further info about the integration from BMC, I understand that it should be something relatively easy to accomplish using the SSH adapter/connector and LAP client?


    2. Hi Mark,

      The example of running discovery and waiting for completion was removed as it was a poor example. The Atrium Orchestrator integration using LAP is intended for long-running command. Running a discovery and waiting for completion is not in fact a long-running command in this sense, because there is not a single command that blocks until a discovery is complete.

      You can use Atrium Orchestrator to start scans using Atrium Orchestrator's remote access. If your only intended use for Atrium Orchestrator with BMC Discovery, you do not need to install the LAP.

      Hope that helps.


    3. Thanks Duncan,


      In regard to using AO to initiate scans without the need for LAP, I assume it'd be a case of configuring AO as per step 7 on the following?


      BMC Atrium Orchestrator VMotion events


      Would AO still need to make use of the ssh adapter?


      Also, if we wanted to be able to query the scan result from an appliance via AO using something like tw_query, would we need LAP on the appliances?

    4. Hi Mark,

      Yes, I think that is the case. Use the connection information from the link you gave, and BMC Atrium Orchestrator would need to use the ssh adapter.

      You wouldn't need LAP on the Discovery appliance for tw_query, LAP is only required for long running blocking commands.

      Hope that helps,