Does BC SOAP plugin support RPC SOAP transactions?
Article ID: KB0089100
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| Not Applicable | - |
Description
Resolution:
BC/SOAP's offering is not strictly Document or RPC style. It is simplistic in its approach and offers SOAP as a packaging format.
The SOAP format consists of a Header section and a Body section. BC/SOAP allows private processes to specify what
they want inside the Header section as well as inside the Body section. The formatting of information inside these two sections
is completely the responsibility of the private processes. If there are schemas that governs them, then they need to match the schema.
With that understanding, BC/SOAP really doesn't enforce RPC or Document style. It is up to the users to decide how the
final SOAP message should look like. This implies that users now need to understand what makes a SOAP message document
style and what makes a SOAP message RPC style.
You could say that BC/SOAP is closer to Document style than RPC style. This is because when users specify what goes inside Header and
what goes inside the Body, the format will be most likely document style. From a B2B perspective, document style is also more suited to
the nature of long lived transactions. RPC style is typically short burst of request/reply. Typical usage may be to have the RPC style
message translated to be an invocation of a java api call. A document style message typically gets translated to be a call to some
back-end systems such as ERPs that will not be able to return things so quickly. A deployment may end up supporting both.
BC does not support SOAP RPC encoding, it only supports RPC-literal encoding. It appears that the RPC encoding scheme is being discouraged from an inter-operability standpoint. Please refer to the document titled "Basic Profile 1.0a - Final Specification" at "http://www.ws-i.org/documents.aspx#document1" for some related comments.
An example demonstrating SOAP RPC using BC is attached to this Solution.
BC/SOAP's offering is not strictly Document or RPC style. It is simplistic in its approach and offers SOAP as a packaging format.
The SOAP format consists of a Header section and a Body section. BC/SOAP allows private processes to specify what
they want inside the Header section as well as inside the Body section. The formatting of information inside these two sections
is completely the responsibility of the private processes. If there are schemas that governs them, then they need to match the schema.
With that understanding, BC/SOAP really doesn't enforce RPC or Document style. It is up to the users to decide how the
final SOAP message should look like. This implies that users now need to understand what makes a SOAP message document
style and what makes a SOAP message RPC style.
You could say that BC/SOAP is closer to Document style than RPC style. This is because when users specify what goes inside Header and
what goes inside the Body, the format will be most likely document style. From a B2B perspective, document style is also more suited to
the nature of long lived transactions. RPC style is typically short burst of request/reply. Typical usage may be to have the RPC style
message translated to be an invocation of a java api call. A document style message typically gets translated to be a call to some
back-end systems such as ERPs that will not be able to return things so quickly. A deployment may end up supporting both.
BC does not support SOAP RPC encoding, it only supports RPC-literal encoding. It appears that the RPC encoding scheme is being discouraged from an inter-operability standpoint. Please refer to the document titled "Basic Profile 1.0a - Final Specification" at "http://www.ws-i.org/documents.aspx#document1" for some related comments.
An example demonstrating SOAP RPC using BC is attached to this Solution.
Issue/Introduction
Does BC SOAP plugin support RPC SOAP transactions?
Attachments
Feedback
Yes
No
Powered by
