Configuring IBM Integration Bus for data enablement
For some data to be available in the Cloud APM console, you must configure IBM® Integration Bus to enable the required data collection.
Before you begin
Make sure that the IBM Integration Bus agent is configured.
About this task
Archive statistics and resource statistics can be monitored by the IBM Integration Bus agent only after the data collection is enabled for the integration node (broker). Similarly, if you want to see the transaction tracking in the middleware and topology dashboards, you must enable transaction tracking within the integration node (broker) before you enable transaction tracking for the IBM Integration Bus agent.
Decide what type of data that you want to monitor with the IBM Integration Bus agent and complete the following steps according to your needs.
Integration servers that are owned by the integration node have a default server.conf.yaml configuration file for each integration server that is stored in a subdirectory of the integration node directory. Any properties that you set for the integration node in the node.conf.yaml file are inherited by the integration servers that it owns. Nonetheless, you can change an integration server's properties by modifying them in its server.conf.yaml file. (For more information, see Configuring an integration node by modifying the node.conf.yaml file in the IBM App Connect Enterprise documentation.)
Procedure
- To enable archive statistics data collection for the integration node (broker), see Enabling archive accounting and statistics data collection.
- To enable resource statistics data for an integration node (broker), see Enabling JVM resource statistics.
- To enable transaction tracking for message flows within an integration node (broker), see Enabling transaction tracking.
- If you no longer want transaction tracking data, remember to disable transaction tracking for the integration node (broker) on which it was enabled. See Disabling transaction tracking.
Enabling archive accounting and statistics data collection
About this task
To enable archive accounting and statistics collection for message flows that belong to the integration node (broker), issue the mqsichangeflowstats command from the bin directory of the integration node (broker) installation directory.
Procedure
Results
- Message Flow Dashboard
- Commits & Backouts
- CPU Microseconds
- Elapsed Microseconds
- Input Byte Rate
- Input Message Rate
- Input Message Size
- Input Message Wait CPU Microseconds
- Input Message Wait Elapsed Microseconds
- Message Flow Errors
- Message Processing Node Statistics
- Processing Node Dashboard
- CPU Microseconds
- Elapsed Microseconds
- Invocations
- Processing Node Status
- Terminal Statistics
Enabling JVM resource statistics
About this task
Procedure
Results
- Garbage Collection Count
- Garbage Collection Duration
- JVM Non-Heap Memory
- JVM Heap Memory
Enabling transaction tracking
Before you begin
- Make sure that the IBM Integration Bus agent is installed. A user exit named KQIUserExit is provided to enable IBM Integration Bus for transaction tracking.
- Make sure that the user who will start the integration node (broker) has access to the KQI User Exit module directory. That is, ensure that you add the user ID that is used to start the integration node (broker) to the group under which you installed the IBM Integration Bus agent.
About this task
You must deploy the KQIUserExit user exit to the integration node (broker). Otherwise, no data is available in the middleware and topology dashboards even after you have enabled the IBM Integration Bus agent for transaction tracking.
- Database and compute nodes where an ODBC data source is specified
- TCP/IP nodes
- File nodes for remote FTP or FTPS servers
- MQ nodes, unless already instrumented
Procedure
To enable transaction tracking for IBM Integration Bus, complete the following steps:
Disabling transaction tracking
Procedure
To disable transaction tracking for IBM Integration Bus, complete the following steps:
What to do next
- For transaction tracking, after you enable transaction tracking for IBM Integration Bus, you must also enable transaction tracking for the agent. For instructions, see Configuring transaction tracking for the IBM Integration Bus agent.
- If you have enabled snapshot data collection for your integration node (broker), configure the IBM Integration Bus agent not to store any snapshot data. Cloud APM does not support snapshot accounting and statistics data due to the amount of data and processing required for the set 20 second snapshot interval. For instructions, see Disabling snapshot data collection for the agent.