Page tree
Skip to end of metadata
Go to start of metadata

To enable Infrastructure Management to communicate with BMC Atrium Orchestrator, you must configure the server cell on the BMC TrueSight Infrastructure Management Server and the BMC Atrium Orchestrator BMC Event Manager and adapter on the BMC Atrium Orchestrator Server.

Related topics

Components of Triage and Remediation Solution 

Using the Triage and Remediation solution

Installing the Triage and Remediation solution

To configure the TrueSight Infrastructure Management Server cell

  1. Open the installationDirectory\pw\server\etc\mcell.dir file, and add the name of the BMC Atrium Orchestrator gateway. (The mcell.dir file must already contain an entry for the local Infrastructure Management server cell.)

    The default entry is BEMGW. If you choose to use a different name for the BMC Atrium Orchestrator gateway, you must modify the ao_actions.mrl file and then recompile and restart the Infrastructure Management server cell. See 755236264.

    gateway.imcomm						BEMGW			mc			<hostIPaddress>:1859

    mc is the default cell encryption key. The hostIPAddress refers to the host name or IP address of the system where BMC Atrium Orchestrator is installed.

  2. If you use the BEMGW default gateway entry, you can proceed to 755236264.
  3. If you modify the default gateway entry in the mcell.dir file, then perform the following steps:
    1. Open the ao_actions.mrl file at installationDirectory\pw\server\etc\cellName\kb\bin.
    2. Change the BEMGW default gateway parameter value of the admin_execute command in all its instances in the ao_actions.mrl file to the new value. For example, the following extract shows the BEMGW default entry in the admin_execute command arguments:

      admin_execute(BEMGW,$EV,"Atrium_Orchestrator_Disk_Full_Workflow",
      	[$CREATECHANGERQUEST, $CHANGEREQUESTTYPE, $CREATEINCIDENT,
      	$REMEDIATE,$UID],YES);



      Enter the new gateway parameter value in each instance of the admin_execute command:

      admin_execute(newValue,$EV,"Atrium_Orchestrator_Disk_Full_Workflow",
      	[$CREATECHANGERQUEST, $CHANGEREQUESTTYPE, $CREATEINCIDENT,
      	$REMEDIATE,$UID],YES);
    3. Recompile the Infrastructure Management server cell by using the following command from the installationDirectory\pw\server\bin directory path:

      mccomp -n  <cellName>
    4. Restart the Infrastructure Management server cell by using the following command from the installationDirectory\pw\server\bin directory path:

      mcontrol -n <cellName> restart
  4. To enable the new DB Tablespace Full workflow for BMC PATROL events, perform the following steps:
    1. Append the entry "tsm" at the end of the installationDirectory\pw\server\etc\cellName\kb\rules\.load file, as shown in the following example:

      #
      # File name: .load
      # Version: 7.4.00
      # Copyright 1998-2009 BMC Software, Inc. All Rights Reserved
      #
      kbversem
      kbverssim
      mc_startup
      .........
      tsm
    2. Recompile the Infrastructure Management server cell by using the following command from the installationDirectory\pw\server\bin directory path:

      mccomp -n <cellName>
    3. Restart the Infrastructure Management server cell by using the following command from the installationDirectory\pw\server\bin directory path:

      mcontrol -n <cellName> restart

      Note

      The Infrastructure Management installation automatically creates the tsm.mrl file.

To configure the BMC Atrium Orchestrator BMC Event Management and Infrastructure Management monitor and actor adapters

  1. Launch the Configuration Distribution Peer (CDP) URL (for example: http://hostName:CDPPort/baocdp/gm).
  2. Add the following BMC Atrium Orchestrator BMC Event Manager and monitor adapter XML configuration properties to the CDP, replacing values as necessary:

    <config> 
    	<port>1859</port> 
    	<gateway-name>BEMGW</gateway-name>
    	<encryption-key>mc</encryption-key>
    </config>
  3. Create a single external configuration file for the BMC Event Manager and actor adapter and store it in the suggested file path.
    1. In Microsoft Windows, create a subdirectory named etc under the C:\Program Files\BMC Software\AO directory path: C:\Program Files\BMC Software\AO\etc.

      In UNIX, add the etc subdirectory to the /opt/bmc/ao/ path: /opt/bmc/ao/etc.
    2. In the new etc subdirectory, create an mcell.dir file: C:\Program Files\BMC Software\AO\etc\mcell.dir (or /opt/bmc/ao/etc/mcell.dir).
    3. Add the following two entries to your mcell.dir file:

      <TYPE>	         <NAME>	           <ENCRYPTION KEY>             <IPAddress:Port>
      cell		   <ProactiveNetcell>             mc			    <hostIPaddress>:1828
      gateway.imcomm	   BEMGW		             mc			        <hostIPaddress>:1859
      

      ProactiveNetcell is a variable. Use the actual name of the cell in your environment.
      The first hostIPaddress entry associated with the cell points to the system where the cell server resides. The second hostIPaddress entry is associated with the BEMGW gateway. It resides on the system where the BMC Event Manager and adapter are configured.

  4. Add the following entry to the BMC Atrium Orchestrator BMC Event Manager and actor adapter XML configuration on the CDP:

    <config>
    	<mcell-dir-file-path>C:\Program Files\BMC Software\AO\etc\mcell.dir
    		</mcell-dir-file-path>
    	<cell-name> <cellName></cell-name>
    </config>

    cellName is a variable. Use the actual name of the cell in your environment.

    Note

    For instructions on how to activate the adapters and other details, refer to the BMC Atrium Orchestrator Application Adapter User Guide for BMC Event Manager and ProactiveNet.

  5. Activate the adapters on Grid Manager. Then, from the Status tab, verify that the BMC Event Manager and monitor and actor adapters are highlighted in green in color.