You can obtain the data produced by the service activity monitoring facility through JMX notification. Optionally, you can use a Log4J log file to capture these JMX notifications.
JMX notification
When enabled, the service activity monitoring facility provides activity information about every transaction in the form of a JMX notification.
The following class diagram provides an example of the JMX notification process.
- The notification com.dwl.base.report.mbean.TransactionDataNotification is sent from the MBean com.dwl.base.report.mbean.TransactionDataBroadcasterMBean.
- The notification containing the com.dwl.base.report.TransactionData object can be obtained by calling the getTransactionData() method on the TransactionDataNotification class.
Each TransactionData object contains the map with information regarding a single InfoSphere® MDM Custom Domain Hub transaction. The names and type of the objects in the map are provided in Configuring the service activity monitoring facility.
In order to capture the JMX notification, InfoSphere MDM Custom Domain Hub registers the listener with the MBean Server, providing the object name of the MBean that issued the notification. The object name is platform-specific and partially depends on the values of the installation parameters configured during installation of InfoSphere MDM Custom Domain Hub.
DWL:type=com.dwl.base.report.mbean.TransactionDataBroadcasterMBean,
deployment=deployment1,J2EEApplication=deployment1,process=server1,
cell=userNode01Cell,node=userNode01Log4J log file
The service activity monitoring facility provides activity information about every transaction in the form of JMX notification. InfoSphere MDM Custom Domain Hub supplies an implementation of JMX listener to capture these JMX notifications and send it to the Log4J log file for output.
The class name of the InfoSphere MDM Custom Domain Hub JMX listener is configured in the Report.Listener.MBean.Impl.className property in the DWLCommon.properties file. When the /IBM/DWLCommonServices/Report/Listener/enabled configuration setting is set to true, InfoSphere MDM Custom Domain Hub registers the listener with the local MBean server.
When the listener receives the JMX notification, it captures activity information in the transactiondata.log file located on the same host. The file name, location, and Log4J settings can be modified by changing the values of several log4j.appender.transactionData_file properties in the Log4J.properties file.
By default, the Log4J log file is configured to use the org.apache.log4j.DailyRollingFileAppender class as an appender. With DailyRollingFileAppender, the output is written to the log files.
The files roll over at user-defined time interval that can be configured in the DatePattern property in the Log4J.properties file. For example, if you choose to have the files roll over at the midnight each day ('.'yyyy-MM-dd), the output is written into the transactiondata.log during the day and at midnight the file will be copied to transactiondata.log.2006-06-19 and logging continues to the transactiondata.log over the course of the next day.
Service activity data are printed into the log file in a comma-separated format to make it easier to import the data into database or a spreadsheet, which could be used to make a report about system activities.
Each line in the log file corresponds to one transaction. The data in the comma-separated line is arranged in the same order as in the table above, Data captured by the service activity monitoring facility. Depending on the transaction type, not all the fields have values; for example, the inquireAsOfDate field for persistent transactions is empty. Null fields are rendered in the log as empty strings "".
