IBM Business Process Manager, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions
Create a service gateway
A Service gateway acts as a proxy to a variety of different services by providing a single entry point for incoming requests.
This scenario is applicable for WebSphere Enterprise Service Bus and IBM BPM Advanced. Mediation modules can be deployed to WebSphere Enterprise Service Bus and IBM BPM. Modules can be deployed to IBM BPM.
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 and static:
- 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
See
- Static service gateway examples
- Create a static service gateway
- Create a dynamic service gateway
- Dynamic service gateway examples
- Service gateway artifacts