pub.event:journal

time	String Date and time that the event occurred, in the format yyyy/mm/dd hh:mm:ss.ss.
productID	String Name of the product that generated the journal log message and the event.
majorCode	String Major code of the message.
minorCode	String Minor code of the message.
severity	String Number indicating the severity of the message. 1 Fatal 2 Error 3 Warning 4 Info 5, 6 Debut 7 - 10 Trace
defaultMessage	String Default message associated with the major code and minor code. The actual message may differ from the default message. For example the default message might be “Package WmART is stopping due to {0}”, where {0} is a placeholder for a run-time parameter. The actual message generated at run time might be “Package WmART is stopping due to ServiceException”.

A journal event handler can have a filter for the major code and minor code of the generated event. The format of the filter is <majorCode>.<minorCode>. For example, the following filter specifies that any journal event with major code of 28 followed by a minor code of 34 will invoke the event handler: *28.34*

If a journal event is created when synchronously or asynchronously. When this parameter is set to true, Integration Server writes the following log message "[ISS.0028.0034I] Package WmISExtDC is stopping " the journal event handler will be passed the following information in addition to the time value:

The watt.server.event.exception.async server parameter indicates whether event handlers for journal events are invoked synchronously or asynchronously. When this parameter is set to true, Integration Server invokes the event handlers that subscribe to journal events asynchronously. When this parameter is set to false, Integration Server invokes the services that subscribe to the journal events synchronously. The default is true (asynchronous).