Multi-Protocol Gateway

A Multi-Protocol Gateway can accept client-originated messages in various protocols. The service can then pass messages to a remote server with various protocols. The protocol that the client uses does not need to be the same as the protocol that the remote server uses.

A Multi-Protocol Gateway supports the following protocols.
  • AMQP
  • FTP
  • HTTP
  • HTTPS
  • IBM® MQ
  • IMS Callout
  • IMS Connect
  • Kafka
  • MEIG AS2
  • NFS
  • SFTP
  • Stateful raw XML
  • Stateless raw XML
  • TIBCO EMS
  • WebSphere® JMS

A Multi-Protocol Gateway can support more than one client protocol. Similarly, the service can support more than one server protocol.

The following figure provides an illustration of the static server architecture that the service supports.
Figure 1. Static server architecture

A Multi-Protocol Gateway can accept client requests through any of the protocol handlers that are shown (HTTP, HTTPS, or IBM MQ). A static URL determines the destination for all traffic. This server-side traffic can employ one of the protocols that are shown (HTTP, HTTPS, or IBM MQ).

When the remote service endpoint is determined dynamically, the Multi-Protocol Gateway supports a stateful raw XML handler. Because the connection is stateful, this protocol handler can communicate with only a remote service that also uses the same protocol. The following figure shows other protocol handlers that can route to the other protocols dynamically.
Figure 2. Dynamic server architecture

The messages can be processed and routed with any of the processing actions that are available to a service.

To support the enforcement of policy on a Multi-Protocol Gateway service, the WebSphere Service Registry and Repository server requires the following extra configuration steps.
  • Verify that the registry is at the correct level (8.0.0.2 or later).
  • Create the SLDFromServiceVersion named query.
  • Create the following objects in the registry.
    • Service Version
    • Service Level Definition (SLD)
    • REST Service Endpoint

The WebSphere Service Registry and Repository documentation includes tutorials and has a tutorial for governing a REST service. This tutorial explains how to create named queries and registry objects.