Register Application options

Authors: KrzysztofKazmierczyk, RalphSchoon

The IBM Engineering Lifecycle Management applications provide different options of registering or reregistering applications in the common scenarios server rename, upgrades and installing a new application. This document shows the advantages and disadvantages as well as the best practices for using the different options to avoid issues.

Available options

repotools -setup (all applications in response file)

Advantages

• The response file can be reused for different scenarios (new installation, server rename, installing additional application)

Disadvantages

• Take the longest time as runs the setup (the setup rerun for all applications)
• Fails if the setup fails at one of the steps even if this step is not necessary (e.g. can fail on ccm setup for server rename scenario)

repotools -setup (only one application in response file)

Advantages

• Executes the setup only for applications which need this
• Response file can be reused for particular scenario (e.g. we can create response file for server rename scenario for all servers)
• Faster than repotools -setup with all parameters

repotools -registerApp command

Advantages

• The simplest and the easiest command to run from server perspective
• As executes only required stuff, it is the least error prone

Disadvantages

• Does not provide password encryption for teamserver.properties
• Not recommended for reregistering (cannot be used for server rename)

Best practices

• For new installation the only option is run repotools –setup with all applications in response file (option 1).
• For reregistering LQE/LEX and other applications after server rename the recommended way is to put only these applications in response file (option 2).
• For registering new applications added to CLM portfolio, like it was with /am recently, the recommended way is the third option.

Related topics:

• Server rename

External links:

• Repotools -registerApp command
• Repotools -setup command