| Oracle® Fusion Middleware Concepts Guide for Oracle Infrastructure Web Services 11g Release 1 (11.1.1.5) E15184-04 |
|
 Previous |
 Next |
| Oracle® Fusion Middleware Concepts Guide for Oracle Infrastructure Web Services 11g Release 1 (11.1.1.5) E15184-04 |
|
Previous |
Next |
This chapter describes how Oracle Infrastructure Web services process messages that are encoded in Message Transmission Optimization Mechanism (MTOM) format.
Binary content, such as an image in JPEG format, can be passed between the client and the Web service. In order to be passed, the binary content is typically inserted into an XML document as an xsd:base64Binary string. Transmitting the binary content in this format greatly increases the size of the message sent over the wire and is expensive in terms of the required processing space and time.
Using MTOM, binary content can be sent as a MIME attachment, which reduces the transmission size on the wire. The binary content is semantically part of the XML document. This is an advantage over SWA (SOAP Messages with Attachments), in that it enables you to apply operations such as WS-Security signature on the message. For more information, refer to the following specifications:
SOAP 1.2: http://www.w3.org/TR/2005/REC-soap12-mtom-20050125
SOAP 1.1: http://www.w3.org/Submission/2006/SUBM-soap11mtom10-20060405
Using MTOM to pass binary content as an attachment improves the performance of the Web services stack. Performance is not affected if an MTOM-encoded message does not contain binary content.
MTOM provides an optimized transmission mechanism for SOAP 1.2 messages with an envelope that contains elements of XML schema type xs:base64 binary. MTOM makes use of data handling mechanisms described in the following specifications:
XOP (XML-binary Optimized Packaging)—Provides a mechanism to more efficiently serialize XML Infosets that have content of type xs:base64Binary. The XOP specification is available at the following Web site: http://www.w3.org/TR/xop10/
DMCBDX (Describing Media Content of Binary Data in XML)—Provides content type information for the binary data in the XML instance and schema. This information can be used to optimize the processing of binary data. The DMCBDX specification is available at the following Web site: http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504/
RRSHB (Resource Representation SOAP Header Block)—allows a SOAP message to carry a representation of a Web resource, such as a JPEG image, in a SOAP header block. When combined with MTOM and XOP, the Web resource contained in a RRSHB SOAP header block can be transmitted as a raw binary MIME attachment instead of an xs:base64Binary string in the SOAP header. The RRSHB specification is available at the following Web site: http://www.w3.org/TR/2005/REC-soap12-rep-20050125/
These specifications fulfill the requirements outlined in OSUCR (SOAP Optimized Serialization Use Cases and Requirements), as described at: http://www.w3.org/TR/2004/WD-soap12-os-ucr-20040608/
As described in Chapter 2, "Attaching Policies to Oracle Infrastructure Web Services,", Oracle WSM provides a set of predefined policies and assertion templates that are automatically available when you install Oracle Fusion Middleware.
The MTOM attachment policies listed in Table 7-1 are available out-of-the-box.
Table 7-1 Predefined MTOM Attachment Policies
| Reliable Messaging Policy | Description |
|---|---|
|
oracle/wsmtom_policy |
Rejects inbound messages that are not in MTOM format and verifies that outbound messages are in MTOM format. |
For more information about the MTOM attachment predefined policies, see "MTOM Attachment Policies" in Security and Administrator's Guide for Web Services.
You can attach MTOM policies to Oracle Infrastructure Web services and clients at design time using Oracle JDeveloper, or at runtime using the Oracle Enterprise Manager. For more information, see Chapter 2, "Attaching Policies to Oracle Infrastructure Web Services."
No configuration steps are required.
