Impact of Server Rename and Integrated Products (Version 4.0 and 4.0.0.x)

Note:This article is outdated and is replaced by Impact of Server Rename and Integrated Products (Version 4.0.1) in the Deployment wiki. In the future, all deployment guidance and best practices will be published in the Deployment wiki rather than as Jazz.net articles.

In version 4 of the Rational solution for Collaborative Lifecycle Management, it is possible to rename one or more server public URLs, for a limited set of scenarios, using the Server Rename feature. Changing server URLs is a complex and potentially disruptive operation due to the linkages that may exist between multiple disparate products, as well as 3rd party applications. Prior to attempting a rename, it is imperative that you understand the supported scenarios, the impact of performing a rename for your deployment scenario, and the server rename procedure itself. If you haven’t already done so, you should review the guidance article on jazz.net.

As noted in the above article and the product documentation, support for server rename is initially limited to two scenarios in version 4.0 and 4.0.0.x: moving a pilot deployment to production, and copying a production deployment for the purpose of creating a staging test environment. In version 4.0.1, we have added support for renaming the production environment and support for many of the integrations that are not supported in version 4.0. (For details, see Impact of Server Rename and Integrated Products (Version 4.0.1). Even for the scenarios supported in version 4.0, it is important that you understand the other products that you integrate with:

  • If you are planning to move a pilot deployment to full production and your deployment includes unsupported integrations, do not perform a server rename. Your integrations will break.
  • If you are setting up a test staging environment, you must create “dummy mappings” in the mapping file for the URLs of any additional integrations in your deployment. This is to prevent contamination or linkages from the staging environment into production.

Rational CLM Product Integrations

For the pilot to production scenario, support is limited to the following integrations:

  • Rational Reporting for Development Intelligence
  • Rational ClearQuest Integrations
  • Rational ClearCase Integrations
As one might expect, not all  products are built on the same technologies and architectures, and they do not all ship on the same release schedule as CLM. When new integrations are supported, the actions needed to repair the integration points will vary by product but may include the following:
  • Changing repository connections to point to new servers
  • Editing configuration files with new server names and restarting software
  • Using an administration GUI to change server URLs
  • Running a tool to change URL references in product data repositories (some downtime would usually be required)

The following tables list the non-CLM product integrations that would be impacted by a CLM server rename. Use these tables to assess the impact on your planned server rename. We are working hard to ensure that each integration is thoroughly tested by IBM before we give it our seal of approval and support. Updated tables applicable to CLM 4.0.1 are included in the 4.0.1 version of this article at Version 4.0.1.

Table 1. Supported non-CLM products that would be impacted by a server rename of the JTS and CLM applications
Non-CLM product Integrates With Support Statement and Documentation

Rational ClearCase v7.1.x, v7.1.2.x and v8.0.0.x

ClearCase Synchronizer and Importer

RTC

Stop and start the synchronization build engine after server rename.

See Updating the Rational ClearCase synchronization environment after renaming the Jazz Team Server for details.

Rational ClearCase v7.1.1.x, v7.1.2.x, and v8.0.0.03 or higher

ClearCase Bridge

RTC

Requires execution of a ClearCase tool that is used to administer RTC task URIs for certain situations.

See Updating RTC task links after a CLM server rename operation for details.

Rational ClearQuest v7.1.x, v7.1.2.x and v8.0.0.x

ClearQuest Synchronizer

RTC, RQM

Requires performing a set of steps to update the synchronizer properties file and force a resynchronization from RTC/RQM to ClearQuest to repair broken links after a CLM server renaming operation.

See Preparing the ClearQuest Synchronizer for renaming Jazz Team Server for details.

Rational ClearQuest v7.1.2.07 or higher and v8.0.0.03 or higher

ClearQuest Bridge

RTC, RQM

RRC

Requires running a tool several times that updates Jazz Team Server public URI artifact links for the Rational solution for CLM. Specifically, the tool updates the URIs that are stored in IBM Rational ClearQuest Web server configuration files. The tool also updates the URIs that are stored in OSLCLink records in the ClearQuest user database.

See Remapping URIs after renaming a CLM server for details.

 

 
Table 2. Unsupported Non-CLM products that would be impacted by a server rename of the JTS and CLM applications
Non-CLM product Integrates With Support Statement and Documentation
Rational AppScan Source 8.5 & Security AppScan Source 8.6
RTC
Not yet supported for Server Rename

Security AppScan Enterprise 8.6

RQM
RTC

Not yet supported for Server Rename
Not yet supported for Server Rename

Rational Build Forge Enterprise Edition 7.1.1.4, 7.1.2
Rational Build Forge Enterprise Plus Edition 7.1.1.4, 7.1.2
Rational Build Forge Standard Edition 7.1.1.4, 7.1.2
RQM
RTC
Not yet supported for Server Rename
Not yet supported for Server Rename
Rational Change 5.3.0.3
Rational Change 5.3.0.3 with Rational Synchronization Server 1.4.0.4
RQM
RTC
Not yet supported for Server Rename
Not yet supported for Server Rename

Rational Synergy 7.2

RTC

Not yet supported for server rename
Rational DOORS 9.3, 9.4
Rational DOORS Web Access 1.4.0.0, 1.5.0.0
RQM
RTC
Not yet supported for Server Rename
Not yet supported for Server Rename
Eclipse Lyo RQM
RTC
Not yet supported for Server Rename
Rational Business Developer 8.5
Rational Developer for Power System Software 8.5
Rational Developer for System z 8.5
Rational Programming Patterns (future release)
RTC Not yet supported for server rename
Rational Focal Point 6.5.2 RRC
RTC
Not yet supported for server rename
Not yet supported for server rename
Git SCM 1.6.4.2 RTC
Not yet supported for server rename
Hudson 2.2 and
Jenkins 1.4.5.8
RTC
Not yet supported for server rename
Rational Insight 1.1.1 RRC
RQM
RTC
Not yet supported for server rename
JIRA 4.4.1
RTC
Not yet supported for server rename
Rational Application Developer for WebSphere Software 8.5 RTC
Not yet supported for server rename
Rational Asset Manager Enterprise Edition 7.5.1
Rational Asset Manager Standard Edition 7.5.1
RRC
RQM
RTC
Not yet supported for server rename
Not yet supported for server rename
Not yet supported for server rename
Rational Software Architect 8.5
Rational Software Architect RealTime Edition 8.5
Rational Software Architect for WebSphere Software 8.5
RTC
Not yet supported for server rename
Rational RequisitePro 7.1.3 RQM
Not yet supported for server rename
Rational Rhapsody 7.6, 8.0
RQM
Not yet supported for server rename
Rational Software Architect Design Manager (beta)
Rational Rhapsody Design Manager (beta)
RRC
RQM
RTC
Not yet supported for server rename
Rational Method Composer 7.5.2 RTC
Not yet supported for server rename
Rational Publishing Engine 1.1.2.2 and
Rational Reporting for Document Generation 1.1.2.2
RRC
RQM
RTC
Not yet supported for server rename
Not yet supported for server rename
Not yet supported for server rename
Rational Connector for SAP Solution Manager 4.0 RRC
RQM
RTC
Not yet supported for server rename
Not yet supported for server rename
Not yet supported for server rename
Rational Functional Tester 8.2.2 RQM
RTC
Not yet supported for server rename
Not yet supported for server rename
Rational Performance Tester 8.2.1 and
Rational Service Tester for SOA Quality 8.2.1
RQM
Not yet supported for server rename
Rational Robot 7.0.3 RQM
Not yet supported for server rename
Rational Test RealTime 8.0 RQM
RTC
Not yet supported for server rename
Not yet supported for server rename

About the authors

Ritchie Schacher is a technical manager with the Jazz Foundation project. He’s been working on Jazz technology and Jazz-based products since the inception of Jazz. He can be contacted at schacher@us.ibm.com.

Deborah Weil is the release manager for the Collaborative ALM Products. She’s been working with the teams since 2009. She can be contacted at deborah.weil@us.ibm.com.


Feedback
Was this information helpful? Yes No 4 people rated this as helpful.