IBM Rational Team Concert for System z …z/OS: v z/OS V1.9 (recommended), or z/OS V1.8 v WebSphere ® Application Server for z/OS V6.1.0.10 1, 2 v IBM 31-bit SDK for z/OS Java 2 Technology

IBM Rational Team Concert for System z Beta Program

Configuration Guide

��

IBM Rational Team Concert for System z Beta Program

Configuration Guide

��

This edition applies to the Beta version of IBM Rational Team Concert for System z (product number 5724-V82) and

to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2008. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Note!

Before using this information and the product it supports, be sure to read the general

information under “Notices” on page 25.

Contents

About this book . . . . . . . . . . . v

About this beta program . . . . . . . . . . v

Chapter 1. Installing prerequisites . . . 1

Chapter 2. SMP/E installation . . . . . 3

Chapter 3. Configuring your installation 5

Create additional Jazz Team Server directories . . . 5

Setting up security with RACF . . . . . . . . 5

Setting up a DB2 database . . . . . . . . . . 6

DB2 prerequisites . . . . . . . . . . . . 6

Setting up DB2 . . . . . . . . . . . . 7

Customizing the configuration files . . . . . . . 8

Customizing the provisioning profiles . . . . . 8

Customizing Jazz Team Server properties files . . 9

Customizing the logging utility files . . . . . 10

Create database tables using Jazz Team Server

repository tools . . . . . . . . . . . . . 10

Deploy Jazz Team Server to WebSphere Application

Server . . . . . . . . . . . . . . . . 11

Additional WebSphere Application Server

considerations . . . . . . . . . . . . 13

Verifying the installation . . . . . . . . . 13

Completing the installation . . . . . . . . 13

Chapter 4. Setting up the Rational

Team Concert client . . . . . . . . . 15

Chapter 5. Running the Jazz Build

Engine . . . . . . . . . . . . . . . 17

Chapter 6. Getting started with Rational

Team Concert for System z . . . . . . 19

Chapter 7. Additional Jazz Team Server

Repository tools tasks . . . . . . . . 21

Exporting the database using the Jazz Team Server

repository tools . . . . . . . . . . . . . 21

Running repository tools to import a Jazz Team

Server database . . . . . . . . . . . . . 21

Chapter 8. Troubleshooting and getting

help . . . . . . . . . . . . . . . . 23

Notices . . . . . . . . . . . . . . 25

Trademarks and service marks . . . . . . . . 27

© Copyright IBM Corp. 2008 iii

iv IBM Rational Team Concert for System z Configuration Guide

About this book

This configuration guide provides information about installing and configuring the

beta version of IBM® Rational® Team Concert for System z™. Rational Team

Concert for System z is a collaborative software delivery environment that allows

teams to simplify, automate, and govern software delivery on z/OS®. This book is

for system administrators responsible for installing and maintaining the Rational

Team Concert client on their workstation and the Jazz Team Server on z/OS. To

use this book, you need to be familiar with the Windows® and z/OS operating

systems.

For the latest version of this document, see https://jazz.net/downloads/rational-team-concert/betas/z1.0Beta1

About this beta program

Rational Team Concert for System z builds on the core Rational Team Concert

product by providing a Jazz Team Server that runs on z/OS, a specific set of

functionality for z/OS, and cross-platform application development. This beta will

include the capabilities of Rational Team Concert with the addition of native

hosting on z/OS.

Restrictions:

1. You cannot use the Jazz Team Server setup wizard to configure the Team Server

database connection for the Rational Team Concert for System z beta product.

The required steps are described in this guide.

2. You cannot use the Jazz Team Server setup wizard to assign repository

permission to new users.

© Copyright IBM Corp. 2008 v

https://jazz.net/downloads/rational-team-concert/betas/z1.0Beta1


vi IBM Rational Team Concert for System z Configuration Guide

Chapter 1. Installing prerequisites

Ensure you have the following prerequisite applications installed and operational

before you proceed with the installation on z/OS:

v z/OS V1.9 (recommended), or z/OS V1.8

v WebSphere® Application Server for z/OS V6.1.0.101, 2

v IBM 31-bit SDK for z/OS Java™ 2 Technology Edition, V5, which includes the

IBM JZOS Batch Launcher3

v DB2® Version 9.1 for z/OS with the Universal JDBC driver configured to ensure

interoperability between the database and z/OS4

Notes:

1. Jazz Team Server requires WebSphere Application Server Version 6.1 with the

IBM Java SDK 1.5 SR5 or later Cumulative Fix applied. We recommend

WebSphere Application Server for z/OS V6.1.0.10 or later, which includes the

SR5 Cumulative Fix. For more information on WebSphere Application Server

for z/OS PTFs, see http://www.ibm.com/support/docview.wss?rs=404&uid=swg27007926

2. WebSphere Application Server security must be enabled. These instructions

assume that RACF® is the security provider. If you use other security providers

on z/OS, consult your security administrator.

