Ztech Blogs

take our word for it

Deploying UrbanCode Deploy Blueprint Designer Cloud Applications Part 3 – Building a Lab Environment

Now that we have covered connecting to AWS and understand agents and agent relays, it is time to take a step back and look at how to construct a lab environment for IBM UrbanCode Deploy (UCD) and the IBM Blueprint Designer (BPD).  There are a number of options to consider and in this blog I will step through three potential approaches.

Option 1 – Partial Home Setup 1

It is possible to host IBM UrbanCode Deploy on a laptop with a combination of the laptop’s native OS and virtual machines. With the aid of glyphs in the IBM Knowledge Center, the topology of my original home setup is provided in Figure 1. The UCD server and a MySQL 5.6 database are installed directly on Mac OS X. The Heat engine requires RHEL 7 so I am also using a RHEL 7.3 instance to host the Blueprint Designer, the Cloud Discovery service, the Heat Engine, the Keystone Identity service and its associated database. The RHEL 7.3 instance on the Mac is sized as 2 CPUs, 4 GB RAM, and 80 GB disk.  The disk space only needs to be large enough to unpack the packages and hold the install base.  Although an agent relay is not needed for this simple setup it is good practice to install one. On AWS I have installed one agent relay on a RHEL 7.3 instance with flavor t2.micro and I have enabled TCP port forwarding in my home router for ports 8080, 8443, and 7918 to allow communication between the UCD server and the agent relay. Alternatively, if you have the resources, you can install the agent relay on your home system in the same VM in which you are hosting BPD. If you do so, open ports 20080, 20081, and 7916 in your firewall instead of 8080, 8081, and 7918. The virtual image below portrays a provisioned instance from the Blueprint Designer and how it communicates with the agent relay and thus the UCD Server.Arnone UCD blog 3

Option 2 – Home Setup 2

Another option for a home setup if you have enough CPU and memory is to place everything on one RHEL 7.3 VM.   The size for the VM should be at least 4 CPU and 6 GB RAM (8 would be better). It is important to install BPD on ports that do not conflict with UCD such as 8444 and 8081.  Further, the default derby database is not an option when UCD and BPD are installed on the same machine.  UCD and BPD support a number of third party databases but perhaps best thing to do, to save some resources, is to use the MariaDB database that is installed as part of the Identity service and Heat engine.  For UCD, configure the connection using the MySQL Connector and for BPD configure the connection using the MariaDB Connector.  Instructions for how to do this are provided in the UCD Knowledge Center at:


Option 3 – Using a Cloud Setup

If you were willing to pay for the service, a third option for an installation would be to install UCD and BPD in Amazon (or some other cloud).  With a cloud environment, you can follow Option 2 above or you can separate all of the individual parts – UCD, BPD, the Openstack Services, the database, and the agent relay.  With such a setup you are nearing a production topology.

Additional Options

For more options concerning UCD and BPD installation environments for production, high availability, and disaster recovery refer to the UCD Knowledge Center at:




About the Author

David J. Arnone

is an ALM and DevOps Architect specializing in IBM CLM and UrbanCode Deploy solutions and services. As a certified Rational CLM Architect, David joined Zilker Technology in January, 2017 and is part of the growing Zilker DevOps practice team.



Don't miss out! Get updates on new webcasts, events, and blogs.