This sample demonstrates how you can use content optimization mechanisms such as Message Transmission Optimization Mechanism (MTOM) and SOAP with Attachments ( SwA) with the ESB.
By default ESB serializes binary data as Base64 encoded strings and sends them in the SOAP payload. MTOM and SwA with the ESBdefine mechanisms over which files with binary content can be transmitted over SOAP web services.
For a list of prerequisites, see Prerequisites to Start the ESB Samples.
This configuration file
synapse_sample_51.xml is available in the
To build the sample
Start the ESB with the sample 51 configuration. For instructions on starting a sample ESB configuration, see Starting the ESB with a sample configuration.
The operation log keeps running until the server starts, which usually takes several seconds. Wait until the server has fully booted up and displays a message similar to "WSO2 Carbon started in n seconds."
Start the Axis2 server. For instructions on starting the Axis2 server, see Starting the Axis2 server.
Deploy the back-end service
MTOMSwASampleService. For instructions on deploying sample back-end services, see Deploying sample back-end services.