3. For more information on the IBM 31-bit SDK for z/OS Java 2 Technology

Edition V5, which includes the JZOS Java Launcher and Toolkit, see

http://www.ibm.com/servers/eserver/zseries/software/java/j5pcont31.html.

The JZOS Java Launcher is required to run the Jazz Team Server repository

tools. For more information about the JZOS Batch Launcher, see the Installation

and User's Guide at http://www.ibm.com/servers/eserver/zseries/software/java/pdf/jzosinstal.pdf

4. See "Using the DB2 Universal JDBC Driver to access DB2 for z/OS" at

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ejbfep.multiplatform.doc/info/ae/ae/tdat_jdbcdb2cfg.html

© Copyright IBM Corp. 2008 1

http://www.ibm.com/support/docview.wss?rs=404&uid=swg27007926

http://www.ibm.com/support/docview.wss?rs=404&uid=swg27007926

http://www.ibm.com/servers/eserver/zseries/software/java/j5pcont31.html

http://www.ibm.com/servers/eserver/zseries/software/java/pdf/jzosinstal.pdf

http://www.ibm.com/servers/eserver/zseries/software/java/pdf/jzosinstal.pdf



2 IBM Rational Team Concert for System z Configuration Guide

Chapter 2. SMP/E installation

This guide does not provide instructions for implementing aspects of Rational

Team Concert for System z; instead, it is intended to guide you through a

successful configuration of the product. The instructions assume you have already

completed the Rational Team Concert for System z System Modification

Program/Extended (SMP/E) installation. The SMP/E instructions are in the

Rational Team Concert for System z Program Directory, available at

https://jazz.net/downloads/rational-team-concert/betas/z1.0Beta1.

The SMP/E installation will install one MVS™ dataset, hlq.SBLZSAMP where hlq

is a high-level qualifier chosen during the SMP/E Installation. The SMP/E

installation will also install one Unix System Services file directory

/@pathPrefix@/usr/lpp/jazz.

After you complete the SMP/E installation, follow the instructions in the

subsequent chapters of this guide to complete the installation and customization

on z/OS, configure the Jazz Team Server, and install the Eclipse-based client on

your PC.




Chapter 3. Configuring your installation

Ensure that the SMP/E installation has ended successfully and then complete the

following steps to configure your Jazz Team Server on z/OS.

Create additional Jazz Team Server directories

The Jazz Team Server on z/OS requires two additional directories in addition to

the USS directory created by the SMP/E installation. One is a directory used to

store Jazz Team Server configuration files and the other is a working directory.

Sample member BLZCPDIR in hlq.SBLZSAMP will be used to create and

populate these directories with necessary files from the SMP/E installed directory.

Three symbolic references will be used through out this guide to refer to these

particular directories as follows:

Symbolic

name Use

Variable in

BLZCPDIR Default directory

@pathPrefix@ The path prefix specified

during the SMP/E install.

HOME

@confPath@ Jazz Team Server

configuration files

directory.

CONF /etc/jazz

@workPath@ Jazz Team Server working

directory.

WORK /u/jazz

Considerations for RACF file access:

1. @confPath@ needs to be accessible for read and write by the WebSphere

Application Server servant user ID

2. @workPath@ needs to be accessible for read and write by the WebSphere

Application Server servant user ID

3. @workPath@ needs to be accessible for read and write by the user ID under

which the Jazz Team Server repository tools will be run

See “Create database tables using Jazz Team Server repository tools” on page 10

for more information.

Tailor member BLZCPDIR in hlq.SBLZSAMP according to the instructions

contained in the sample. Use the SUBMIT command to submit the modified JCL

and check the job log. If everything was set up properly, all steps will end with

return code 0.

Setting up security with RACF

The RACF tasks should be handled by your system administrator responsible for

security.

Note: These instructions assume you are using WebSphere Application Server

security using RACF.


The Jazz Team Server uses four roles that must be defined as RACF EJBROLE

profiles for security control. Define the four Jazz Team Server roles in the

EJBROLE class.

1. Define the EJBROLE profiles:

JazzAdmins

Jazz repository administrators with full read-write access

JazzDWAdmins

Jazz repository administrators with specific permissions to control the

data warehouse on a Jazz Team Server

JazzGuests

Users with read-only access to the Jazz repository

JazzUsers

Users with regular read-write access to the Jazz repositoryFor example:

RDEFINE EJBROLE JazzAdmins UACC(NONE)

RDEFINE EJBROLE JazzDWAdmins UACC(NONE)

RDEFINE EJBROLE JazzGuests UACC(READ)

RDEFINE EJBROLE JazzUsers UACC(NONE)

2. Permit the appropriate users or groups to the various roles.

For example:

Permit JazzAdmins CLASS(EJBROLE) ID(jazAdmns) ACCESS(READ)

Permit JazzDWAdmins CLASS(EJBROLE) ID(jDwadmns) ACCESS(READ)

Permit JazzUsers CLASS(EJBROLE) ID(jazzgrp) ACCESS(READ)

