WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Message Interceptor

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.

Mediation primitive properties

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

dataSourceName: The JNDI data source name.
  • Promoted: Yes
  • Default: jdbc/MESSAGEDB

cacheInterval: Database batch update frequency (milliseconds).

XPathMsg: An XPath expression to the SMO which is stored in the database.
  • Promoted: Yes
  • Default: /body
XPathTarget: An XPath expression to the SMO segment which will hold the target address.
  • Promoted: Yes

Description

The Access Gateway uses the Message Interceptor mediation primitive. The Message Interceptor mediation primitive performs message capturing, as it courses through the flow. It stores requester and specific target information in addition to other attributes, when compared with the previously used WebSphere ESB Message Logger mediation primitive.

Policy configuration

This mediation primitive uses the following policies for runtime configuration:

message.LoggingEnabled

Indicates whether message logging should be performed on this request.
  • Type: Boolean
  • Default: False

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.

Considerations for migrating from TWSS version 6.2

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).

Within the database tables, the comparable field names are as follows:
Table 1. Changes to field names from TWSS version 6.2
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



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.