Copyright © TIBCO Software Inc. All Rights Reserved

> Configuring Agreement Protocol Binding for Services Plug-in
> To configure Services Plug-in agreement protocol bindings:

> 1. | On the New Agreement page, click Add Protocol Bindings.

> 2. | On the Select Protocol page, select the EZComm check box.

> 3. | Click OK.

> The New Agreement page is displayed.

> 4. | Click the EZComm link in the Agreement Protocol Binding list.

> The following tabs for configuring protocol binding options are available:

> − | Operation Bindings Tab

> − | Document Security Tab

> − | Transports Tab

> − | Show Advanced Tab

> Operation Bindings Tab
> Use the Operations Binding tab to configure the Services Plug-in operations that each participant in a business agreement can initiate and respond to.
> The Host ’X’ Can Initiate and Partner ’Y’ Can Initiate areas list the activities that the host/partner can initiate and the partner/host can respond to.

> 1. | Enter information according to Table 18.

> Table 18 Edit Protocol Binding: Operation Binding Tab
> Field | Description
> Allow All Operations | If the check box is selected, you do not need to specify operation bindings that the host or partner can initiate. If the check box is cleared, you need to define the specific operation bindings.
> Non-Repudiation Logging | The non-repudiation log is used to provide proof of the delivery of messages. For details, see TIBCO BusinessConnect Concepts, Non-Repudiation.

> 2. | In the Initiating Operations section, click Add Operation Binding.

> 3. | Expand the operation tree and select the operation.

> 4. | Click OK.

> The selected operation is displayed in the Operation Name list.
> Edit Operation Bindings for the Host
> Click the operation in the Initiating Operations section. The following tabs for configuring options are available:

> • | Operation Settings Tab

> • | Action Settings Tab

> • | Transports Tab

> Operation Settings Tab
> Override the operation settings as shown in Table 19.

> Table 19 Override Outbound Settings: Operation Settings Tab (All Operations)
> Field | Description
> Override Operation Settings | Select the check box to override the operation settings for this operation. These settings have been previously configured, as explained in Importing the Tutorial. Note When a BusinessConnect server acts as the Initiator, the transport for sending an outbound document can be overridden for all operation types bound in this section. Such overriding does not apply to the outbound responses of an Asynchronous Request Response operation in cases when the BusinessConnect server acts as the Responder.
> Inbound
> Validate Message | When selected, an inbound messages (either request or response) are validated. This should be selected in the following cases:
> • | If the Initiator needs the response from the partner to be validated.
> • | If the Responder needs the request to be validated.
> Outbound
> Validate Message | When selected, either the request or response is validated. This check box should be selected in the following cases:
> • | Initiator needs that the request to the partner be validated
> • | Responder needs that the response be validated

> Click Save or Cancel (if no changes have been made).
> Action Settings Tab.
> Override the action settings using Table 20.

> Table 20 Override Outbound Settings: Actions Tab (Notify and Asynchronous Request-Response Operations)
> Field | Description
> Override Action Settings | Select the check box to override the originally configured action settings for the host.
> Require Digital Signature | ( Notify operation with HTTP and HTTPS transports only ) Select to override the originally configured signature settings for the host.
> Require Content Encryption | ( Notify operation with HTTP and HTTPS transports only ) Select to override the originally configured encryption settings for the host.
> Wait Time for Response (seconds) | (Asynchronous Request-Response operation only) Select to override the originally configured Wait time for the Initiator. The default is 3600 seconds (60 minutes).

> Click Save or Cancel (if no changes have been made).
> Transports Tab
> Configure transport settings as shown in Table 21.

> Table 21 Override Outbound Settings: Transports Tab (All Operations)
> Field | Description
> Override Transports | Select the check box to override the originally configured transport for the host.
> Override Outbound Transports
> Primary Transport | Select any of the transports previously configured for the partner. See Add Transport for the Initiator Partner for details.

> Click Save or Cancel (if no changes have been made).
> Edit Operation Bindings for a Partner

> | When a BusinessConnect sever acts as the Responder, the transport for sending an outbound document can only be overridden when sending the response for asynchronous operation types bound in this section.

> Click the operation in the Responding Operations section. The following tabs for configuring options are available:

> • | Operation Settings Tab

> • | Action Settings Tab

> • | Transports Tab

> Operation Settings Tab
> Override the operation settings as shown in Table 22.

> Table 22 Override Inbound Settings: Operation Settings Tab (All Operations)
> Field | Description
> Override Operation Settings | Select the check box to override the operation settings for this operation. These settings have been previously configured, as explained in Importing the TutorialI.
> Inbound
> Validate Message | When selected, an inbound messages (either request or response) are validated. This should be selected in the following cases:
> • | If the Initiator needs the response from the partner to be validated.
> • | If the Responder needs the request to be validated.
> Outbound
> Validate Message | When selected, either the request or response is validated. This check box should be selected in the following cases:
> • | Initiator needs that the request to the partner be validated
> • | Responder needs that the response be validated

> Click Save or Cancel (if no changes have been made).
> Action Settings Tab
> To configure either the Synchronous or Asynchronous Request Response operation, click the Action Settings tab and override the action settings as shown in Table 23.

> Table 23 Override Inbound Settings: Actions Tab (Synchronous and Asynchronous Request Response)
> Field | Description
> Override Action Settings | Select to override the originally configured action settings for the partner.
> Private Process Wait (seconds) | Select to override the originally configured Wait time (amount of time the Responder waits for the response from the private process). The default is 3600 seconds (60 minutes).

