Over a million developers have joined DZone.

Connecting Servers to Each Other with Cluster Connections

DZone 's Guide to

Connecting Servers to Each Other with Cluster Connections

Setting up a cluster of IBM's UrbanCode Deploy servers? Check out how you can make sure your cluster is setup correctly and performs properly.

· Integration Zone ·
Free Resource

One important part of setting up a high-availability cluster of IBM UrbanCode Deploy servers is making sure that the agents can connect to the servers. If you’ve got four servers, how does an agent know which server to connect to? Part of that task, of course, is getting your failover connections set up properly. Another part is getting cluster connections configured between the servers.

Cluster connections, formerly known as network relays, open a port for Java Message Service communication between servers. These connections allow the servers to accept incoming JMS connections from agents and route the agent communications to the appropriate server. That way, each agent connects to the server that is running workflows on that agent.

For a while, I thought that every server had to have a cluster connection to every other server, but I was wrong. Because the servers share the connections, you need only one cluster connection to each server in the cluster, including the server on which you create the connections. So if I’ve got four servers, I go to Settings > Network on one of those servers and create entries for each server. Those four connections look like this:

Four cluster connections that point to four servers in an HA clusterFor more info on setting up a high-availability IBM UrbanCode Deploy topology, see High availability and failover.

cluster ,jms ,ibm ,urbancode deploy ,load balancing

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}