A service gateway allows routing to multiple endpoints
using a messaging or HTTP binding. Requests can have the headers,
body or both manipulated in a mediation module before being forwarded
to the service provider.
About this task
Using
WebSphere® Integration Developer you can build a
gateway service, which allows routing messages to multiple endpoints
using messaging or HTTP binding. This allows the gateway to handle
different portTypes with a single generic export. Requests containing
different portTypes arrive at a generic endpoint, which is the entry
into the gateway. These requests can have the headers, body or both
manipulated in a mediation module before being forwarded to the service
provider. There are two types of service gateways, the dynamic service
gateway and the static service gateway:
The following bindings are supported in a service gateway scenario:
- JMS
- Generic JMS
- MQ JMS
- MQ
- HTTP
Figure 1. Actor (service requester) and system (ESB)
The following sections explain how to use bindings with
static and dynamic service gateways.