MTOM/XOP example using JAX-WS / SOA Suite & OSB - 2

Oracle SOA Suite

Below we show how to consume the service that is MTOM enabled in Oracle SOA Suite. We implement it by attached the MTOM client WS-Policy to the reference binding as shown below :

Oracle Service Bus

Oracle Service Bus supports parsing inbound messages & sending outbound messages in MTOM/XOP format. This capability is available for any XML based (or) WSDL based services.

The below image shows how to enable MTOM support as part of the message handling tab for the proxy services.

Include Binary data by Reference - can be used for pass through scenarios where in we don't really need to parse the attachment (or) to pass the attachment directly to MFL or Java callout. The attachment will be available as part of $body/ctx:binary-content variable.

Include Binary data by Value - can be used when you want to validate the xml schema (or) scenarios where the outbound service doesn't support MTOM. In this case, the xop:include will be replaced with the actual base64 binary content.

One important point to note is that, if MTOM is enabled on a OSB Service we cannot attach any other OWSM policy to it( not mentioned in any documents as far as i know)