How to configure the event integration between TrueSight Middleware and Transaction Monitor and TrueSight Infrastructure Management
TrueSight Middleware and Transaction Monitor (TMTM) generates events when defined conditions (called triggers) are met. These events can be forwarded to one or more actions (e.g. EMail, LogToFile, PutToQ, Execute Script, and BEM). TrueSight Infrastructure Management provides an environment to correlate and manage events from a variety of sources, including TMTM.
If you have both TMTM and TrueSight Infrastructure Management, it is recommended to use the BEM action to integrate the TMTM events into TrueSight Infrastructure Management. This topic describes the configuration steps needed to enable this process.
How it works
As described in How to configure the data integration between TrueSight Middleware and Transaction Monitor and TrueSight Infrastructure Management, the fundamental architecture of TMTM is publish/subscribe based, with each TMTM extension talking to a specific technology to retrieve all of the key properties of all of the key objects under that technology.
When any of these properties changes, the extension publishes the changed value using an API supplied by the TMTM agent (called QPEA). The agent then transmits that topic/value pair to the TMTM server where it is received by the Topic Service component (QPTS). QPTS then sends a copy to any other components of the TMTM server that have registered interest in the topic.
One of these subscribers is called the TMTM Event Service (QPES). In configuring QPES, you define one or more Boolean conditions based on any combination of topic values. For example, you could define a condition for an MQ queue when (Messages Waiting > 0 && Read Rate = 0). This provides a very proactive notification of an MQ-based application not processing data. When such a condition is defined, QPES subscribes to all of the topics needed to evaluate the condition. If the condition is true, QPES then calls the defined action(s). For details of this configuration, see Events.
BMC provides a collection of thousands of these possible conditions gathered into TMTM Policies. For a recommendation of which events to enable, see the Tech_Agents_Standard_BEM Policy supplied in TMTM (where Tech is WMQ, WMB, EMS, DataPower, WAS, etc). When the BEM action is selected (as with those with the *_BEM Policies referenced above), QPES calls msend and passes an event of class BMTM_Event to the target TSIM Cell.
To configure the event integration
- Compile the TMTM Event Classes into the TrueSight Infrastructure Management Cell(s):
- On the Impact Manager host, navigate to the $MCELL_HOME/etc/$CELL_NAME/kb directory.
- Copy the BAROC file (bmtm.baroc) provided in the BEM folder on the TMTM install media into the classes sub-directory of the kb directory.
- Edit the .load file in the classes directory, adding
bmtmto the list.
- Recompile the knowledge base, using the command:
- Restart the cell.
- Install a TrueSight Infrastructure Management Cell on the TMTM server,
ORInstall the msend binary on the TMTM server system:
- Locate the msend binary in the BMC Impact and Event Management installation.
- Make the msend binary available to the user that will be starting the TMTM Event Service.
- Copy the msend binary and grant permissions to the TMTM Event Service user.
- The msend binary must be on the PATH of the TMTM Event Service user.
- Set the MCELL_HOME environment variable, if not already set. For a remote Impact Manager, the cell directory configuration should be copied across from the remote IM and placed under the MCELL_HOME directory.
- Test msend setup by issuing the
msendcommand from the user environment that will be starting the TMTM Event Service
- Log in as the user running the TMTM Event Service.
- At a command line, run
msend -n <cell_name> -a BMTM_Event -m "Testing BMTM Integration"Note that the event should be visible in the BMC Impact Explorer (IX).
- Add an mcell_name property value to the [Event_Service] section of the services.cfg file in the TMTM server installation directory.
- Restart the TMTM Event Service.
- At this point, any events generated in TMTM using the BEM action will appear in the TrueSight Infrastructure Management Cell. Work with your TMTM Administrator to enable these events (through the Tech_Agents_Standard_BEM Policy in TMTM, or manually).
Note that TMTM events will appear in TrueSight Infrastructure Management under the BMTM_Event class. The BEM_Generic Format script in the BEM_Generic Action will assign variable event slots such as Severity, Category and Sub-Category to each event based on the TMTM trigger (the condition causing the event).
Values are assigned to all BMC supplied event conditions. Appropriate values can be assigned to custom TMTM events by editing the BEM_Generic script. If no value is assigned for a particular TMTM trigger, the BMTM_Event will be assigned Severity = UNKNOWN, Category = OPERATIONS_MANAGEMENT, and SubCategory = OTHER, so look for BMTM_Events with UNKNOWN Severity and work with your TMTM Administrator to assign the required values for those triggers.