RegisterApplicationOptions < Deployment

<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 register applications to ELM deployments. <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"> 
%DKGRAY% Authors: [[Main.KrzysztofKazmierczyk][Krzysztof Kazmierczyk]], [[Main.RalphSchoon][Ralph Schoon]] <br>
Build basis: ELM 4.0 and later

%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>
The IBM Engineering Lifecycle Management Solutions (ELM) can be deployed in different [[StandardTopologiesOverview][topologies]]. ELM deployments consist of a Jazz Team Server (JTS) and applications registered to the JTS. This document explains how to register applications to the JTS in the initial deployment and how to add applications to an existing deployment.

---++ Manual setup
The IBM Engineering Lifecycle Management Solution provides capabilities to perform a manual install and setup of an ELM deployment. It also provides capabilities to manually register new applications to an existing deployment. The following options are available when performing a manual install and setup.

---+++ Initial setup of a deployment

During the initial manual install process of a deployment the available applications can be discovered and registered in the *Register Applications* step of the initial JTS setup. 

---+++ Adding an application to an existing deployment

To manually register a new application to an existing deployment use the *Add* button in the *Registered Applications* page of the JTS admin web UI.
  
---++ Automation for setup

The IBM Engineering Lifecycle Management Solution provides capabilities to automate deploying the ELM solutions. It allows to automate the initial install and setup of ELM deployments. It also allows to automate installing and registering new applications to an existing deployment. 

---+++ Available commands

The following commands are available.

---++++ repotools -setup 

This command is used to setup the initial deployment of a JTS and to register the applications initially available. This command was introduced in version 4.0.

---++++ repotools -registerApp 

This command is used to register new applications to an ELM instance. This command was introduced in version 6.0.1.

---++ Best Practices

  * Repotools -registerApp was introduced in version 6.0.1 to separate the registration of new applications to an existing deployment from the initial setup of a deployment. Since 6.0.1 repotools -registerApp is the only command that should be used to register a new application to an ELM instance. 

  * Since 6.0.1 repotools -setup is meant to be only ever run once to setup the initial deployment a JTS and associated applications. Do not run repotools -setup again. Especially do not run repotools -setup again subsequently to register new applications. Running this command again can cause undesired results.  

---+++++!! Related topics: 
   * [[ServerRename][Server rename]]

---+++++!! External links:          

   * [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/r_repotools_registerapp.html][Repotools -registerApp command]]
   * [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/r_repotools_setup.html][Repotools -setup command]]


<sticky></div></sticky>

This topic: Deployment > WebHome > DeploymentInstallingUpgradingAndMigrating > RegisterApplicationOptions

History: r3 - 2019-06-26 - 07:54:14 - Main.rschoon

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.