Configuring Enhanced Logging for Messaging
Integration Server provides many configuration options for enhanced logging. The granularity of the options makes it possible for Integration Server to generate logging data more tailored to your needs. For example, perhaps you want to see logging for all messages sent using a particular messaging connection alias. Or maybe you want a narrower focus in the logging entries and only want to see log entries for messages sent by a messaging connection alias to a particular destination.
When configuring enhanced logging for messaging, you need to decide:
Which messaging connection aliases for which you want to use enhanced logging. Enhanced logging is configured on a per messaging connection alias basis. You can configure enhanced logging for
Universal Messaging connection alias for
webMethods messaging or JMS connection alias.
Whether
Integration Server writes enhanced logging entries to the server.log or the messaging log.
Whether to generate enhanced logging for message consumers and/or producers that use the messaging connection alias. You can further limit the message producers for which
Integration Server performs enhanced logging by identify the specific destinations for which you want additional logging.
Integration Server writes enhanced logging only for messages sent to the specific destinations using the messaging connection alias. Similarly, you can also instruct
Integration Server to generate additional logging for all triggers that use the messaging connection alias to receive messages or just specific triggers.
The logging level for enhanced logging. Where you set the logging level depends on whether
Integration Server writes enhanced logging entries to the messaging log or the server log.
For the messaging log, you configure the logging level on the messaging audit logger. For information about configuring the messaging audit logger, see the
webMethods Audit Logging Guide.
For the server log, you configure the logging level for the 0168 Messaging (Enhanced Logging) server log facility. You must set the facility to at least the Info logging level for
Integration Server to write enhanced logging entries. For information about configuring the server.log see
Specifying Amount and Type of Information
to Include in the Server Log.
Enhanced logging has a performance cost. The additional logging by Integration Server consumes resources and impacts performance negatively. The additional log entries can very quickly fill up disk space. Keep this information in mind when using enhanced logging for messaging.