Oracle Service Bus use case

By decoupling the service provider from service consumers, we have achieved high flexibility. Now, let's have a look at what happens if we deploy a new version of EmployeeTravelStatus service which has a slightly different interface and different endpoint address. If we did not use mediation, we would have to modify and re-deploy all service consumers. In our case, there is no need to do that. Instead, we can simply modify the Proxy message flow and service consumers do not need to be aware of the change.

Now, we will demonstrate this scenario. Let's say that the new version of service uses the same namespace, but different input. The old version of service accepts the employee of the following type:

<xsd:complexType name="EmployeeType">
<xsd:sequence>
<xsd:element name="FirstName" type="xsd:string" minOccurs="0"/>
<xsd:element name="LastName" type="xsd:string" minOccurs="0"/>
<xsd:element name="Department" type="xsd:string" minOccurs...