The Access Gateway uses the Message Interceptor mediation primitive to capture message contents as they pass through, and stores them in a relational database. It also allows for the logging of specific target information contained in the message based on a preconfigured policy, and performing async write.
This mediation primitive uses the following configuration property parameters. The properties can be modified using WebSphere® Integration Developer (WID) tooling. Properties that are promoted can be configured using the Integrated Solutions Console
cacheInterval: Database batch update frequency (milliseconds).
This mediation primitive uses the following policies for runtime configuration:
message.LoggingEnabled
message.Logging.Targets
A comma separated list of target addresses to be tracked. You can add this policy in the Service Policy Manager, with the value as the targets to be tracked. By default, however, this policy is present in the Service Policy Manager.
If you used customized message processing flows in TWSS version 6.2, and if you want to preserve data that was collected by the old Message Logging mediation primitive, you will need to copy the data from the ESBLOG.MSGLOG database table WebSphere Enterprise Service Bus Message Logger mediation primitive, to the MESSAGELOG table (which is used by the new Message Interceptor mediation primitive).
Field name in version 6.2 | Field name in version 7.1 |
---|---|
ESBLOG.MSGLOG.TIMESTAMP | MESSAGELOG.TIMESTAMP |
ESBLOG.MSGLOG.MESSAGEID | MESSAGELOG.GTRANID |
ESBLOG.MSGLOG.MEDIATIONNAME | MESSAGELOG.MEDIATIONNAME |
ESBLOG.MSGLOG.MODULENAME | MESSAGELOG.MODULENAME |
ESBLOG.MSGLOG.MESSAGE | MESSAGELOG.MESSAGE |
ESBLOG.MSGLOG.VERSION | MESSAGELOG.VERSION |
null value | MESSAGELOG.REQUESTERID |