The kind of SCA modules that WebSphere ESB supports
are called mediation modules, which provide a simple way to change
the format, content or target of service requests and responses.
How does the integration developer use WebSphere Integration Developer to
create a mediation module?
Suppose there is a requester service that has to access a service provider.
The requester wants to send a customer ID, and the provider expects a customer
ID, but their protocols are different.
Figure 1. A requester accessing a service provider that uses a different
protocol..
There is a need to transform between the SOAP/HTTP
protocol used by the requester and the SOAP/JMS protocol used by the service
provider.
So the developer creates a mediation module. And it might be sufficient
to create an import and an export with the appropriate
associations to achieve the desired effect.
Figure 2. A simple mediation module, with only an import binding of SOAP/HTTP
and an export binding of SOAP/JMS declared..
This is enough for
the mediation module to automatically transform between the two protocols.
In this way the integration developer can very quickly integrate services:
- to get standard protocol conversion without having to write code.
- to simplify matters where a service might have a number of possible interfaces.
- to render a system immune to physical changes.