Rather than change the host name when you perform a server rename, you can change just
the context root.
Before you begin
- To perform a server rename, you must obtain a feature key file from IBM Software Support. When
you contact IBM Support, mention that you are requesting a
server rename feature key file
.
The key file is named ImportURLMappings.activate. Copy the file to the
JazzInstallDir/server/conf directory for the applications
that you will rename. The key is only needed to execute the repotools
importURLMappings command.
- Before you proceed with the rename, check that the required version of the Engineering Lifecycle Management software
is installed and that your environment meets the criteria for a server rename. See Software version requirements and Supported scenarios for using server rename for details.
For a case study about changing the context root, see Case study: Server rename.
About this task
Although it is most common to change the host name during a server rename, it is also possible to
change the context root. Doing so requires a new server installation that mirrors the old
installation, but with new context roots. Make sure that you generate a mapping file against the
original server, as detailed in Preparing the mapping file. Change the necessary
context roots in this mapping file. For more information about changing the context root, see Case
study: server rename.
Procedure
- Use Installation Manager to install a separate, Jazz® Team Server.
When you get to the Context Root Options panel, click Select custom
context root values and enter your custom context root values. Even if you are renaming
only the context root for a single application, you must install all of the applications that you
intend to run. For further installation instructions, see Installing the IBM Engineering Lifecycle Management by using IBM Installation Manager.
- Copy the following configuration files from the old installation
server/conf/oldContextRoot to the new installation
server/conf/newContextRoot. Copy all of these configuration files, even if you
are not renaming a particular application's context root.
Note: If you changed the context roots in the old installation, replace these default examples with
your own customized versions.
- From server/conf/jts, copy: teamserver.properties and
the indices directory.
- From server/conf/ccm, copy teamserver.properties and
the indices directory.
- From server/conf/dcc, copy: teamserver.properties and
the indices directory.
- From server/conf/gc, copy: teamserver.properties and
the indices directory.
- From server/conf/qm, copy: teamserver.properties and
the indices directory.
- From server/conf/relm, copy: teamserver.properties and
the indices directory.
- From server/conf/rm, copy: teamserver.properties and
the indices directory.
- From server/conf/rs, copy: app.properties.
Note: The Lifecycle Query Engine (LQE) and Link Index Provider (LDX) do not support changing the
context root.
- Ensure that the
following database properties in the teamserver.properties files for JTS, CCM,
DCC, GC, QM, RELM, and RM are pointed at the correct database
locations.
Note: The Lifecycle Query Engine (LQE) and Link Index Provider (LDX) do not support changing the
context root.
- com.ibm.team.repository.db.jdbc.location
- com.ibm.team.datawarehouse.db.jdbc.location
Finally, fix the relative text indices location to use the new location. Be sure to include the
new context root in the
path.
com.ibm.team.fulltext.indexLocation=conf/new_context_root/indices/workitemindex
- Optional: Update the name of all renamed applications.
- Log in to the Jazz Team Server
admin UI and go to the .
- Click Edit and rename each application to its new context root
or to any other name of your choosing.
What to do next
Proceed with configuring your deployment database. For more
information, see Configuring your deployment after a database server move.