Configuring the Microsoft Operations Manager 2005 adapter

You configure an adapter in Grid Manager. The configuration provides information about how the adapter interacts with the Microsoft Operations Manager 2005 application. While each adapter must have a unique name, you can create multiple adapters with the same adapter type to allow for different configuration properties.

The form view provides an easy-to-use interface for configuring adapters. The form view prevents human errors that might occur as a result of copying the configuration XML from the XML sample into the UI when configuring an adapter. You can switch to the XML view to configure all those elements and attributes using XML only. However, after you switch to the XML view and save the configuration in the XML from that view, you cannot thereafter use the form view for modifying that configuration.

Note

The default name for the actor adapter is MOM2005Adapter.

To configure the actor adapter, monitor adapter, or both

  1. Log on to the BMC Atrium Orchestrator Grid Manager.
  2. Access the adapters page by clicking the Manage tab; then click the Adapters tab.
  3. In the Adapters in Repository list:
    • Select the ro-adapter-microsoft-operations-manager-2005-actor check box to configure the actor adapter.
    • Select the ro-adapter-microsoft-operations-manager-2005-monitor check box to configure the monitor adapter.
    • Select both check boxes to configure both adapters.
  4. Click Add to Grid to include the adapter in the Adapters on Grid list.
  5. Click Configure corresponding to the newly added adapter.
  6. On the Add an Adapter Configuration page, perform the following substeps to configure the adapter using the form view or skip to step 7 to configure the adapter using the XML view:
    1. Enter a name for the adapter.
    2. Enter a description for the adapter.
    3. Under Properties, enter or select values for the configuration elements. Include all required elements indicated with an asterisk ( * ).
    4. Click OK.
  7. ( optional ) Configure the adapter in the XML view using the following substeps:
    1. Enter a name and a description for the adapter.
    2. Click Switch to XML View.
    3. On the Warning message that appears, click Switch View.
    4. In Properties, enter the adapter configuration properties in an XML format, including all required elements as indicated in the following table.

      The Properties text box must contain a valid XML configuration node for the adapter.

      Note

      If the default value for an optional element is acceptable, omit the element. Do not include empty elements.

    5. On the Warning message that appears, click Save.

      This saves the adapter configuration with settings in the XML view permanently. The newly configured adapter is now listed in the Adapters on Grid list.

      The following table describes the node elements required to configure the actor adapter:

      Node elements for configuring the actor adapter

      UI Label

      Element

      Definition

      Required

      Target

      <target>

      Specifies the IP address of the server on which the MOM web service is running Default value: 99.99.99.999

      Yes

      Port

      <port>

      Specifies the port on which the MOM web service is running Default value: 1271

      Yes

      Transport

      <transport>

      Specifies the transport protocol for the message Default value: http-rpc

      Yes

      User Name

      <user-name>

      Specifies the user name required for authentication

      Yes

      Password

      <password>

      Specifies the password associated with the <user-name> provided

      Yes

      Connector Prop Path

      <connector-prop-path>

      Specifies the connector properties file path on the peer where the adapter is enabled This file contains the connector registration IDs that are required for performing Create, Update, and Delete operations on alerts. These registration IDs are created the first time that the adapter is enabled. If the adapter is enabled on multiple peers and you want to use the same connectors for each of them, copy the same properties file to all the peers. This is required if you expect the same alert data to be retrieved from all the enabled adapters. If you do not copy the properties file to all the peers where the adapter is enabled, new connector registrations are done, and a new properties file is created on each peer.

      Yes

The following figure shows an XML sample for configuring the actor adapter.

XML sample for configuring the actor adapter

 <config>
  <target>99.99.99.999</target>
  <port>1271</port>
  <user-name>Administrator</user-name>
  <password>********</password>
  <transport>http-rpc</transport>
  <connector-prop-path>C:/MomTest</connector-prop-path>
</config>


The following figure describes the node elements required to configure the monitor adapter:

Node elements for configuring the monitor adapter

UI Label

Element

Description

Required

Port

<port>

Specifies the port on the CDP computer that listens for SNMP traps from the Microsoft Operations Manager 2005 application adapter Valid value: 162 (Only the default port is allowed.)

Yes

Version

<version>

Specifies the version of SNMP

Yes

Mibs Directory

<mibs-directory>

Specifies the directory in which you have copied the Microsoft Operations Manager 2005 application adapter Management Information Base (MIB) file Valid value: test/conf/mibs directory To use the monitor adapter successfully, verify that the MIBs directory path exists on all the peers on which you enable this adapter. An invalid path causes the adapter to go into a fault state.

No

The following figure shows an XML sample for configuring the monitor adapter.

XML sample for configuring the monitor adapter

 <config>
  <port>162</port>
  <version>1</version>
  <mibs-directory>*****</mibs-directory>
</config>

Enabling custom logging

To enable custom logging for the adapter, you must specify a log file name. You can also provide additional parameters for logging.

Note

You must be using BMC Atrium Orchestrator Platform version 7.8 or later to use the custom logging feature. These parameters will be ignored in earlier versions of BMC Atrium Orchestrator Platform.

These parameters are available with supported adapter versions. See your adapter documentation for details.

  • Log File Name: Provide a name for the log file.
    This file will be stored in the AO_HOME/tomcat/logs directory. If Log File Max Backup Index value is greater than 0, the log file name is suffixed with the backup index. For example, if the parameter value is a.log, backup log files will have names, such as a.log.1, a.log.2.
  • Log File Size: Specify a size limit for the log file. 
    If the value specified for Log File Max Backup Index is greater than 0, when the specified size is reached, the current file is renamed with the suffix .1. Otherwise, the log file will be reset and over-written. The default value is 10MB. The available units are KiloBytes (KB), MegaBytes (MB) or GigaBytes (GB).
  • Log File Max Backup Index: Enter the maximum number of backup files allowed. The default value is 10.
  • Log File Append: Select this option to append new log information to the existing information in the file. If unselected, the file will be overwritten with new log information.
  • Log Level: Enter the logging level using one of the following choices:

    Logging level

    Description

    DEBUG

    The most detailed logging level; logs low-level messages, normal execution, recoverable erroneous conditions, and unrecoverable erroneous conditions

    INFO

    (default)

    Logs normal execution, recoverable erroneous conditions, and unrecoverable erroneous conditions

    WARN

    Logs recoverable erroneous conditions and unrecoverable erroneous conditions

    ERROR

    The least detailed logging level; logs only error conditions that are not usually recoverable

Was this page helpful? Yes No Submitting... Thank you

Comments