The following table describes the settings available for an ebXML 1.0 or 2.0 binding.
Table 6-6 Settings Available For an ebXML 1.0 or 2.0 Binding
Setting Description Required/
Optional
In the Name field, enter the binding name.
The name used to identify the binding within the system. The name must be unique within the trading partner profile. When you add a new binding, a default name is automatically generated using the following convention:
<partner>-<protocol>-<qualifier>
For example:
acme-ebxml20-4
If you choose to change the default name, make sure the name you choose is unique.
Note: This field is only available on the Add Binding page. It cannot be edited on the Edit Binding page.
Required
Check or uncheck the Default Binding check box.
When checked, the binding is designated as the default binding for the ebXML protocol. Only one binding of the same protocol version can be designated as the default binding.
The default is unchecked.
Optional
Transport Configuration
From the Transport Protocol drop-down list, select the HTTP or HTTPS.
The transport protocol for sending and receiving messages.
The default is HTTP.
A d d i n g P r o t o c o l B i n d i n g s t o a T r a d i n g P a r t n e r
From the Transport Protocol Version, select the version.
The version of the transport protocol.
If HTTP is selected for the Transport Protocol, select 1.0 or 1.1. The default is 1.0.
If HTTPS is selected for Transport Protocol, 1.1 is currently the only option.
Optional
In the Endpoint field, enter the URL for the transport endpoint.
The URL or URI for the transport endpoint.
For information about specifying an endpoint as a URI, for more information, see Defining Endpoints for Projects Containing Multiple JPDs With the Same Name.
Required
In the Timeout field, enter the transport timeout.
The transport timeout for the specified Endpoint. The default value is 0, which indicates no timeout.
Optional
Quality of Service
From the Delivery Semantics drop-down list, do one of the following:
• For ebXML 1.0, select BESTEFFORT or ONCEANDONLYONCE • For ebXML 2.0, select
BESTEFFORT,
ONCEANDONLYONCE, ATLEASTONCE, or ATMOSTONCE
The reliable message service behavior: BESTEFFORT
Best effort. No reliable messaging. ONCEANDONLYONCE
Once and only once reliable messaging. Select this option for messaging that requires acknowledgement and duplicate elimination.
ATLEASTONCE
At least once reliable messaging. Select this option for messaging that requires acknowledgement, but not duplicate elimination.
ATMOSTONCE
At most once reliable messaging. Select this option for messaging that requires duplicate elimination, but not acknowledgement.
Required
Table 6-6 Settings Available For an ebXML 1.0 or 2.0 Binding (Continued)
Setting Description Required/
In the Retry Count field, enter the number of retries.
The maximum number of retries for sending a reliably delivered message. The default is 0.
The value is ignored if BESTEFFORT or
ATMOSTONCE is selected for Delivery Semantics. If ONCEANDONLYONCE or ATLEASTONCE is selected, the message is retried until the
acknowledgement is received or the number of retries specified in the Retry Count field is exhausted.
Required if ONCEANDON LYONCE or ATLEASTON CE is selected,
In the Retry Interval field, enter the interval.
The time interval before a message is resent following a timeout waiting for a message acknowledgement. The following are examples of valid entries: 500 ms or 500 msecs,
5 s, or 5 sec, or 5 secs 5 m or 5 mins 5 h or 5 hours 5 d or 5 days
Any combination of the above are also valid. For example:
1 d 5 h 1 sec 500 ms The default is 1 min.
Required if Retry Count is 1 or greater.
Table 6-6 Settings Available For an ebXML 1.0 or 2.0 Binding (Continued)
Setting Description Required/
A d d i n g P r o t o c o l B i n d i n g s t o a T r a d i n g P a r t n e r
In the Persist Duration, enter the interval.
Specifies the duration for which messages have to be stored persistently for the purpose of duplicate elimination.
The following are examples of valid entries: 500 ms or 500 msecs,
5 s, or 5 sec, or 5 secs 5 m or 5 mins 5 h or 5 hours 5 d or 5 days
Any combination of the above are also valid. For example: 1 d 5 h 1 sec 500 ms The default is 0. Required if ONCEANDON LYONCE or ATMOSTONC E is selected,
Note: When defining an ebXML binding for a local trading partner, set the values for Retry Count, Retry Interval, and Persist Duration to the same values as the remote trading partner.
XML Digital Signature Configuration for Non-Repudiation
From the Signature Certificate drop-down list, select an existing certificate or NONE. If you have not yet added the certificate, click Add certificate and follow the instructions in
“Adding Certificates to a Trading Partner” on page 6-22.
The name of the signature certificate used to digitally sign messages. NONE indicates no digital signature.
Optional
Check or uncheck the Signature Required check box.
When checked, the message is digitally signed using the signature certificate of the trading partner sending the message. The default is unchecked.
Archiving of signed messages in a secure audit log is controlled by the secure audit logging configuration. For more information, see Configuring Secure Audit Logging.
Optional
Table 6-6 Settings Available For an ebXML 1.0 or 2.0 Binding (Continued)
Setting Description Required/
Check or uncheck the Signature Receipt Required check box.
When checked, the message is acknowledged by a digitally signed receipt acknowledgement message using the signature certificate of the trading partner sending the acknowledgement. The default is unchecked.
Archiving of signed messages in a secure audit log is controlled by the secure audit logging configuration. For more information, see Configuring Secure Audit Logging.
Optional
Note: Within Oracle WebLogic Integration, the ebXML protocol supports non-repudiation by digitally signing outbound messages and acknowledgements based on the settings for the Signature Required and Signature Receipt Required properties of the binding. In addition to the preceding properties:
• A predefined set of algorithms and parameters are provided by the Oracle WebLogic Integration implementation. To learn more about the implementation, see Using WebLogic Integration Security in
Deploying WebLogic Integration Solutions.
• Optional XPath filtering transforms can be applied to messages for signing purposes. For more information, see Configuring Signature Transforms for ebXML Bindings.
Table 6-6 Settings Available For an ebXML 1.0 or 2.0 Binding (Continued)
Setting Description Required/
A d d i n g P r o t o c o l B i n d i n g s t o a T r a d i n g P a r t n e r