How to configure the data integration between TrueSight Middleware and Transaction Monitor and TrueSight Infrastructure Management

How it works

The fundamental architecture of TrueSight Middleware and Transaction Monitor is publish/subscribe based. Each TrueSight Middleware and Transaction Monitor extension talks to a specific technology to retrieve all of the key properties of all of the key objects under that technology. For example, the monitoring extension for WebSphere MQ connects to each queue manager and retrieves the queue manager properties as well as the properties of all child queues, channels, listeners, etc. 

When any of these properties changes, the extension publishes the changed value using an API supplied by the TrueSight Middleware and Transaction Monitor agent (called QPEA). The agent then transmits that topic/value pair to the TrueSight Middleware and Transaction Monitor server where it is received by the Topic Service component (QPTS). QPTS then sends a copy to any other components of the TrueSight Middleware and Transaction Monitor server that have registered interest in the topic. 

One of these subscribers is the ProactiveNet Service (QPPS). When configuring QPPS, use a History Template to select the "Enable ProactiveNet" column for each attribute that you wish to propagate to TrueSight Infrastructure Management. 

For example, you may want to propagate the MsgDeqRate (the Read rate) for an MQ queue, since this is a key performance attribute, but not the setting on the Trigger Control Switch (a 0-1 Boolean value) since that rarely changes. For each monitored object type, TrueSight Middleware and Transaction Monitor provides a SAMPLE History Template including recommended attributes for the data integration to TrueSight Infrastructure Management. 

When QPPS receives an update to the value of such a monitored attribute, it enqueues the data into a configured file location referred to as the Dropoff Directory. A BPM (Patrol) Agent is then installed into this environment and the Middleware and Transaction Management (MTM) KM is loaded into that agent. This is typically done using TrueSight Infrastructure Management CMA Policies. The only required configuration setting for the MTM KM is the path to the Dropoff Directory. Once loaded, the MTM KM reads the data from the Dropoff Directory and propagates it into TrueSight Infrastructure Management using the standard Patrol Agent mechanisms.

Related topics

Integrating-with-TrueSight-Infrastructure-Management

Integrating 

Planning

To configure the data integration

  1. On the TrueSight Middleware and Transaction Monitor Server, create a Dropoff directory to hold files from QPPS to the BPM Agent.

    • Can be any directory, e.g. {TrueSight Middleware and Transaction Monitor_HOME}/PNetDropoff

    • Both Patrol Agent and TrueSight Middleware and Transaction Monitor ProactiveNet Service must have full permissions to this directory

  2. On the TrueSight Middleware and Transaction Monitor Server, configure the Dropoff directory for QPPS in the services.cfg in the TrueSight Middleware and Transaction Monitor Server installation directory.

    [ProactiveNet_Service]
    enable_proactivenet_integration=true
    disk_space_to_reserve_in_megabytes=100
    seconds_between_full_tree_resynchronizations=300
    seconds_to_check_for_configuration_changes=1800
    update_directory_path=Path/To/DropoffDirectory
    show_bmtm_agents_as_top_level_devices=    true
     

  3. Use the BPM Common Installer or CMA to install the Patrol Agent on the TrueSight Middleware and Transaction Monitor Server and load the MTM KM into that Patrol Agent.

    1. Connect the Patrol Agent to your Integration Service or TrueSight Infrastructure Management Server as normal.

    2. MTM KM is in TrueSight Infrastructure Management Extended Repository and in the TrueSight Middleware and Transaction Monitor Install Directory.

      1. From the TrueSight Middleware and Transaction Monitor Install Directory, extract MTM_ALL_8100.zip (or .tar) into the installer directory and run the installer.

      2. The version of the MTM KM must exactly match the version of the TrueSight Middleware and Transaction Monitor Server.

    3. Set up a CMA Policy to load the MTM KM, setting the Droppoff Directory path into the CMA properties.

  4. Start the TrueSight Middleware and Transaction Monitor ProactiveNet Service.

    1. Service is set to Manual by default on Windows.

    2. From the TrueSight Middleware and Transaction Monitor Server installation directory, run qpps --start on Linux.

  5. Work with your TrueSight Middleware and Transaction Monitor Administrator to associate the appropriate History Templates with your objects either by using the Policy called Tech_Agents_Level where Tech is WMQ, WMB, DataPower, and Level is Basic for just the data integration. Note that if you are configuring both the data and event integrations, Level should be Standard_BEM (see How to configure the event integration between TrueSight Middleware and Transaction Monitor and TrueSight Infrastructure Management).

  6. When this is complete, you should see a TrueSight Infrastructure Management device created for each TrueSight Middleware and Transaction Monitor Agent. That device should contain a monitor for each TrueSight Middleware and Transaction Monitor object and you should see the data begin to populate very quickly for the attributes specified.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*