3. After completing the steps in this guide to configure Jazz Team Server, you

must log on as a Jazz Team Server administrator to verify this configuration.

Before attempting to verify the configuration, provide at least one user ID or

group with read authority to the JazzAdmins profile in the EJBROLE class.

Note: Whenever user IDs are added to the Jazz Team Server repository, they

must also be given read authority to the appropriate RACF profile in the

EJBROLE class (JazzAdmins, JazzDWAdmins, JazzGuests, JazzUsers).

Setting up a DB2 database

The following DB2 setup tasks should be handled by your DB2 administrator.

DB2 prerequisites

Ensure DB2 Version 9.1 for z/OS with the Universal JDBC driver is installed and

running on the z/OS machine that will be used as the database server. This might

not be the same machine on which the Jazz Team Server will run.

The Jazz Team Server requires that the WLM procedures associated with the DB2

stored procedures SYSPROC.DSNUTILS and SYSIBM.SQLxxx are active. If

necessary, this can be verified by comparing the names of the DB2 WLM

environment variables with the active WLM procedures. The following SQL

statement can be used to retrieve the WLM procedure names via DB2 SPUFI or

your preferred technique. Use the SELECT command to produce query results like

the following example:

SELECT DISTINCT WLM_ENVIRONMENT FROM SYSIBM.SYSROUTINES WHERE

(NAME=’DSNUTILS’ OR (SCHEMA=’SYSIBM’ AND NAME LIKE ’SQL%’));

---------+---------+---------+---------+---------+---------+---

WLM_ENVIRONMENT

---------+---------+---------+---------+---------+---------+---

DSN9WLM1


Use the following command from the z/OS Console to display the WLM active

procedures: D WLM,APPLENV=*. This command produces results like the

following example:

SDSF SYSLOG 2493.101 2094 2094 07/10/2008 0W 14886 COMMAND ISSUED

RESPONSE=RALNS32

IWM029I 16.31.12 WLM DISPLAY 465

APPLICATION ENVIRONMENT NAME STATE STATE DATA

BBOASR1 AVAILABLE

BBOASR2 AVAILABLE

BBOC001 AVAILABLE

CBINTFRP AVAILABLE

CBNAMING AVAILABLE

CBSYSMGT AVAILABLE

DSN9WLM1 AVAILABLE

DSN9WLM2 AVAILABLE

DSN9WLM3 AVAILABLE

In this case, you can see that the DSN9WLM1 procedure is active.

Setting up DB2

When running the Jazz Team Server on DB2 you must create a DB2 storage group

and a DB2 database. You will also need to authorize the Jazz Team Server user to

that storage group and database.

Note: The following steps must be performed before running the repository tools

database builder utility, which creates the Jazz repository tables in your

database instance. None of these steps will be performed by the Jazz Team

Server database builder in the repository tools. See “Create database tables

using Jazz Team Server repository tools” on page 10 for more information.

Create a storage group

The storage group will need to be appropriate to the machine. The

example below shows a DB2 SQL create statement:

CREATE STOGROUP JAZZSTG VOLUMES (’*’) VCAT yourHlq ;

Notes:

1. The storage group could be named something other than JAZZSTG

2. The storage group name will be used later in “Customizing Jazz Team

Server properties files” on page 9 for the Jazz Team Server

teamserver.properties com.ibm.team.repository.db.db2.dsn.stogroup

property

3. yourHlq is the high level qualifier of your DB2 files, it must exist on

your system and the Jazz Team Server user must have full access to it

Create a database

The database will need to be appropriate to the machine. The example

below shows a DB2 SQL create statement:

CREATE DATABASE JAZZDB STOGROUP JAZZSTG BUFFERPOOL bpx ;

Notes:

1. The database could be named something other than JAZZDB

2. The database name will be used later in “Customizing Jazz Team


teamserver.properties com.ibm.team.repository.db.db2.dsn.dbname

property

3. bpx is the buffer pool name


4. The buffer pool name will be used later in “Customizing Jazz Team


teamserver.properties com.ibm.team.repository.db.db2.dsn.bufferpool

properties

Authorize Jazz Team Server user

The Jazz Team Server requires a user ID and password in order to access

the Jazz Team Server DB2 repository. This user ID and password will be

specified later in the Jazz Team Server teamserver.properties file. This user

ID is not used to log on to the Jazz Team Server, but is used only to

provide authority for the Jazz Team Server to access the DB2 database.

Specifically, this user ID needs permissions as shown below. See

“Customizing Jazz Team Server properties files” on page 9 for more

information. In the example below, the user has the name jazz.

GRANT DBADM ON DATABASE jazzdb TO jazz ;

GRANT USE OF STOGROUP jazzstg TO jazz ;

GRANT USE OF BUFFERPOOL bpx TO jazz ;

COMMIT ;

In addition, if the value of field DBADM CREATE AUTH was set to NO

on panel DSNTIPP during DB2 installation, you must grant SYSADM

