Removes a data object from a service message object (SMO) using an XPath expression configuration on the mediation primitive.
The Message Element Remover mediation primitive removes a data object from a service message object (SMO) using an XPath expression corresponding to twssHeader (/headers/SOAPHeader[name=twssHeaders]). Removal of a data object can result in modification of the SOAP headers or SOAP request that is sent to the backend platform. The Message Element Remover mediation primitive also has an exception list for trusted requesters; a requester that is in the exception list will not have its data objects removed during flow processing.
Within the context of Access Gateway default flows, this mediation primitive is used to remove SOAP headers, during flow processing, that might have been mistakenly or maliciously inserted by client applications.
This mediation primitive is also used to remove sensitive SOAP headers before returning a Web service response back to the client. The exception list is used to allow trusted entities, such as the service platform when sending outbound notifications through the Access Gateway, to communicate using SOAP headers within Access Gateway flow logic. It is an optional plug-in and is used by the default Access Gateway flow:
This mediation primitive uses the following policies for runtime configuration:
None
This mediation primitive uses the following configuration properties. These properties can be modified using WebSphere® Integration Developer (WID) tooling. Properties that are promoted can be configured using the Integrated Solutions Console.
Property | Type | Promoted? | Description |
---|---|---|---|
request.requesterExceptionList | string | yes | A comma-delimited list of requester
names whose message elements should not be removed during processing. Default: /notification |
response.requesterExceptionList | string | yes | A comma-delimited list of requester
names whose message elements should not be remove during processing. Default: (blank) |
Some JNDI parameters are configured for lower level objects. These parameters do not represent promoted properties.
JVM Argument | JNDI Name | Description |
---|---|---|
com.ibm.websphere.sca.soap.attachments.ExpirationPolicy | sca/attachments/ExpirationPolicy | Expiration cleanup default for attachment support
specified in milliseconds. Default: 300000 (5 minutes) |
com.ibm.ws.sca.soap.attachments.spi.DatabaseCache | sca/attachments/DatabaseCache | Data source name for the Database cache implementation to use for attachment support. There is no default. |
SOAP_ATTACHMENT_CLEANUP_THREAD_COUNT | sca/attachments/CleanupThreadCount | Number of scheduler threads that will be used
to clean up attachments database cache table. Default: 1 |
com.ibm.websphere.sca.soap.attachments. MaxSizeAttachmentPart | sca/attachments/MaxSizeAttachmentPart | Maximum size allowed for an attachment part.
This is an integer number measured in MBytes (when followed by M or
m), KBytes (when followed by K or k), or bytes (when followed by B
or b). Default: 1M |
com.ibm.websphere.sca.soap.attachments.MaxSizeAttachments | sca/attachments/MaxSizeAttachments | Maximum size allowed for all attachment parts
for a given message. This is an integer number measured in MBytes
(when followed by M or m), KBytes (when followed by K or k), or bytes
(when followed by B or b). Default: 1M |
The following SOAP header elements are expected from upstream mediation primitives:
None
The following SOAP header elements are added or modified for downstream mediation primitives:
None
Messages that are successfully processed by the Message Element Remover mediation primitive are passed to the output terminal of the mediation primitive. If an error occurs while processing the message, the error is logged and processing continues with the original SMO message.