Configuring Bindings for Delivery Channels
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.
Note –
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:
General
These parameters allow you to define general eXchange settings. See the eXchange Integrator User’s Guide for information on these parameters.
ToPartner Transport
These parameters allow you to supply information needed to transport data to the TP. Find these parameters under the ToPartner Transport subtab.
Note –
For a complete description of how to enter these parameters for both ToPartner Transport and FromPartner Transport parameters, seeXDC Parameters.
All Purpose End Point
Description
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.
Values
A valid URL, according to the syntax given under XDC Parameters; required.
Default
None
Use Synchronous Channel
Description
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.
Values
Select true, false, or None; not required.
Default
false
Track for Auditing
Description
Specifies whether the message is tracked using Enterprise Manager’s Message Tracker. Choosing true enables the Message Tracker.
Values
Select true, false, or None; not required.
Default
false
Destination URL
Description
Allows you to enter the destination URL for the current TP.
Values
A valid URL according to the syntax given under XDC Parameters; required.
Default
None
Header Names/Values
Description
Allows you to enter any needed message headers and/or values that may be required by the current TP to reach its destination.
Values
Valid message header names and/or values; not required.
Default
None
FromPartner Transport
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.
ToPartner Packaging
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.
SOAP Media Type
Description
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.
Values
Multipart/Related; required.
Default
Multipart/Related
Digital Envelope Protocol
Description
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.
Values
Select http://www.w3.org/2001/04/xmlenc#, SMIME2.0, or SMIME3.0; not required.
Default
http://www.w3.org/2001/04/xmlenc#
Non-Repudiation Protocol
Description
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.
Value
Select XMLDSIG; not required.
Default
XMLDSIG
Signature Algorithm
Description
Identifies the algorithm used to compute the value of the digital signature.
Values
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.
Default
http://www.w3.org/2000/09/xmldsig#dsa-sha1
Digest Method/HashFunction
Description
Identifies the algorithm used to compute the digest of the message being signed.
Value
Select http://www.w3.org/2000/09/xmldsig#sha1; not required.
Default
http://www.w3.org/2000/09/xmldsig#sha1
Canonicalization Method
Description
Identifies the canonicalization method applied to the data to be signed.
Values
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.
Default
http://www.w3.org/TR/2001/REC-xml-c14n-20010315
Encryption Algorithm
Description
Identifies the encryption algorithm to be used.
Value
Select DES3; not required.
Default
DES3
Signature Type
Description
Specifies the XML digital signature type to be used (see http://www.w3.org/TR/xmldsig-core/).
Values
Select Enveloped, Enveloping, Detached, or SoapEnveloped; not required.
Default
SoapEnveloped
Ack Signature Required
Description
Designates how the signed attribute within the AckRequested element in the SOAP message header is set.
Values
Select Always, Never, or perMessage; not required.
Default
None
Note –
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.
Ack Request is Per Message
Description
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.
Values
true or false; not required.
Default
false
Additional Information
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.
Duplicate Elimination is Per Message
Description
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.
Values
true or false; not required.
Default
false
Additional Information
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.
SOAP Actor
Description
Allows you to specify the current message’s final destination. By using toPartyMSH, you make the receiving party the final destination.
Note –
Values are listed in the drop-down menu.
Values
Select urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH; required.
Default
None
Sync Reply
Description
Specifies the mode of the reply to the current message.
Values
Select None or mshSignalsOnly; required.
Default
None
Language
Description
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.
Values
A valid string supplied by the user; required.
Default
en-us (English, U.S.)
FromPartner Packaging
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.
Digital Envelope Protocol
Description
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.
Values
Select http://www.w3.org/2001/04/xmlenc#, SMIME2.0, or SMIME3.0; not required.
Default
http://www.w3.org/2001/04/xmlenc#
Non-Repudiation Protocol
Description
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.
Value
Select XMLDSIG; not required.
Default
XMLDSIG
Signature Type
Description
Specifies the XML digital signature type to be used (for more information, see http://www.w3.org/TR/xmldsig-core/).
Values
Select Enveloped, Enveloping, Detached, or SoapEnveloped; not required.
Default
SoapEnveloped
Ack Signature Required
Description
Designates how the signed attribute within the AckRequested element in the SOAP message header is set.
Values
Select Always, Never, or Per Message; not required.
Default
None
Note –
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.
Ack Request is Per Message
Description
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).
Values
true or false; not required.
Default
false
Duplicate Elimination is Per Message
Description
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).
Values
true or false; not required.
Default
false
SOAP Actor
Description
Allows you to specify the current message’s final destination. By using toPartyMSH, you make the receiving party the final destination.
Note –
Values are listed in the drop-down menu.
Values
Select urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH; required.
Default
None
Sync Reply
Description
Specifies the mode of the reply to the current message.
Values
Select None or mshSignalsOnly; required.
Default
None
Language
Description
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.
Values
A valid string supplied by the user; required.
Default
en-us (English, U.S.)
- © 2010, Oracle Corporation and/or its affiliates