You can use IBM® App Connect Enterprise with
the existing high availability manager for Windows Server (Failover Cluster
Manager).
About this task
For more information about the versions of Windows Server that are supported
by IBM App Connect Enterprise, see the IBM App Connect Enterprise system
requirements web page.
This
topic summarizes how to complete the following tasks:
- Complete the prerequisite setup.
- Configure a local group.
- Create an integration node.
- Add integration node instances to the additional nodes.
- Add the integration node service to the cluster configuration
- Start and stop an integration node.
- Delete an integration node.
Procedure
- To complete the prerequisite setup, complete the following
steps:
- Validate your Failover Cluster Manager configuration.
- Complete all of the steps documented in 'Supporting the Microsoft Cluster Service' of the IBM MQ
documentation to create a cluster configuration that contains the queue manager on which you want
the integration node to run.
- Note the haregtyp.exe command as a prerequisite for creating IBM MQ resources in the cluster.
- To configure a local group, ensure that the domain user
under which you want the integration node to run exists in the
local
mqbrkrs
group on all nodes on which you
want the integration node to run.
- To create an integration node, use the following mqsicreatebroker command on
the node on which your cluster is currently running.
mqsicreatebroker INODE -q MQ1 -e E:\ACE\Workspace
where:
- INODE is the
name of the integration node.
MQ1
is the name of the queue manager.
E:\ACE\Workspace
is
the directory of a shared disk (nonquorum) in your cluster
configuration.
- To add this integration node instance to the other nodes
in your cluster, switch your cluster to each node in turn. When a
node is active, use the following mqsiaddbrokerinstance command.
mqsiaddbrokerinstance INODE -e E:\ACE\Workspace
where:
- INODE is the
name of the integration node.
E:\ACE\Workspace
is
the directory of a shared disk (nonquorum) in your cluster
configuration.
- To add an integration node generic service resource to
the cluster which contains the integration node queue manager, complete
the following steps:
- Select the IBM App Connect Enterprise component
integration_node
service when asked. All
other settings can be left unchanged.
- Add a dependency on the IBM MQ resource, to ensure
that the queue manager is started before the integration node.
- To start and stop the integration node resource, use Failover
Cluster Manager.
- To delete an integration node resource from the Failover
Cluster Manager, take the following steps:
- Delete the integration node generic service from the
cluster configuration.
- Use the mqsiremovebrokerinstance command
on all nodes but one, moving the cluster between nodes before running
each command.
- On the final node, use the mqsideletebroker command to
completely remove the integration node configuration.
Results
For further information about configuring IBM MQ with a high
availability manager for Windows Server, see the IBM MQ
product documentation online.
See the following
topics:
- Introducing MSCS clusters
- Supporting the Microsoft Cluster
Service (MSCS)
- Setting up IBM MQ for MSCS clustering