Software AG Products 10.11 | Administering Integration Server | Setting Up Universal Messaging Client Logging | Event Lifecycle Logging | Configuring Event Lifecycle Logging
 
Configuring Event Lifecycle Logging
When you configure event lifecycle logging on Integration Server, you specify the logging level, the message stores (channels or queues) for which logging is performed, and the amount of space that lifecycle logging can consume on the machine that hosts Integration Server.
Event life cycle logging configuration on Integration Server (the UM client) is separate from lifecycle logging configuration on Universal Messaging. Configure event lifecycle logging on Integration Server and Universal Messaging server to generate logs that provide more complete details of an event progressing through the messaging system.
When enabled, event lifecycle logging can impact Integration Server performance.
*To configure event lifecycle logging
1. Open Integration Server Administrator.
2. Go to Logs > Logging configuration.
3. In the Logger List, click UM Client Logger.
4. Click Edit UM Client Logger.
5. Under UM Client Event Lifecycle Log Configuration, provide the following information to enable and configure event lifecycle logging.
Field
Description
Trace Store Log Level
Logging level for the trace logger. The trace logger writes the detailed log messages for the stores. Set to one of the following:
*Off - Event lifecycle logging is disabled for this Integration Server. This is the default value.
*Info - Event lifecycle logging is enabled. A trace logger writes info level messages for the queues or channels specified in Trace Stores.
*Trace - Event lifecycle logging is enabled. A trace logger writes trace level messages for the queues or channels specified in Trace Stores. The Trace log level is more detailed than the Info log level.
Trace Stores
Comma-separated list of the message stores, specifically queue names or channel names, for which event lifecycle logging is performed. Specify * for trace loggers to be used with all queues or channels that this Integration Server sends messages to and receives messages from. The default is *.
When specifying a queue or channel that uses folders in Universal Messaging, separate the folder names with a forward slash. For example, a publishable document type named myFolder.mySubFolder:documentABC is equivalent to a Universal Messaging channel name of wm/is/myFolder/mySubFolder/documentABC
Integration Server does not validate the list of message stores to see if a queue or channel with that name actually exists.
Trace Folder Log Size
The maximum size in MB of all the log files for event lifecycle logging. That is, the maximum size of all the log files, including archives, in the Integration Server_directory /instances/instanceName/logs/umEventLifecycle. The default is 1024 MB.
Make sure to set the value of the Trace Folder Log Size large enough to accommodate the trace logs for each message store as well as the number of archive log files that you want to keep for each message store.
Trace Store Log Size
The maximum size in MB of the trace log file for an individual message store. That is, the maximum size of an individual log file in Integration Server_directory /instances/instanceName/logs/umEventLifecycle. The default is 10 MB.
When the event lifecycle log reaches this size, the UM client creates an archive of the log (.zip) and starts a new lifecycle log for the store.
The UM client does not keep lifecycle log archive files for message stores if the Trace Folder Log Size value is not large enough to accommodate trace logs for all the message stores. Instead, the UM client just rotates the trace store log file for each store.
6. Click Save Changes.