Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 8 Configuring Business Agreements : Operation Bindings Tab

Operation Bindings Tab
Use the Operation Bindings tab to configure the SOAP operations that each participant in a business agreement can initiate and respond to.
The Initiating Operations and Responding Operations areas list the activities that the host and partner can initiate and the partner/host can respond to.
The following properties apply to all the activities that you import in Operations Editor, as shown in Table 12.
When the check box is cleared, it is required that the operation in the Responding Operations area be explicitly bound in the Initiating Operations area also. Otherwise, the following error message is displayed:
The Initiating Operations area lists the activities that the host can initiate and the partner can respond to. To bind an operation in this area, perform the following steps:
1.
Click Add Operation Bindings.
3.
The Responding Operations area lists the activities that the partner can initiate and the host can respond to. To bind an operation in this area, perform the following steps:
1.
Click Add Operation Bindings.
3.
A sample of the operation bindings for the host and partner is displayed, as shown in Figure 23.
Figure 23 Operation Bindings Added for Host and Partner
Editing an Operation Binding for the Host
You can use the Operation Settings, Action Settings, and Transports tabs to override the operation, action, and transport settings of the host.
Operation Settings Tab
To override the operation settings of the host, perform the following steps:
1.
Click a Notify or a Synchronous Request-Response operation binding link in the Initiating Operations area.
2.
Click the Operation Settings tab.
3.
4.
Click Save.
Action Settings Tab
To override the action settings of the host, perform the following steps:
1.
Click a Notify or a Synchronous Request-Response operation binding link in the Initiating Operations area.
2.
Click the Action Settings tab.
3.
Select this check box and then select General from the list to override the action settings originally configured.
Send the outbound action message with WSS:UsernameToken where the user name and password are provided by the private process, which is the message producer.
Require that the inbound message of the same operation must also carry the WSS:UsernameToken element to be used for the inbound message authentication. If the inbound message does not have the WSS:UsernameToken element, the message is rejected with an error message being replied to the trading partner.
If your trading partners use WSS:UsernameToken to authenticate the message they send to you, you must define the external users associated with these trading partners.
If selected, SAML 2.0 assertion is used for request messages in conformance with NHIN/esMD Authorization Framework. You must also select the Require Digital Signature check box, so that the messages are digitally signed with SAML assertion.
4.
Click Save.
Transports Tab
To override the transports settings of the host, perform the following steps:
1.
Click a Notify or a Synchronous Request-Response operation binding link in the Initiating Operations area.
2.
Click the Transports tab.
3.
4.
Click Save.
Editing an Operation Binding for the Partner
You can use the Operation Settings and Action Settings tabs to override the operation and action settings of the partner.
Operation Settings Tab
To override the operation settings of the partner, perform the following steps:
1.
Click a Notify or a Synchronous Request-Response operation binding link in the Responding Operations area.
2.
Click the Operation Settings tab.
3.
4.
Click Save.
Action Settings Tab
To override the action settings of the partner, perform the following steps:
1.
Click a Synchronous Request-Response operation binding link in the Responding Operations area.
2.
Click the Action Settings tab.
3.
Select this check box and then select General from the list to override the action settings originally configured.
Send the outbound action message with WSS:UsernameToken where the user name and password are provided by the private process, which is the message producer.
Require that the inbound message of the same operation must also carry the WSS:UsernameToken element to be used for the inbound message authentication. If the inbound message does not have the WSS:UsernameToken element, the message is rejected with an error message being replied to the trading partner.
If your trading partners use WSS:UsernameToken to authenticate the message they send to you, you must define the external users associated with these trading partners.
The default value is 3600 seconds (60 minutes).
4.
Click Save.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved