r18 - 2017-07-28 - 21:38:17 - KenTessierYou are here: TWiki >  Deployment Web > DeploymentInstallingUpgradingAndMigrating > IBMQuickDeployerOld > IBMQuickDeployerMappingAndTaggingRulesOld

IBM Quick Deployer mapping and tagging rules

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

IBM UrbanCode Deploy (UCD) supports a mapping system and a tagging system. IBM Quick Deployer (QD) makes use of these to ensure it only installs and executes the required scripting and middleware on the individual servers in the environment.

To ensure QD has all the required components available follow the instructions in topic import QD application.

To ensure QD has all the required tags available follow the instructions in topic create agent tags.

By following this topic it ensures that when you create a QD Environment all the required tags are available and that all the required components are mapped. Mapping and tagging brings flexibility, which allows the user to create environments with more servers and different application distributions than the 4 node CLM topology described in the UCD Environment topic. Tagging rules are required to manage this flexibility and to ensure that when you run the Install Applications process to deploy your system you do not waste time and resources. In the early stage of execution QD will test the tagging rules and fail if they are not met. This topic explains these rules.

Mapping rules

In a QD environment there are 3 types of server each requiring a different set of mapped components
  • database (DB)
    • Rational_QD_Database_60x
    • Rational_QD_SystemPre-Requisite_60x
  • reverse proxy (IHS)
    • Rational_QD_ApplicationServer_60x
    • Rational_QD_InstallationManager_60x
    • Rational_QD_SystemPre-Requisite_60x
  • application (WAS & "app")
    • Rational_QD_Application_60x
    • Rational_QD_ApplicationServer_60x
    • Rational_QD_InstallationManager_60x
    • Rational_QD_SystemPre-Requisite_60x

Tagging rules

  1. QD supports a fixed set of tags [WAS, IHS, DB, JTS, CCM, QM, RM, RS, DCC, RELM, LDX, GC, LQE, DM]
  2. QD supports the following application tags [JTS, CCM, QM, RM, RS, DCC, RELM, LDX, GC, LQE, DM]
  3. there can only be one instance of any application tag in the QD environment
  4. the environment must contain one and only one IHS tagged agent and it cannot contain any other tags
  5. the environment must contain one and only one DB tagged agent and it cannot contain any other tags
  6. the environment must contain at least one WAS tagged agent
  7. the WAS tag must be present on any agent containing an application tag
  8. there must be at least one application tag on every WAS agent in the environment
  9. there must be a JTS tag on one of the WAS agents in the environment
  10. if the LDX tag is present it must be on the same agent as the JTS tag
  11. if Configuration Management is going to be enabled then the environment must contain the GC and LDX application tags

Example environment

Here is an example of a 3 server environment that meets the mapping and tagging rules

system meeting rules

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: r18 < r17 < r16 < r15 < r14 | More topic actions
Deployment.IBMQuickDeployerMappingAndTaggingRulesOld moved from Deployment.IBMQuickDeployerMappingAndTaggingRules on 2017-07-28 - 20:18 by KenTessier -
 
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