High availability overview

An overview of the high availability configuration and topology options available in IBM® Integration Bus.

For high availability in IBM Integration Bus, you must set up a shared file system.

In IBM Integration Bus, you can create a high availability solution in the following ways:

Multi-instance integration nodes with WebSphere® MQ

Use a multi-instance integration node so that the integration node is available in the same location as the WebSphere MQ multi-instance queue manager in a high availability WebSphere MQ configuration. The multi-instance integration node can either dynamically start in all locations where the multi-instance queue manager runs, or can be set as an MQ Service dependency.

For more information, see Configuring multi-instance integration nodes.

An existing high availability manager

Use an external high availability manager by mounting the external resources to the shared file system. Script files are provided for the common tasks that are required to create a multi-instance integration node.

For more information, see Using an integration node with an existing high availability manager.

An existing Windows Cluster

Add an integration node to the nodes in a Windows Cluster.

For more information, see Using an integration node with an existing Windows Cluster (Windows Server).

HTTP proxy servlet

Use the HTTP proxy servlet in a servlet container so that you can support high availability, load distribution, access to the integration node from multiple IP addresses and ports, and a larger number of concurrent HTTP sessions.

For more information, see HTTP proxy servlet overview.

External web servers

IBM Integration Bus is frequently a component in Service Oriented Architecture (SOA) patterns that include external web servers and other HTTP solutions. Use WebSphere Application Server to simplify administration in this topology.

For more information, see Using external web servers with IBM Integration Bus.