Impact of server rename on the Engineering Workflow Management application

Restart all clients

After the server administrator renames a server, you must restart any client that connects to that server. If you leave a client open during the server rename operation, it is possible that artifacts that include the previous server URL could be stored in the repository.

Use 4.0 or later clients and build engines for production scenarios

For the pilot-to-production scenario and the production-to-production scenario, all user clients and build engines must be at version 4.0 or later prior to the rename operation.

Use staging workspace for test staging environment using production data scenario

For the preparing a test staging environment using production data scenario, always use a staging workspace for connecting to the staging server. Do not re-use an existing production workspace to connect to the staging server.

Check in changes into repository workspace before renaming server

If you use the IBM® Engineering Workflow Management source control, check in all of your changes into your repository workspace before you rename the server. This ensures that your changes are safely stored in the repository and no changes are lost during the rename operation.

Deactivate non-Jazz Build Engine (JBE) build engines

Before performing a server rename operation, deactivate any build engines of type Build Forge, Build Agent, and Hudson/Jenkins to prevent builds from running on these external systems until you verify the engine connection details. After the rename operation, verify the connection details for these build engines. Verification is needed especially in the preparing a test staging environment using production data scenario to prevent builds in the staging environment from running on production build servers. Verification might be needed for other scenarios, depending on whether the target build servers are moving with the renamed CCM server. If the connection details are correct after the rename operation, you can reactivate the engines if appropriate for your scenario. Other options are to leave these build engines deactivated; change their connection details to something invalid (if this was not done in the mapping); or delete them.

Because the JBE process is run with a given Engineering Workflow Management server URL, it does not have the same issue as non-JBE build engines. Production JBE instances will continue to run against the production CCM server. However, cross-contamination from the staging environment to the production environment might be possible if JBE instances are run against the staging environment, and build scripts or build properties refer to production servers. Review for such cases before you perform the server rename operation.

Update server URLs in work item templates

The server rename operation does not update the server URL in work item templates. For any work item templates that include the server URL in a field, you must change the URL to the one used by the renamed server.

Specify full URI of renamed server in full-text searches

To search for work items that contain the URI of the renamed server, you must specify the full URI; searching for URI fragments is not supported.

Query limitations

In a work item query, you cannot search for a renamed server URI in a small or medium string/html attribute.

Plan limitations

URLs within the Notes (wiki) tab of a plan do not get renamed as a result of the server rename operation.