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


Chapter 7 Setting Up Trading Hosts and Partners : Configuring the SOAP Protocol for a Partner

Configuring the SOAP Protocol for a Partner
To configure the SOAP protocol for a trading partner, perform the following steps:
1.
In TIBCO Administrator, expand BusinessConnect > Participants.
2.
Click a partner participant link in the right panel.
3.
Click the Protocols tab.
If SOAP is not displayed in the list of protocols, perform the following steps:
a.
Click Enable.
b.
Select the SOAP check box.
c.
4.
Click the SOAP link. The following configuration options are available:
5.
Click Save.
Configuring General Properties for a Partner
Use the General tab to configure general information about your trading partner.
See Adding a Domain Identity for a Partner to add or edit a domain identity.
You can configure the prefix for the envelope namespace. The string SOAP-ENV is still the default, but you can replace it by any string of your choice. For example, a SOAP message can have the following format:
<abc:Envelope
xmlns:abc="http://www.w3.org/2003/05/soap-envelope">
<abc:Header>
</abc:Header>
<abc:Body>
</abc:Body>
</abc:Envelope>
where abc replaces the previously pre-defined string SOAP-ENV.
Note: The value Envelope is not applied to SOAP faults, which always have SOAP-ENV as the default namespace.
TIBCO BusinessConnect SOAP Protocol supports both SOAP versions 1.1 and 1.2 by selecting SOAP 1.1 Protocol or SOAP 1.2 Protocol in the SOAP Version field. The default value is SOAP 1.1 Protocol. The configuration is used to set the outbound messages.
TIBCO BusinessConnect SOAP Protocol supports MTOM by selecting the SOAP MTOM Enabled check box. The configuration is used to set the outbound messages.
For outbound messages, if the content of the binary data is not in base64 format in the body node of the request private process messages, the messages processed by MTOM might not be decoded correctly by the responder side which is also MTOM enabled.
If the SOAP MTOM Enabled check box is selected, the value under xop > tagName > value of the private process message must be populated according to the binary data element in the body node. If not, the request is rejected and the outbound process is ended.
If the SOAP MTOM Enabled check box is not selected, and the value under xop > tagName > value in the private process is provided, the request is rejected and the outbound process is ended.
MTOM and attachments from the private process cannot be used together. If the SOAP MTOM Enabled check box is selected, and some attachments are also specified from the private process request message, the request is rejected and the outbound process is ended.
When selecting the SOAP MTOM Enabled and Require Content Encryption check boxes to send outbound messages, the binary content which refers to the value under xop > tagName > value in the private process message is ignored. The encrypted data in the CipherValue element after encryption is used to construct the MTOM attachment.
Adding a Domain Identity for a Partner
To add a domain identity, perform the following steps:
1.
2.
3.
Select a domain from the Domain list and type an identity in the Identity field.
4.
Click Save.
5.
Configuring Transports for a Partner
To add the transport for a partner, perform the following steps:
1.
Click the Transports tab.
2.
Click Add.
In the New Transport window, type data as explained in Table 11.
Select HTTP or HTTPS from the Type list.
3.
4.
5.
Click Save three times.
See the information about setting up HTTP/S for a trading partner in TIBCO BusinessConnect Trading Partner Administration.

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