Message Optimization Specifications 

Message optimization is sending web service messages as quickly as possible. In web services communication, this is accomplished by encoding messages before transmission and decoding them after they arrive at their final destination. Choose Message optimizer that will help to amplify your business growth.

Figure- Message Optimization Specifications

Choose Message optimizer specs diagram

Along with Core XML specifications, the following specifications were used for optimization:

SOAP: The SOAP wire protocol is currently supported by JAX Web Services. Client requests and web service responses are typically sent as Simple Object Access Protocol (SOAP) messages over HTTP in SOAP implementations, allowing for entirely interoperable communication between clients and web services running on different platforms and in different parts of the Internet. SOAP- an XML-based protocol that follows the HTTP request-and-response architecture. HTTP is a well-known request-and-response standard for transmitting messages over the Internet. The SOAP part of a conveyed message in SOAP 1.1 handles the following:

• Defines an XML-based envelope for describing the contents of a message and how to process it.
• Within the message, XML-based encoding rules express instances of application-defined data types.
• Defines an XML-based convention describing the remote service’s request and the response.

Web service endpoint addresses can be supplied in the XML-based SOAP envelope rather than the transport header (such as the HTTP transport header) in SOAP 1.2 implementations, making SOAP messages transport independent.

Web Services Addressing: With Java Web Services Developer’s Pack 2.0, the Java APIs for W3C Web Services Addressing were released first (JWSDP 2.0). This specification expresses abstract properties and an XML Infoset representation that can be tied to a SOAP message to reference web services and simplify end-to-end message addressing. An object, processor, or resource that can be referenced and to which web service messages can be addressed is a web service endpoint.

Endpoint references provide the necessary information for addressing a web service endpoint. The standard provides two constructs: message addressing attributes and endpoint references, which normalize information generally provided by transport protocols in an independent way of the transport or messaging system. This is performed using XML tags instead of the HTTP header to provide web service addresses in the SOAP message. These capabilities enable messaging systems to handle message transmission over networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.

Web Services Secure Conversation in Choose Message optimizer:

In a standardized manner, this specification improves message-level security and performance in multiple-message exchanges. It defines the basic mechanisms on which secured messaging semantics for multiple-message exchanges are based. It also allows for the establishment of contexts and the exchange of potentially more efficient keys or new key material, thereby improving subsequent exchanges’ overall performance and security.

When used in conjunction with the XML-binary Optimized Packaging, the SOAP Message Transmission Optimization Mechanism (MTOM) facilitates standard mechanisms for optimizing the transmission and/or wire format of SOAP messages. The Choose Message Optimizer does this by selectively encoding portions of the SOAP message while still presenting an XML Infoset to the SOAP application (XOP). This technique enables a SOAP node to establish a hop-by-hop contract with the next SOAP node in the SOAP message pipeline, enabling the efficient transmission of optimized data included inside headers or body of SOAP messages relayed by an intermediate. It also enables message optimization that is not dependent on the binding.