> Click Save or Cancel (if no changes have been made).
> Transports Tab
> Override transport settings as shown in Table 24.

> Table 24 Override Inbound Settings: Transports Tab (All Operations)
> Field | Description
> Override Transports | Select the check box to override the originally configured transport for the partner. Note For the Synchronous Request Response operation, this option is invalid.
> Override Outbound Transports
> Primary Transport | Select any of the transports previously configured for the partner.

> Click Save or Cancel (if no changes have been made).
> Document Security Tab
> To learn how to edit this tab, see TIBCO BusinessConnect Trading Partner Administration Guide, Document Security Tab.
> See also TIBCO BusinessConnect Concepts, Chapter 8, Security.
> Shadow Credential Usage for the Services Plug-in
> Sending Signed or Encrypted Messages
> When sending signed or encrypted messages over HTTP, HTTPS, or HTTPSCA transports, you can use shadow credentials during overlay and shadow credential period to sign or encrypt these messages.
> Receiving Signed or Encrypted Messages
> When receiving signed or encrypted messages from a trading partner over HTTP, HTTPS, or HTTPSCA transports, credentials are picked during the overlay period in the following order:

> a. | Shadow credential is tried for authentication or decryption.

> b. | If this fails, the original credential is tried.

> For the shadow credential period, only the shadow credential is tried.
> Transports Tab
> The Transports tab is divided in two sections as follows:

> • | The top section is used for specifying transport information for the outbound, or host to trading partner, direction.

> • | The bottom section is used for specifying transport information for the inbound, or trading partner to host, direction.

> Configure transports for the host according to Table 25.

> Table 25 Configure Transports for the Host
> Field | Description
> Outbound Transports for Host
> Primary Transport | Select the outbound transport that was previously configured. See Add Transport for the Initiator Partner for more details.
> AS2 MDN Async Reply Transport | Select any of the configured transports. For more information, see TIBCO BusinessConnect Trading Partner Administration Guide.
> AS2 Async MDN Remote Server Certificate | For more information, see TIBCO BusinessConnect Trading Partner Administration Guide.
> Client Authentication Identity for HTTPS, FTPS, HTTPSCA | For more information, see TIBCO BusinessConnect Trading Partner Administration Guide.
> Client Authentication Identity for SSHFTP | For more information, see TIBCO BusinessConnect Trading Partner Administration Guide, Edit Protocol Bindings: Transports Tab.
> Allowed Inbound Transports for Partner
> (list of configured partner transports) | Select the appropriate check boxes to allow certain inbound transports for the partner.

> Click Save twice.
> Show Advanced Tab
> The Show Advanced tab on the Edit Protocol Bindings page allows you to configure additional settings for the host in a business agreement.

> 1. | Click Show Advanced.

> The Edit Protocol Bindings page is displayed with two additional tabs: Host’s Configuration and Partner’s Configuration.

> 2. | To hide the Host’s and Partner’s Configuration tabs, click Hide Advanced.

> Override Settings for the Host
> To override general settings for the host:

> 1. | Select the tab representing the host.

> 2. | Enter or select information according to Table 26.

> Table 26 Edit Protocol Bindings: Advanced Settings for Host
> Field | Description
> Override Settings | If you select the Override Settings check box, it overrides the values set on the host level: the AS2 Identity selected from the AS2 Identifier list is used to override the default AS2 identity for the host configured by using the procedure described in the following sections:
> • | TIBCO BusinessConnect Trading Partner Administration Guide, Set the Host’s AS2 Identifier for a Protocol.
> • | TIBCO BusinessConnect Trading Partner Administration Guide, Disabling Session Cache for HTTPS.
> If you clear the Override Settings check box, the default AS2 identity for the host remains valid.
> AS2 Identifier | Select an AS2 identity that is used to override the default AS2 identity.

> 3. | Click Save.

> Override Settings for the Partner
> To override general settings for the partner:

> 1. | Select the tab representing the partner.

> 2. | Enter or select information according to Table 27.

> Table 27 Edit Protocol Binding: Advanced Settings for Partner
> Field | Description
> Override Settings | If you select the Override Settings check box, this overrides the values set on the partner level: the AS2 Identity selected from the AS2 Identifier list is used to override the default AS2 identity for the host configured using the procedure described in the following sections:
> • | TIBCO BusinessConnect Trading Partner Administration Guide, Set the Host’s AS2 Identifier for a Protocol.
> • | TIBCO BusinessConnect Trading Partner Administration Guide, Disabling Session Cache for HTTPS.
> If you clear the Override Settings check box, the default AS2 identity for the partner remains valid.
> AS2 Identifier | Select an AS2 identity that is used to override the default AS2 identity.
> Allow override of filename via HTTP parameter (applies only to HTTP/S transports) | If this check box is selected, and a file reference is being passed from the private process, then the name of the file is passed on to the Responder in an HTTP header called filename. Each partner has this check box. If it is selected and there is a fileName field in the HTTP message header or in QueryString (in that order), the message is written to a fileName file. This file is created in the shared directory located under the partner’s name directory. The file size is irrelevant in this case. Note This feature is fully supported for the Notify and Asynchronous Request Response operations. For the Synchronous Request Response operations, only request can send the filename to the partner while the partner cannot send the filename on the response: a synchronous response cannot be written to the file that the partner wants.

> 3. | Click Save.

Copyright © TIBCO Software Inc. All Rights Reserved