Installing and configuring the integration

There are additional installation and configuration steps required to integrate Rational Developer for System z and Rational Team Concert for System z.

Before you begin
Follow the installation and configuration steps for the Remote Systems Explorer (RSE) server and daemon in the Rational Developer for System z Host Configuration Guide (SC23-7658-02).
Limitation: Do not install the Rational Team Concert for System z client in combination with the Rational Developer for System z client until you have successfully installed and configured the Rational Team Concert for System z toolkit as an RSE extension as described in this section.

These steps require that the Build System Toolkit for System z has been installed. If you have not completed the installation, see Installing the Build System Toolkit for System z for more information.

Because the CLASSPATH environment variable that can be specified on the z/OS file system has a size limit, you must create symbolic links to the Build System Toolkit for System z .jar files. You can create the symbolic links by completing the following steps:

  1. Configure the sample JCL member BLZCRSYM in hlq.SBLZSAMP, where hlq is the high-level qualifier specified during the SMP/E installation. This job will create a symbolic link directory in your jazz config directory, normally /etc/jazz/ and will contain symbolic links to all the .jar files in the buildtoolkit directory. Submit the modified JCL and check the job log and ensure the job finishes with a return code 0. You should see some output in the SYSTSPRT portion of the job output that lists the .jar file name and the symbolic link created. For example, One of these lines looks like this:
    jar.6=com.ibm.team.build.client_2.0.0.I200906091854.jar 
    sym.6=com.ibm.team.build.client.jar
  2. Locate the rsed.envvars file in the RSE configuration directory. See rsed.envvars, RSE on page 19 of the Rational Developer for System z Host Configuration Guide for instructions.
  3. Save a copy of this file using this command:
    cp rsed.envvars rsed.envvars.org
  4. Edit the rsed.envvars file using the ISPF 3.17 oedit command (oedit rsed.envvars) if you use OMVS, or the Rational Developer for System z editor if you use RSE.
  5. You must add additional classpath statements for Rational Team Concert for System z to the existing CLASSPATH environment variable. Find the CLASSPATH assignment, which should be CLASSPATH=.:$CLASSPATH and immediately before it copy the sample member BLZENVAR from hlq.SBLZSAMP, where hlq is the high-level qualifier specified during the SMP/E installation. This member contains the list of Rational Team Concert for System z CLASSPATH assignments.
  6. Stop and restart the RSE server and daemon.
    Note: These changes should be applied to every instance of the RSE server that you use if you want that server to also be enabled for Rational Team Concert for System z. After performing the above configuration steps, you must recreate any RSE connections that existed previously in your Rational Developer for System z clients.
What to do next
Create a file called FileAgentConfiguration.dat in the same directory where rsed.envvars is located. This .dat file must contain comma-separated entries that identify a Rational Team Concert for System z Jazz repository URL, a user ID to be used by the file agent to authenticate to the Jazz repository, and the password for that user ID. For example:
https://myexample.jazz.repository.com:9443/jazz, myrepouserid, myrepopassword
Note: The URL you specify for the Jazz Repository Connection must match the Jazz server entry in the file agent miner FileAgentConfiguration.dat file.