E
dit
A
ttach
P
rintable
r6 - 2019-06-27 - 12:32:08 -
RalphSchoon
You are here:
TWiki
>
Deployment Web
>
DeploymentInstallingUpgradingAndMigrating
>
RegisterApplicationOptions
<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 [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/c_configuring_the_server.html][register applications to the JTS in the initial deployment]] and how to [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.repository.web.admin.doc/topics/t_register.html][add and register applications to an existing deployment]]. ---+ Manual setup The IBM Engineering Lifecycle Management Solution provides capabilities to perform a [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/c_configuring_the_server.html][manual install and setup of an ELM deployment]]. It also provides capabilities to [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.repository.web.admin.doc/topics/t_register.html][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. The top of the page will show a prompt with a link to the setup wizard for the application. To finalize the registration follow the link and execute the setup wizard for the application. ---++ Manual setup best practices * Use the *Add* button in the *Registered Applications* page of the JTS admin web UI to register a new application to an existing deployment. Do not run the jts/setup again to register new applications to an existing deployment. ---+ Automation for setup The IBM Engineering Lifecycle Management Solution provides capabilities to automate deploying the ELM solutions. It allows to [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/r_repotools_registerapp.html][automate the initial install and setup]] of ELM deployments. It also allows to automate installing and [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/r_repotools_setup.html][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 deployment. This command was introduced in version 6.0.1. ---++ Automation 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 existing ELM deployment. * Since 6.0.1 repotools -setup is meant to be only ever run once to setup the initial deployment of a JTS and associated applications. Do not run repotools -setup again. Especially do not run repotools -setup again subsequently to register new applications to an existing ELM deployment. Running this command again can cause undesired results. ---+ Additional information ---+++++!! Related topics: * [[StandardTopologiesOverview][Standard topologies]] * [[ServerRename][Server rename]] ---+++++!! External links: * [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/c_configuring_the_server.html][Initial setup and configuring the server]] * [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.repository.web.admin.doc/topics/t_register.html][Register applications to an existing deployment]]. * [[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]] * [[https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/interactive_guides.html][Interactive Guides for installing, upgrading, and adding applications]] <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r6
<
r5
<
r4
<
r3
<
r2
|
M
ore topic actions
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
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
.