Topic title (use a lowercase style, which is known as "sentence-style" capitalization)

Quick Deployer ships with a set of sample blueprints which are pre-set templates based on the CE/CLM Recommended Topologies. This page describes a method for using Quick Deployer to install CE/CLM environments using these blueprints.

Standard Topology Blueprints installed by Quick Deployer

Once Quick Deployer is installed, the user can select the Resources tab and explore the available Resource Templates.

Select one of the templates and drill down to explore in more detail.

In the example above, The Departmental Continuous Engineering template is shown. You can Expand all to see more detail.

As you can see, the applications are distributed over 5 nodes or VMs three of which are Application Server environments.

How to leverage the Blueprints

The blueprints can be leveraged by connecting the agents - which are installed on the target VMs - to the application environment using a naming convention set up in the Agent prototype.

Taking a slice from the example above:-

If you edit the agent prototype for each node it will show the naming convention to be used for the target VM names. For instance,

Here the agent name for the DB server must include the environment name and end in '-db'. So if the environment is going to be called win16qd21, the DB server name should be something like win16qd21-db

Similarly, the agent prototypes for the IHS and other nodes:-

Again if we use win16qd21 as our environment name, this nets out to agent names as follows:-

• db: win16qd21-db
• ihs: win16qd21-ihs
• node 1: win16qd21-os-1
• node 2: win16qd21-os-2
• node 3: win16qd21-os-3

If the agents are installed on target VMs using the client from the appropriate UCD server, then they will automatically come online.

VM naming convention

Environment naming convention

Heading 1

Related topics: Deployment web home, Deployment web home

External links:

• IBM

Additional contributors: TWikiUser, TWikiUser