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


Chapter 10 Advanced Topics : Using the Passthrough Feature

Using the Passthrough Feature
In cases that some of the header values are missing from the inbound URL, TIBCO BusinessConnect SOAP Protocol uses the following rules to process the inbound message:
The tpName and opid parameter values are the minimum information in the URL for inbound message to be processed end-to-end.
The tpName parameter value indicates which trading partner the message is sent from, and the opid parameter value indicates which operation is used to process the message. In a synchronous request-response operation type, the response message can be sent back if everything else is correct.
If either tpName or opid parameter value is missing, the following two situations occur:
If the Allow Anonymous SOAP Messages check box is selected, the message is processed in passthrough mode and forwarded directly to private process without validation and parsing. For a synchronous request reply operation, the message is processed as a notify operation without any response being sent back.
The Allow Anonymous SOAP Messages check box can be configured in various locations. If the host parameter value is present in the URL, the Allow Anonymous SOAP Messages check box in the configuration of the local host referred by this host parameter value takes effect. If the tpName parameter value is present in the URL, the Allow Anonymous SOAP Messages From This Trading Partner check box in the configuration of the trading partner referred by this tpName parameter value takes effect. If neither host or tpName value is present, the configuration of the default host takes effect.
If the Allow Anonymous SOAP Messages check box is unselected in either the related host or trading partner configuration, the message is rejected.
Here are the detailed descriptions of some typical scenarios:
Case 1
SOAP header is absent; URL has no parameters.
Example: http://www.SOAPServer.com:6700/dmz/SOAP
The SOAP message is rejected by default, and a SOAP fault is generated and sent back to the trading partner. To avoid messages from trading partners being rejected, you must select the Allow Anonymous SOAP Messages check box under BusinessConnect > Participants > Default Host > Protocols > SOAP > General.
When anonymity is enabled, TIBCO BusinessConnect SOAP Protocol has no context for the inbound message. It can only handle the incoming message as a notify operation. TIBCO BusinessConnect server forwards the inbound SOAP message to the private process through the ResponderRequest message. The request and requestHeader fields of this message contain the incoming SOAP header and body information in XML format. Once the inbound SOAP message is forwarded to the local private process, BusinessConnect server sends an HTTP 204/No Content response back to the trading partner.
Case 2
SOAP header is absent; URL has no tpName and host parameters.
Example:
  http://www.SOAPServer.com:6700/dmz/SOAP
    ?opid=Sync/1.0/PORequest
    &transid=1232456789
TIBCO BusinessConnect SOAP Protocol cannot determine the trading partner context information. The behavior is identical to when no parameters are present.
Case 3
SOAP header is absent; URL has no opid parameter, but has the tpName parameter.
Example:
  http://www.SOAPServer.com:6700/dmz/SOAP
    ?tpname=SOAPClient
    &transid=1232456789
The SOAP message is rejected by default, and a SOAP fault is generated and sent back to the trading partner. To avoid messages from trading partners being rejected, you must select the Allow Anonymous SOAP Messages From This Trading Partner check box under BusinessConnect > Participants > SOAPClient > Protocols > SOAP > General.
When anonymity is enabled for this trading partner, TIBCO BusinessConnect SOAP Protocol has no operation-related context for the inbound message. It can only handle the incoming message as a notify operation. TIBCO BusinessConnect SOAP Protocol forwards the inbound SOAP message to the private process through the ResponderRequest message. The request and requestHeader fields of this message contain the incoming SOAP header and body information in XML format. Once the incoming SOAP message is forwarded to the local private process, BusinessConnect server sends an HTTP 204/No Content response back to the trading partner. For this transaction, host is the default host of the system.
Case 4
SOAP header is absent; URL has no transid parameter, but has the tpName and opid parameters.
Example:
http://www.SOAPServer.com:6700/dmz/SOAP
    ?tpname=SOAPClient &opid=Sync/1.0/PORequest
TIBCO BusinessConnect SOAP Protocol has the complete context of the inbound SOAP message. The transaction is processed as a regular synchronous request response or notify transaction, depending on the type of operation in the incoming message. A unique transaction ID is generated and this ID is passed to the private process.
Case 5
SOAP header is absent; URL has no opid parameter, but has the host and tpName parameters.
Example:
http://www.SOAPServer.com:6700/dmz
   /SOAP?host=SOAPClient&tpname=SOAPServer
The SOAP message is rejected by default and a SOAP fault is generated and sent back to the trading partner, because no operation context is used for processing the inbound message. To avoid messages from trading partners being rejected, you must select the Allow Anonymous SOAP Messages From This Trading Partner check box under BusinessConnect > Participants > SOAPClient > Protocols > SOAP > General. With the host and tpName parameters, the configuration of the trading partner that is SOAPClient referred by the tpName takes precedence. BusinessConnect server forwards the inbound SOAP message to the private process through the ResponderRequest message. The request and the requestHeader fields of this message contain the incoming SOAP header and body information in XML format. Once the incoming SOAP message is forwarded to the local private process, BusinessConnect server sends an HTTP 204/No Content response back to the trading partner.

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