Appendix D: Controlling the Logging Service in IBM WebSphere BI Monitor v4.2.4

IBM WebSphere Business Integration (BI) Monitor provides you with the capability of logging all the messages that are transacted at run time in its various components. You can control the Logging service to log only specific types of messages, or to log all types of messages that are associated with one or more function areas (components) of the application.

The ability to control the logging service manifests significant importance as it limits the amount, and type, of the data that is saved to the BI Monitor log file. This remarkably enables the user, and thus customer support team members, to trace source of a particular problem more easily by limiting the logging of messages to only those pertaining to the parts of the application in which problems take place. Hence, this eliminates the need for analyzing and scrolling down unneeded messages (e.g. Error, Warning…etc) that may exist in a conventional stretched log file.

The produced BI Monitor log files are mainly stderr.txt and stdout.txt. In case of WAS 4.0, they could be found in the folder named Logs that resides in the directory on which you have deployed the BI Monitor. In case of WAS 5.0, they could be found in the folder named Logs that resides in the root WebSphere directory.

The control of logging service is implemented through the definition of one or more categories and/or detail Level in the Java Virtual Machine tab in WAS 4.0.2, or WAS 5.0.

The following sections describes message logging ,tracing and controlling logging service.