authorization to the Jazz Team Server user.

GRANT SYSADM TO jazz ;

COMMIT ;

Customizing the configuration files

There are several Jazz Team Server configuration files that will need to be modified

based on the directories you have chosen for @pathPrefix@, @workPath@, and

@confPath@. The following sections provide instructions for modifying the

configuration files.

The Jazz Team Server for z/OS properties files are ASCII files. There are several

techniques you can use to edit ASCII files under z/OS Unix System Services. For

example, you can:

v Download or use FTP to transfer the files to a Windows PC, modify them, and

transfer them back to the z/OS system

v If you use Rational Developer for System z, you can connect via Remote System

Explorer and modify the files

v If you have z/OS 1.9 and the PTF for APAR OA22250, you can use ISPF option

3.17 to edit ASCII files under USS

v If you have other tools for editing ASCII files under USS, you can use those

tools

.

Customizing the provisioning profiles

If you have used the @pathPrefix@, you should edit the following files:

@confPath@/provision_profiles/profile.ini

Change the following :

url=file:/usr/lpp/jazz/update-site

to url=file:/@pathPrefix@/usr/lpp/jazz/update-site

For example:


url=file:/myroot/usr/lpp/jazz/update-site

@confPath@/provision_profiles/license-profile.ini

Change the following:

url=file:/usr/lpp/jazz/license-update-site

to url=file:/@pathPrefix@/usr/lpp/jazz/license-update-site

For example:

url=file:/myroot/usr/lpp/jazz/license-update-site

Customizing Jazz Team Server properties files

This section describes how to edit teamserver.properties to configure the database

connection.

Edit the @confPath@/teamserver.properties file.

To configure the server, locate the following lines:

com.ibm.team.repository.db.vendor = db2z

com.ibm.team.repository.db.jdbc.location=//ipAddress:ipPort

/location:fullyMaterializeLobData=false;user=db2admin;password={password};

com.ibm.team.repository.db.jdbc.password=db2admin

com.ibm.team.repository.db.db2.dsn.dbname=JAZZDB

com.ibm.team.repository.db.db2.dsn.bufferpool=bpx

com.ibm.team.repository.db.db2.dsn.stogroup=JAZZSTG

Edit these lines to match the database configuration you created in previous steps

and to match your DB2 configuration. Edit the location, user, password, dbname,

bufferpool and stogroup properties according to your configuration. For reference

use the DIS DDF command for your DB2 subsystem to display some of the values

you need to supply. For example, you can retrieve the location, ipaddr, and port

(tcpport) from the following display:

-DSN9 DIS DDF

DSNL080I -DSN9 DSNLTDDF DISPLAY DDF REPORT FOLLOWS: 548

DSNL081I STATUS=STARTD

DSNL082I LOCATION LUNAME GENERICLU

DSNL083I NS32DB NETA.NS32DB -NONE

DSNL084I TCPPORT=3500 SECPORT=3510 RESPORT=3501 IPNAME=-NONE

DSNL085I IPADDR=::9.42.81.74

DSNL086I SQL DOMAIN=RALNS32.rtp.raleigh.ibm.com

DSNL086I RESYNC DOMAIN=RALNS32.rtp.raleigh.ibm.com

DSNL099I DSNLTDDF DISPLAY DDF REPORT COMPLETE

Specifically, edit the following:

1. Modify:

com.ibm.team.repository.db.jdbc.location=//ipAddress:ipPort/

location:fullyMaterializeLobData=false;user=db2admin;password={password};

with the following:

__ Replace location with your location

__ Replace ipAddress with your ipaddr

__ Replace ipPort with your tcpport

__ Replace user with the user ID you created, which will have appropriate

access to the DB2 database

Note: Do not modify password={password}

2. Modify:


com.ibm.team.repository.db.jdbc.password=db2admin

with the following:

__ Replace db2admin with the password for your DB2 user3. Modify:

com.ibm.team.repository.db.db2.dsn.dbname=JAZZDB

with the following:

__ Replace JAZZDB with the name of the database you created4. Modify:

com.ibm.team.repository.db.db2.dsn.bufferpool=bpx

with the following:

__ Replace bpx with the bufferpool you chose when you created the

database5. Modify:

com.ibm.team.repository.db.db2.dsn.stogroup=JAZZSTG

with the following:

__ Replace JAZZSTG with the storage group you created

In addition, replace all instances of @workPath@ in the teamserver.properties with

the path that you selected for @workPath@ in the following properties:

v com.ibm.team.repository.content.tmpdir

v com.ibm.team.fulltext.indexLocation

Note: Jazz Team Server will create these directories.

Customizing the logging utility files

The @confPath@/log4j.properties file configures the logging framework used by

the Jazz Team Server. By default, the log4j.properties file writes Jazz Team Server

messages to the WebSphere Application Server stdout file (generally the

application server servant job log) as well as to a separate file that is specified in

the log4j.properties file. Edit the @confPath@/log4j.properties file and locate the

line:

log4j.appender.file.File=@workPath@/logs/jazz.log

This line should be updated to reflect the value that you are using for your Jazz

Team Server @workPath@ directory.

Create database tables using Jazz Team Server repository tools

Although the DB2 database was created in earlier steps, you must use the Jazz

Team Server repository tools to create the required database tables and indexes for

the Jazz Team Server.

Tailor member BLZCREDB in hlq.SBLZSAMP following the instructions

contained in the sample JCL. The Jazz Team Server and the Jazz Team Server

repository tools require access to the DB2 V9 JDBC license jar file on your system.

This file is named db2jcc_license_cisuz.jar and is located by default at

/usr/lpp/db2910_jdbc/classes. If the file is in a different directory, then modify the

sample job to point to your location. Submit the modified JCL and check the job

log. The following message must end the STDOUT:


The database tables were created successfully.

The details are in the JCL sample.

Note: The user who submits repository tools jobs must have read access to the

RACF EJBROLE.JazzAdmins profile.

Deploy Jazz Team Server to WebSphere Application Server

Before setting up the Jazz Team Server to work with WebSphere Application

Server, you should have the following tasks completed. These tasks should be

performed by your Websphere Application Server administrator.

v WebSphere Application Server is already installed

v The database is created and the teamserver.properties file is updated with your

database settings

Notes:

1. Although the Websphere Application Server allows you to use a

case-insensitive login, Jazz Team Server stores user records with user IDs in

exact case as they are imported. When you log in 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 Java 2 security

option is turned off. When you have logged onto the Websphere Application

Server administrative console go to Security -> Secure administration,

applications, and infrastructure.

3. This document does not teach 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 at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/welc6topsecuring.html.

4. The Jazz Team Server Web UI requires that authentication be configured in

order to perform authorization and personalize the application.

Once 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

WebSphere Application Server:

1. Update the JVM arguments.

The Jazz Team Server needs some specific settings on the Java Virtual Machine

in which it is run. First, it needs to know where to find the configuration files

for the server and for log4j, the logging framework used by the server. This is

done by setting the system properties com.ibm.team.server.config URL and

log4j.configuration. These properties use a URL rather than a simple path, so

the value should be specified with the URI scheme name of file:///.

The JVM system properties that must be set to control certain server behaviors

are listed below.

Tip: Before modifying the Generic JVM Arguments consider making a backup

of the file. If you enter invalid arguments and update the master

configuration, you might have problems starting your 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:


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.web20fep.multiplatform.doc/info/ae/ae/welc6topsecuring.html



/u/WebSphere/V6R1/AppServer/profiles/default/config/cells/APC1

/nodes/TST1/servers/server1/servant.jvm.options

Where TST1 would be substituted with your mainframe node. If you

cannot restart the server after applying the generic JVM arguments, use

the backup file to recover.Use the WebSphere Application Server administrative console to set these

properties.

a. Click Servers > Application Servers

b. Click server1

c. Click Java and Process Management > Process Definition > Servant

d. Click Java Virtual Machine

e. Set maximum heap size to 1000

f. Add the following additional arguments to the Generic JVM Arguments, all

on one line, but replace @confPath@ with your directory name. Specify the

location of the DB2 license file named db2jcc_license_cisuz.jar. Replace

@db2pathPrefix@ with your DB2 directory path prefix.

-Dcom.ibm.team.server.configURL=file:///@confPath@/teamserver.properties

-Dlog4j.configuration=file:///@confPath@/log4j.properties

-Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true

-Dcom.ibm.team.repository.provision.profile=@confPath@/provision_profiles

-DDB2Z_JDBC=@db2pathPrefix@/usr/lpp/db2910_jdbc/classes

For example:

-Dcom.ibm.team.server.configURL=file:///etc/jazz/teamserver.properties

-Dlog4j.configuration=file:///etc/jazz/log4j.properties

-Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true

-Dcom.ibm.team.repository.provision.profile=etc/jazz/provision_profiles

-DDB2Z_JDBC=/usr/lpp/db2910_jdbc/classes

Note: If you use different directories, change the directory names.

g. Click OK

h. Click Save

i. Restart the WebSphere Application Server to pick up the modified JVM

arguments2. Install the Jazz Team Server application

a. Open the administrative console for your WebSphere Application Server

b. Click Applications > Install New Application

c. Under Path to new Application, select remote file system

d. Under Full path enter:

@pathPrefix@/usr/lpp/jazz/jazz.war

e. Set Context Root to jazz

f. Accept the defaults for the next three screens by clicking Next

g. Click Finish to install the jazz_war file

h. Click Save directly to the master configuration

i. Click Applications > Enterprise Applications

j. Check the box next to jazz_war, and click Start

A green arrow should appear indicating the application started successfully.


Additional WebSphere Application Server considerations

To allow attachments in work items and messages larger than 10 MB, enable

message chunking. From the WebSphere Application Server administrative console:

