The easiest way to add servers to a cluster is to install new servers. The
installation program sets them up to be part of the cluster.
Before you begin
Set up a cluster of servers, including setting up a load balancer, shared database,
and network storage. See Setting up clusters of servers.
Each server must run the same version of IBM UrbanCode Deploy.
Ensure that each server can connect to each other
server on the network. For example, ensure that your firewall rules allow the servers to
communicate over HTTPS and JMS.
Procedure
On the system on which you are installing the new server, set up a connection to the
network storage. For example, on Linux systems, you might
mount a remote drive to the local file system.
When the installation program asks for database information, specify the shared
database for the cluster.
When the installation program asks for the host name for users to access, specify
the host name of the load balancer.
When the installation program asks whether the server is part of a
high-availability cluster, specify yes.
When the installation program asks for the location of the application data,
specify the same folder on the network storage that the other cluster servers are
using. If this is the first server in the cluster, you can specify any folder on the
network storage. In this case, other servers that you add to the cluster must also
use this folder.
Set the new server to use the same security certificate as the existing
servers. For example, you can copy the certificate in the
/opt/tomcat/conf/tomcat.keystore file to the other servers. When
you import the certificate into other servers, in the server.xml
file, set the keyAlias property to point to the imported
certificate.
If there are other servers in the cluster, create a cluster connect on one of the existing
servers to the new server. See Creating cluster connections.
Configure the load balancer to send HTTP/HTTS traffic to the new cluster
server.
Moving existing servers to a cluster
Before you begin
Set up a cluster of servers, including setting up a load balancer, shared database,
and network storage. See Setting up clusters of servers.
Each server must run the same version of IBM UrbanCode Deploy.
Ensure that each server can connect to each other
server on the network. For example, ensure that your firewall rules allow the servers to
communicate over HTTPS and JMS.
Procedure
On the system that hosts the server, set up a connection to the network
storage. For example, on Linux systems, you might mount a remote drive to the local file system.
If the sever contains elements that you want to keep, such as components,
applications, or processes, export those elements and import them into an existing
cluster server.
Stop the server.
Edit the installed.properties file on the server, located in the
install_folder/conf/server directory.
Set the server.appdata.dir property to the location of the application
data folder that the cluster servers are using.
Copy the value of the encryption.keystore.alias property to the equivalent
file on the new cluster server from a server that is already in the cluster.
Add the following line of code to the file:
com.urbancode.ds.UDeployServer.multiserver=true
Update the database settings to use the same database as the other servers in the
cluster.
Set the new server to use the same security certificate as the existing
servers. For example, you can copy the certificate in the
/opt/tomcat/conf/tomcat.keystore file to the other servers. When
you import the certificate into other servers, in the server.xml
file, set the keyAlias property to point to the imported
certificate.
Start the server.
On the new cluster server, click Settings > System Settings, and set the External Agent URL and the
External User URL to the URL for the load balancer.
Click Save.
On one of the existing cluster servers, create a network relay to the new
server. See Creating cluster connections.