Column | Description |
Date/Time | Date and time the audit record was written to the database or file system. |
Audit time stamp | Date and time the entry was written to the log. |
Mode | Indicates whether the message logger wrote the log entry on behalf of a message producer or consumer for webMethods messaging or JMS messaging. The messaging log uses the abbreviation MSG for webMethods messaging. For example MSG_PRODUCER and MSG_CONSUMER are the modes for webMethods messaging producer and consumer, respectively. |
Message | Text of the logged message. |
Alias | Name of the messaging connection alias associated with the sent or received message. The messaging connection alias can be a Universal Messaging connection alias or a JMS connection alias. |
Destination | Destination to which the message was sent. For webMethods messaging, the destination is the name of the channel to which the message was sent. The name of the channel corresponds to the publishable document type for which Integration Server published an instance document. For JMS messaging, the destination contains the JNDI lookup name for the queue or topic to which the JMS message was sent. |
Trigger | Name of the trigger that received the message. |
UUID | Universally unique identifier for the message being sent or received. In webMethods messaging, you can set a value for the _env/uuid field when publishing the document. You can only use a user-defined UUID for messages sent to Universal Messaging by the pub.publish:publishservice. If you do not set a UUID value or if you are using a service for a user-defined UUID cannot be set, Integration Server assigns one during publication. For JMS messaging, you can set a UUID in the JMSMessage/properties/uuid field when sending the JMS message. For JMS messaging, the uuid field is optional. Integration Server does not generate or assign a UUID if one is not specified. Click in a row to view all the messaging log messages for the UUID. |
Message ID | The ID assigned to the message by the messaging provider. For webMethods messaging, the message ID is the Universal Messaging event ID which Universal Messaging generates when it first receives the message. For JMS messaging, the message ID is the JMSMessageID which is generated on behalf of the JMS provider. |
Server ID | IP address or host name of the server on which the Integration Server that generated the audit event is running. This is necessary information when Integration Servers are clustered and writing to a shared RDBMS. The ID can be DNSname:port or IPaddress:port. Note: The port is always the Integration Server's primary port, even if the event occurred on a different (non-primary) Integration Server port. |
Root Context Parent Context Current Context | Context information Monitor uses to connect related entries from different logs. |