Integration Server 10.7 | Audit Logging Guide | Setting Up IS Core Audit Logging | Configure Audit Logging | Configure Logging Mode (Synchronous or Asynchronous) | Configure Asynchronous Mode | Specify the Connection Alias for the Universal Messaging Queue
 
Specify the Connection Alias for the Universal Messaging Queue
If the logger will use a Universal Messaging queue, select the Universal Messaging connection alias for the logger to use. If the alias does not exist yet, click Connection Alias to create the alias. For information about creating a Universal Messaging connection alias, see the Working with Messaging Connection Aliases section in webMethods Integration Server Administrator’s Guide.
The connection alias is a webMethods messaging connection alias that contains configuration information for establishing a connection to a Universal Messaging server. The logger can use a webMethods connection alias that is also used with webMethods messaging triggers, or you can create a Universal Messaging connection alias specifically for use with audit logging.
Note:
If you want multiple Integration Servers to use the same Universal Messaging queue as the logging queue across a Universal Messaging realm, the Universal Messaging connection alias used for logging must have the Client Prefix Is Shared check box selected. This ensures that Universal Messaging includes the client prefix in the namespace portion of the Universal Messaging queue name. Each of the Integration Servers in the cluster must use the same Universal Messaging connection alias.
Integration Server creates a session pool for each Universal Messaging connection alias that is used by a logger. The session pool contains the Universal Messaging sessions used by the logger to write an entry to the Universal Messaging queue. For example, if the error logger uses aliasOne and the service and session loggers use aliasTwo, Integration Server creates a session pool for aliasOne that is used only by the error logger, and a session pool for aliasTwo that is shared by the service and session loggers. You specify the minimum and maximum size of the session pools used to contain Universal Messaging sessions on the watt.server.audit.um.sessionPool.min and watt.server.audit.um.sessionPool.max server configuration parameters. For instructions on setting the parameters, see webMethods Integration Server Administrator’s Guide watt.server..
Note:
The Connection Alias field does not apply to the messaging audit logger because the messaging audit logger cannot be configured to use a Universal Messaging queue as the audit logging queue.