v Navigate to Servers > Application servers > Serverx > Web Container Settings

> Web Container Transport Chains >WCinboundDefaultSecure > Web

Container Inbound Channel (WCC 4) > Custom properties

v Define the property named disableRequestMessageChunking and set it to false

Verifying the installation

The tasks required to verify the installation should be performed by your Jazz

Team Server administrator.

Using a Web browser, log in to the Jazz Team Server using the URL:

https://yourHostName:yourWASsecurePort/jazz/admin

For example:

https://mvshost:9443/jazz/admin

Log in with the user ID created during the RACF security setup process.

Tip: If you cannot access the Jazz Team Server administration Web interface

successfully or errors are occur in the Server Status Summary panel within

the administration Web interface, closely examine your WebSphere

Application Server servant logs for error messages or exceptions. In particular,

pay attention to any reported permission errors that might have been

encountered. Depending on your system configuration, you might need to

provide additional write permissions to allow the WebSphere Application

Server servant write access to the directory you configured in your

teamserver.properties with the com.ibm.team.repository.tmpdir property.

Completing the installation

The tasks required to complete the installation should be performed by your Jazz

Team Server administrator.

You can access the Jazz Team Server setup wizard using the https://yourHostName:yourWASsecurePort/jazz/setup URL. For example:

https://mvshost:9443/jazz/setup

To ensure the server is operating properly, run the setup wizard, which will guide

you through the steps for setting up users and adding e-mail addresses. To verify

that the Jazz Team Server is connecting to the database, look at the server log or

console output. The connection and database information is echoed on its first

access.

These instructions assume your server is available using a URL like:

https://yourHostName:yourWASsecurePort/jazz/admin

Log in with a JazzAdmin user ID that is defined in RACF.

Choose a setup path. The setup wizard has two main paths:

v The Fast Path Setup uses the default configuration. If you want to complete the

installation quickly, the fast path setup is a good option. During the Fast Path

Setup, you create the user registry.


v The Custom Setup guides you through the detailed setup procedures, including

the ability to enable e-mail notifications. During the Custom Setup, you create

the user registry and enable e-mail notification.

After the server is installed, you must consider some configuration options before

continuing.

v Some files contain passwords. Those files should be protected so that they are

readable only by users authorized to know the password for the accounts. The

Jazz Team Server requires that the database password is stored in

JazzInstallDir/server/teamserver.properties. When properties files are saved, the

application always makes a backup copy of the previous version in the same

directory. If you want to remove all files that contain the clear-text password,

remove the backup properties files after configuring the server for the first time.

v If you configured the application server to use ports other than the defaults,

these ports should also be configured in the Jazz configuration. These port

numbers are used for composing URLs for things like feed links and item links

in email notifications. To update the defaults, use the advanced properties

configuration page of the Admin Web UI to modify the following properties:

com.ibm.team.repository.servlet.internal.ServletConfigurationService

- Repository HTTP port

- Repository HTTPS port com.ibm.team.repository.service.internal.webuiInitializer

.ConfigPropertyInitializer

- URL HTTP Port

- URL HTTPS Port

You are now ready to connect to the server with the Rational Team Concert client

or a Web browser.


Chapter 4. Setting up the Rational Team Concert client

Complete the following steps to install the Rational Team Concert client (also

called the Eclipse client) on Windows:

1. Download the client zip file RTC-Client-for-i-and-z-1.0Beta1.zip

2. Extract the .zip file to an installation directory of your choice. Relative to the

installation directory you choose, the client path is JazzInstallDir/jazz/client.

3. To start the client, double click on the TeamConcert.exe application in the

directory JazzInstallDir/jazz/client/eclipse.

Note: Depending on which unzip utility you use, you might experience problems

with path lengths being too long when extracting the client zip file. To avoid

this problem, it is recommended that you use as short a prefix as possible

for JazzInstallDir, for example c:\ or d:\.

You will use the Rational Team Concert Eclipse client with the Tutorial exercises.

See Chapter 6, “Getting started with Rational Team Concert for System z,” on page

19.



Chapter 5. Running the Jazz Build Engine

Setting up the Jazz Build Engine is optional. You can complete these steps now, or

when you decide to run the Jazz Build Engine on z/OS. This step is only required

if you decide to execute builds on z/OS.

Before performing the setup steps in this chapter, review Lesson 8: Team Builds in

the tutorial, Getting Started with Rational Team Concert at https://jazz.net/jazzdocs/index.jsp?topic=/com.ibm.team.concert.tutorial.doc/topics/tut_rtc_build.html. The

Jazz Build Engine is installed when you install the Jazz Team Server. You need to

register a build engine instance using the Rational Team Concert client. Follow the

instructions in the tutorial to create a build engine. Before starting a build engine,

create an encrypted password file for the build engine to use to prevent casual

observation.

Tailor member BLZBPASS in hlq.SBLZSAMP following the instructions contained

in the sample JCL. This password file can also be used in your build scripts.

