ebXML Module 7.1 SP1 | Understanding and Using webMethods EBXML Module | Installing and Using ebxml Module | ebXML Module Messaging Features | Payload Compression
 
Payload Compression
ebXML Module provides support for payload compression using zip and gzip compression algorithms. For outbound ebXML messages, ebXML Module performs the payload message compression only if you set the TPA parameters to perform compression.
*To enable payload compression
1. Start the Trading Networks Console.
2. Open the agreement for edit:
a. From Trading Networks Console, select View > Agreements.
b. Select the agreement you would like to edit. ClickEdit.
The Agreements Details screen appears.
c. On the right side of the Agreement Details screen, click Set Inputs.
The input for com.wm.estd.ebxml.documents appears.
Note:
You can edit the TPA parameters in an agreement only if the Agreement Status is Proposed. For information about changing the TPA agreement status, see the webMethods Trading Networks Administrator’s Guide for your release.
3. Modify the default TPA parameters, as necessary. For a list of the TPA parameters and the valid values for individual parameters, see Trading Partner Agreement Parameters Version 2. 0 and Trading Partner Agreement Parameters Version 2. 0.
*If you are using ebXML Message Service Version 1.0 Specification, set the following example parameters:
Parameter
Value
CollaborationProtocolAgreement.Packaging.CompositeList.Encapsulation:mimetype
application/zip or application/gzip
CollaborationProtocolAgreement.Packaging.SimplePart:Id
payload-id
*If you are using ebXML Message Service Version 2.0 Specification, set the following example parameters:
Parameter
Value
CollaborationProtocolAgreement.Packaging.CompositeList.Encapsulation:mimetype
application/zip or application/gzip
CollaborationProtocolAgreement.SimplePart:Id
payload-id
4. For inbound ebXML messages, the ebXML Module processes a payload for decompression only if the Content-Type MIME header for the payload is specified as "application/xml" or "application/gzip". Note that the Content-Type of the decompressed payload defaults to "text/xml" if there is no matching "Content-ID" in the processing TPA packaging section.