Installing the Rational solution for Collaborative Lifecycle Management by using IBM Installation Manager

You can install the Rational solution for Collaborative Lifecycle Management (CLM) in two ways. Both methods involve IBM® Installation Manager.

Before you begin

Restriction: You cannot install Jazz Team Server on the IBM i or z/OS® operating systems by using Installation Manager.

About this task

The first installation method is a web-based installation that includes a smaller download and connects to the Internet during the installation to get the repository files. If you must install the server in an environment without Internet access, use the second installation method: download and extract the repository files to a local computer to install the server.

Note: For instructions to install the IBM Rational® Team Concert Eclipse client, see Installing Rational Team Concert clients.

The launchpad program includes links to install Jazz Team Server and the Change and Configuration Management (CCM), Quality Management (QM), and Requirements Management (RM) applications. The launchpad also includes links to install the IDE clients for Rational Team Concert, a build system toolkit, the Rational ClearCase® and Rational ClearQuest® Synchronizers, and the Microsoft Windows shell extensions. By default, the server includes a Derby database that is limited to 10 users. If you use a production environment or want to enable more users, install other supported databases, such as IBM DB2®, Oracle, or SQL Server. To obtain programs such as DB2, IBM WebSphere Application Server, and Rational Reporting for Development Intelligence, in the launchpad, click the Optional Programs link.

Note: You install the product documentation with Jazz Team Server by using the clmhelp.war file. For any application that is deployed on a different server, you must configure the location of the clmhelp.war file, as described in Configuring the location of the help in a distributed environment. In a WebSphere environment, the clmhelp.war file must be explicitly deployed, as described in Deploying applications for the Rational solution for Collaborative Lifecycle Management on WebSphere Application Server.

Procedure

  1. Download either the web installer or the Installation Manager repository package for your platform.
    Tip: To improve download performance and reliability, see Download tips.
  2. Extract the .zip file to a temporary directory. To avoid issues, do not use long paths and directories that have spaces in their names.
  3. Install by using either the web installer or the Installation Manager repository package.
    • To install by using the web installer:
      1. Open the directory that you extracted the .zip file to, and run the launchpad executable file. The launchpad opens.
        Note: If you want to install the product as a non-root user on UNIX systems or as a non-administrator on Windows systems, from the Select user mode for Installation Manager list, select Non-Administrator. When you select Non-Administrator, the software packages will be installed in the user's directory and the package group will be named My IBM Collaboration Lifecycle Management.
      2. Follow the steps in the launchpad to continue the installation. As you follow the steps in the launchpad, Installation Manager opens to install the software packages. For installation tips, see the "Tips" section in this topic.
    • To install by using the Installation Manager repository package:
      1. Start Installation Manager.

        If you do not have Installation Manager version 1.7 or later, you can obtain it from Jazz.net or download the web installer, which includes Installation Manager version 1.7.

      2. Click File > Preferences, and then select Add Repository.
      3. To specify the repository location, browse to the directory where you downloaded the .zip file and open the repository.config file.
      4. Click OK, and then click Install to start the installation process.
      5. Follow the instructions in Installation Manager to complete the installation. For installation tips, see the "Tips" section in this topic.
      Tips: As you follow the steps in Installation Manager, be aware of this information:
      • If you are installing to upgrade from a previous version, on the Install Packages page, choose one application at a time and in a later step, select the appropriate context root. However, if you are upgrading only one application and want to install the other two applications as new instances on the same application sever (for example, in an evaluation topology), select all of the applications.
      • If this is your first time installing by using Installation Manager, after you accept the license agreement, you are prompted to create a shared resource directory. You create this directory only once; it is shared by all of the products that you subsequently install by using Installation Manager.
      • In the Location pane, if you are installing in a WebSphere Application Server environment, change the installation path to one that contains no spaces, such as C:\IBM\JazzTeamServer.
      • In the Common Configuration pane, to install the included Apache Tomcat server, select Install Tomcat 7. If you already have a supported Tomcat application server installed and plan to use it, or if you plan to deploy the web applications (WAR files) into IBM WebSphere Application Server, clear Install Tomcat 7 and specify a location to place the web applications for later deployment. The default directory is JazzInstallDir/server/webapps.
      • Although the installation works on 32-bit systems, only 64-bit systems are tested and supported.
      • When you are prompted to select a context root option, if this is a new installation or you are upgrading from a release of version 4.0, select Use default application context roots. If you want to edit the default values and customize the application context roots, select Select custom context root values (advanced).

        Based on your application choices and the context root options, these context root values are used:

        Table 1. Application context root values.
        Note: The context root is the part of the URL that accesses each application and Jazz Team Server. For example, if your installation originated from Rational Team Concert version 2, the context root for the CCM application is /jazz, rather than /ccm.
        Application Default application context roots Rational Team Concert 2.x context root Rational Quality Manager 2.x context root Rational Requirements Composer 2.x context root
        Change and Configuration Management (CCM) application ccm jazz    
        Jazz Team Server jts      
        Lifecycle Project Administration admin    
        Quality Management (QM) application qm jazz
        Requirements Management (RM) application rm rdm
  4. When the installation is complete, in the "Which program do you want to start" section, make sure that the Documentation to configure the server for new or upgrade installations check box is selected, and then click Finish. The product documentation opens to a page that includes the next steps to configure the server, including instructions to upgrade, set up databases other than the default Apache Derby database, set up WebSphere Application Server, and run the setup wizard.

What to do next

Tomcat installations only:

If you installed on a Windows system, verify that the Start the Jazz Team Server and Stop the Jazz Team Server menu options are available from the Windows Start menu. To check for the menu options, click Start > All Programs > IBM Collaborative Lifecycle Management.

If you installed on a Linux system, verify that the Start the Jazz Team Server and Stop the Jazz Team Server menu options are available from the Applications menu of your Linux distribution.


video icon Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog