2.3 BMC Software Event Manager

Integrating BMC Impact Manager with Operations Center requires the following components:

Follow the steps in Section 2.3.1, Integrating BMC Event Manager to integrate Event Manager and Operations Center, with the considerations noted in the additional subsections. Completing these steps connects the adapter to the MCORB, and the MCORB to the MCELL.Next, configure the MCELL so that the MCORB is treated as an MCELL. This requires a propagation rules that sends add, change and delete events to the MCORB.

Note the adapter to MCORB communications uses RMI, and the MCORB to MCELL communications uses the Impact Integration C API.

The Operations Center server (where the adapter runs), MCORB and MCELL can reside on different hosts. However, note that MCORB supporting Impact Manager requires a Windows 2003 server (32‑bit only) or a Solaris (SPARC) 9 or 10 (32‑bit only).

2.3.1 Integrating BMC Event Manager

To integrate Event Manager:

  1. Install the Event Manager MCORB software.

    For instructions, see Section 10.0, ORB Installation.

  2. Integrate the BMC Impact Manager which includes configurations for the MCORB, the BMC Event Manager, and MCELL by doing the configurations as outlined in Section 2.3.2, Configuring MCORB and Section 2.3.3, Configuring MCELL.

  3. Run the mcorbtest to validate the connectivity with the MCORB.

    For information on the mcorbtest command, see Section 10.2.4, Starting, Stopping, and Testing MCORB.

  4. Start the MCORB using the standard command listed in Section 10.2.4, Starting, Stopping, and Testing MCORB. For example:

    mcorb start

  5. Create a BMC Event Manager adapter for each instance of Event Manager on the network.

    For general instructions on creating adapters, see Section 5.1, Creating an Adapter.

  6. Modify the adapter properties.

    In the appropriate fields in the Create Adapter dialog box, specify the BMC Event Manager server’s host name, MCORB port number (1099, or the one chosen earlier), and cells to be discovered by the adapter in the adapter’s properties.

    1. Set RemoteHost to the hostname or IP address where the MCORB is installed.

    2. Set RemotePort to the MCORB RMI Port.

    3. Set CellsToDiscover to the name of the MCELL entered in the MCORB mcell.dir file entry; for example:

      sunfire440

    4. Accept the defaults for the remaining adapter properties.

      In general, it is acceptable to use these defaults. For more information about adapter properties, see Section A.4, BMC Software Event ManagerSection A.4, BMC Software Event Manager.

      For detailed descriptions of the adapter properties, see Section A.4, BMC Software Event Manager.

2.3.2 Configuring MCORB

To configure the MCORB software:

  1. Verify the following for the MCORB installation:

    • Hostname: The host on which MCORB is installed. This host name is required for configuring both the Event Manager adapter and the BMC Impact Manager Cell.

    • RMI Port Number: The RMI port number is used to configure the Event Manager adapter.

      The default is 1099. If the MCORB is installed on the same server as the Operations Center server, select a different port, such as 2099, because other Operations Center Server components typically use port 1099.

    • MCORB Cell Name: The RMI port number is used to configure the Event Manager adapter.

      This MCORB Cell Name must begin with mcorb_. The typical naming convention is mcorb_hostname. For example, if the host name is sunfire440, the cell name is mcorb_sunfire440.

  2. Verify there is a valid Java 1.6 VM available, and set the Java Home location appropriately; for example:

    opt/java16

  3. Edit the ~MCORB/config/mcell.dir file.

    Add an entry for both the MCORB and the MCELL. An example:

    # sunfire440 cell definition
cell sunfire440 mc sunfire440:1828
# mcorb cell definition
cell mcorb_devtower6 mc devtower6:1828

  4. After completing the configuration, copy the new native library over the installed native library in the ~MCORB/lib directory over to a directory on the Operations Center server:

    • For Windows, copy mosbmclib.dll and bmciiapi.dll.

    • For Solaris SPARC, copy MosBmcLib.so and bmciiapi.dll.

    Verify that the target directory is defined for the server’s LD_LIBRARY_PATH for Solaris/Unix, or the PATH environment variable on Windows.

2.3.3 Configuring MCELL

To configure the MCELL to communicate with MCORB:

  1. Create a mcell.dir file entry for the MCORB; for example:

    # devtower6 mcorb definition
cell    mcorb_devtower6 mc      devtower6:1828

  2. Create an MCORB propagate rule.

    For example, create the ~MCELL/etc/sunfire440/kb/rules/mcorb_propagate.mrl file, then add the following lines to the file:

    propagate mcorb_propagate :
   EVENT ($EV)
   to all [ mcorb_devtower6 ]
END

  3. Add the mcorb_propagate rule to the Ruleset.

    For example, add a line to ~MCELL/etc/sunfire440/kb/rules/.load, such as:

    mcorb_propagate

  4. Stop MCELL.

    Assuming that your MCELL environment is set up, run the following command:

    mkill sunfire440

  5. Compile the Ruleset.

    Assuming that your MCELL environment is set up, run the following command:

    mccomp -n sunfire440

  6. Start MCELL.

    For example, run the following command:

    mcell -n sunfire440