Managing a SOAP Version Mismatch Issue Using Oracle Service Bus
Recently, we discovered a version mismatch issue in which two SOAP services on different versions (Service-A on SOAP 1.2 and Service-B on SOAP 1.1) were failing to communicate with each other. Here, we explain how to resolve this issue.
Difference between SOAP 1.1 and SOAP 1.2
Before diving into the solution, let’s look at the improvements SOAP Version 1.2 provides over SOAP 1.1.
- Offers a clear processing model;
- Provides improved interoperability with testing and implementation requirements;
- Based on XML Information Set (i.e. It is specified as an Infoset, which is carried from one SOAP node to another, whereas SOAP 1.1 was based on XML 1.0 serialization.);
- Offers protocol independence for developers by providing a binding framework;
- Includes HTTP binding for improved integration to the World Wide Web;
- Delivers a well-defined extensibility model; and
- Provides improved support for Web standards.
WSDL changes observed in SOAP 1.2
- Namespace Changes: SOAP 1.2 supports the following namespace definition:
2. SOAP 1.2 uses “application/soap+xml” as the Content Type, whereas SOAP 1.1 uses “text/xml”.
3. SOAP:Operation and SOAP Binding must be specified in SOAP 1.2 WSDL.
Now, to overcome the versioning mismatch issue mentioned above, we must follow these steps:
- Generate the OSB Proxy as a Message Based Proxy service. This will be based on the XSD with only the “body” part with required parameters to call Service-A (SOAP 1.2) and Service-B (SOAP 1.1).
- Create a Pipeline Service based on the same methodology explained in number 1, above.
- In the Pipeline Service, navigate to Message Flow and add a Pipeline Pair – rename it per the process standards.
- In the Request Pipeline node, add a Stage and rename it per process standards.
- Inside the Stage, add a Service Callout, then browse for the Proxy Service for the wrapper of Service-A or the business service of Service-A. The Service Callout configuration is shown below with the required message to Service-A parameters assigned.
- After the above Pipeline Pair is complete, add a Route Node.
- Inside the Route Node, add a Routing Operation and configure the same for the Business Service of Service-B.
- Inside the Request Actions, assign or replace the Body and Header to make a successful call for Business Service. The following snapshot illustrates this.
As always, if you have any questions regarding this issue or solution, leave us a comment below or contact us at email@example.com and our team will get back to you.