This section describes how to configure ebXML Protocol Manager’s bindings for XDCs. You set up and define these bindings by supplying values for the ToPartner transport attributes, the FromPartner transport attributes, and the combined To/FromPartner packaging attributes.
This section explains in detail how to configure ePM’s ebXML-specific parameters. You can find the Delivery Channels (XDCs) subtab example shown under the Components tab.
The ePM user interface refers to XDCs under tabs called Delivery Channels .
These configuration parameters define settings that allow ebXML Protocol Manager to deliver messages to TPs. Their categories are:
These parameters allow you to define general eXchange settings. See the eXchange Integrator User’s Guide for information on these parameters.
These parameters allow you to supply information needed to transport data to the TP. Find these parameters under the ToPartner Transport subtab.
For a complete description of how to enter these parameters for both ToPartner Transport and FromPartner Transport parameters, seeXDC Parameters.
An endpoint specifies the logical address of where messages can be received. The all- purpose end point is used to designate the receipt address of all ebXML messages.
A valid URL, according to the syntax given under XDC Parameters; required.
None
Specifies whether the communication between the message service handler (MSH) servers is synchronous or asynchronous. When set to true, the MSH response message is returned on the same HTTP connection as the inbound request, with an appropriate HTTP response code.
This parameter is not required and is not used in the current release of ebXML Protocol Manager. However, it is provided for compatibility with previous releases.
Ext Attribute SyncReplyMode replaces this parameter in the current release, since ebXML requires a string (for example, None or mshSignalsOnly) and not a Boolean value.
Select true, false, or None; not required.
false
Specifies whether the message is tracked using Enterprise Manager’s Message Tracker. Choosing true enables the Message Tracker.
Select true, false, or None; not required.
false
Allows you to enter the destination URL for the current TP.
A valid URL according to the syntax given under XDC Parameters; required.
None
Allows you to enter any needed message headers and/or values that may be required by the current TP to reach its destination.
Valid message header names and/or values; not required.
None
These parameters allow you to supply information needed to transport data from the TP. See ToPartner Transport for an explanation of these parameters. Find these parameters under the FromPartner Transport tab.
These parameters allow you to define the packaging for data being transported to the TP. Find these parameters under the ToPartner Packaging tab. .
The initial set of parameters before SOAP Media Type are eXchange parameters common to all protocol managers. See the eXchange Integrator User’s Guide for information on these parameters.
Specifies the Simple Object Access Protocol (SOAP) media type. In accordance with the SOAP specification, the multipurpose Internet mail extension (MIME) media type of the SOAP message has the value text/xml.
SOAP media type means the content type for SOAP with Attach, which is multipart and related.
Multipart/Related; required.
Multipart/Related
Provides the sender’s requirements for message encryption using the digital-envelope (DIGENV) method. Digital enveloping is a procedure in which the message is encrypted by symmetrical encryption (using a shared secret key), and the secret key is sent to the message recipient encrypted, along with the recipient’s public key.
Select http://www.w3.org/2001/04/xmlenc#, SMIME2.0, or SMIME3.0; not required.
http://www.w3.org/2001/04/xmlenc#
Identifies the technology used to digitally sign a message. This parameter has a single implied version attribute whose value is a string that identifies the version of the specified technology.
Select XMLDSIG; not required.
XMLDSIG
Identifies the algorithm used to compute the value of the digital signature.
Select http://www.w3.org/2000/09/xmldsig#dsa-sha1, http://www.w3.org/2000/09/xmldsig#rsa-sha1, or http://www.w3.org/2000/09/xmldsig#hmac-sha1; not required.
http://www.w3.org/2000/09/xmldsig#dsa-sha1
Identifies the algorithm used to compute the digest of the message being signed.
Select http://www.w3.org/2000/09/xmldsig#sha1; not required.
http://www.w3.org/2000/09/xmldsig#sha1
Identifies the canonicalization method applied to the data to be signed.
Select http://www.w3.org/TR/2001/REC-xml-c14n-20010315 or http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments; not required.
http://www.w3.org/TR/2001/REC-xml-c14n-20010315
Identifies the encryption algorithm to be used.
Select DES3; not required.
DES3
Specifies the XML digital signature type to be used (see http://www.w3.org/TR/xmldsig-core/).
Select Enveloped, Enveloping, Detached, or SoapEnveloped; not required.
SoapEnveloped
Designates how the signed attribute within the AckRequested element in the SOAP message header is set.
Select Always, Never, or perMessage; not required.
None
When ebXML Protocol Manager sends an encrypted but unsigned message to a TP then gets a signed acknowledgment from the TP, the system cannot verify the signature and logs an error.
Allows you to designate whether the AckRequested element within the SOAP message header is operating.
The value true requests an acknowledgment for each message. Setting it to false disables this feature.
true or false; not required.
false
Requesting acknowledgments per message depends on the following configuration parameters in ePM:
Send Acknowledgments: Provided in ePM by eXchange.
Ack Request is Per Message: ebXML-specific.
If the Ack Request is Per Message value is true, regardless of what is specified in the Send Acknowledgments parameter, the system uses the eXchange setting provided at run-time for outbound messages, that is, the setting under EX_INTERNAL.
If the Ack Request is Per Message value is false, the system checks the value set under Send Acknowledgments. If Send Acknowledgments is true, the system checks for negative acknowledgments. If this value is false, the system ignores negative acknowledgments.
Allows you to designate whether the DuplicateElimination element within the SOAP message header is operating.
If you set this parameter to true, the system keeps each message from being duplicated. Setting it to false disables this feature.
true or false; not required.
false
Eliminating duplicates per message depends on the following configuration parameters in ePM:
Check For Duplicates: Provided in ePM by eXchange.
Duplicate Elimination is Per Message: ebXML-specific.
If the Duplicate Elimination is Per Message value is true, regardless of what is specified in the Check For Duplicates parameter, the system uses the eXchange setting provided at run-time for outbound messages, that is, the setting under EX_INTERNAL.
If the Duplicate Elimination is Per Message value is false, the system checks the value set under Check For Duplicates. If Check For Duplicates is true, the system checks for duplicates. If this value is false, the system ignores duplicates.
Allows you to specify the current message’s final destination. By using toPartyMSH, you make the receiving party the final destination.
Values are listed in the drop-down menu.
Select urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH; required.
None
Specifies the mode of the reply to the current message.
Select None or mshSignalsOnly; required.
None
Specifies the language in which the description, errors, and so on, are sent out. Refer to the appropriate ebXML documentation on their Web site for details.
A valid string supplied by the user; required.
en-us (English, U.S.)
These parameters allow you to define the packaging for data being transported from the TP. Find these parameters under the FromPartner Packaging tab. .
The initial set of parameters before Digital Envelope Protocol are eXchange parameters common to all protocol managers. See the eXchange Integrator User’s Guide for information on these parameters.
Provides the sender’s requirements for message encryption using the digital-envelope (DIGENV) method. Digital enveloping is a procedure in which the message is encrypted by symmetrical encryption (using a shared secret key), and the secret key is sent to the message recipient encrypted, along with the recipient’s public key.
Select http://www.w3.org/2001/04/xmlenc#, SMIME2.0, or SMIME3.0; not required.
http://www.w3.org/2001/04/xmlenc#
Identifies the technology used to digitally sign a message. This parameter has a single implied version attribute whose value is a string that identifies the version of the specified technology.
Select XMLDSIG; not required.
XMLDSIG
Specifies the XML digital signature type to be used (for more information, see http://www.w3.org/TR/xmldsig-core/).
Select Enveloped, Enveloping, Detached, or SoapEnveloped; not required.
SoapEnveloped
Designates how the signed attribute within the AckRequested element in the SOAP message header is set.
Select Always, Never, or Per Message; not required.
None
When a signed acknowledgment is received from a TP and its associated outbound request message is not signed, ebXML Protocol Manager is unable to verify the signature and logs an error.
Allows you to designate whether the AckRequested element within the SOAP message header is operating.
If you set this parameter to true, the system requests an acknowledgment for each message. Setting it to false disables this feature (see Additional Information).
true or false; not required.
false
Allows you to designate whether the DuplicateElimination element within the SOAP message header is operating.
If you set this parameter to true, the system keeps each message from being duplicated. Setting it to false disables this feature (see Additional Information).
true or false; not required.
false
Allows you to specify the current message’s final destination. By using toPartyMSH, you make the receiving party the final destination.
Values are listed in the drop-down menu.
Select urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH; required.
None
Specifies the mode of the reply to the current message.
Select None or mshSignalsOnly; required.
None
Specifies the language in which the description, errors, and so on, are sent out. Refer to the ebXML documentation on their Web site for details.
A valid string supplied by the user; required.
en-us (English, U.S.)