The <mtom_options> element

Specifies when to use MTOM for outbound SOAP messages for pipelines that do not support Java.

Used in:

  • Service provider
  • Service requester

Attributes:

Attribute Description
send_mtom Specifies if MTOM should be used to convert the outbound SOAP message into a MIME message:
no
MTOM is not used for outbound SOAP messages.
same
In service provider mode, MTOM is used for SOAP response messages whenever the requester uses MTOM. This is the default value in a service provider pipeline.

In service requester mode, specifying this value is the same as when you specify send_mtom="yes".

yes
MTOM is used for all outbound SOAP messages. This is the default value in a service requester pipeline.
send_when_no_xop Specifies if an MTOM message should be sent, even when there are no binary attachments present in the message.
no
MTOM is only used when binary attachments are being sent with the message.
yes
MTOM is used for all outbound SOAP messages, even when there are no binary attachments to send in the message. This is the default value, and is primarily used as an indicator to the receiving program that the sender supports MTOM/XOP.
This attribute can be combined with any of the send_mtom attribute values, but has no effect if you specify send_mtom="no".

Example

<provider_pipeline>
	<cics_mtom_handler>
		<dfhmtom_configuration version="1">
		  <mtom_options send_mtom="same" send_when_no_xop="no"/>
		</dfhmtom_configuration>
	</cics_mtom_handler>
...
</provider_pipeline>
In this provider pipeline example, SOAP messages are converted into MTOM messages only when binary attachments need to be sent with the message, and the service requester sent an MTOM message.


dfhws_mtom_options.html | Timestamp icon Last updated: Sunday, 4 June 2017