The IBM Engineering Lifecycle Management Solutions (ELM) can be deployed in different
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.
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 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.
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 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:
External links: