To set up blueprint design servers and engines in a clustered configuration, you install them on separate systems and connect them to the same database and network storage. You can install as many blueprint design servers and engines as you need. You can also install blueprint design servers and engines as cold-standby servers to serve as disaster recovery units. You can install a blueprint design server and an engine on each cluster node, or you can install blueprint design servers and engines on separate nodes. If you install an engine and a blueprint designer on the same node, ensure that your operating system is compatible with the engine.
You do not need to install the same number of blueprint design servers and engines. Most high-availability setups need more engines than blueprint design servers.
Then, you configure a load balancer to distribute the traffic to the blueprint design servers. Instead of accessing the blueprint design servers and engines directly, users access the load balancer URL. To the users, that URL appears to host a single instance of the blueprint design server or engine.
To connect to OpenStack-based clouds, the topology is different because the Heat engines are installed via the OpenStack server, not via IBM UrbanCode Deploy:
You can set up a cluster of blueprint design servers and engines independently of the IBM UrbanCode Deploy server. You do not necessarily have to have a cluster of IBM UrbanCode Deploy servers.
Several server processes behave differently than with individual servers. See High-availability server processes.