Submit the modified JCL. The job must end with a return code 0. Do not save the

modified JCL with any password in it.

Tailor member BLZBENG in hlq.SBLZSAMP following the instructions contained

in the sample JCL. Submit the modified JCL. The job must remain active and the

following messages must end the STDOUT:

2008-05-27 11:08:46 Running build loop... 2008-05-27 11:08:46 Waiting for request..

When you submit a build request to this build engine from Rational Team Concert,

you will see a message like:

2008-07-24 20:00:38 Found a request for build definition "SampleBuild"

Note: Make sure that the WebSphere Application Server user ID has read access

for the buildData directory folder that hosts the build scripts and write

access for the folder that will be used to create the build artifacts. These

folders are defined in the build definition and in the build scripts.


https://jazz.net/jazzdocs/index.jsp?topic=/com.ibm.team.concert.tutorial.doc/topics/tut_rtc_build.html

https://jazz.net/jazzdocs/index.jsp?topic=/com.ibm.team.concert.tutorial.doc/topics/tut_rtc_build.html


Chapter 6. Getting started with Rational Team Concert for

System z

Keep in mind that the Rational Team Concert for System z Beta is an early release

version. The documentation referenced is included with the distributed version of

Rational Team Concert and many but not all of the topics are applicable to

Rational Team Concert for System z Beta product.

The Jazz.net Web site has many resources to help you get started with Jazz

components and Rational Team Concert. Register at Jazz.net and seeTutorial: Get

started with Rational Team Concert at https://jazz.net/jazzdocs/topic/com.ibm.team.concert.tutorial.doc/topics/tut_rtc_abstract.html. The tutorial will

teach you to:

v Set up a project and team

v Get connected as a user

v Create and understand work items

v Organize team work

v Save and share source

v Use the Web user interface

v Examine the Jazz build

Expect to spend a few hours to complete the tutorial.

For a faster introduction, see the Jazz technology platform quick reference at

https://jazz.net/jazzdocs/topic/com.ibm.team.platform.doc/topics/c_jazz-platform-quick-ref.html. See the Rational Team Concert online help at

https://jazz.net/jazzdocs/index.jsp for additional information.

To get started using Rational Team Concert for System z, start with the following

online help topics:

v Managing the Jazz Team Server through the Web interface at https://jazz.net/jazzdocs/topic/com.ibm.team.repository.web.admin.doc/topics/tworkwithadminwebui.html

v Working with projects, teams, and process at https://jazz.net/jazzdocs/topic/com.ibm.team.platform.doc/topics/t_projects_teams_process.html

Explore the online help and the Jazz.net Web site for product details, concepts,

troubleshooting, for Rational Team Concert, the Jazz platform, and new incubator

technologies.


https://jazz.net/jazzdocs/topic/com.ibm.team.concert.tutorial.doc/topics/tut_rtc_abstract.html

https://jazz.net/jazzdocs/topic/com.ibm.team.concert.tutorial.doc/topics/tut_rtc_abstract.html

https://jazz.net/jazzdocs/topic/com.ibm.team.platform.doc/topics/c_jazz-platform-quick-ref.html

https://jazz.net/jazzdocs/topic/com.ibm.team.platform.doc/topics/c_jazz-platform-quick-ref.html

https://jazz.net/jazzdocs/index.jsp

https://jazz.net/jazzdocs/topic/com.ibm.team.repository.web.admin.doc/topics/tworkwithadminwebui.html



https://jazz.net/jazzdocs/topic/com.ibm.team.platform.doc/topics/t_projects_teams_process.html

https://jazz.net/jazzdocs/topic/com.ibm.team.platform.doc/topics/t_projects_teams_process.html


Chapter 7. Additional Jazz Team Server Repository tools tasks

Before completing the tasks in this chapter, review the Repository Tools overview

topic in the Rational Team Concert information center at https://jazz.net/jazzdocs/topic/com.ibm.team.install.doc/topics/c_repotools_overview.html .

Exporting the database using the Jazz Team Server repository tools

Tailor member BLZEXPOR in hlq.JAZZ.SAMPJCL following the instructions

contained in the sample JCL. Submit the modified JCL and check the job log. The


Export completed successfully. The user "ADMIN" has logged out of the database

Notes:

1. The user who submits repository tools jobs must have read access to the RACF

EJBROLE.JazzAdmins profile.

2. When you use repotools, you can specify the codepage to use, by specifying the

JVM option –Dfile.encoding, -Dfile.encoding=UTF-8, or

-Dfile.encoding=EBCDIC. If you export in UTF-8, you can move your .tar file

to a distributed system and import it using that system. If you export in

EBCDIC, you .tar file can only be imported using a repository tools import

performed on System z.

Running repository tools to import a Jazz Team Server database

Tailor member BLZIMPOR in hlq.JAZZ.SAMPJCL following the instructions

contained in the sample JCL. Submit the modified JCL and check the job log. The


Import completed successfully. The user "ADMIN" has logged out of the database.

