Enabling the Data Collector for WebSphere Message Broker

After you have installed the Data Collector for WebSphere Message Broker, you must enable it.

Before you begin

Before enabling the Data Collector for WebSphere Message Broker, you should first configure the KK3.dc.properties file. Set the following properties:
  • default.monitor=on
  • default.tt.enabled=true
  • default.tt.serverstring=address of Transaction Collector
  • default.ttdc.mq.installdir=path-to-MQTracking-installation-directory
See KK3.dc.properties for further information.
Note: Check that the account you use to run the configuration script has permission to write to the MQSI_WORKPATH/common/profiles directory. That user also needs permissions to write to the WebSphere Message Broker and IBM Tivoli Monitoring directories.

About this task

To enable the Data Collector for WebSphere Message Broker, enable the KK3UserExit for all Message Flows to be monitored. The KK3UserExit can be enabled for individual Message Flows, or it can be enabled for an entire WebSphere Message Broker instance.

Procedure

To enable the Data Collector for WebSphere Message Broker environment:

  1. Check that the account you want to use to run the configuration script has permission to write to the MQSI_WORKPATH/common/profiles directory.
  2. Run the configDC script to configure an environment to load the user exit library. For example, on AIX systems:
    cd /opt/IBM/ITM/aix513/k3/bin
./configDC.sh -enable /opt/IBM/mqsi/7.0
    On Linux systems:
    cd /opt/IBM/ITM/ls3263/k3/bin
. ./configDC.sh -enable /opt/IBM/mqsi/7.0
    Tip: Ensure you are using the UTF-8 character set.
  3. Verify that the KK3UserExitProfile script is created in MQSI_WORKPATH/common/profiles.
  4. Close the consoles or shells:
    • On Windows systems, close all WebSphere Message Broker Command Consoles
    • On UNIX and Linux systems, close all shells that have loaded the MQSI environment
  5. Load the MQSI environment for the broker installation for which you want to upgrade the user exits:

    On Windows systems, select the Command Console shortcut from the WebSphere Message Broker start menu.

    On UNIX systems, use the mqsiprofile script in the WebSphere Message Broker installation bin directory. For example, . /opt/ibm/mqsi/7.0/bin/mqsiprofile.

  6. Stop the WebSphere Message Broker instance on which you want to configure user exits. 
    mqsistop broker_name
  7. Optional: Run the mqsichangebroker command to enable the KK3UserExit for all Message Flows on the WebSphere Message Broker instance: 
    mqsichangebroker broker_name -e "KK3UserExit"

    If you skip this step, the KK3UserExit is disabled for all Message Flows by default.

    Note: This command overrides the current set of default active user exits. Specify additional user exits using the colon (:) character.
  8. Restart the message brokers to load the user exit libraries. For example:
    mqsistart broker_name
  9. Optional: If you skipped step 5, run the following command to enable the KK3UserExit for a particular Message Flow: 
    mqsichangeflowuserexits broker_name -e egName -f \
   messageFlowName -a "KK3UserExit"
    Tip: Specify additional user exits using a colon-separated list.
Parent topic: Preparing Data Collector for WebSphere Message Broker