Rather than change the host name when you perform a server
rename, you can change just the context root.
Before you begin
- To enable server rename you must obtain a feature key file, called ImportURLMappings.activate,
from IBM® Software Support. You
must then copy the file to the server directory.
When you contact IBM support,
be sure to mention that you are requesting a Server Rename Feature
Key File.
- For a case study about changing the context root, see https://jazz.net/library/article/1148.
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, version
4 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. .
- 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/admin, copy admin.properties and friends.rdf.
- From server/conf/jts, copy: teamserver.properties and
the indices directory.
- From server/conf/relm, copy teamserver.properties and
the indices directory.
- From server/conf/lqe, copy: teamserver.properties and
the indices directory.
- From server/conf/sparql, copy fronting.properties and
the indices directory.
- Ensure that the following database properties in the teamserver.properties files
are pointed at the correct database locations.
- 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
- If you are using WebSphere® Application
Server, uninstall the applications from the old installation and install
them in the new installation. Also, update JAZZ_HOME to point to
the new installation.
- If you are using the Tomcat user registry, copy the OldJazzInstallDir/server/tomcat/conf/tomcat-users.xml file
to the NewJazzInstallLocation/server/tomcat/conf directory,
to sync the existing users.
- Follow the standard rename instructions, starting at the importURLMappings step.
You must run the importURLMappings command against
the new installation using the generated mapping file from the old
installation. Do not perform any additional steps against the old
installation, which serves only as a backup until you are sure that
the new installation is working correctly.
Note: It is
possible that the old application context root will appear in the
server rename status UI. The UI displays the registered application
name. By default, the name is the context root. Therefore, if you
never changed the name from the default, the old context root is shown.
- 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.