Rational Team Concert 2.x has a single, monolithic WAR file that has the Jazz Platform and Rational Team Concert application. Other related products such as Rational Quality Manager (RQM) and Rational Requirements Composer (RRC) also followed the same architecture, which led to longer download times and large file sizes. With Rational Team Concert 3.0, the product functionality is decomposed into the Jazz Team Server (JTS) and Change and Configuration Management (CCM) application.
A Jazz Team Server provides basic services that enable a group of applications to work together as a single logical server. The following domain-specific applications are defined as a part of the new architecture:
The Change and Configuration Management (CCM) application delivers capabilities for Change Management (work items), Configuration Management (SCM), planning, and automation/build.
The Requirements Management (RM) application delivers capabilities for capturing, managing, and tracing requirements throughout the development lifecycle.
The Quality Management (QM) application delivers capabilities for test management, including test planning, creation, and execution.
The upgrade process splits the version 2.x Rational Team Concert server into two version 3.0 applications (the Jazz Team Server and the Change and Configuration Management application). The server and application are deployed separately to an application server such as WebSphere.
The following table summarizes the deployed context roots in version 2 with that of a new installation of version 3 and an upgrade from version 2 to version 3. Note that an upgrade from version 1 is not supported. If you want to upgrade from version 1, then you need to first upgrade from version 1 to version 2, and then upgrade to version 3.
Context Root for Rational Team Concert 2.x versus Rational Team Concert 3.0
|
Product/application |
Rational team concert/CCM |
|---|---|
|
2.x |
/jazz |
|
3.0 – New Installation |
/jts, /ccm |
|
3.0 – Migration |
/jts, /jazz |
After Rational Team Concert 3.0 is downloaded and installed via web installer, the start menu looks like the next screenshot. Notice that the Jazz Team Server and IBM Rational Team Concert are listed as two separate menu items.
The next step is to start the Jazz Team Server and configure it. Click Start Jazz Team Server and wait until the server is started. Go to https://localhost:9443/jts/setup URL and set up the Jazz Team Server. As seen in the next screenshot, the Jazz Team Server recognizes the ccm application and is registered here:
At each configuration step, you can test the configuration parameters with the help of the Test button. Once the setup is successful, navigate to the URL that you provided at the time of setup (for example, https://localhost:9443/jts). You should be able to log in with the administrative user you created during setup. The ADMIN user name may no longer be valid depending on the options you selected during the setup.
Jazz Team Server application lets you to do server administration, user management, and application administration. As you can see in the following screenshot, the Jazz Team Server recognizes the Change and Configuration Management application:
In Rational Team Concert version 3.0, the Change and Configuration Management application is installed on a separate root called ccm. If Rational Team Concert is migrated from 2.x, then the root will be jazz. Navigate to the ccm application (for example, https://localhost:9443/ccm) to access the project area, users, and project templates. You can do the CCM application administration right from the same UI and see the associated Jazz Team Server as in the next screenshot:
In Rational Team Concert 2.x, the Jazz Platform and Rational Team Concert modules are installed on the same application root /jazz. From the previous steps, we have seen that Rational Team Concert 3.0 has two separate applications for Jazz Team Server (with context root /jts) and Change and Configuration Management (with context root /ccm or /jazz). If you are doing a migration from 2.x to 3.0, a detailed article is available at http://jazz.net/library/article/524.