Note: Pay attention to the JVM properties, like Xms and Xmx.


https://jazz.net/jazzdocs/topic/com.ibm.team.install.doc/topics/c_repotools_overview.html

https://jazz.net/jazzdocs/topic/com.ibm.team.install.doc/topics/c_repotools_overview.html


Chapter 8. Troubleshooting and getting help

The Jazz.net forum and bug tracking page are available for solving problems,

creating bug reports, and answering questions related to the Rational Team Concert

for System z Beta program. To use the forums or open bug reports, first register

with Jazz.net. When you receive your password, log on to Jazz.net using those

credentials.

To use the forum:

1. Browse the Jazz.net forums at https://jazz.net/community/forums.jsp

2. Use the jazz.user forum at https://jazz.net/forums/viewforum.php?f=1 to

search for similar problems or questions by clicking the Search link at the

bottom of the page

3. To create a new forum topic, click the New topic button, and fill in the

following fields:

v In the Subject field enter [RTCz] along with a brief topic description. For

example, “[RTCz] Starting Jazz Team Server generates errors.”

v Enter a description in the Message body.

v Click Submit.

To search for or create a bug report or work item, go to the Jazz Bug Tracking page

at https://jazz.net/bugs/bugs.jsp to browse or search for bug reports. To search

existing bug reports you can use a predefined work item query or create a custom

query of your own. To get a list of all of the work items for Rational Team Concert

for System z, run the RTC on System z work items query at https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.runSavedQuery&id=_sBRfwFgMEd2m4t10AgGhCQ&tq=1216830746000.

To submit a work item or bug report, complete the following steps:

v Click New work item

v In the Summary field enter a brief topic description

v From the Type list, select Defect (the default option) if you are reporting a

problem, or Enhancement if you are suggesting a new feature or improvement.

v From the Filed against list, select the (Show All) category and then open the

Filed against drop-down list again and choose "RTC on System z"

v Enter a detailed description in the Description field

v Optional: Enter a level of Severity and/or Priority

v If you want to add a file attachment or screen capture of the problem, that

option is available on the Links tab

v Click Save to submit your work item

v Record your work item number for future reference

You can use the discussion section of the work item to add comments using the

Add Comment link on the right of the discussion section at the bottom of the

Overview tab. Developers can also add comments or respond to your questions

there. You will be notified by e-mail when the work item changes or when

comments are added.


https://jazz.net/community/forums.jsp

https://jazz.net/forums/viewforum.php?f=1

https://jazz.net/bugs/bugs.jsp

https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.runSavedQuery&id=_sBRfwFgMEd2m4t10AgGhCQ&tq=1216830746000



Tip: For advice on effective bug reporting, see How to Report Bugs Effectively at

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html


http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may

be used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not grant you

any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other

country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or

implied warranties in certain transactions, therefore, this statement may not apply

to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the publication. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM

product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software

IBM Corporation

20 Maguire Road

Lexington, MA 02421-3112

U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement or any equivalent agreement

between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may

vary significantly. Some measurements may have been made on development-level

systems and there is no guarantee that these measurements will be the same on

generally available systems. Furthermore, some measurement may have been

estimated through extrapolation. Actual results may vary. Users of this document

should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of

performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the

suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or

withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business

operations. To illustrate them as completely as possible, the examples include the

names of individuals, companies, brands, and products. All of these names are

fictitious and any similarity to the names and addresses used by an actual business

enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrates programming techniques on various operating platforms. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating

platform for which the sample programs are written. These examples have not

been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or

imply reliability, serviceability, or function of these programs. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM for the purposes of developing, using, marketing, or distributing application

programs conforming to IBM’s application programming interfaces.


Each copy or any portion of these sample programs or any derivative work, must

include a copyright notice as follows:

(c) (your company name) (year). Portions of this code are derived from IBM Corp.

Sample Programs. (c) Copyright IBM Corp. _enter the year or years_. All rights

reserved.

Additional legal notices are described in the legal_information.html file that is

included in your Rational software installation.

Trademarks and service marks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of

International Business Machines Corporation in the United States, other countries,

or both. If these and other IBM trademarked terms are marked on their first

occurrence in this information with a trademark symbol (® or

™), these symbols

indicate U.S. registered or common law trademarks owned by IBM at the time this

information was published. Such trademarks may also be registered or common

law trademarks in other countries. A current list of IBM trademarks is available on

the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Microsoft® and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.

UNIX® is a registered trademark of The Open Group in the United States and

other countries.

Java is a trademark of Sun Microsystems, Inc. in the United States, other countries,

or both.

Other company, product, or service names may be trademarks or service marks of

others.

Notices 27


��

Printed in USA

Documents

IBM Rational Team Concert for System z …z/OS: v z/OS V1.9 (recommended), or z/OS V1.8 v WebSphere ® Application Server for z/OS V6.1.0.10 1, 2 v IBM 31-bit SDK for z/OS Java 2 Technology