MIME Encoding Payloads
The ebXML Module supports MIME encoding for payloads. The ebXML Module supports all the character encodings defined in RFC 2045 such as "base64", "quoted-printable", "7bit", "8bit", and "binary". Also supports "uuencode" character encoding.
To configure MIME encoded payload support, set the appropriate TPA parameters.
To configure the
ebXML Module for MIME encoded payloads
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.
4. Set the required character encoding, as follows:
For
ebXML Message Service Version 1.0 Specification messages, set the following TPA parameter as shown below:
Set this parameter... | To... |
CollaborationProtocolAgreement.Packaging.SimplePart.mimeparameters | The value of the required character encoding. For example, for base64 character encoding, set the value to content-transfer-encoding="base64". |
For
ebXML Message Service Version 2.0 Specification, set the following TPA parameter as shown below:
Set this parameter... | To... |
CollaborationProtocolAgreement.SimplePart.mimeparameters | The value of the required character encoding. For example, for base64 character encoding, set the value to content-transfer-encoding="base64". |