r26 - 2017-08-31 - 20:53:05 - ThomasPiccoliYou are here: TWiki >  Deployment Web > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployer > IBMQuickDeployerSetupAndRun > IBMQuickDeployerEnvironmentConstruction

IBM Quick Deployer environment construction

Authors: ThomasPiccoli, KennethThomson, JenniferLiu, KenTessier, ClareCarty
Build basis: CLM 6.0, CLM 6.0.x, CE 6.0.x

This topic guides you through creating and populating the UCD environment to represent the system you are going to install. By following this topic you will

  • create the environment
  • attach agents to connect UCD to each target server
  • map UCD components to each agent
  • add tags to each agent
By mapping components and adding tags to the environment Quick Deployer will only install and execute the required scripting and middleware on the individual servers in the environment.

This is the simplest method for creating an environment in UCD. However, being the simplest also means that it is the least dynamic method. UCD supports many other methods for creating and managing environments, which are not be described here. You might want to review of the options described in the Knowledge Center for the version of UCD that you are running. You can find the version by navigating the Help link from the UCD web UI.

Environment construction (overview)

You can create environments with different application distributions than the example below depicts. The rules for how to control application distribution are described on the mapping and tagging rules wiki page. The general process is described in this section and more detailed example follows.
  1. Open the Resource Tree tab on the Resources page and select Create Top-Level Group.
    Provide a name for the resource and press Save.
  2. Open application Rational_QD_60x and select Create Environment.
    Provide a name for the environment and press Save.
  3. Open the environment and add the top level resource created above
  4. Add the UCD agents that were installed on the target VMs, as described in the system requirements, to the base resource just added to the environment.
    Instructions for installing agents on the target VMs can be found on the UCD Installing Agents online documentation.
    If you are using your own Database Server ensure that a UCD agent is also installed on it.
  5. Add Tags and map components to the agents.

Environment construction (example)

  1. To continue creating an environment as described here you must have already deployed the VMs that meet the requirements described on the System Requirements page. Note: all the VMs in an environment must be running the same operating system, either all RHEL or all Windows.
  2. Open the Resource Tree tab on the Resources page and select Create Top-Level Group.
    Provide a name for the resource and press Save.

    create resource

  3. Open application Rational_QD_60x and select Create Environment.
    Provide a name for the environment and press Save.

    create top level group



    create environment

  4. Open the environment and add the top level resource created above

    add top level resource

  5. Add the 4 UCD agents that were installed on the target VMs, as described in the system requirements, to the base resource just added to the current environment above. Instructions for installing agents on the target VMs can be found on the UCD Installing Agents online documentation. If you are using your own Database Server ensure that a UCD agent is also installed on it.

    add agents

  6. Map components to the agents as follows: Select a resource, then click Actions > Add Component. If you are using your own database server ensure that the correct components are mapped to it.

    map components

  7. Add tags to the agents as shown below. If you're installing Continuous Engineering make sure to add the DM tag to one of the WAS servers. In QD 1.3 the DB2 tag has been changed to DB.

    add tags



    all tags added

Miscellaneous

Notes:

  • Throughout the IBM Quick Deployer wiki the screen captures are for reference only.
    In some cases if the functionality they display has not changed in the latest release they will be from a previous release

Related topics:

External links:

Additional contributors: MichelleCrane, NathanBak, ChristianLopez

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r26 < r25 < r24 < r23 < r22 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the 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.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project