(r2) IBMQuickDeployerExampleDeployFromBlueprint < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

~~EditAttach~~Printable

TWiki > Deployment Web > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployer > IBMQuickDeployerSetupAndRun > IBMQuickDeployerExampleDeployFromBlueprint

Revision 2 - 2017-12-07 - 19:49:04 - Main.ccarty

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! How to use the topology blueprints included with Quick Deployer <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> 
%DKGRAY% Authors: Main.ClareCarty<br>
Build basis: CE/CLM 6.0.4+
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

Quick Deployer ships with a set of sample blueprints which are pre-set templates that distribute the components and application tabs across the available nodes based on the [[https://jazz.net/wiki/bin/view/Deployment/RecommendedALMDeploymentTopologies6][Recommended ALM 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. 

<img src="%ATTACHURLPATH%/resource_temp.png" alt="resource_temp.png" width="800" height="510" />

Select one of the templates and drill down to explore in more detail. For example, the Departmental Continuous Engineering template:-

<img src="%ATTACHURLPATH%/rt_nodes.png" alt="rt_nodes.png" width="799" height="589" />

You can select *Expand all* to see more detail.

<img src="%ATTACHURLPATH%/agent_prot_tags.png" alt="agent_prot_tags.png" width="1173" height="708" />

As you can see, the applications are distributed over 5 nodes or VMs; a database node, an ihs or reverse proxy node and three Application Server nodes denoted as os-1, -2 and -3. 

---++ How to leverage the Blueprints

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

Taking a slice from the example above:-

<img src="%ATTACHURLPATH%/edit_agent_prot.png" alt="edit_agent_prot.png" width="995" height="87" />

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,

<img src="%ATTACHURLPATH%/ex_agent_prot.png" alt="ex_agent_prot.png" width="513" height="267" />

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

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

     <img src="%ATTACHURLPATH%/ex_agent_prot2.png" alt="ex_agent_prot2.png" width="489" height="245" />

  
     <img src="%ATTACHURLPATH%/ex_agent_prot3.png" alt="ex_agent_prot3.png" width="499" height="249" />

  
     <img src="%ATTACHURLPATH%/ex_agent_prot4.png" alt="ex_agent_prot4.png" width="503" height="249" />

  
     <img src="%ATTACHURLPATH%/ex_agent_prot5.png" alt="ex_agent_prot5.png" width="505" height="249" />

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

The agents are installed on target VMs using the client from the appropriate UCD server. They will automatically come online if configured to do so. 

<img src="%ATTACHURLPATH%/agents.png" alt="agents.png" width="1070" height="339" />

*Note* that you can change the naming convention in your agent prototypes if you want and name your environment and agents accordingly. 



---++ Creating the environment using the blueprint

When you create the environment, you use the environment name already selected, the blueprint you want to use and the default resource group which contains your agents.

<img src="%ATTACHURLPATH%/create_bp_env.png" alt="create_bp_env.png" width="692" height="739" />

 <img src="%ATTACHURLPATH%/env_with_blueprint.png" alt="env_with_blueprint.png" width="1197" height="666" />

By using the naming convention and the blueprint, the environment and the agents are automatically connected and everything mapped automatically for deployment. 

You can then run the applications processes to install your CE/CLM applications and the applications will be laid down on the nodes according to the topology defined in the blueprint. 

%INCLUDE{"IBMQuickDeployerInsertMiscellaneous"}%

<sticky></div></sticky>

Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.