Deploying the Jazz Team Server to the WebSphere Application Server

This topic lists the prerequisite tasks your WebSphere® Application Server administrator must perform, and describes the steps you must complete to deploy the Jazz™ Team Server.
Before setting up the Jazz Team Server to work with the WebSphere Application Server, make sure your WebSphere Application Server administrator completes the following tasks:
  • Install the WebSphere Application Server.
  • Create the database and update the teamserver.properties file with your database settings.
Notes:
  1. Although you can use an ID that is not case sensitive with the WebSphere Application Server, Jazz Team Server stores user records with user IDs in the exact case in which they are imported. When you log on to Jazz Team Server, the user record is retrieved from the list of users and the case must match exactly.
  2. Ensure that Enable application security is enabled and that the log in Java 2 security option is turned off. When you have logged on to the WebSphere Application Server administrative console, go to Security -> Secure administration, applications, and infrastructure.
  3. This document does not deal with the configuration of WebSphere authentication or SSL, which is a complex topic. Detailed information on authentication and encryption options is available in the WebSphere Application Server Information Center.
  4. The Jazz Team Server Web user interface requires you to configure authentication to perform authorization and to personalize the application.

After the WebSphere Application Server is installed and the database is created, complete the following tasks to set up the Jazz Team Server to work with the WebSphere Application Server.

  1. Update the JVM arguments.
    • The Jazz Team Server requires some specific settings on the Java™ Virtual Machine in which it is run. It must know where to find the configuration files for the server, and also where to find the configuration files for log4j, the logging framework used by the server. To do this, set the system properties com.ibm.team.server.config URL and the log4j. configuration. These properties use a URL instead of a simple path, so the value should be specified with the URI scheme name of file:///.
    • You must set the following JVM system properties to control certain server behaviors.
      Tip: Before modifying the JVM arguments, consider making a backup of the file. If you enter arguments that are not valid, and then update the master configuration, you might have problems starting the server again. If you cannot start the server, you cannot modify the JVM arguments using the WebSphere Application Server administrative console. The settings are stored in a file similar to:
       /u/WebSphere/V6R1/AppServer/profiles/default/config/cells/TST1
      /nodes/TST1/servers/server1/servant.jvm.options
      TST1 should be substituted with your mainframe node. If you cannot restart the server after applying the JVM arguments, use the backup file to recover.

      Use the WebSphere Application Server administrative console to set these properties.

      1. Click Servers > Application Servers.
      2. Click server1.
        Note: If you are creating multiple Jazz schemas to support separate repositories, you will need to create a separate WebSphere Application Server for each schema. You will then need to perform the following steps for each WebSphere Application Server that is supporting a Jazz server repository.

        For information on creating WebSphere Application Servers, see the WebSphere Application Server for z/OS documentation.

      3. Click Java and Process Management > Process Definition > Servant.
      4. Click Java Virtual Machine.
      5. Set maximum heap size to 1000.
      6. Click Custom Properties.

        For each name/value pair, click New, enter the names and values shown below:

        Name Value
        com.ibm.team.repository.provision.profile
        Note: The property com.ibm.team.repository.provision.profile needs to point to the directory which contains the provision_profiles.
        /@confPath@/provision_profiles
        com.ibm.team.server.configURL file:///@confPath@/teamserver.properties (as file URL)
        log4j.configuration file:///@confPath@/log4j.properties (as file URL)
        DB2Z_JDBC @db2pathPrefix@/db2910_jdbc/classes
        java.awt.headless true
        org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin true
      7. Click Save directly to the master configuration.
  2. Install the Jazz Team Server application:
    1. Open the administrative console for your WebSphere Application Server.
    2. Click Applications > Install New Application.
    3. Under Path to new Application, select remote file system.
    4. Under Full path, enter: @pathPrefix@/usr/lpp/jazz/jazz.war.
    5. Set Context Root to jazz.
    6. Accept the defaults for the next three screens by clicking Next
    7. Click Finish to install the jazz_war file.
    8. Click Save directly to the master configuration.
    9. Click Applications > Enterprise Applications.
    10. Check the box next to jazz_war and click Start.
    A green arrow should be displayed to indicate that the application started successfully.
  3. Stop and restart the WebSphere Application Server.

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug