A Service gateway acts as a proxy to a variety of different
services by providing a single entry point for incoming requests.
Note: This scenario is applicable for WebSphere® Enterprise Service Bus and IBM® Business Process Manager Advanced.
Mediation modules can be deployed to WebSphere Enterprise Service Bus and IBM Business Process Manager.
Modules can be deployed to IBM Business Process Manager.
All requesters interact with a single endpoint address exposed
by the gateway. The gateway is responsible for performing a common
operation on every message and routing the request to the correct
service provider.
A service gateway has a single generic export and a single generic
gateway interface, which allows the gateway to handle messages for
different port types. Messages entering the gateway can have the headers,
body or both manipulated within a mediation flow before being forwarded
onto the service provider.
There are two types of service gateways, the dynamic service gateway
and the static service gateway:
- In a dynamic service gateway, the endpoint address of the
service provider is determined within the mediation flow by looking
up information from a database, a registry or from the message contents.
The mediation flow typically modifies the header information in the
message.
- In a static service gateway, the import is created using
a specific interface known before the message enters the gateway.
The mediation flow typically modifies the information contained in
the body and header of a message.
The following bindings are supported in a service gateway scenario:
- Web service
- HTTP
- JMS
- Generic JMS
- MQ JMS
- MQ