RegisterLog In to Jazz.net dW

Rational Team Concert for Power Systems Software 2.0.0.2 interim fix 1

Product Release Trial | April 13, 2010
Installing Rational Team Concert for Power Systems Software

Installing Rational Team Concert for Power Systems Software


Contents

Installing Rational Team Concert for Power Systems Software

IBM Rational Team Concert for Power Systems Software is a team collaboration tool that is built on a scalable, extensible platform that seamlessly integrates tasks across the software lifecycle. It is specifically designed for teams that are involved with software lifecycle activities for cross-platform software. Many aspects of the software development lifecycle are integrated, including iteration planning, process definition, source control, defect tracking, build management, and reporting. Rational Team Concert for Power Systems Software extends the core Rational Team Concert product by providing features and functions specifically for development on IBM i.

Upgrading to Rational Team Concert for Power Systems Software 2.0.0.2

There are several scenarios you can follow to upgrade to Rational Team Concert for Power Systems Software 2.0.

Note:
If you use the IBM Installation Manager to install Rational Team Concert for Power Systems Software 2.0.0.2 on a computer where Rational Team Concert for Power Systems Software 2.0 is not currently installed, the Installation Manager prompts you to select the languages to install. However if you update from 2.0 to 2.0.0.2, the IBM Installation Manager assumes that you want to use the current languages and does not prompt you to select languages. To select the additional languages, after you update to 2.0.0.2, select Modify from the main screen in the IBM Installation Manager, then select the offering. The next screen shows the list of supported languages. Select the ones you need.

If you start the Jazz Team Server after you update to 2.0.0.2 and before you select Modify to add or remove languages, you must reset the server as follows:

  1. In a Web browser, navigate to
    https://<server-host>:<jazz-port>/jazz/admin?internal#action=com.ibm.team.repository.admin.serverReset
  2. Click Request Server Reset.
  3. Shut down the server.

Then you can select Modify in the IBM Installation Manager to add or remove languages.

The process for upgrading to Rational Team Concert for Power Systems Software 2.0.0.2 is similar to upgrading to Rational Team Concert 2.0.0.2. The key steps involved in this process are:

  1. Export the existing Rational Team Concert for i or Rational Team Concert repository using the repository tools from your current version.
  2. Install and configure Rational Team Concert for Power Systems Software 2.0.0.2 including creating a new database.
  3. Import the repository using the Rational Team Concert for Power Systems Software repository tools.
  4. Copy required installation files from a previous server installation.
  5. Install Rational Team Concert for Power Systems Software 2.0.0.2 Activation keys

You can upgrade to Rational Team Concert for Power Systems Software 2.0.0.2 in several ways, including the following scenarios:

  • Upgrade from a v1.0, v1.0.1 or v1.0.1.1 of Rational Team Concert to Rational Team Concert for Power Systems Software 2.0.0.2
  • Upgrade from Rational Team Concert for i 1.0 or 1.0.1.1 to Rational Team Concert for Power Systems Software 2.0.0.2 on IBM i, Windows, or AIX,
  • Upgrade from Rational Team Concert 2.0 to Rational Team Concert for Power Systems Software 2.0.0.2
  • Upgrade from Rational Team Concert for Power Systems Software 2.0 to Rational Team Concert for Power Systems Software 2.0.0.2

Upgrading a Rational Team Concert for Power Systems Software Client for Eclipse IDE

If you have 1.0 or 1.0.1.1 versions of the Rational Team Concert for i Client for Eclipse IDE, it is required that you obtain the Rational Team Concert for Power Systems Software 2.0.x client to connect to your new Rational Team Concert for Power Systems Software 2.0.x server. You can install this using IBM Installation Manager installations.

If you have Rational Team Concert for Power Systems Software 2.0 client, you can update 2.0 to 2.0.0.2 using IBM Installation Manager update.

Note:
Rational Team Concert 2.0.x clients can connect to Rational Team Concert for Power Systems Software 2.0.x servers; however, Rational Team Concert clients will not be able to use Rational Team Concert for Power Systems Software specific functions.

Installing a Rational Team Concert for Power Systems Software Client for Microsoft Visual Studio IDE

If you have 1.0.1.1 version of the Rational Team Concert for i Client for Microsoft Visual Studio IDE, it is required that you obtain the Rational Team Concert for Power Systems Software 2.0.x client to connect to your Rational Team Concert for Power Systems Software 2.0.x Server.

Remember:
A .zip file is not provided for the Rational Team Concert for Power Systems Software 2.0.x Client for Microsoft Visual Studio. To install Rational Team Concert for Power Systems Software 2.0.x Client, you must use IBM Installation Manager.

Upgrading a Server from a trial release to a permanent release

From the 2.0.x trial release, you can make your server permanent by purchasing and installing the Server Activation Kit for your edition, which is available here: http://www.ibm.com/software/rational/products/rtcp/. The activation kit consists of a JAR file containing the permanent server key. It is installed using the License Key Management page of your server's administrative Web interface.

Upgrading a server from Rational Team Concert for i 1.0 or 1.0.1.1

You can upgrade to the 2.0.0.2 release of Rational Team Concert for Power Systems Software from previous releases of Rational Team Concert for i. A database migration is required for 1.x to 2.x updates. For information on performing a database migration, see Migrating the Jazz repository after upgrading the Jazz Team Server for Power Systems Software.

To update Rational Team Concert for i 1.0 or 1.0.1.1 to Rational Team Concert for Power Systems Software 2.0.0.2 of the same edition, complete the following steps:

  1. Before you begin upgrading, reset the server by navigating to https://servername:9443/jazz/admin#action=com.ibm.team.repository.admin.serverReset and clicking Request Server Reset
  2. Stop the server
  3. Export the v1.0 or v1.0.1.1 database contents using repotools
  4. To install Rational Team Concert for Power Systems Software 2.0 on IBM i, see Installing V2.0 Build System Toolkit for Power and Jazz Team Server for Power on IBM i
  5. Copy over the required configuration files from a previous server installation. See Copying the required configuration files from a previous server installation
  6. To apply Rational Team Concert for Power Systems Software 2.0.0.2 PTF on IBM i, see Applying the V2.0.0.2 PTF to Build System Toolkit for Power and Jazz Team Server for Power on IBM i
  7. Create the 2.0.0.2 repository database
  8. Enable the job message queue to wrap when it becomes full by running the command: CHGSYSVAL SYSVAL(QJOBMSGQFL) VALUE(*WRAP)
  9. Import the .tar file created in step 3 into the v2.0.0.2 repository database using repotools.
  10. Re-start the server
  11. To upgrade a WebSphere Application Server deployment of the Jazz Team Server for Power Systems Software 2.0.0.2, see WebSphere Application Server configuration updates
  12. To complete the upgrade, see Installing 2.0 activation keys.

Upgrading a server from Rational Team Concert for Power Systems Software 2.0 on IBM i

You can upgrade to the 2.0.0.2 release of Rational Team Concert for Power Systems Software from Rational Team Concert for Power Systems Software 2.0.

To update Rational Team Concert for Power Systems Software 2.0 to 2.0.0.2 of the same edition, complete the following steps:

  1. Before you begin upgrading, reset the server by navigating to https://servername:9443/jazz/admin#action=com.ibm.team.repository.admin.serverReset and clicking Request Server Reset
  2. Stop the server
  3. To apply Rational Team Concert for Power Systems Software 2.0.0.2 PTF on IBM i, see Applying the V2.0.0.2 PTF to Build System Toolkit for Power and Jazz Team Server for Power on IBM i
  4. Run repotools.qsh -addTables
  5. Re-start the server
  6. To upgrade a WebSphere Application Server deployment of the Jazz Team Server for Power Systems Software 2.0.0.2, see WebSphere Application Server configuration updates

You can upgrade directly to the 2.0.0.2 release of Rational Team Concert for Power Systems Software from 2.0 on Windows and AIX.

Note:
Before you begin upgrading a WebSphere Application Server, reset the server by navigating to https://{servername}:9443/jazz/admin#action=com.ibm.team.repository.admin.serverReset and clicking Request Server Reset.

You can either install 2.0.0.2 as a separate instance or update the previous instance to 2.0.0.2. If you install a separate instance of the server for the 2.0.0.2 release, select Create a new package group on the Install Packages page of the installation wizard.

Note:
To upgrade a WebSphere Application Server deployment of the Jazz Team Server for Power Systems Software 2.0.0.2, update your jazz.war file of the previous version to 2.0.0.2 jazz.war file

To complete the upgrade, see Copying the required configuration files from a previous server installation.

Upgrading a Server from one Rational Team Concert for Power Systems Software edition to another

You can upgrade between Rational Team Concert for Power Systems Software editions. Typical upgrades include moving from Express to Standard. You can also downgrade in the opposite direction by following the same process.

Because all Rational Team Concert for Power Systems Software 2.0.0.2 editions for Windows or AIX support Derby databases, you do not need to migrate from Derby to DB2 or Oracle if you are moving from Express to Standard onWindows or AIX . We recommend that you migrate your server edition first, make sure things work smoothly with the existing database, and then perform a database migration if required. For information on performing a database migration, see .

On IBM i, licensed programs are installed in different IFS directories and there is no intersection among editions.

If you installed your previous edition from a zip file, then there is no intersection with the previous install. You can install the new edition from a zip in a new location, or you can use the IBM Installation Manager install for the new edition. We recommend that the IBM Installation Manager be used for production servers to enable future updates to be applied.

If you used IBM Installation Manager to perform your previous server install, and want to use IBM Installation Manager to install your new edition, during the new Installation Manager install, do not overlay the previous edition. On the Install Packages page of the installation wizard, select Create a new package group.

This will install the new edition in a different location and create program shortcuts using the new package group name.

If you do not perform this task, the installation will fail with a file collision. This occurs if you see an error dialog titled Installation Failed, and the details show the following text:

Installation failed.
  Error during "install" phase:
    Failed to extract zip standard 1.0.1.I20081018-1820.  File
    D:\JazzTeamServer\server\license-update-site\site.xml already exists.

To complete the upgrade, see Copying the required configuration files from a previous server installation and Installing 2.0 activation keys.

WebSphere Application Server configuration updates

The following steps are required to properly configure WebSphere Application Server in Rational Team Concert for Power Systems Software 2.0.

  1. Ensure that the latest fix packs for WebSphere Application Server and the associated Java SDK are installed. If deploying in WebSphere Application Server 7.0, it is critical that at least WebSphere Application Server 7.0.0.3 is installed. With WebSphere Application Server 6.1, it is critical that at least WebSphere Application Server 6.1.0.23 is installed.
  2. To reset Java Virtual Machine parameters for WebSphere Application Server on IBM i, Navigate to JazzInstallDir/jazz/server/script_py and run ./RTCI_JVM.qsh
  3. For WebSphere Application Server on Windows or AIX when updating from 1.x versions, you need to manually reset Java Virtual Machine parameters:
    1. Remove the old custom JVM properties:
      1. com.ibm.team.repository.provision.profile
      2. com.ibm.team.server.configURL
      3. log4j.configuration
    2. Add the new custom JVM property JAZZ_HOME and set the value to:
      file:///JazzInstallDir/server/conf   
  4. Ensure that the WAS security setting "Use available authentication data when an unprotected URI is accessed" is checked. If you are using the WAS Integrated Solutions Console, you can do this by:
    1. Navigating to Security > Secure administration, applications, and infrastructure > Web Security - General Settings
    2. Selecting the checkbox for "Use available authentication data when an unprotected URI is accessed."
  5. Expand Applications in the WAS Integrated Solutions Console, select Enterprise Application and click the Update button to update your jazz.war file of the previous version to 2.0.0.2 jazz.war file

Copying the required configuration files from a previous server installation

Copy the following files from the source server to the target server. First, rename the original files in the upgraded server install to create backups. If you used the IBM Installation Manager to update from 2.0 to 2.0.0.2, a backup directory containing your 2.0 configuration files was created with a name, such as backup-config-timestamp in the server subdirectory of the installation location.

  • workitemindex (directory)
  • teamserver.properties
  • log4j.properties
  • If previous server is installed on IBM i and the upgraded server is installed on the same IBM i machine and you want to re-use the previous WebSphere Application Server instance, copy over RTCi_JVM.qsh
  • If you are using Derby, copy the repositoryDB directory tree.
  • If you are using Tomcat and have changed the configuration, copy over the tomcat/conf directory.
  • If you are using the Tomcat user database, copy over tomcat-users.xml.
  • If you are using Tomcat and you have customized the application deployment descriptor, copy the changes from your modified web.xml file for jazz.war, located in \JazzTeamServer\server\tomcat\webapps\jazz\WEB-INF and reapply them to your new 2.0.0.2-based web.xml.
    Tip:
    In Rational Team Concert for Power Systems Software 2.0, the web.xml file has changed significantly. It is recommended that you start with the new 2.0.x-based web.xml and reapply any changes to the new file rather than copying the old version.

If you are upgrading to Standard or Enterprise edition, and you have purchased the Developer Client Activation Kit for Express, purchase and install the Developer Client Activation Kit for Standard or Enterprise Editions, so that you can use those client licenses. Your Developer license assignments will still be in effect, but the Developer licenses will be deactivated until the correct activation kit is installed.

Installing 2.0 activation keys

The Rational Team Concert for Power Systems Software 2.0.0.2 release uses the Rational Team Concert for Power Systems Software 2.0 activation keys. If a server is upgraded from 1.0.1.1 to 2.0.x or from Rational Team Concert to Rational Team Concert for Power Systems Software, it reverts to a trial license after the upgrade, and you must obtain the Rational Team Concert for Power Systems Software 2.0 activation keys from Passport Advantage. Below are the names of the applicable key zip files for each kit:

  • IBM Rational Team Concert for Power Systems Software Express Edition - Server License Activation Kit V2.0 Multiplatform (RTCpower2.0_server_enterprise_activation_kit.zip)
  • IBM Rational Team Concert for Power Systems Software Express Edition - Developer Client License Activation Kit V2.0 Multiplatform (RTCpower2.0_express_developer_activation_kit.zip)
  • IBM Rational Team Concert for Power Systems Software - Contributor Client License Activation Kit V2.0 Multiplatform (RTCpower2.0_Auth_contributor_activation_kit.zip
  • IBM Rational Team Concert for Power Systems Software Standard Edition - Server License Activation Kit V2.0 Multiplatform (RTCpower2.0_server_standard_activation_kit.zip)
  • IBM Rational Team Concert for Power Systems Software - Standard and Enterprise Edition Developer Client License Activation Kit V2.0 Multiplatform (RTCpower2.0_Std_Ent_Auth_developer_activation_kit.zip)
  • IBM Rational Team Concert for Power Systems Software - Standard and Enterprise Edition Floating Developer Client License Activation Kit V2.0 Multiplatform (RTCpower2.0_Std_Ent_Float_developer_activation_kit.zip)
  • IBM Rational Team Concert for Power Systems Software - Standard and Enterprise Edition Floating Contributor Client License Activation Kit V2.0 Multiplatform (RTCpower2.0_Std_Ent_Float_contributor_activation_kit.zip)
  • IBM Rational Team Concert for Power Systems Software Enterprise Edition - Server License Activation Kit V2.0 Multiplatform (RTCpower2.0_server_enterprise_activation_kit.zip )

Setting a project timeline

In Rational Team Concert 1.x or Rational Team Concert for i 1.x, projects could have multiple timelines (previously called "development lines") and all of these timelines were considered equal.

In Rational Team Concert for Power Systems Software 2.0, projects can still have multiple timelines, but one of them can be marked as the "project timeline." When migrating your database to 2.0, the project's primary timeline is not known, so your projects will not have a project timeline set. You can manually update your projects to set the project timeline, after you upgrade to 2.0

Configuring the Source Control Management snapshot

The Source Control Management (SCM) snapshot for the data warehouse collects data on streams, including information about the size of streams and the activity (change set and file/folder changes) within it. In version 1.x, this snapshot automatically collected information about all streams. As this can be a costly operation, in version 2.0, the configuration options are added to the SCM snapshot to let the users decide for which streams the data should be collected. The immediate impact of this change is that, unless you configure it, no data will be collected.

To configure the Source Control snapshot:

  1. You must have write permissions for the stream that you want to collect data for.
  2. Go to the Reports page in Web UI.
  3. In the left navigation panel, select Administer SCM Snapshot. A list of streams is displayed.
  4. Select the checkbox for one or more streams, and then select Save Changes.

Data will be collected for the selected streams in all subsequent snapshots.

Incompatible changes to BIRT reports

If you have used the BIRT report designer to create your own report templates, you might encounter problems when trying to use these reports in version 2.0. You should be aware of the following issues:

  • Changes to the order in which Java and JavaScript classes are resolved: If you have written JavaScript code in your BIRT report that uses the importPackage() statement to import the java.lang package, be aware that unqualified references to Object in the code, which previously referred to the Java class, might now refer to the JavaScript class and as a result will not work properly. Other classes that are identically named between JavaScript and Java, such as java.util.Date, might have the same problem. The solution is to fully qualify your reference to the Java class and remove the importPackage() statement.
  • Changes to the processing of data sets: In the past, the act of binding an element (such as a Label) to a data sets, caused the data set to be processed in its entirety when the element was rendered. This was useful because it meant you could enforce an ordering to data set processing by using (hidden) labels bound to the data sets in the order they should be processed. Now, such a binding will process only the first row of the data set. To get the previous behavior, use a Dynamic Text element and invoke some JavaScript code, which will force processing of the entire data set. Total.count() is a good choice.
  • BIRT report designer bugs can cause loss of data: These problems appear when you open a BIRT report design file created in BIRT 2.2.2 (RTC 1.0) with the BIRT 2.3.2 (RTC 2.0) report designer. The following issues have been observed:
    • When editing a data set for the first time with BIRT 2.3.2, on the "Parameters" page, the "Default Value" and "Report Parameter" fields may be lost. The workaround is to re-enter the values, or to copy and paste the values from a previous version of the editor. After saving the file with the new values entered, the problem will not recur.
    • When editing a report design file for the first time with BIRT 2.3.2, the default value for report parameters may be lost. This may also occur after the previous problem described. The workaround is to re-enter the values, or to copy and paste the values from a previous version of the editor. After saving the file with the new values entered, the problem will not recur.

    These issues can be very serious if not noticed, as the data gathered by the report could be incorrect. It is a good practice to check each data set and each report parameter when editing a report for the first time with the BIRT 2.3.2 report designer. These problems do not occur for new reports that are created with the BIRT 2.3.2 tools.

    The above changes are made to all Rational Team Concert for Power Systems Software 2.0 out-of-the-box reports. No action is required on your part. However, if you have manually created report templates in your project area using our out-of-the-box reports, and have not specified an appropriate identifier (consistent with our usage), your report template will not be refreshed when it is migrated. That is, the content will be out of date, and will not work. In that case, you should upload new content for the affected templates, using the appropriate out-of-the-box .rptdesign file.

Import of the Work Items data in the data warehouse

In Rational Team Concert for Power Systems Software 2.0.x, there are several schema changes to the work items tables in the data warehouse. As a consequence, when migrating from 1.x to 2.0.x, the importer will ignore any warehoused work items data. As a result, when you start the 2.0.x server for the first time, your work items reports might not function correctly. The workaround is either to wait for the work items snapshot to run for the first time, or to manually cause it to run after you start the server. On the first run after migration, the work items snapshot will reconstitute the entire historical work items information in the data warehouse. This also means that the first run of the snapshot after migration is likely to take much longer than an average nightly run.

Discovering new reports

In Rational Team Concert for Power Systems Software 2.0.x, several new reports are added. While these reports appear in the new process templates that ship with the product, they are not automatically added to the existing project areas on migration. We have added a new action that will help you to discover and deploy these new report templates in your existing project areas after migration. To deploy new report templates:

  1. In the Eclipse client, open the Team Artifacts view.
  2. Expand your project area, expand Reports.
  3. Right-click Report Templates and select Deploy New Templates.

The dialog will help you to discover any report templates that are available but not already deployed to your project area. You can select one or more of them and they will be created. After creation, you can create new reports from those templates using the available menu actions.

Customizations

Changes that you make to work item types, attributes, workflows, roles, and event handlers are preserved when you upgrade from 1.x to 2.0.x. If you customized a predefined process template (such as Scrum), be aware that if you redeploy the predefined template (in the Process Templates view), you will overwrite your customizations. If you need to redeploy the predefined template, you should first change the name and ID of the predefined template that you customized, so it will not be overwritten.

RTC Power: Installation overview

Information to help you understand the requirements for a successful installation.

  1. Choose a Rational Team Concert for Power Systems Software edition.
  2. Plan your installation and complete the optional installation planning worksheet.
  3. Install the Jazz Team Server for Power Systems Software. On IBM i, you are required to install the Build System Toolkit for Power Systems Software prior to installing the server.
  4. Optional: Set up the application server, LDAP server, and database.
  5. Configure the Jazz Team Server for Power Systems Software.
  6. Install the Rational Team Concert for Power Systems Software client.
  7. Optional: Install the Build System Toolkit for Power Systems Software.
  8. Optional: Install the ClearCase Connector and ClearQuest Connector.

RTC Power: Planning the installation

Information that helps you plan the installation.

RTC Power: Installation planning overview

There are several things to consider when planning your installation.

  • Choose a Rational Team Concert for Power Systems Software edition.
  • Review the supported operating environments.
  • Optional: Fill out the planning worksheet.
    Note:
    By default, the Jazz Team Server for Power Systems Software is configured to work without additional configuration on AIX and Windows. On IBM i, you have to configure Jazz Team Server for Power with IBM WebSphere Application Server. If you plan to enable any of the supported application servers, databases or optional features, use the planning worksheet to guide you through your installation and configuration decisions and details.
  • Review the special considerations.

RTC Power: Installation planning worksheet

This worksheet helps you plan a successful installation and choose your custom configuration options.

The following table lists the choices and information you might need to provide during the installation and setup process. This table helps in filling out forms while installing and setting up your server.

Table 1. Installation planning worksheet
Determine your needs and configuration details Installation considerations and some example answers

Choose an edition.

  • Rational Team Concert for Power Systems Software Express edition
  • Rational Team Concert for Power Systems Software Standard edition
  • Rational Team Concert for Power Systems Software Enterprise edition

How many Client Access Licenses (CALs) do you need?

Note:
Each user needs to be assigned a Client Access License in order to perform certain functions within Rational Team Concert for Power. See Client Access Licenses for a listing of actions allowed for each Client Access License type. To configure CALs for each user on a server running on AIX or Windows, see Managing client access licenses. To configure CALs for each user on a server running on IBM i, see Managing user access licenses.
  • Contributor
  • Developer
  • Build System
  • ClearCase Connector
  • ClearQuest Connector

Verify your server environment is supported.

Record the server information

  • Hostname: jazzserver.example.com
  • IP address: 192.168.1.1
  • Platform: IBM i 6.1

Choose an application server (not applicable for IBM i).

Note:
On IBM i, Rational Team Concert for Power only supports IBM WebSphere Application Server. You can not choose any other application server.

The following instructions are applicable for AIX and Windows. They not applicable for IBM i.

Choose an application server:

  • Apache Tomcat (included)
  • IBM WebSphere Application Server

If you are installing Jazz Team Server for Power Systems Software to use with IBM WebSphere Application Server, record the following information:

  • Web application directory:
    • Windows: Program Files\IBM\JazzTeamServer\server (default)
    • AIX: /opt/IBM/JazzTeamServer/server (default)

If the default ports conflict with ports that are already in use, list the ports you use instead.

  • http port: 9080 (default)
  • https port: 9443 (default)

Choose a database and connection type (not applicable for IBM i).

Note:
On IBM i, Rational Team Concert for Power only supports DB2 for i which is already part of the operating system. You can not choose any other database.
Note:
Although a Derby database is included in the default configuration and requires no installation, this database cannot support more than 10 users. If you want to support more than 10 users and do not have access to an existing DB2 or Oracle database, install the bundled DB2 Workgroup Server edition.

The following instructions are applicable for AIX, Windows and Linux. They are not applicable for IBM i.

Database Information:

  • Derby (default)
  • DB2 Workgroup Server (included)
  • DB2
  • Oracle

On IBM i, only DB2 for i is supported.

Database connection type:

  • JDBC
    • JDBC Password: db2admin
    • JDBC Location: //localhost:50000/JAZZ:fullyMaterializeLobData=false (default)
    • User name: db2admin
  • J2EE
    • J2EE Datasource: jdbc/mydatasource

Database location:

  • Database port: 50000
    Tip:
    In the DB2 Command Window, run the command db2 get dbm cfg, then find the line that contains SVCENAME, which indicates the DB2 port name or number. If this command displays a number, use it as the port number (in place of 50000 in the example above). If the command returns a non-numeric name, determine what port number was assigned for this name and use that port number. On Linux, the file /etc/services contains the mapping between port names and numbers, and on Windows, the file C:\windows\system32\drivers\etc\services contains the mapping. For more information, ask your database administrator or consult the database documentation.
    Tip:
    If you are installing DB2 Workgroup Server, accepting the defaults during the installation simplifies the Jazz Team Server for Power Systems Software configuration.

How do you want to manage the users?

Identity management option:

  • Apache Tomcat user database realm (not applicable for IBM i)
    • User ID: username
    • Name: Full Name
    • E-mail Address: username@example.com
  • LDAP
    • LDAP Registry Location: ldap://ldap.example.com:389
    • User Name: username
    • Password: SecretPassword
    • Base User DN: o=[company],l=[your city],c=[your country]
    • User Property Names Mapping: userId=mail,name=cn,emailAddress=mail
    • Base Group DN: ou=memberlist,ou=yourgroups,o=example.com
    • Jazz to LDAP Group Mapping: JazzAdmins= YourGroupA, JazzUsers= YourGroupB, JazzDWAdmins= YourGroupC, JazzGuests= YourGroupD, JazzProjectAdmins= YourGroupE
    • Group Name Property: cn
    • Group Member Property: uniquemember
  • Non-LDAP custom realm
    • User ID: username
    • Name: Full Name
    • User roles: JazzAdmins, JazzUsers, JazzDWAdmins, JazzGuests, JazzProjectAdmins
      Note:
      You need to set up groups that can be mapped to the Jazz J2EE security roles.

Optional: Do you want to enable e-mail notification?

SMTP Server details

  • SMTP Server: smtp.example.com
  • SMTP Username: EmailUserName
  • SMTP Password: SecretPassword
  • Mail From Address: you@example.com
  • Mail From Name: Your Mail Name
  • SMTP Reply Address: from@example.com
  • SMTP Server Port: 25
  • Use STARTTLS: True or False

Do you plan to enable the e-mail whitelist to restrict e-mail notifications? For example, *@example.com only allows e-mails to your company e-mail addresses.

Optional: Do you want to enable the Jabber chat server?

Jabber Server details

  • Server URL: jabberserver.example.com
  • Port: 5222 or 5223

Verify that your client environment is supported.

Do you want to use the ClearCase Connector or ClearQuest Connector?

RTC Power: Choosing an application server

This information addresses some considerations for choosing an application server on AIX and Windows. On IBM i, Rational Team Concert for Power only supports IBM WebSphere Application Server. You can not choose any other application server.

The Jazz Team Server for Power Systems Software includes Apache Tomcat as the default application server.

If you already have Apache Tomcat installed, the Jazz Team Server for Power Systems Software can be configured to run in your existing environment.

The Jazz Team Server for Power Systems Software can also be configured to run with a WebSphere Application Server.

Apache Tomcat:

  • Supported on all editions.
  • Simple installation and no setup required. Apache Tomcat is installed and configured with default Jazz Team Server for Power Systems Software.

WebSphere Application Server:

  • Supported on all editions.
  • Supports a more powerful user registry setup. You can configure WAS to allow users to log in from either a local user registry and a LDAP registry at the same time.

RTC Power: Choosing a database

This information addresses some considerations for choosing a database. On IBM i, Rational Team Concert for Power only supports DB2 for i which is already part of the operating system. You can not choose any other database.

The Jazz Team Server for Power Systems Software includes Derby as the default database.

Note:
Although a Derby database is included in the default configuration and requires no installation, this database cannot support more than 10 users. If you want to support more than 10 users and do not have access to an existing DB2 or Oracle database, install the bundled DB2 Workgroup Server edition.

All editions of Rational Team Concert for Power Systems Software include a version of DB2 Workgroup Server Edition.

If you are already using DB2 or Oracle in your environment, the Jazz Team Server for Power Systems Software can be configured to run with your existing database software.

RTC Power: Special DB2 instructions

Review the following information when using a DB2 database. Note, however, that the information is not applicable for DB2 for i.

Note:
Commands listed in this topic are only examples. Consult your product documentation for details.
Note:
An 8 KB page size is required when creating a database in DB2.

Review the DB2 documentation to verify your system meets the requirements and is configured correctly.

To take advantage of state-selection fetching optimization, which can improve performance on large databases, DB2 users must set DB2_OPTPROFILE. Run the following commands to set DB2_OPTPROFILE.

db2set DB2_OPTPROFILE=YES
db2stop
db2start
Note:
After the command runs, stop and restart the database. A later step in the installation process requires you to stop and start the database. If you are just beginning the installation, you can restart the database then.

Make sure all the above succeed. To see if it is set run the command:

db2set DB2_OPTPROFILE

RTC Power: Choosing a user management method

Choose one of the following user management options.

RTC Power: Managing users with Apache Tomcat user database

The default user management enables you to manage users without any external user management system. Managing users with the Apache Tomcat user database is for Apache Tomcat installations only. Since Rational Team Concert for Power Systems Software does not support Apache Tomcat on IBM i, this user management system is not available when running the server on IBM i.

The user names and encrypted passwords are stored in the tomcat-users.xml file. Updates, such as, creating a new user and changing user passwords or repository permission roles are automatically written to the xml file. You do not need to edit the file.

Note:
The file is located in JazzInstallDir/server/tomcat/conf.
RTC Power: Managing users with Lightweight Directory Access Protocol (LDAP)

This information helps you configure your LDAP registry to manage users.

If you plan to use an LDAP registry with your Jazz Team Server for Power Systems Software, you must configure your Apache Tomcat (only supported on AIX and Windows) or WebSphere Application Server to use an LDAP registry to authenticate users.

To configure LDAP to work with Jazz Team Server for Power Systems Software, follow these tasks:

  1. Understanding the LDAP configuration parameters.
  2. LDAP configuration setup process.
  3. Configure the Web container for LDAP in Apache Tomcat.
    Note:
    The Jazz Team Server for Power Systems Software user identity is case sensitive. When using LDAP for user management, turn off the case-insensitive option. Work with your server administrator or consult your product documentation to ensure that the settings are case-sensitive.
  4. Configure the WebSphere Application Server with LDAP realm.
  5. Create an initial user. This user is the initial Jazz Team Server for Power Systems Software administrator.
  6. Using the LDAP sync task.
  7. Use the setup wizard to configure the Jazz Team Server for Power Systems Software to use LDAP.
  8. Import the users.

Understanding the LDAP configuration parameters

Table 2. LDAP Parameters and descriptions
Parameter Value description
LDAP Registry Location The URL that references your LDAP server. ldap://ldap.example.com:389
User Name The user name to log in to this LDAP server. Some LDAP servers allow anonymous login and password. In this case, this parameter is blank.
Password The password associated with the user name.
Base User DN The search base indicates where in the hierarchy to begin the search for the users. For example, "o=company,l=your city,c=your country"
User Property Names Mapping The mapping of Jazz user property names to LDAP registry entry attribute names. You must define the following mappings:
  • userId =[LDAP user ID]
  • name =[LDAP user name]
  • emailAddress =[LDAP user e-mail]

The userid property identifies the user ID that is used when a user logs into the system. The name property is used to render the name in the user interface.

For example, userId=mail,name=cn,emailAddress=mail

Base Group DN This search base indicates where in the hierarchy to begin the search of group names, for example, ou=memberlist,ou=yourgroups,o=example.com
Jazz to LDAP Group Mapping The mapping between Jazz groups and LDAP groups. One Jazz group can be mapped to multiple LDAP groups. The LDAP groups must be separated by a semicolon. For example, JazzAdmins=LDAPAdmins1;LDAPAdmins2 maps JazzAdmins group to LDAPAdmins1 and LDAPAdmins2. Jazz Team Server for Power Systems Software defines 4 groups to map with:
  • JazzAdmins =[LDAP Group for Jazz admins]
  • JazzUsers =[LDAP Group for Jazz users]
  • JazzDWAdmins =[LDAP Group for Jazz Data Warehouse Admin]
  • JazzGuests =[LDAP Group for Jazz guest]
  • JazzProjectAdmins =[LDAP Group for Jazz project admins]
For example, JazzAdmins= YourGroupA, JazzUsers= YourGroupB, JazzDWAdmins= YourGroupC, JazzGuests= YourGroupD, JazzProjectAdmins= YourGroupE.
Group Name Property The LDAP Property that represents the name of the Jazz groups in the LDAP registry. For example, cn. This is used in the query to retrieve an LDAP group. To retrieve an LDAP group, a query uses a combination of the Base group DN and the Group Name Property.
Group Member Property The LDAP Property that represent the members of a group in the LDAP registry. For example, uniquemember.

LDAP configuration setup process

To configure LDAP connection and import users follow these steps:

  1. Stop the server.
  2. If you have previously tried to install your LDAP server, backup the JazzInstallDir/jazz/server/tomcat/conf/server.xml file.
  3. Open the JazzInstallDir/jazz/server/tomcat/conf/server.xml file for editing and uncomment the following realm tag:
    <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
                 resourceName="UserDatabase" 
                 digest="SHA-1"
                 digestEncoding="UTF-8"/>
  4. Save the file and restart the server.
  5. Open a Web browser window and go to https://localhost:9443/jazz/setup.
  6. Login with ADMIN/ADMIN (both username and password are case sensitive).
  7. Click the Custom Setup button.
  8. click Next until you reach page 5, Setup User Registry.
  9. In the Step 1 section under Type, select the Tomcat User Database radio button.
  10. Under Step 3, select the checkbox for Disable default ADMIN access.
  11. Under Step 4, Select the checkbox for Rational Team Concert - Developer license.
  12. Click Next to create this first user.
  13. Click Previous to go back to page 5, Setup User Registry.
  14. Under Step 1, select the LDAP radio button.
  15. Fill out the fields in Section 2. For more information, see Understanding the LDAP configuration parameters.
  16. Shut down the server.
  17. Configure the Web container for LDAP in Apache Tomcat.
  18. Restart the server.
  19. Open a Web browser window and go to https://localhost:9443/jazz/admin.
  20. Login with the user ID that you created to test your connection.

Configure the Web container for LDAP in Apache Tomcat

For additional information about configuring Apache Tomcat for LDAP, see the related links below. To configure the Web container for LDAP in Apache Tomcat follow these steps:

  1. Open the JazzInstallDir/jazz/server/tomcat/conf/server.xml file for editing and comment the following tag:
    <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
                 resourceName="UserDatabase" 
                 digest="SHA-1"
                 digestEncoding="UTF-8"/>
  2. Add the following tag for Oracle Internet Directory (OID):
    <Realm className="org.apache.catalina.realm.JNDIRealm" 
     debug="99"
     connectionURL="ldap://ldap.company.com:389"
     roleBase="cn=Groups,dc=company,dc=com"
     roleSearch="(uniquemember={0})" 
     roleName="cn"
     userBase="cn=Users,dc=company,dc=com"
     userSearch="(uid={0})"/>
    Add the following tag for Microsoft Active Directory:
    <Realm className="org.apache.catalina.realm.JNDIRealm" 
     debug="99"
     connectionURL="ldap://ldap.company.com:3268"
     authentication="simple"
     referrals="follow"
     connectionName="cn=LDAPUser,ou=Service Accounts,dc=company,dc=com"
     connectionPassword="VerySecretPassword" 
     userSearch="(sAMAccountName={0})"
     userBase="dc=company,dc=com" 
     userSubtree="true"
     roleSearch="(member={0})" 
     roleName="cn" 
     roleSubtree="true"
     roleBase="dc=company,dc=com"/>
  3. Open the JazzInstallDir/jazz/server/tomcat/webapps/jazz/WEB-INF/web.xml file for editing and link and map the security role references to the security roles:
    <web-app id="WebApp">
    <servlet id="bridge">
    <servlet-name>equinoxbridgeservlet</servlet-name>
    <display-name>Equinox Bridge Servlet</display-name>
    <description>Equinox Bridge Servlet</description>
    <servlet-class>org.eclipse.equinox.servletbridge.BridgeServlet</servlet-class>
    <init-param><!-- ... --></init-param>
    <!-- ... -->
    <load-on-startup>1</load-on-startup>
    
    <!-- Addendum
    If the names of your LDAP Groups are the same as the default Jazz roles
    you don't need to add the following tags
    -->
    <security-role-ref>
    <role-name>JazzAdmins</role-name>
    <role-link>[LDAP Group for Jazz admins]<role-link>
    </security-role-ref>
    
    <security-role-ref>
    <role-name>JazzDWAdmins</role-name>
    <role-link>[LDAP Group for Jazz Data Warehouse admins]<role-link>
    </security-role-ref>
    
    <security-role-ref>
    <role-name>JazzGuests</role-name>
    <role-link>[LDAP Group for Jazz guests]<role-link>
    </security-role-ref>
    
    <security-role-ref>
    <role-name>JazzUsers</role-name>
    <role-link>[LDAP Group for Jazz users]<role-link>
    </security-role-ref>
    
    <security-role-ref>
    <role-name>JazzProjectAdmins</role-name>
    <role-link>[LDAP Group for Jazz project admins]<role-link>
    </security-role-ref>
    
    </servlet>
    <!-- ... -->
    </web-app>
    Use the following tags to declare the LDAP groups as security roles:
    <web-app id="WebApp">
    <servlet id="bridge">
    <!-- ... -->
    <security-role>
    <role-name>JazzAdmins</role-name>
    <role-name>JazzDWAdmins</role-name>
    <role-name>JazzGuests</role-name>
    <role-name>JazzUsers</role-name>
    <role-name>JazzProjectAdmins</role-name>
    
    <!-- Addendum
    If the names of your LDAP Groups are the same as the default Jazz roles
    you don't need to add the following tags
    -->
    <role-name>[LDAP Group for Jazz Admins]</role-name>
    <role-name>[LDAP Group for Jazz Data Warehouse Admins]</role-name>
    <role-name>[LDAP Group for Jazz Guests]</role-name>
    <role-name>[LDAP Group for Jazz Users]</role-name>
    <role-name>[LDAP Group for Jazz Project Admins]</role-name>
    
    <!-- End Addendum -->
    </security-role>
    <!-- ... -->
    </web-app>
    Use the following tags to update the security-constraint section:
    <web-app id="WebApp">
    <!-- ... -->
    <security-constraint>
    <web-resource-collection>
    <web-resource-name>secure</web-resource-name>
    <url-pattern>/*</url-pattern>
    </web-resource-collection>
    
    <auth-constraint>
    <role-name>JazzUsers</role-name>
    <role-name>JazzAdmins</role-name>
    <role-name>JazzGuests</role-name>
    <role-name>JazzDWAdmins</role-name>
    <role-name>JazzProjectAdmins</role-name>
    
    <!-- Addendum
    If the names of your LDAP Groups are the same as the default Jazz roles
    you don't need to add the following tags
    -->
    
    <role-name>[LDAP Group for Jazz Admins]</role-name>
    <role-name>[LDAP Group for Jazz Data Warehouse Admins]</role-name>
    <role-name>[LDAP Group for Jazz Guests]</role-name>
    <role-name>[LDAP Group for Jazz Users]</role-name>
    <role-name>[LDAP Group for Jazz Project Admins]</role-name>
    
    <!-- End Addendum -->
    
    </auth-constraint>
    
    <user-data-constarint>
    <transport-guarantee>CONFIDENTIAL</transport-guarantee>
    </user-data-constraint>
    </security-constraint>
    <!-- ... -->
    </web-app>
    Repeat the same addendum on each security-constraint referencing a Jazz group:
    <web-app id="WebApp">
    <!-- ... -->
    <security-constraint>
    <web-resource-collection>
    <web-resource-name>adminsecure</web-resource-name>
    <url-pattern>/admin/cmd/*</url-pattern>
    </web-resource-collection>
    <auth-constraint>
    <role-name>JazzAdmins</role-name>
    <!-- Addendum -->
    <role-name>[LDAP Group for Jazz Admins]</role-name>
    <!-- End addendum -->
    </auth-constraint>
    <user-data-constraint>
    <transport-guarantee>CONFIDENTIAL</transport-guarantee>
    </user-data-constraint>
    </security-constraint>
    <!-- ... -->
    </web-app>

RTC Power: Managing users with a custom realm

Configure authentication and group membership in IBM WebSphere Application Server or Apache Tomcat.

Jazz Team Server for Power Systems Software uses J2EE security roles for authentication, access to protected resources, and authorization for some repository operations. These roles are mapped to users and groups within a realm configured in the application server. When the server is configured to use the Apache Tomcat user database realm (only supported on AIX and Windows) or an LDAP realm, Jazz Team Server for Power Systems Software can import users from the realm into the repository and display the roles (groups) that a user has. It is possible to configure your own realm for authentication and group membership in IBM WebSphere Application Server or Apache Tomcat. When you use that option, Jazz Team Server for Power Systems Software cannot import users or display their roles, but those roles are used for authentication and authorization. The local operating system realm for authentication in IBM WebSphere Application Server is an example of a custom realm.

RTC Power: Special server instructions

Some server environments have special configuration considerations.

If your configuration includes one or more of the application servers or operating systems listed below, review the information before you begin installing.

RTC Power: Security certificates

The Jazz Team Server for Power Systems Software includes a self-signed certificate for SSL with the Apache Tomcat server. Note that the Apache Tomcat server is only supported on AIX and Windows.

Some browsers and clients might display a warning when accessing your Jazz repository. To stop the warnings, do one of the following:

  • Purchase a certificate from a well-known trusted Certificate Authority and install it.
  • If you do not need encryption, configure the server for HTTP rather than HTTPS access.
RTC Power: Installing a security certificate

Replace the self-signed certificate with a certificate that belongs to your company.

  • Configure an Apache Tomcat security certificate (supported only on AIX and Windows).

    In the file, JazzInstallDir/server/tomcat/conf/server.xml, Apache Tomcat is configured to read the server's certificate from JazzInstallDir/server/tomcat/ibm-team-ssl.keystore. The default keystore password is set to, ibm-team. This keystore includes a self-signed certificate identifying the server as "localhost".

    Note:
    To improve security, change the default keystore password.

    The IBM JRE included with Jazz Team Server for Power Systems Software includes an IBM tool that is useful for managing keys on the server. The tool iKeyman is located in the directory JazzInstallDir/server/jre/bin/ (ikeyman.exe on Windows).

    The ikeyman tool can help you create your own self-signed certificate identifying the host by its proper network name or you can request a certificate signed by a trusted certificate authority (CA). A self-signed certificate will require acceptance by the Team Concert client or web browser.

    For more information see, http://download.boulder.ibm.com/ibmdl/pub/software/dw/jdk/security/50/GSK7c_SSL_IKM_Guide.pdf .

  • Configure a WebSphere Application Server security certificate.

    For more information on see,

RTC Power: Disabling security certificate settings

If you do not require secure connections, the security settings can be disabled.

About this task

Important:
The information below explains how to disable the SSL certificate. Following these steps allows unencrypted connections to the server, including user login credentials. If you require secure connections, create your own self-signed certificate identifying the host by its proper network name, or request a certificate signed by a trusted certificate authority (CA).
Modifying the Apache Tomcat settings (only supported on AIX and Windows)

  1. Make sure you have started Apache Tomcat at least once already.
  2. Go to the JazzInstallDir/server/tomcat/webapps/jazz/WEB-INF directory.
  3. Edit the web.xml file in this directory and change all occurences of "CONFIDENTIAL" to "NONE".
  4. Go to the JazzInstallDir/server/tomcat/conf directory and edit server.xml.
  5. Remove the redirectPort attribute from the 9080 Connector element so that the element appears as follows:
    <Connector port="9080" maxHttpHeaderSize="8192" 
      maxThreads="150" minSpareThreads="25" maxSpareThreads="75" 
      enableLookups="false" acceptCount="100" 
      connectionTimeout="20000" disableUploadTimeout="true" 
      URIEncoding="UTF-8"/>
  6. Restart Apache Tomcat.
  7. Verify that you can login using http://localhost:9080/jazz/admin and do not get redirected to https://localhost:9443/jazz/admin.
Modifying the WebSphere Application Server settings

  1. Modify the web.xml from the jazz .war file that was installed into WebSphere Application Server. You may need to extract the jazz .war file into a temporary area first to get to the file.
  2. Change all occurrences of "CONFIDENTIAL" to "NONE" (There should be 3).
  3. Make sure WebSphere Application Server is running and goto https://localhost:9043/ibm/console/logon.jsp.
  4. Goto the Applications -> Enterprise Applications page.
  5. Select the jazz_war application and click the Update button.
  6. Select the "Replace or add a single file" radio button option.
  7. In the "Specify the path beginning with the installed application archive file to the file to be replaced or added." entry field, enter "jazz.war/WEB-INF/web.xml".
  8. Click the browse button and select the same web.xml that was modified in an earlier step.
  9. Click next and follow through until the application has been saved.
  10. Go back to the Applications->Enterprise Applications page and stop and start the jazz_war application.
  11. Verify that you can login using http://localhost:9080/jazz/admin and not get redirected to https://localhost:9443/jazz/admin.

Installing Rational Team Concert for Power Systems Software Express edition

RTC Power: Express edition installation overview

The installation package includes everything you need to get started.

This section covers the installation of the Rational Team Concert for Power Systems Software Express edition on AIX and Windows. For installation on i, see Installing Rational Team Concert for Power Systems Software on IBM i.

The default configuration includes these items:

  • The supported versions of a Java Development Kit (JDK) for Windows and AIX.
  • A working image of Apache Tomcat Web application server that contains the Jazz Web application.
  • A Derby database and all necessary database libraries.
    Important:
    Using Jazz Team Server for Power Systems Software with a Derby database supports up to 10 users. To support more than 10 users, use a DB2 Workgroup Server, DB2 or Oracle database. DB2 Workgroup Server is included with the Enterprise, Standard, and Express edition installation packages when you use the IBM Installation Manager. If you use the .zip file installation method, the DB2 Workgroup Server download is available on the same site as the Rational Team Concert for Power Systems Software download. After DB2 Workgroup Server is installed, you must install and configure it as described in the installation setup guide.
Note:
An optional planning worksheet is available within the online help to help you choose your configuration and record your decisions.

RTC Power: Installing the Express edition

To get started, obtain the installation files.

About this task

The Jazz Team Server for Power Systems Software, Rational Team Concert for Power Systems Software client, Build System Toolkit for Power Systems Software, ClearCase Connector, ClearQuest Connector and other incubator files can be downloaded from https://jazz.net. To purchase Rational Team Concert for Power Systems Software, go to http://www.ibm.com/software/rational/products/rtcp/, where you can download an installable image or order a DVD. To purchase Rational Developer for Power Systems Software, go to http://www.ibm.com/software/rational/products/rdp/, where you can download an installable image or order a DVD.

RTC Power: Installing the Express edition from the IBM Installation Manager

After obtaining the installation files, start the installation.

About this task

The Jazz Team Server for Power Systems Software, Rational Team Concert for Power Systems Software client, Build System Toolkit for Power Systems Software, ClearCase Connector, ClearQuest Connector and other incubator files can be downloaded from https://jazz.net. To purchase Rational Team Concert for Power Systems Software, go to http://www.ibm.com/software/rational/products/rtcp/, where you can download an installable image or order a DVD. To purchase Rational Developer for Power Systems Software, go to http://www.ibm.com/software/rational/products/rdp/, where you can download an installable image or order a DVD.

  1. Download one of the following installation packages.

    There are two methods to install Rational Team Concert for Power Systems Software Express edition by using IBM Installation Manager.

    • Installation Manager local install for server, build system toolkit and optional components .zip file: This archive file contains the Installation Manager launchpad program and a local copy of all the installable resources for server, build system toolkit and DB2 workgroup server. This method allows the installation to proceed without an Internet connection once the .zip file is downloaded. This is not a self-extracting .zip file.
  2. Start the launchpad program.

    If the Installation Manager is not running, start it.

    Note:
    You must have administrator privileges to run the launchpad program.
    • If you are using the Installation Manager local install for server, build system toolkit and optional components .zip file, extract the contents of the archive into a temporary directory and run the launchpad program.
      • To run the file on Windows, run this command:
        launchpad.exe
      • To run the file on AIX, run this command:
        sh launchpad.sh
  3. When the launchpad program starts you see a list of items to install. Install each package that you want to use in the order listed.
    1. Install the Jazz Team Server for Power Systems Software.

      When using the IBM Installation Manager, note the Installation Directory on the Location page during the installation process. The directory is referred to as JazzInstallDir.

      Note:
      If you are planning to use an existing application server, instead of the included Apache Tomcat server, clear the Apache Tomcat package check box. Doing so, installs only the files required to use with your existing application server. The Installation Manager prompts you to choose a location to install these files.
    2. Optional: Install DB2 Workgroup Server.
      Note:
      Although a Derby database is included in the default configuration and requires no installation, this database cannot support more than 10 users. If you want to support more than 10 users and do not have access to an existing DB2 or Oracle database, install the bundled DB2 Workgroup Server edition.

      If you install DB2 Workgroup Server, record the user ID, password and port number. This information is needed later. Accepting the defaults during the installation simplifies the Jazz Team Server for Power Systems Software configuration.

    3. Install the Rational Team Concert for Power Systems Software client.
    4. Optional: Install the Build System Toolkit for Power Systems Software.

RTC Power: Installing the Express edition from the .zip file

After obtaining the installation files, extract the contents.

About this task

The Jazz Team Server for Power Systems Software, Rational Team Concert for Power Systems Software client, Build System Toolkit for Power Systems Software, ClearCase Connector, ClearQuest Connector and other incubator files can be downloaded from https://jazz.net. To purchase Rational Team Concert for Power Systems Software, go to http://www.ibm.com/software/rational/products/rtcp/, where you can download an installable image or order a DVD. To purchase Rational Developer for Power Systems Software, go to http://www.ibm.com/software/rational/products/rdp/, where you can download an installable image or order a DVD.

Note:
When using the compressed archive files to complete installation, record the directory in which you extract the files. The directory is referred to as JazzInstallDir.

  1. Download the .zip file for Rational Team Concert for Power Systems Software Express edition server to your computer.
  2. Extract the contents of the package to your file system.
  3. Optional: Install DB2 workgroup Server.
    Note:
    While a Derby database is included in the default configuration and requires no installation, this database has a 10 user limit. You should install the bundled DB2 Workgroup Server if you have a need to support more than 10 users and do not have access to an existing DB2 or Oracle database.

    If you install DB2 Workgroup Server, record the user ID, password and port number. This information is needed later. Accepting the defaults during the installation simplifies the Jazz Team Server for Power Systems Software configuration.

RTC Power: Setting up the database

After your database is installed, configuration work is required.

Fast path:
If you are using the included Derby database no additional setup is necessary. Proceed to RTC Power: Starting the server.

The overview steps for setting up a database are:

  1. Create a database.
  2. Configure the properties files.
  3. Create the database tables.

If you are using any supported DB2 editions, proceed to RTC Power: Setting up a DB2 database.

If you are using Oracle, proceed to RTC Power: Setting up an Oracle database.

If you are using SQL Server, proceed to RTC Power: Setting up a SQL Server database.

RTC Power: Setting up a DB2 database

Set up a supported DB2 or the bundled DB2 Workgroup Server database to work with the Jazz Team Server for Power Systems Software.

Before you begin

This procedure assumes the following prerequisites have been met. Consult your DB2 documentation or a DB2 database administrator (DBA) for help.

  • Review the DB2 documentation to verify your system meets the requirements and is configured correctly.
  • DB2 is installed and running on a machine to be used as the database server. This machine can be a different one from that on which the Jazz Team Server for Power Systems Software runs.
  • You reviewed Special DB2 instructions.
  • The user performing these instructions has system admin authority on the DB2 database.
    Tip:
    On Linux, to get system admin authority on the DB2 database, sudo to the DB2 user db2fenc1 and run bash.

About this task

To set up a DB2 database:

  1. Create the database in the DB2 Command Window. The example commands create a new database called JAZZ. These commands run in the DB2 Command Window. The Command Window can be opened from the application Start menu under the DB2 Command Line Tools menu.
    • On Windows:
      db2 create database JAZZ on c: using codeset UTF-8 territory en PAGESIZE 8192
    • On Linux:
      db2 create database JAZZ using codeset UTF-8 territory en PAGESIZE 8192
    Note:
    To ensure proper handling of Unicode content, the database character set must be UTF-8 encoding. Because the AUDITABLE_LINKS table does not fit in the default page size of 4K on Windows, set the page size to at least 8K.
    Tip:
    If the database is not running, the command db2start starts DB2.
  2. Locate the file teamserver.properties in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.derby.properties.
  3. Locate the file teamserver.db2.win32.properties on Windows or teamserver.db2.linux.properties on Linux in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.properties.
  4. Specify the database and connection details in the file teamserver.properties.

    The default connection specification connects to a DB2 database that runs on localhost on port 50000. On Windows, the database is called JAZZ, and both the user name and password are db2admin. If the default values were used when setting up your database, the teamserver.properties file might already be configured correctly. If not, change this information to match your configuration.

    1. Open the file teamserver.properties in a text editor.
    2. Locate the following lines:
      com.ibm.team.repository.db.vendor = DB2
      com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
      com.ibm.team.repository.db.jdbc.password=db2admin
    3. Edit the value of com.ibm.team.repository.db.jdbc.location for your DB2 server and database.
      Tip:
      In the DB2 Command Window, run the command db2 get dbm cfg, then find the line that contains SVCENAME, which indicates the DB2 port name or number. If this command displays a number, use it as the port number (in place of 50000 in the example above). If the command returns a non-numeric name, determine what port number was assigned for this name and use that port number. On Linux, the file /etc/services contains the mapping between port names and numbers, and on Windows, the file C:\windows\system32\drivers\etc\services contains the mapping. For more information, ask your database administrator or consult the database documentation.
    4. Edit the value of com.ibm.team.repository.db.jdbc.location for your DB2 user name.
      Note:
      The DB2 user must have permissions to create tables, tablespaces, and modify the database configuration. DB2 users are created by the operating system.
    5. Specify the user password in the property com.ibm.team.repository.db.jdbc.password.
      Note:
      Do not change the password={password} text in the com.ibm.team.repository.db.jdbc.location property.
    6. If necessary, change the property com.ibm.team.repository.db.db2.content.tablespace.location to a path on your Jazz Team Server for Power Systems Software where the main tablespace can be created.
      Note:
      If this value is not changed from the default of content_tablespace, the tablespace is created under the database storage location. On Windows, if a new path is specified, it must be specified by using double backslashes, for example: com.ibm.team.repository.db.db2.content.tablespace.location=c:\\db2\\jazz\\content_tablespace.

Results

You are finished setting up your database. Continue with Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle.

RTC Power: Setting up an Oracle database

Set up an Oracle database to work with the Jazz Team Server for Power Systems Software.

Before you begin

This assumes the following prerequisites have been met. Consult your Oracle documentation or an Oracle database administrator (DBA) for help.

  • Oracle is installed on a machine to be used as the database server. This machine can be a different one from that on which the Jazz Team Server for Power Systems Software runs.
  • A default database exists on the Oracle server.
    Tip:
    When you install Oracle, you have the option to create a database automatically.
    Important:
    To ensure proper handling of Unicode content, the database character set must be UTF-8 encoding.
  • The user who performs these instructions has system administration authority on the Oracle database.

When running Jazz Team Server for Power Systems Software on Oracle, create an Oracle tablespace to improve performance. You must create a user linked to that tablespace.

Remember:
Neither of these steps are performed by the database builder with the repository tools.

About this task

To set up an Oracle database:

  1. Create a tablespace. The tablespace location must be appropriate to the machine and disk drive.
    Note:
    The tablespace can have any of these properties:
    • A name other than oracle_tbs
    • A location in another directory
    • A size larger than 1GB. For large installations, you need to allocate more space.
    The example below shows a create statement executed on a Windows machine:
    CREATE BIGFILE TABLESPACE oracle_tbs DATAFILE 'D:\oracle_tbs\oracle_tbs.dbf' SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    Important:
    The directory path (in this example D:\oracle_tbs) must exist. It is not necessary to create a separate special tablespace. You can use the Oracle default USERS tablespace, but Oracle performs better with a pre-allocated space on the disk that it manages.
  2. Create an Oracle user.

    After the tablespace is created, a special Oracle user must be created for Jazz to use the Oracle database.

    In this example, the user has the name jazzDBuser and password (IDENTIFIED BY in Oracle terms) jazzDBpswd and exists in the tablespace created in 1.
    CREATE USER jazzDBuser IDENTIFIED BY jazzDBpswd DEFAULT TABLESPACE oracle_tbs
    After the user is created, the user should be given the necessary permissions needed to initialize the Jazz database. The following SQL commands can be used to grant the appropriate permissions:
    GRANT CREATE SESSION TO jazzDBuser;
    GRANT CREATE TABLE, ALTER ANY TABLE, DROP ANY TABLE, CREATE ANY INDEX, ALTER ANY INDEX, DROP ANY INDEX TO jazzDBuser;
    GRANT INSERT ANY TABLE, UPDATE ANY TABLE, DELETE ANY TABLE TO jazzDBuser;
    GRANT CREATE PROCEDURE TO jazzDBuser;
    GRANT CREATE VIEW TO jazzDBuser;
  3. Locate the file teamserver.properties in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.OtherDBProvider.properties.
  4. Locate the file teamserver.oracle.properties in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.properties.
    Tip:
    Renaming the original teamserver.properties file enables you to restore the file to the previous working version. By default, the DB Provider is derby.
  5. Configure the server
    1. Edit the server configuration file if you used a different user name, password, or db name, installed Oracle server on a different machine than Jazz Team Server for Power Systems Software, or are using a port other than the default. Open the file teamserver.properties in JazzInstallDir/server/conf/jazz directory, and change the information listed below to match your setup.

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

      com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@localhost:1521/ORCL

      Change jazzDBuser with the user created for Jazz to use the Oracle database. If you are using localhost, uncomment this line by removing # from the beginning of the line and comment the next location line. Localhost connection strings should not include the preceding //. Change 1521 with your Oracle server machine TCIP port. Change ORCL with your Oracle database name.

      com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@//oracleserver.example.com:1521/ORCL

      If you are using a non-localhost connection, uncomment this line by removing the # from the beginning of the line and comment the previous location line. Non-localhost connection strings must include the preceding //.

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

      Change jazzDBpswd with the password of the user created for Jazz to use the Oracle database.

      Important:
      Do not change the {password} text in the property com.ibm.team.repository.db.jdbc.location. The user password must be specified in the property com.ibm.team.repository.db.jdbc.password.

      If you are using Oracle Express, use 1521 for TCIP port and XE for Oracle database name:

      com.ibm.team.repository.db.vendor = ORACLE
      com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@localhost:1521/XE
      com.ibm.team.repository.db.jdbc.password=jazzDBpswd
    2. In the same directory as the server scripts (JazzInstallDir/server), create a directory named oracle.
    3. Locate the Oracle JDBC driver JAR file, named ojdbc14.jar. The location can vary depending on the Oracle product and operating system. Copy this file to the directory named oracle.
      Note:
      If you are using WebSphere Application Server, configure a property named "ORACLE_JDBC"; then set it to the absolute file path (not URL) to the Oracle JDBC drivers. This task is described in the WebSphere Application Server setup instructions. Make a note of the file path for later use in these instructions.

Results

You are finished setting up your database and can continue with Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle.

RTC Power: Setting up a SQL Server database

Set up a SQL Server database to work with the Jazz Team Server for Power Systems Software.

This procedure assumes that the following prerequisites have been met:

  • You have SQL Server installed
  • SQL Server service is started
  • You have the SQL Server JDBC drivers installed. For more information, see http://msdn2.microsoft.com/en-us/data/aa937724.aspx
  • The TCP protocol is enabled for SQL Server
  • The user who creates the DB table must have one of the following permissions:
    • A membership in the sysadmin fixed server role, or ownership of the database (dbo)
Remember:
The default login name defined in JazzInstallDir/server/teamserver.properties file for a SQL Server database is jazzDBuser and the default password is jazzDBpswd. These values are used in the steps below for creating a database. You can substitute these values with the user name and password for your database.

Setting up a database

This section describes how to set up the SQL Server database by using the command line tool sqlcmd, which is provided with the SQL Server installation. You can also use a visual tool, such as SQL Server Studio Management, which is also available for the Express version as SQL Server Studio Management Express. See the SQL Server documentation or an SQL Server database administrator (DBA) for more information.

To set up an SQL Server database by using the command tool sqlcmd:

  1. Create a Jazz Team Server for Power Systems Software database. From the command line tool, type:
    CREATE DATABASE jazz 
    GO 
  2. Create a user and password and change the ownership of the Jazz Team Server for Power Systems Software database. From the command line tool, type:
    CREATE LOGIN jazzDBuser
    WITH PASSWORD = 'jazzDBpswd';
    USE jazz;
    exec sp_changedbowner 'jazzDBuser'
    GO 
  3. Change the collation of the Jazz Team Server for Power Systems Software database. From the command line tool, type:
    ALTER DATABASE jazz COLLATE SQL_Latin1_General_CP437_CS_AS 
    GO

Configuring the server

Remember:
By default, the teamserver.properties file in JazzInstallDir/server/conf/jazz directory is not set up to connect to a SQL Server database. All default settings, along with SQL Server-specific settings, are contained in the teamserver.sqlserver.properties file in the same directory.

To configure the server:

  1. Rename the following files:
    • Rename the JazzInstallDir/server/conf/jazz/teamserver.properties file to teamserver.OtherDBProvider.properties
    • Rename the teamserver.sqlserver.properties file to teamserver.properties
    Tip:
    Renaming the original teamserver.properties file enables you to restore the file to the previous working version. By default, the DB Provider is derby.
  2. Edit the server configuration file if you used a different user name, password, or db name, installed SQL server on a different machine than Jazz Team Server for Power Systems Software, or are using a port other than the default. Open the file teamserver.properties in JazzInstallDir/server/conf/jazz directory, and change the information listed below to match your setup.
    com.ibm.team.repository.db.vendor = SQLSERVER
    com.ibm.team.repository.db.jdbc.location=//SQL SERVER MACHINE IP:SQL SERVER TCIP PORT;databaseName=JAZZ DATABASE NAME;user=JAZZ USERNAME;password={password}
    com.ibm.team.repository.db.jdbc.password=JAZZ LOGIN PASSWORD
    Important:
    Do not change the password={password} text in the property com.ibm.team.repository.db.jdbc.location. The user password must be specified in the property com.ibm.team.repository.db.jdbc.password.

To specify the jar file location for JDBC:

  1. In the same directory as the server scripts (JazzInstallDir/server), create a directory named sqlserver.
  2. Locate the SQL Server JDBC driver JAR file, named sqljdbc.jar. The location can vary depending on where the drivers were installed, as noted in the prerequisites section. Copy the file into the newly created sqlserver directory.
  3. Specify the JDBC JAR file location for JDBC by completing the following task:
    • Set up the environment variable SQLSERVER_ABSPATH to point to the directory that contains the JAR file. If the path contains space characters, you must include them with quotations.
      Tip:
      If you use WebSphere Application Server, configure a property named SQLSERVER_JDBC; then set it to the absolute file path (not URL) to the SQL Server JDBC drivers directory. For more information, see the WebSphere Application Server setup instructions. Note the file path for later use in these instructions.

You have completed setting up your database. Now, create the Jazz Team Server for Power Systems Software database tables. For more information, see Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle.

Troubleshooting

If the repotools command does not succeed, check the log file named repotools_createTables.log, located in the JazzInstallDir/server directory.

Also, verify the following:

  • The SQL Server is configured to allow connections using the TCP/IP protocol. If required, restart the SQL service.
  • The SQL Server machine host name, and the port is correctly reflected in the teamserver.properties file.
  • The login name, password, and database name are properly reflected in the teamserver.properties file.
  • A firewall does not prevent you from accessing the SQL Server. Use a telnet command to telnet to the machine using hostname and port from the teamserver.properties file.
  • The created user has proper permissions in the Jazz Team Server for Power Systems Software database.
Note:
The database code for Jazz Team Server for Power Systems Software was designed to be generic and standard in order to run on multiple database platforms; however, differences between the enterprise database vendors exist in syntax, optimization strategies, and locking semantics. The server has been tested on SQL Server using a combination of automated tests and simulations of normal workloads and stress testing. The simulation of normal workloads showed acceptable performance. In some instances database deadlocks have been observed in automated concurrency tests; however, these have not been consistently reproduced on different server hardware.

The server is designed to service a large number of simultaneous requests. In exceptional cases, deadlocks can occur in the repository database, as similar or equal objects are updated concurrently in transactions associated with the requests. These are rare, but normal events. The system is designed to be defensive against this, and data integrity is maintained; there is no loss of data. Occasionally, deadlocks are logged by tasks, such as build engine execution. Generally, the condition is detected, and the task is re-tried. The deadlock can result in a failed build. In very rare cases, it can be a user action, such as working with work items or source code, that is aborted to resolve a deadlock. In that case, the user action fails and an error with details regarding a deadlock is displayed to the user. The user can then retry the action.

All deadlocks encountered are logged on the server to provide information about what happened when the deadlock occurred. The log entry has text similar to the following: com.ibm.team.repository.common.RetryableDatabaseException: Serialization failure.

If your system encounters deadlocks, see the error log, which is available at https://servername:9443/jazz/service/com.ibm.team.repository.common.internal.IFeedService?category=SystemLog.

If you encounter frequent deadlock exceptions, contact your product support, or check the forums on jazz.net for the latest information, updates, or mitigating techniques.

Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle

Create the database tables using the repository tools.

About this task

To create the database tables:

  1. Run the command repotools -createTables to create the database tables for a Jazz repository.

    The repotools file is located in JazzInstallDir/server.

    The command uses the configuration properties in teamserver.properties for the connection and size settings. By default, the command looks in the current directory. The parameter teamserver.properties can be used to reference a different properties file.

    • On Windows:
      repotools -createTables
    • On AIX:
      ./repotools.sh -createTables
    This command creates the tablespace and all the required tables and indexes for a Jazz Team Server for Power Systems Software repository.
  2. After the database tables are created, you must stop and restart the database to make sure all changes are in effect.
    Tip:
    DB2 only. Example commands that stop and start DB2 are db2stop and db2start. These commands are run at the DB2 Command Window. The Command Window can be opened from the application start menu under the DB2 Command Line Tools cascade menu.

Results

You are finished setting up your database and can continue with RTC Power: Starting the server.

RTC Power: Starting the server

This topic describes the different options for running the server startup scripts.

About this task

If you plan to use the included Apache Tomcat application server, you are ready to start the Jazz Team Server for Power Systems Software.

If you plan to use the WebSphere Application Server, set up your server environment as described in RTC Power: Setting up a WebSphere Application Server.

RTC Power: Starting the Apache Tomcat server

You are now ready to start the Apache Tomcat server.

Apache Tomcat has been installed in the directory JazzInstallDir/server/tomcat. The Web application (jazz.war) has been installed in the Apache Tomcat directory webapps. In a command window, set your current directory to JazzInstallDir/server. The server startup and shutdown scripts are located in this directory.

  • If you want to run the start and stop scripts from any other directory, you must change the profiles.ini file in JazzInstallDir/server/conf/jazz/provision_profiles to use an absolute path.
  • Apache Tomcat is configured to use the ports 9080 and 9443 in file JazzInstallDir/server/tomcat/conf/server.xml. If necessary, change them as appropriate for your system. If necessary, also update the configuration settings of Jazz server Repository HTTP ports in the Advanced Properties configuration page of in the Jazz Admin Web UI.
  • The directory JazzInstallDir/server/logs contains the server log files. If you have trouble starting the server, check the log files.
  • The JazzInstallDir/server/tomcat/conf/server.xml file contains SSL settings that specify an algorithm only available in the IBM JRE. To run the server with a Sun JRE, in the server.xml file, change the settings for Connector port="9443", so that sslProtocol="TLS" instead of "SSL". Also remove the algorithm parameter.

Starting the server on Windows

Run the startup file to start your server on Windows.

About this task

  1. To start the server, from the JazzInstallDir/server directory, run this command:
    server.startup.bat
    Note:
    A separate Apache Tomcat console window opens. Do not close this window or the server will stop working. Also, several informational messages launch, including a message about the Apache Tomcat Native Library. These informational messages do not affect the Jazz Team Server for Power Systems Software functionality.
  2. To stop the server, from the JazzInstallDir/server directory, run this command:
    server.shutdown.bat

What to do next

Note:
The example above runs the start and stop scripts directly from the directory JazzInstallDir/server. If you installed Jazz Team Server for Power Systems Software using IBM Installation Manager, you can also run the commands from the Jazz Team Server for Power Systems Software Windows start menu.

After the server is started, proceed to RTC Power: Running the setup wizard.

Starting the server on AIX

Run the startup file to start the server on AIX.

About this task

  1. To start the server, from the JazzInstallDir/server directory, as user root, run this command:
    ./server.startup
    If your user ID has administrator access, run this command:
    sudo ./server.startup

    A separate Apache Tomcat console window is not visible. You can check the server startup progress by viewing the log file at JazzInstallDir/server/logs/jazz.log.

  2. To stop the server, from the JazzInstallDir/server directory, as user root, run this command:
    ./server.shutdown
    If your user ID has administrator access, run this command:
    sudo ./server.shutdown

What to do next

Note:
This example runs the start and stop scripts directly from the directory JazzInstallDir/server. If you installed Jazz Team Server for Power Systems Software by using IBM Installation Manager, you can also run the commands from the Jazz Team Server for Power Systems Software application start menu.

After the server is started, proceed to RTC Power: Running the setup wizard.

Running Jazz Team Server for Power Systems Software in Apache Tomcat as a Windows service

Apache Tomcat has the ability to run as a Windows service. This can be useful if you want to run the Jazz Team Server for Power Systems Software on a Windows-based machine without having to be logged on.

Before you begin

This topic assumes that your Jazz Team Server for Power Systems Software deployment is rooted at C:\jazz; adjust your paths accordingly based on your actual root directory.

  1. Open a command prompt and execute the following command to install the Tomcat service.
    C:\jazz\server\tomcat\bin\service.bat install
  2. If you are using Derby as your database for your Jazz Repository, edit C:\jazz\server\conf\jazz\teamserver.properties to make the DB location an absolute path. For example, change the value of db.jdbc.location to C:\jazz\server\repositoryDB.
  3. Execute C:\jazz\server\tomcat\bin\tomcat5w.exe to configure the service.
  4. Click the Java tab and clear the check box for Use default.
  5. Add the following path to Java Virtual Machine. You can also click the ellipsis icon to browse for the jvm.dll file.
    C:\jazz\server\jre\bin\j9vm\jvm.dll
  6. Add the following lines at the bottom of the Java Options text field
    -DJAZZ_HOME=file:///c:/jazz/server/conf
    -Djava.awt.headless=true 
    -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true 
    -Dcom.ibm.team.repository.tempDir=%TEMP%
    If you are using Oracle database, add the following line:
    -DORACLE_JDBC=[path to Oracle JDBC driver jar]
    If you are using SQL Server database, also add the following line:
    -DSQLSERVER_JDBC=[path to SQL Server JDBC driver jar]
  7. Change the Maximum memory pool size to 700.
  8. On the Startup and Shutdown tabs, make sure that jvm is selected for the Mode setting.
  9. Click the General tab and change the Startup type to Automatic if you want to start the service automatically when Windows starts.
  10. Start the service to test the server.

Deploying Jazz Team Server for Power Systems Software into an existing Apache Tomcat

This topic describes how to setup the Jazz Team Server for Power Systems Software to work with your existing Apache Tomcat server.

About this task

To deploy the jazz.war file into your existing Apache Tomcat server, follow these steps:

  1. Copy the jazz.war file from JazzInstallDir to your tomcat\webapps directory.
  2. Open your tomcat startup file for editing and add the following system property settings:
    set CATALINA_OPTS=-Dcom.ibm.team.server.configURL=file:///"%cd%"/teamserver.properties -Dlog4j.configuration=file:///"%cd%"/log4j.properties 
    set JAVA_OPTS=-Djava.awt.headless=true -DORACLE_JDBC="%ORACLE_JDBC%" -DDB2I_JDBC="%DB2I_JDBC%" -DDB2Z_JDBC="%DB2Z_JDBC%" -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -Dcom.ibm.team.repository.provision.profile="%cd%"\provision_profiles -Dcom.ibm.team.repository.tempDir=%TEMP% -Xmx700M
  3. Save and close the startup file.
  4. Open and edit the teamserver.properties file to point to your database.
  5. Save and close teamserver.properties.

RTC Power: Setting up a WebSphere Application Server

This topic describes how to set up the Jazz Team Server for Power Systems Software to work with WebSphere Application Server. This setup assumes that you are installing the Jazz Team Server for Power Systems Software on the same machine as the Websphere Application Server.

Before you begin

Before beginning these steps, you should have the following completed:

  • WebSphere Application server is already installed.
  • The database is created and the teamserver.properties file is updated with your database settings.
  • Refer to your WebSphere documentation for security setup and turn off the case-insensitive property.
    Note:
    Although Websphere and many LDAP directories allow you to log in case-insensitive, Jazz Team Server for Power Systems Software stores user records with user IDs in exact case as they are imported. When you log in to the Jazz Team Server for Power Systems Software, the user record is retrieved from the list of users and the case must match exactly.
  • Java 2 Security option should be turned off. If this option is turned on in WebSphere Application Server it will cause the Jazz Team Server for Power Systems Software .war to fail to start.
  • Ensure that the WAS security setting "Use available authentication data when an unprotected URI is accessed" is checked. If you are using the WAS Integrated Solutions Console, you can do this by:
    1. Navigating to Security -> Secure administration, applications, and infrastructure -> Web Security - General Settings.
    2. Selecting the checkbox for "Use available authentication data when an unprotected URI is accessed".
  • The Jazz Team Server for Power Systems Software includes the files required to run a complete Apache Tomcat-based server. For a WebSphere installation you only need a subset of the Jazz Team Server for Power Systems Software files and you should place them in a directory on your WebSphere server machine. Further instructions refer to this as the Jazz Team Server for Power Systems Software installation directory, or JazzInstallDir for short. From this directory, use:
    • The file JazzInstallDir/server/tomcat/webapps/jazz.war.
    • The directory JazzInstallDir/server/update-site.
    • The directory JazzInstallDir/server/conf.
    • The default repository database in JazzInstallDir/repositoryDB.
    • The repository tools in JazzInstallDir/repotools.
    • The directory JazzInstallDirserver/license-update-site.
    • The directory JazzInstallDir/server/nl1-update-site.
    • The directory JazzInstallDir/server/nl2-update-site.
Tip:
When using the IBM Installation Manager the Jazz Team Server for Power Systems Software files can be installed into a Web application directory. During the installation process, you should not install the included Apache Tomcat application server; this makes the Installation Manager ask for a Web Application directory and install only the files needed for WebSphere. The default directory is C:\Program Files\IBM\JazzTeamServer on Windows or /opt/IBM/JazzTeamServer on AIX. The installation directory is referred to as JazzInstallDir in this procedure. If you use the IBM Installation Manager to install the files into the WebSphere Application Server Web applications directory, then you do not need to manually move the files as described above.

About this task

Note:
This document does not teach the configuration of WebSphere authentication or SSL, which is a complex topic. Detailed information about the various authentication and encryption options for WebSphere is covered in the WebSphere Information Center. For more information, go to the WebSphere Information Center and search for Securing applications and their environment. The Jazz Web UI requires that authentication be configured in order to perform authorization and personalize the application.

  1. Review and update the database location in the teamserver.properties file
    com.ibm.team.repository.db.vendor = DB2
    com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
    com.ibm.team.repository.db.jdbc.password=db2admin
    Note:
    This is a sample DB2 configuration. The teamserver.properties should be updated depending on the database vendor (Oracle/MS-SQL).
  2. Verify or update the WebSphere Application Server level.

    Jazz Team Server for Power Systems Software requires WebSphere Application Server Version 6.1 with the IBM Java SDK 1.5 SR5 or later Cumulative Fix applied or WebSphere Application Server Version 7.0 with at least 7.0.0.3 installed. The IBM Java SDK 1.5 SR6 SDK update is available from http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24017492. With WebSphere 6.1 and the GA IBM Java SDK, Jazz starts to report "proxy errors" after some number of operations.

    You must obtain the corresponding WebSphere Application Server i-fixes for fixes to IBM Java SDK 1.5 SR9 or IBM Java SDK 1.6 SR4 that are necessary for IBM Rational Team Concert for Power Systems Software 2.0 to run correctly. Otherwise, some services in the server might not start correctly. The i-fixes are available under their corresponding WebSphere Application Server APARs. For IBM Java SDK 1.5/WebSphere Application Server 6.1, the APAR is PK85942 and you can download the files from ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixes/PK85942/. Install at least WebSphere Application Server 6.1 fixpack 19 before installing the JRE i-fix. For IBM Java SDK 1.6/WebSphere Application Server 7.0, the APAR is PK 86771 and you can download the files from ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixes/PK86771/.

  3. Update the JVM arguments.

    The Jazz Team Server for Power Systems Software needs some specific settings on the Java Virtual Machine in which it is run.

    First, it needs to know where to find some configuration files. This is done by setting a system property JAZZ_HOME. This property uses a URL rather than a simple path, so the value should be specified as a file://-style URL.

    The second property which is required for the Jazz JVM is to provide it with more than the default maximum memory allocation, using the -Xmx setting. This should be set based on the size of the team supported by the server and the memory capacity of the server where Jazz Team Server for Power Systems Software is running. A typical medium-size team can use a value of -Xmx1000M, providing 1000 MB of heap memory for the Jazz Team Server for Power Systems Software process.

    If you are connecting to an Oracle or SQL Server database then you need to add a property named "ORACLE_JDBC" or "SQLSERVER_JDBC". Set the property to the absolute file path (not a URL) to the appropriate jdbc drivers.

    There are a couple other system properties which need to be set to control some behavior of the server, they are included below. Here are the specifics of setting these JVM properties in the WebSphere Administrative Console, substitute JazzInstallDir with your Jazz Team Server for Power Systems Software installation directory:

    1. Click on Servers -> Application Servers.
    2. Click on server1.
    3. Click on Java and Process Management -> Process Definition.
    4. Click on Java Virtual Machine.
    5. Add the value 100 to the Initial Heap.
    6. Add the value 1000 to the Maximum Heap Size.
    7. Click Apply.
    8. Click Logging and Tracing. Click Change Log Detail Levels. The Jazz Team Server for Power Systems Software uses the BIRT reporting engine. To prevent BIRT informational entries from being written to the WebSphere log file, set the logging level to severe for the org.eclipse.birt.* packages. Click Apply.
    9. Click Custom Properties
    10. Add the following properties: Click New; enter the Name and Value; then click OK.
      • Name: java.awt.headless Value: true
      • Name: org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin Value: true
      • Name: JAZZ_HOME Value: file:///JazzInstallDir/server/conf
    11. Click Save directly to the master configuration.
  4. Restart Websphere to install the Jazz Application

    In the following command line examples, WASInstallDir represents the location where WebSphere Application Server is installed on your server.

    • On Windows, the default value for WebSphere installation directory is:
      C:\Program Files\IBM\WebSphere\AppServer

      You can restart the server with the following commands on Windows:

      cd WASInstallDir\bin 
      stopServer.bat server1 [for a secure server, include: -username {LDAP_User} -password {LDAP_Password}] 
      startServer.bat server1
    • On AIX, the default value for WebSphere installation directory is:
      /opt/IBM/WebSphere/AppServer

      You can restart the server with the following commands on AIX:

      cd WASInstallDir/bin 
      ./stopServer.sh server1 [for a secure server, include: -username {LDAP_User} -password {LDAP_Password}] 
      ./startServer.sh server1
    1. Open the Admin console for your WebSphere Application Server.
    2. Click on Applications -> Install New Application.
    3. Under Path to new Application, click Local file system.
    4. Under Full path enter:
      JazzInstallDir/server/jazz.war
    5. Set Context Root to /jazz.
    6. Click Next and continue through the remaining Install New Application steps.
    7. Click Finish.
    8. Click Save directly to the master configuration.
    9. Click on Applications -> Enterprise Applications.
    10. Select the box next to jazz_war; click Start.

      A green arrow should appear indicating the application started successfully.

What to do next

After the server is started, proceed to RTC Power: Running the setup wizard.

For more information about this topic visit the following links:

https://jazz.net/library/techtip/321

https://jazz.net/wiki/bin/view/Main/WASSetupFAQ

RTC Power: Running the setup wizard

Running the setup wizard verifies that the server is operating properly and guides you through the steps configure the server.

About this task

To verify that the Jazz Team Server for Power Systems Software is connecting to the database, look at the server log or console output. The connection and database information is echoed on its first access. The directory JazzInstallDir/server/logs is used for the server log files.

This procedure assumes your server is available using the hostname localhost and the default ports 9443. If necessary, replace localhost with your server hostname and replace the port 9443.

Start the setup wizard to configure your server. Use the URL https://localhost:9443/jazz/setup.
The default user name and password are case-sensitive:

  • The user name is ADMIN.
  • The password is ADMIN.

If you configured the LDAP directory Web container, log in with a JazzAdmin user that is defined in your LDAP directory.

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

  • The Fast Path Setup uses the default configuration. If you want to get the server running quickly, the fast path setup is a good option. During the Fast Path Setup, setup
    • the user registry.
  • The Custom Setup guides you through the detailed server configuration, including the ability to enable e-mail notifications. During the Custom Setup, you set up the following items:
    • Database
    • E-mail notification
    • User registry
    Note:
    By default, the server is configured to use Derby as the database. To use another database, such as DB2, select the custom setup path and complete Step 2: Configure Database.


When the initial setup is complete, additional options can be configured from the Jazz Team Server for Power Systems Software Admin Web user interface by using the URL https://localhost:9443/jazz/admin.

What to do next

If the server setup wizard does not load, check the following items:

  • Verify that the application server has started. Use the URL http://localhost:9080.
  • Verify the Jazz Team Server for Power Systems Software has started by logging in to the Jazz Team Server for Power Systems Software Admin Web UI using the URL https://localhost:9443/jazz/admin. If the page does not load or the server has errors, the server did not start correctly. See the troubleshooting information at Troubleshooting server issues.
  • The URI root for the Jazz Team Server for Power Systems Software path must be /jazz. For example https://example.com:9443/jazz must be used rather than https://example.com:9443.

RTC Power: Completing the installation

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

About this task

After the installation, there are a few additional actions to take.

  • 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.
    • teamserver.properties - The Jazz Team Server for Power Systems Software requires that the database password is stored in JazzInstallDir/server/conf/jazz/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.

  • When connecting to the server with the Rational Team Concert for Power Systems Software client or a Web browser, you might see security certificate warnings. To disable the warning, see RTC Power: Security certificates.
  • 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 for Power Systems Software client or a Web browser.

  • Related concepts
  • RTC Power: Security certificates
    The Jazz Team Server for Power Systems Software includes a self-signed certificate for SSL with the Apache Tomcat server. Note that the Apache Tomcat server is only supported on AIX and Windows.

Installing Rational Team Concert for Power Systems Software Standard edition and Enterprise edition

RTC Power: Standard and Enterprise editions installation overview

The installation package includes everything you need to get started.

This section covers the installation of the Rational Team Concert for Power Systems Software Standard and Enterprise editions on AIX and Windows. For installation on i, see Installing Rational Team Concert for Power Systems Software on IBM i.

The default configuration includes:

  • The supported versions of a Java Development Kit (JDK) for Windows and AIX.
  • A working image of Apache Tomcat Web application server containing the Jazz Web application.
  • A Derby database and all necessary database libraries.
    Important:
    Using Jazz Team Server for Power Systems Software with a Derby database supports up to 10 users. To support more than 10 users, use a DB2 Workgroup Server, DB2 or Oracle database. DB2 Workgroup Server is included with the Enterprise, Standard, and Express edition installation packages when you use the IBM Installation Manager. If you use the .zip file installation method, the DB2 Workgroup Server download is available on the same site as the Rational Team Concert for Power Systems Software download. After DB2 Workgroup Server is installed, you must install and configure it as described in the installation setup guide.
Note:
An optional planning worksheet is available within the online help to help you choose your configuration and record your decisions.

RTC Power: Installing the Standard or Enterprise edition

To get started, you need to obtain the installation files.

About this task

The Jazz Team Server for Power Systems Software, Rational Team Concert for Power Systems Software client, Build System Toolkit for Power Systems Software, ClearCase Connector, ClearQuest Connector and other incubator files can be downloaded from https://jazz.net. To purchase Rational Team Concert for Power Systems Software, go to http://www.ibm.com/software/rational/products/rtcp/, where you can download an installable image or order a DVD. To purchase Rational Developer for Power Systems Software, go to http://www.ibm.com/software/rational/products/rdp/, where you can download an installable image or order a DVD.

RTC Power: Installing the Standard or Enterprise edition from the IBM Installation Manager

After obtaining the installation files, start the installation.

About this task

The Jazz Team Server for Power Systems Software, Rational Team Concert for Power Systems Software client, Build System Toolkit for Power Systems Software, ClearCase Connector, ClearQuest Connector and other incubator files can be downloaded from https://jazz.net. To purchase Rational Team Concert for Power Systems Software, go to http://www.ibm.com/software/rational/products/rtcp/, where you can download an installable image or order a DVD. To purchase Rational Developer for Power Systems Software, go to http://www.ibm.com/software/rational/products/rdp/, where you can download an installable image or order a DVD.

  1. Download one of the following installation packages. Choose the platform you are installing on.

    There are two methods to install Rational Team Concert for Power Systems Software Standard edition or Enterprise Edition by using IBM Installation Manager.

    • Installation Manager local install for server, build system toolkit and optional components .zip file: This archive file contains the Installation Manager launchpad program and a local copy of all the installable resources for server, build system toolkit and DB2 workgroup server. This method allows the installation to proceed without an Internet connection once the .zip file is downloaded. This is not a self-extracting .zip file.
  2. Start the launchpad program.

    If the Installation Manager is not running, start it.

    Note:
    You must have administrator privileges to run the launchpad program.
    • If you are using the Installation Manager local install for server, build system toolkit and optional components .zip file, extract the contents of the archive into a temporary directory and run the launchpad program.
      • To run the file on Windows, run this command:
        launchpad.exe
      • To run the file on AIX, run this command:
        sh launchpad.sh
  3. When the launchpad program starts, you see a list of items to install. Install each package that you want to use in the order listed.
    1. Install the Jazz Team Server for Power Systems Software.

      When using the IBM Installation Manager, note the Installation Directory on the Location page during the installation process. The directory is referred to as JazzInstallDir.

      Note:
      If you are planning to use an existing application server, instead of the included Apache Tomcat server, clear the Apache Tomcat package check box. Doing so, installs only the files required to use with your existing application server. The Installation Manager prompts you to choose a location to install these files.
    2. Optional: Install DB2 Workgroup Server.
      Note:
      Although a Derby database is included in the default configuration and requires no installation, this database cannot support more than 10 users. If you want to support more than 10 users and do not have access to an existing DB2 or Oracle database, install the bundled DB2 Workgroup Server edition.

      If you install DB2 Workgroup Server, record the user ID, password and port number. This information is needed later. Accepting the defaults during the installation simplifies the Jazz Team Server for Power Systems Software configuration.

    3. Install the Rational Team Concert for Power Systems Software client.
    4. Optional: Install the Build System Toolkit for Power Systems Software.
    5. Optional: Install the ClearCase Connector.
    6. Optional: Install the ClearQuest Connector.

RTC Power: Installing the Standard or Enterprise edition from the .zip file

After obtaining the installation files, extract the contents.

About this task

The Jazz Team Server for Power Systems Software, Rational Team Concert for Power Systems Software client, Build System Toolkit for Power Systems Software, ClearCase Connector, ClearQuest Connector and other incubator files can be downloaded from https://jazz.net. To purchase Rational Team Concert for Power Systems Software, go to http://www.ibm.com/software/rational/products/rtcp/, where you can download an installable image or order a DVD. To purchase Rational Developer for Power Systems Software, go to http://www.ibm.com/software/rational/products/rdp/, where you can download an installable image or order a DVD.

Note:
When using the compressed archive files to complete installation, record the directory in which you extract the files. The directory is referred to as JazzInstallDir.

  1. Download the .zip file for Rational Team Concert for Power Systems Software Standard edition server or Enterprise edition server to your computer.
  2. Extract the contents of the package to your file system.
  3. Optional: Install DB2 Workgroup Server.
    Note:
    While a Derby database is included in the default configuration and requires no installation, this database has a 10 user limit. You should install the bundled DB2 Workgroup Server if you have a need to support more than 10 users and do not have access to an existing DB2 or Oracle database.

    If you install DB2 Workgroup Server, record the user ID, password and port number. This information is needed later. Accepting the defaults during the installation simplifies the Jazz Team Server for Power Systems Software configuration.

RTC Power: Setting up the database

After your database is installed, configuration work is required.

Fast path:
If you are using the included Derby database no additional setup is necessary. Proceed to RTC Power: Starting the server.

The overview steps for setting up a database are:

  1. Create a database.
  2. Configure the properties files.
  3. Create the database tables.

If you are using any supported DB2 editions, proceed to RTC Power: Setting up a DB2 database.

If you are using Oracle, proceed to RTC Power: Setting up an Oracle database.

If you are using SQL Server, proceed to RTC Power: Setting up a SQL Server database.

RTC Power: Setting up a DB2 database

Set up a supported DB2 or the bundled DB2 Workgroup Server database to work with the Jazz Team Server for Power Systems Software.

Before you begin

This procedure assumes the following prerequisites have been met. Consult your DB2 documentation or a DB2 database administrator (DBA) for help.

  • Review the DB2 documentation to verify your system meets the requirements and is configured correctly.
  • DB2 is installed and running on a machine to be used as the database server. This machine can be a different one from that on which the Jazz Team Server for Power Systems Software runs.
  • You reviewed Special DB2 instructions.
  • The user performing these instructions has system admin authority on the DB2 database.
    Tip:
    On Linux, to get system admin authority on the DB2 database, sudo to the DB2 user db2fenc1 and run bash.

About this task

To set up a DB2 database:

  1. Create the database in the DB2 Command Window. The example commands create a new database called JAZZ. These commands run in the DB2 Command Window. The Command Window can be opened from the application Start menu under the DB2 Command Line Tools menu.
    • On Windows:
      db2 create database JAZZ on c: using codeset UTF-8 territory en PAGESIZE 8192
    • On Linux:
      db2 create database JAZZ using codeset UTF-8 territory en PAGESIZE 8192
    Note:
    To ensure proper handling of Unicode content, the database character set must be UTF-8 encoding. Because the AUDITABLE_LINKS table does not fit in the default page size of 4K on Windows, set the page size to at least 8K.
    Tip:
    If the database is not running, the command db2start starts DB2.
  2. Locate the file teamserver.properties in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.derby.properties.
  3. Locate the file teamserver.db2.win32.properties on Windows or teamserver.db2.linux.properties on Linux in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.properties.
  4. Specify the database and connection details in the file teamserver.properties.

    The default connection specification connects to a DB2 database that runs on localhost on port 50000. The database is called JAZZ, and both the user name and password are db2admin. If the default values were used when setting up your database, the teamserver.properties file might already be configured correctly. If not, change this information to match your configuration.

    1. Open the file teamserver.properties in a text editor.
    2. Locate the following lines:
      com.ibm.team.repository.db.vendor = DB2
      com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
      com.ibm.team.repository.db.jdbc.password=db2admin
    3. Edit the value of com.ibm.team.repository.db.jdbc.location for your DB2 server and database.
      Tip:
      In the DB2 Command Window, run the command db2 get dbm cfg, then find the line that contains SVCENAME, which indicates the DB2 port name or number. If this command displays a number, use it as the port number (in place of 50000 in the example above). If the command returns a non-numeric name, determine what port number was assigned for this name and use that port number. On Linux, the file /etc/services contains the mapping between port names and numbers, and on Windows, the file C:\windows\system32\drivers\etc\services contains the mapping. For more information, ask your database administrator or consult the database documentation.
    4. Edit the value of com.ibm.team.repository.db.jdbc.location for your DB2 user name.
      Note:
      The DB2 user must have permissions to create tables, tablespaces, and modify the database configuration. DB2 users are created by the operating system.
    5. Specify the user password in the property com.ibm.team.repository.db.jdbc.password.
      Note:
      Do not change the password={password} text in the com.ibm.team.repository.db.jdbc.location property.
    6. If necessary, change the property com.ibm.team.repository.db.db2.content.tablespace.location to a path on your Jazz Team Server for Power Systems Software where the main tablespace can be created.
      Note:
      If this value is not changed from the default of content_tablespace, the tablespace is created under the database storage location. On Windows, if a new path is specified, it must be specified by using double backslashes, for example: com.ibm.team.repository.db.db2.content.tablespace.location=c:\\db2\\jazz\\content_tablespace.

Results

You are finished setting up your database. Continue with Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle.

RTC Power: Setting up an Oracle database

Set up an Oracle database to work with the Jazz Team Server for Power Systems Software.

Before you begin

This assumes the following prerequisites have been met. Consult your Oracle documentation or an Oracle database administrator (DBA) for help.

  • Oracle is installed on a machine to be used as the database server. This machine can be a different one from that on which the Jazz Team Server for Power Systems Software runs.
  • A default database exists on the Oracle server.
    Tip:
    When you install Oracle, you have the option to create a database automatically.
    Important:
    To ensure proper handling of Unicode content, the database character set must be UTF-8 encoding.
  • The user who performs these instructions has system administration authority on the Oracle database.

When running Jazz Team Server for Power Systems Software on Oracle, create an Oracle tablespace to improve performance. You must create a user linked to that tablespace.

Remember:
Neither of these steps are performed by the database builder with the repository tools.

About this task

To set up an Oracle database:

  1. Create a tablespace. The tablespace location must be appropriate to the machine and disk drive.
    Note:
    The tablespace can have any of these properties:
    • A name other than oracle_tbs
    • A location in another directory
    • A size larger than 1GB. For large installations, you need to allocate more space.
    The example below shows a create statement executed on a Windows machine:
    CREATE BIGFILE TABLESPACE oracle_tbs DATAFILE 'D:\oracle_tbs\oracle_tbs.dbf' SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    Important:
    The directory path (in this example D:\oracle_tbs) must exist. It is not necessary to create a separate special tablespace. You can use the Oracle default USERS tablespace, but Oracle performs better with a pre-allocated space on the disk that it manages.
  2. Create an Oracle user.

    After the tablespace is created, a special Oracle user must be created for Jazz to use the Oracle database.

    In this example, the user has the name jazzDBuser and password (IDENTIFIED BY in Oracle terms) jazzDBpswd and exists in the tablespace created in 1.
    CREATE USER jazzDBuser IDENTIFIED BY jazzDBpswd DEFAULT TABLESPACE oracle_tbs
    After the user is created, the user should be given the necessary permissions needed to initialize the Jazz database. The following SQL commands can be used to grant the appropriate permissions:
    GRANT CREATE SESSION TO jazzDBuser;
    GRANT CREATE TABLE, ALTER ANY TABLE, DROP ANY TABLE, CREATE ANY INDEX, ALTER ANY INDEX, DROP ANY INDEX TO jazzDBuser;
    GRANT INSERT ANY TABLE, UPDATE ANY TABLE, DELETE ANY TABLE TO jazzDBuser;
    GRANT CREATE PROCEDURE TO jazzDBuser;
    GRANT CREATE VIEW TO jazzDBuser;
  3. Locate the file teamserver.properties in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.OtherDBProvider.properties.
  4. Locate the file teamserver.oracle.properties in the directory JazzInstallDir/server/conf/jazz and rename it to teamserver.properties.
    Tip:
    Renaming the original teamserver.properties file enables you to restore the file to the previous working version. By default, the DB Provider is derby.
  5. Configure the server
    1. Edit the server configuration file if you used a different user name, password, or db name, installed Oracle server on a different machine than Jazz Team Server for Power Systems Software, or are using a port other than the default. Open the file teamserver.properties in JazzInstallDir/server/conf/jazz directory, and change the information listed below to match your setup.

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

      com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@localhost:1521/ORCL

      Change jazzDBuser with the user created for Jazz to use the Oracle database. If you are using localhost, uncomment this line by removing # from the beginning of the line and comment the next location line. Localhost connection strings should not include the preceding //. Change 1521 with your Oracle server machine TCIP port. Change ORCL with your Oracle database name.

      com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@//oracleserver.example.com:1521/ORCL

      If you are using a non-localhost connection, uncomment this line by removing the # from the beginning of the line and comment the previous location line. Non-localhost connection strings must include the preceding //.

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

      Change jazzDBpswd with the password of the user created for Jazz to use the Oracle database.

      Important:
      Do not change the {password} text in the property com.ibm.team.repository.db.jdbc.location. The user password must be specified in the property com.ibm.team.repository.db.jdbc.password.

      If you are using Oracle Express, use 1521 for TCIP port and XE for Oracle database name:

      com.ibm.team.repository.db.vendor = ORACLE
      com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@localhost:1521/XE
      com.ibm.team.repository.db.jdbc.password=jazzDBpswd
    2. In the same directory as the server scripts (JazzInstallDir/server), create a directory named oracle.
    3. Locate the Oracle JDBC driver JAR file, named ojdbc14.jar. The location can vary depending on the Oracle product and operating system. Copy this file to the directory named oracle.
      Note:
      If you are using WebSphere Application Server, configure a property named "ORACLE_JDBC"; then set it to the absolute file path (not URL) to the Oracle JDBC drivers. This task is described in the WebSphere Application Server setup instructions. Make a note of the file path for later use in these instructions.

Results

You are finished setting up your database and can continue with Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle.

RTC Power: Setting up a SQL Server database

Set up a SQL Server database to work with the Jazz Team Server for Power Systems Software.

This procedure assumes that the following prerequisites have been met:

  • You have SQL Server installed
  • SQL Server service is started
  • You have the SQL Server JDBC drivers installed. For more information, see http://msdn2.microsoft.com/en-us/data/aa937724.aspx
  • The TCP protocol is enabled for SQL Server
  • The user who creates the DB table must have one of the following permissions:
    • A membership in the sysadmin fixed server role, or ownership of the database (dbo)
Remember:
The default login name defined in JazzInstallDir/server/teamserver.properties file for a SQL Server database is jazzDBuser and the default password is jazzDBpswd. These values are used in the steps below for creating a database. You can substitute these values with the user name and password for your database.

Setting up a database

This section describes how to set up the SQL Server database by using the command line tool sqlcmd, which is provided with the SQL Server installation. You can also use a visual tool, such as SQL Server Studio Management, which is also available for the Express version as SQL Server Studio Management Express. See the SQL Server documentation or an SQL Server database administrator (DBA) for more information.

To set up an SQL Server database by using the command tool sqlcmd:

  1. Create a Jazz Team Server for Power Systems Software database. From the command line tool, type:
    CREATE DATABASE jazz 
    GO 
  2. Create a user and password and change the ownership of the Jazz Team Server for Power Systems Software database. From the command line tool, type:
    CREATE LOGIN jazzDBuser
    WITH PASSWORD = 'jazzDBpswd';
    USE jazz;
    exec sp_changedbowner 'jazzDBuser'
    GO 
  3. Change the collation of the Jazz Team Server for Power Systems Software database. From the command line tool, type:
    ALTER DATABASE jazz COLLATE SQL_Latin1_General_CP437_CS_AS 
    GO

Configuring the server

Remember:
By default, the teamserver.properties file in JazzInstallDir/server directory is not set up to connect to a SQL Server database. All default settings, along with SQL Server-specific settings, are contained in the teamserver.sqlserver.properties file in the same directory.

To configure the server:

  1. Rename the following files:
    • Rename the JazzInstallDir/server/conf/jazz/teamserver.properties file to teamserver.OtherDBProvider.properties
    • Rename the teamserver.sqlserver.properties file to teamserver.properties
    Tip:
    Renaming the original teamserver.properties file enables you to restore the file to the previous working version. By default, the DB Provider is derby.
  2. Edit the server configuration file if you used a different user name, password, or db name, installed SQL server on a different machine than Jazz Team Server for Power Systems Software, or are using a port other than the default. Open the file teamserver.properties in JazzInstallDir/server/conf/jazz directory, and change the information listed below to match your setup.
    com.ibm.team.repository.db.vendor = SQLSERVER
    com.ibm.team.repository.db.jdbc.location=//SQL SERVER MACHINE IP:SQL SERVER TCIP PORT;databaseName=JAZZ DATABASE NAME;user=JAZZ USERNAME;password={password}
    com.ibm.team.repository.db.jdbc.password=JAZZ LOGIN PASSWORD
    Important:
    Do not change the password={password} text in the property com.ibm.team.repository.db.jdbc.location. The user password must be specified in the property com.ibm.team.repository.db.jdbc.password.

To specify the jar file location for JDBC:

  1. In the same directory as the server scripts (JazzInstallDir/server), create a directory named sqlserver.
  2. Locate the SQL Server JDBC driver JAR file, named sqljdbc.jar. The location can vary depending on where the drivers were installed, as noted in the prerequisites section. Copy the file into the newly created sqlserver directory.
  3. Specify the JDBC JAR file location for JDBC by completing the following task:
    • Set up the environment variable SQLSERVER_ABSPATH to point to the directory that contains the JAR file. If the path contains space characters, you must include them with quotations.
      Tip:
      If you use WebSphere Application Server, configure a property named SQLSERVER_JDBC; then set it to the absolute file path (not URL) to the SQL Server JDBC drivers directory. For more information, see the WebSphere Application Server setup instructions. Note the file path for later use in these instructions.

You have completed setting up your database. Now, create the Jazz Team Server for Power Systems Software database tables. For more information, see Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle.

Troubleshooting

If the repotools command does not succeed, check the log file named repotools_createTables.log, located in the JazzInstallDir/server directory.

Also, verify the following:

  • The SQL Server is configured to allow connections using the TCP/IP protocol. If required, restart the SQL service.
  • The SQL Server machine host name, and the port is correctly reflected in the teamserver.properties file.
  • The login name, password, and database name are properly reflected in the teamserver.properties file.
  • A firewall does not prevent you from accessing the SQL Server. Use a telnet command to telnet to the machine using hostname and port from the teamserver.properties file.
  • The created user has proper permissions in the Jazz Team Server for Power Systems Software database.
Note:
The database code for Jazz Team Server for Power Systems Software was designed to be generic and standard in order to run on multiple database platforms; however, differences between the enterprise database vendors exist in syntax, optimization strategies, and locking semantics. The server has been tested on SQL Server using a combination of automated tests and simulations of normal workloads and stress testing. The simulation of normal workloads showed acceptable performance. In some instances database deadlocks have been observed in automated concurrency tests; however, these have not been consistently reproduced on different server hardware.

The server is designed to service a large number of simultaneous requests. In exceptional cases, deadlocks can occur in the repository database, as similar or equal objects are updated concurrently in transactions associated with the requests. These are rare, but normal events. The system is designed to be defensive against this, and data integrity is maintained; there is no loss of data. Occasionally, deadlocks are logged by tasks, such as build engine execution. Generally, the condition is detected, and the task is re-tried. The deadlock can result in a failed build. In very rare cases, it can be a user action, such as working with work items or source code, that is aborted to resolve a deadlock. In that case, the user action fails and an error with details regarding a deadlock is displayed to the user. The user can then retry the action.

All deadlocks encountered are logged on the server to provide information about what happened when the deadlock occurred. The log entry has text similar to the following: com.ibm.team.repository.common.RetryableDatabaseException: Serialization failure.

If your system encounters deadlocks, see the error log, which is available at https://servername:9443/jazz/service/com.ibm.team.repository.common.internal.IFeedService?category=SystemLog.

If you encounter frequent deadlock exceptions, contact your product support, or check the forums on jazz.net for the latest information, updates, or mitigating techniques.

Creating the Jazz Team Server for Power Systems Software database tables on DB2 and Oracle

Create the database tables using the repository tools.

About this task

To create the database tables:

  1. Run the command repotools -createTables to create the database tables for a Jazz repository.

    The repotools file is located in JazzInstallDir/server.

    The command uses the configuration properties in teamserver.properties for the connection and size settings. By default, the command looks in the current directory. The parameter teamserver.properties can be used to reference a different properties file.

    • On Windows:
      repotools -createTables
    • On AIX:
      ./repotools.sh -createTables
    This command creates the tablespace and all the required tables and indexes for a Jazz Team Server for Power Systems Software repository.
  2. After the database tables are created, you must stop and restart the database to make sure all changes are in effect.
    Tip:
    DB2 only. Example commands that stop and start DB2 are db2stop and db2start. These commands are run at the DB2 Command Window. The Command Window can be opened from the application start menu under the DB2 Command Line Tools cascade menu.

Results

You are finished setting up your database and can continue with RTC Power: Starting the server.

RTC Power: Starting the server

This topic describes the different options for running the server startup scripts.

About this task

If you plan to use the included Apache Tomcat application server, you are ready to start the Jazz Team Server for Power Systems Software.

If you plan to use the WebSphere Application Server, set up your server environment as described in RTC Power: Setting up a WebSphere Application Server.

RTC Power: Starting the Apache Tomcat server

You are now ready to start the Apache Tomcat server.

Apache Tomcat has been installed in the directory JazzInstallDir/server/tomcat. The Web application (jazz.war) has been installed in the Apache Tomcat directory webapps. In a command window, set your current directory to JazzInstallDir/server. The server startup and shutdown scripts are located in this directory.

  • If you want to run the start and stop scripts from any other directory, you must change the profiles.ini file in JazzInstallDir/server/conf/jazz/provision_profiles to use an absolute path.
  • Apache Tomcat is configured to use the ports 9080 and 9443 in file JazzInstallDir/server/tomcat/conf/server.xml. If necessary, change them as appropriate for your system. If necessary, also update the configuration settings of Jazz server Repository HTTP ports in the Advanced Properties configuration page of in the Jazz Admin Web UI.
  • The directory JazzInstallDir/server/logs contains the server log files. If you have trouble starting the server, check the log files.
  • The JazzInstallDir/server/tomcat/conf/server.xml file contains SSL settings that specify an algorithm only available in the IBM JRE. To run the server with a Sun JRE, in the server.xml file, change the settings for Connector port="9443", so that sslProtocol="TLS" instead of "SSL". Also remove the algorithm parameter.

Starting the server on Windows

Run the startup file to start your server on Windows.

About this task

  1. To start the server, from the JazzInstallDir/server directory, run this command:
    server.startup.bat
    Note:
    A separate Apache Tomcat console window opens. Do not close this window or the server will stop working. Also, several informational messages launch, including a message about the Apache Tomcat Native Library. These informational messages do not affect the Jazz Team Server for Power Systems Software functionality.
  2. To stop the server, from the JazzInstallDir/server directory, run this command:
    server.shutdown.bat

What to do next

Note:
The example above runs the start and stop scripts directly from the directory JazzInstallDir/server. If you installed Jazz Team Server for Power Systems Software using IBM Installation Manager, you can also run the commands from the Jazz Team Server for Power Systems Software Windows start menu.

After the server is started, proceed to RTC Power: Running the setup wizard.

Starting the server on AIX

Run the startup file to start the server on AIX.

About this task

  1. To start the server, from the JazzInstallDir/server directory, as user root, run this command:
    ./server.startup
    If your user ID has administrator access, run this command:
    sudo ./server.startup

    A separate Apache Tomcat console window is not visible. You can check the server startup progress by viewing the log file at JazzInstallDir/server/logs/jazz.log.

  2. To stop the server, from the JazzInstallDir/server directory, as user root, run this command:
    ./server.shutdown
    If your user ID has administrator access, run this command:
    sudo ./server.shutdown

What to do next

Note:
This example runs the start and stop scripts directly from the directory JazzInstallDir/server. If you installed Jazz Team Server for Power Systems Software by using IBM Installation Manager, you can also run the commands from the Jazz Team Server for Power Systems Software application start menu.

After the server is started, proceed to RTC Power: Running the setup wizard.

Running Jazz Team Server for Power Systems Software in Apache Tomcat as a Windows service

Apache Tomcat has the ability to run as a Windows service. This can be useful if you want to run the Jazz Team Server for Power Systems Software on a Windows-based machine without having to be logged on.

Before you begin

This topic assumes that your Jazz Team Server for Power Systems Software deployment is rooted at C:\jazz; adjust your paths accordingly based on your actual root directory.

  1. Open a command prompt and execute the following command to install the Tomcat service.
    C:\jazz\server\tomcat\bin\service.bat install
  2. If you are using Derby as your database for your Jazz Repository, edit C:\jazz\server\conf\jazz\teamserver.properties to make the DB location an absolute path. For example, change the value of db.jdbc.location to C:\jazz\server\repositoryDB.
  3. Execute C:\jazz\server\tomcat\bin\tomcat5w.exe to configure the service.
  4. Click the Java tab and clear the check box for Use default.
  5. Add the following path to Java Virtual Machine. You can also click the ellipsis icon to browse for the jvm.dll file.
    C:\jazz\server\jre\bin\j9vm\jvm.dll
  6. Add the following lines at the bottom of the Java Options text field
    -DJAZZ_HOME=file:///c:/jazz/server/conf
    -Djava.awt.headless=true 
    -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true 
    -Dcom.ibm.team.repository.tempDir=%TEMP%
    If you are using Oracle database, add the following line:
    -DORACLE_JDBC=[path to Oracle JDBC driver jar]
    If you are using SQL Server database, also add the following line:
    -DSQLSERVER_JDBC=[path to SQL Server JDBC driver jar]
  7. Change the Maximum memory pool size to 700.
  8. On the Startup and Shutdown tabs, make sure that jvm is selected for the Mode setting.
  9. Click the General tab and change the Startup type to Automatic if you want to start the service automatically when Windows starts.
  10. Start the service to test the server.

Deploying Jazz Team Server into an existing Apache Tomcat

This topic describes how to setup the Jazz Team Server for Power Systems Software to work with your existing Apache Tomcat server.

About this task

To deploy the jazz.war file into your existing Apache Tomcat server, follow these steps:

  1. Copy the jazz.war file from JazzInstallDir to your tomcat\webapps directory.
  2. Open your tomcat startup file for editing and add the following system property settings:
    set CATALINA_OPTS=-Dcom.ibm.team.server.configURL=file:///"%cd%"/teamserver.properties -Dlog4j.configuration=file:///"%cd%"/log4j.properties 
    set JAVA_OPTS=-Djava.awt.headless=true -DORACLE_JDBC="%ORACLE_JDBC%" -DDB2I_JDBC="%DB2I_JDBC%" -DDB2Z_JDBC="%DB2Z_JDBC%" -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -Dcom.ibm.team.repository.provision.profile="%cd%"\provision_profiles -Dcom.ibm.team.repository.tempDir=%TEMP% -Xmx700M
  3. Save and close the startup file.
  4. Open and edit the teamserver.properties file to point to your database.
  5. Save and close teamserver.properties.

RTC Power: Setting up a WebSphere Application Server

This topic describes how to set up the Jazz Team Server for Power Systems Software to work with WebSphere Application Server. This setup assumes that you are installing the Jazz Team Server for Power Systems Software on the same machine as the Websphere Application Server.

Before you begin

Before beginning these steps, you should have the following completed:

  • WebSphere Application server is already installed.
  • The database is created and the teamserver.properties file is updated with your database settings.
  • Refer to your WebSphere documentation for security setup and turn off the case-insensitive property.
    Note:
    Although Websphere and many LDAP directories allow you to log in case-insensitive, Jazz Team Server for Power Systems Software stores user records with user IDs in exact case as they are imported. When you log in to the Jazz Team Server for Power Systems Software, the user record is retrieved from the list of users and the case must match exactly.
  • Java 2 Security option should be turned off. If this option is turned on in WebSphere Application Server it will cause the Jazz Team Server for Power Systems Software .war to fail to start.
  • Ensure that the WAS security setting "Use available authentication data when an unprotected URI is accessed" is checked. If you are using the WAS Integrated Solutions Console, you can do this by:
    1. Navigating to Security -> Secure administration, applications, and infrastructure -> Web Security - General Settings.
    2. Selecting the checkbox for "Use available authentication data when an unprotected URI is accessed".
  • The Jazz Team Server for Power Systems Software includes the files required to run a complete Apache Tomcat-based server. For a WebSphere installation you only need a subset of the Jazz Team Server for Power Systems Software files and you should place them in a directory on your WebSphere server machine. Further instructions refer to this as the Jazz Team Server for Power Systems Software installation directory, or JazzInstallDir for short. From this directory, use:
    • The file JazzInstallDir/server/tomcat/webapps/jazz.war.
    • The directory JazzInstallDir/server/update-site.
    • The directory JazzInstallDir/server/conf.
    • The default repository database in JazzInstallDir/repositoryDB.
    • The repository tools in JazzInstallDir/repotools.
    • The directory JazzInstallDirserver/license-update-site.
    • The directory JazzInstallDir/server/nl1-update-site.
    • The directory JazzInstallDir/server/nl2-update-site.
Tip:
When using the IBM Installation Manager the Jazz Team Server for Power Systems Software files can be installed into a Web application directory. During the installation process, you should not install the included Apache Tomcat application server; this makes the Installation Manager ask for a Web Application directory and install only the files needed for WebSphere. The default directory is C:\Program Files\IBM\JazzTeamServer on Windows or /opt/IBM/JazzTeamServer on AIX. The installation directory is referred to as JazzInstallDir in this procedure. If you use the IBM Installation Manager to install the files into the WebSphere Application Server Web applications directory, then you do not need to manually move the files as described above.

About this task

Note:
This document does not teach the configuration of WebSphere authentication or SSL, which is a complex topic. Detailed information about the various authentication and encryption options for WebSphere is covered in the WebSphere Information Center. For more information, go to the WebSphere Information Center and search for Securing applications and their environment. The Jazz Web UI requires that authentication be configured in order to perform authorization and personalize the application.

  1. Review and update the database location in the teamserver.properties file
    com.ibm.team.repository.db.vendor = DB2
    com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
    com.ibm.team.repository.db.jdbc.password=db2admin
    Note:
    This is a sample DB2 configuration. The teamserver.properties should be updated depending on the database vendor (Oracle/MS-SQL).
  2. Verify or update the WebSphere Application Server level.

    Jazz Team Server for Power Systems Software requires WebSphere Application Server Version 6.1 with the IBM Java SDK 1.5 SR5 or later Cumulative Fix applied or WebSphere Application Server Version 7.0 with at least 7.0.0.3 installed. The IBM Java SDK 1.5 SR6 SDK update is available from http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24017492. With WebSphere 6.1 and the GA IBM Java SDK, Jazz starts to report "proxy errors" after some number of operations.

    You must obtain the corresponding WebSphere Application Server i-fixes for fixes to IBM Java SDK 1.5 SR9 or IBM Java SDK 1.6 SR4 that are necessary for IBM Rational Team Concert for Power Systems Software 2.0 to run correctly. Otherwise, some services in the server might not start correctly. The i-fixes are available under their corresponding WebSphere Application Server APARs. For IBM Java SDK 1.5/WebSphere Application Server 6.1, the APAR is PK85942 and you can download the files from ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixes/PK85942/. Install at least WebSphere Application Server 6.1 fixpack 19 before installing the JRE i-fix. For IBM Java SDK 1.6/WebSphere Application Server 7.0, the APAR is PK 86771 and you can download the files from ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixes/PK86771/.

  3. Update the JVM arguments.

    The Jazz Team Server for Power Systems Software needs some specific settings on the Java Virtual Machine in which it is run.

    First, it needs to know where to find some configuration files. This is done by setting a system property JAZZ_HOME. This property uses a URL rather than a simple path, so the value should be specified as a file://-style URL.

    The second property which is required for the Jazz JVM is to provide it with more than the default maximum memory allocation, using the -Xmx setting. This should be set based on the size of the team supported by the server and the memory capacity of the server where Jazz Team Server for Power Systems Software is running. A typical medium-size team can use a value of -Xmx1000M, providing 1000 MB of heap memory for the Jazz Team Server for Power Systems Software process.

    If you are connecting to an Oracle or SQL Server database then you need to add a property named "ORACLE_JDBC" or "SQLSERVER_JDBC". Set the property to the absolute file path (not a URL) to the appropriate jdbc drivers.

    There are a couple other system properties which need to be set to control some behavior of the server, they are included below. Here are the specifics of setting these JVM properties in the WebSphere Administrative Console, substitute JazzInstallDir with your Jazz Team Server for Power Systems Software installation directory:

    1. Click on Servers -> Application Servers.
    2. Click on server1.
    3. Click on Java and Process Management -> Process Definition.
    4. Click on Java Virtual Machine.
    5. Add the value 100 to the Initial Heap.
    6. Add the value 1000 to the Maximum Heap Size.
    7. Click Apply.
    8. Click Logging and Tracing. Click Change Log Detail Levels. The Jazz Team Server for Power Systems Software uses the BIRT reporting engine. To prevent BIRT informational entries from being written to the WebSphere log file, set the logging level to severe for the org.eclipse.birt.* packages. Click Apply.
    9. Click Custom Properties
    10. Add the following properties: Click New; enter the Name and Value; then click OK.
      • Name: java.awt.headless Value: true
      • Name: org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin Value: true
      • Name: JAZZ_HOME Value: file:///JazzInstallDir/server/conf
    11. Click Save directly to the master configuration.
  4. Restart Websphere to install the Jazz Application

    In the following command line examples, WASInstallDir represents the location where WebSphere Application Server is installed on your server.

    • On Windows, the default value for WebSphere installation directory is:
      C:\Program Files\IBM\WebSphere\AppServer

      You can restart the server with the following commands on Windows:

      cd WASInstallDir\bin 
      stopServer.bat server1 [for a secure server, include: -username {LDAP_User} -password {LDAP_Password}] 
      startServer.bat server1
    • On AIX, the default value for WebSphere installation directory is:
      /opt/IBM/WebSphere/AppServer

      You can restart the server with the following commands on AIX:

      cd WASInstallDir/bin 
      ./stopServer.sh server1 [for a secure server, include: -username {LDAP_User} -password {LDAP_Password}] 
      ./startServer.sh server1
    1. Open the Admin console for your WebSphere Application Server.
    2. Click on Applications -> Install New Application.
    3. Under Path to new Application, click Local file system.
    4. Under Full path enter:
      JazzInstallDir/server/jazz.war
    5. Set Context Root to /jazz.
    6. Click Next and continue through the remaining Install New Application steps.
    7. Click Finish.
    8. Click Save directly to the master configuration.
    9. Click on Applications -> Enterprise Applications.
    10. Select the box next to jazz_war; click Start.

      A green arrow should appear indicating the application started successfully.

What to do next

After the server is started, proceed to RTC Power: Running the setup wizard.

For more information about this topic visit the following links:

https://jazz.net/library/techtip/321

https://jazz.net/wiki/bin/view/Main/WASSetupFAQ

RTC Power: Running the setup wizard

Running the setup wizard verifies that the server is operating properly and guides you through the steps configure the server.

About this task

To verify that the Jazz Team Server for Power Systems Software is connecting to the database, look at the server log or console output. The connection and database information is echoed on its first access. The directory JazzInstallDir/server/logs is used for the server log files.

This procedure assumes your server is available using the hostname localhost and the default ports 9443. If necessary, replace localhost with your server hostname and replace the port 9443.

Start the setup wizard to configure your server. Use the URL https://localhost:9443/jazz/setup.
The default user name and password are case-sensitive:

  • The user name is ADMIN.
  • The password is ADMIN.

If you configured the LDAP directory Web container, log in with a JazzAdmin user that is defined in your LDAP directory.

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

  • The Fast Path Setup uses the default configuration. If you want to get the server running quickly, the fast path setup is a good option. During the Fast Path Setup, setup
    • the user registry.
  • The Custom Setup guides you through the detailed server configuration, including the ability to enable e-mail notifications. During the Custom Setup, you set up the following items:
    • Database
    • E-mail notification
    • User registry
    Note:
    By default, the server is configured to use Derby as the database. To use another database, such as DB2, select the custom setup path and complete Step 2: Configure Database.


When the initial setup is complete, additional options can be configured from the Jazz Team Server for Power Systems Software Admin Web user interface by using the URL https://localhost:9443/jazz/admin.

What to do next

If the server setup wizard does not load, check the following items:

  • Verify that the application server has started. Use the URL http://localhost:9080.
  • Verify the Jazz Team Server for Power Systems Software has started by logging in to the Jazz Team Server for Power Systems Software Admin Web UI using the URL https://localhost:9443/jazz/admin. If the page does not load or the server has errors, the server did not start correctly. See the troubleshooting information at Troubleshooting server issues.
  • The URI root for the Jazz Team Server for Power Systems Software path must be /jazz. For example https://example.com:9443/jazz must be used rather than https://example.com:9443.

RTC Power: Completing the installation

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

About this task

After the installation, there are a few additional actions to take.

  • 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.
    • teamserver.properties - The Jazz Team Server for Power Systems Software requires that the database password is stored in JazzInstallDir/server/conf/jazz/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.

    • The ClearCase Connector sync engine requires that user passwords be stored in an properties file.
    • cqconnector.properties - The ClearQuest Connector requires that both ClearQuest user IDs and passwords be stored in a properties file.
  • When connecting to the server with the Rational Team Concert for Power Systems Software client or a Web browser, you might see security certificate warnings. To disable the warning, see RTC Power: Security certificates.
  • 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 for Power Systems Software client or a Web browser.

  • Related concepts
  • RTC Power: Security certificates
    The Jazz Team Server for Power Systems Software includes a self-signed certificate for SSL with the Apache Tomcat server. Note that the Apache Tomcat server is only supported on AIX and Windows.

Installing Rational Team Concert for Power Systems Software on IBM i

This section contains step-by-step instructions on how to install Rational Team Concert for Power Systems Software on IBM i.

The following terms are used:

yourServerHostName
Refers to the TCP/IP host name or IP address for your IBM i server (for example, rtci.example.com or 192.123.1.111).
yourJazzServerPortNumber
Refers to the WebSphere Application Server port which is used to connect to the Jazz Team Server application (for example, 9443).
yourWASAdminPortNumber
Refers to the WebSphere Application Server port which is used to access the WebSphere Application Server Administration console (for example, 9060).
yourWASInstanceName
Refers to the WebSphere Application Server instance which is used to deploy the jazz.war file.
JazzInstallDirectory
Refers to directory /QIBM/Proddata/RTCi/V2.0/Express for Jazz Team Server Express Edition, to directory /QIBM/ProdData/RTCi/V2.0/Standard for Jazz Team Server Standard Edition and to directory /QIBM/ProdData/RTCi/V2.0/Enterprise for Jazz Team Server Enterprise Edition.

RTC Power: Prerequisites and system requirements

This section describes the prerequisites and requirements for installing IBM Rational Team Concert for Power Systems Software on IBM i.

Hardware requirements

Jazz Team Server for Power on IBM i requires an IBM POWER server running IBM i 5.4 or 6.1.

Get information about hardware requirements for the Rational Team Concert for Power client and Rational Developer for Power in the hardware requirements listed in the Rational Developer for Power Systems Software Installation Guide.

Software requirements

Prerequisites for Build System Toolkit for Power on IBM i

Installing Build System Toolkit for Power on IBM i requires:

  • IBM i 5.4 or 6.1
  • To compile RPG, COBOL, C, C++, CL, or DDS on IBM i using Build System Toolkit for Power, the compilers must be installed. The IBM i compilers are in product 5722WDS for IBM i 5.4 and 5761WDS for IBM i 6.1.
  • IBM J2SE 5.0 32-bit JVM with the applicable PTF applied:
    • IBM i 5.4 - SI36811 for product 5722JV1
    • IBM i 6.1 - SI35746 for product 5761JV1

Prerequisites for Jazz Team Server for Power on IBM i

The following are software requirements for Jazz Team Server for Power on IBM i.

Make sure that you have the following prerequisite applications installed and operational before you proceed with the installation of Jazz Team Server for Power on IBM i.

  • IBM i 5.4 or 6.1 with these program temporary fixes (PTFs):
    • IBM i 5.4
      • SI31547 for product 5722JC1 (IBM Toolbox for Java)
      • SI32280 for product 5722SS1 (IBM i)
    • IBM i 6.1
      • SI31554 for product 5761JC1 (IBM Toolbox for Java)
      • SI31976 for product 5761SS1 (IBM i)
      • MF46740 for product 5761999 (IBM i)
  • IBM J2SE 5.0 32-bit JVM with the applicable PTF applied:
    • IBM i 5.4
      • SI36811 for product 5722JV1
    • IBM i 6.1
      • SI35746 for product 5761JV1
  • WebSphere Application Server V6.1 (product 5733W61), or WebSphere Application Server V7.0 (product 5733W70) with the latest group PTF applied.
    Note:
    Using Rational Team Concert for Power with WebSphere Application Server V7.0 requires IBM J2SE 6.0 32-bit JVM with the applicable PTF applied:
    • IBM i 5.4
      • SI36102 for product 5722JV1
    • IBM i 6.1
      • SI36138 for product 5761JV1
  • IMPORTANT: By default, the WebSphere Application Server V6.1 is configured to use the IBM i Java Developer Kit 5.0 JVM (also known as the classic JVM). Rational Team Concert for Power on IBM i requires IBM J2SE 5.0 32-bit JVM. For instructions, see the enablejvm command in the WebSphere Application Server Information Center.

Prerequisites for Rational Team Concert for Power Web client

To access Jazz Team Server for Power using the web, one of the following browsers is required:

  • Microsoft Internet Explorer 7.0 or 8.0
  • Mozilla Firefox 3.0 or 3.5

For additional online information about Rational Team Concert for Power, see the product web site at

You can also register at jazz.net at

Installing V2.0 Build System Toolkit for Power and Jazz Team Server for Power on IBM i

Build System Toolkit for Power and Jazz Team Server for Power are packaged for IBM i in several ways and available in three editions:

  • Edition: Standard, Express, or Enterprise
  • V2.0 Media: DVD for IBM i or PC installation, or electronic image via Passport Advantage download.

For information to help you choose the Jazz Team Server for Power edition and installation method that are right for you, see the editions and licenses information in the Rational Team Concert for Power Information Center. To purchase and download the Build System Toolkit for Power and Jazz Team Server for Power packages, go to the Passport Advantage Web site at

Note:
By default, Jazz Team Server for Power is installed with a trial license. You can convert a trial licence to a permanent license by downloading the Server Activation Key from the Passport Advantage Web site. For more information, see the licensing considerations in Completing the installation.

For detailed step-by-step installation instructions, follow the links below. The procedures vary slightly, depending on file names and media type. For a new installation, start with Installing Build System Toolkit for Power Systems Software on IBM i and complete all steps in that section. Depending on the edition you are using, continue with Installing Jazz Team Server for Power Express Edition on IBM i ,Installing Jazz Team Server for Power Standard Edition on IBM i, or Installing Jazz Team Server for Power Enterprise Edition on IBM i. To update from Version 2.0 to Version 2.0.0.2, continue with Applying the V2.0.0.2 PTF to Build System Toolkit for Power and Jazz Team Server for Power on IBM i .Then proceed with RTC Power: Configuring your installation.

Here is an overview of the installation sequence for a new installation using WebSphere Application Server V6.1. For WebSphere Application Server V7.0, the steps are the same only the paths are slightly different.

  1. Restore Rational Team Concert for Power 2.0 License Program.
  2. Edit teamserver.properties and replace jazzDBuser with your user ID. Your user ID must have the authority to create and write to a library on the system.
  3. Replace jazzDBpswd with your password.
    Note:
    Do not modify the entry
    password={password}
  4. Create Group profiles with names such as JAZZADMINS, JAZZDWADMS, JAZZGUESTS, JAZZUSERS and JAZZPROJECTADMINS, for example using command
    crtusrprf usrprf(JAZZADMINS) password(*none) grpprf(*none) 
    		text('Group profile for JAZZADMINS')
  5. Add your user ID to the JAZZADMINS group, for example using command
    chgusrprf usrprf(yourUserID) grpprf(JAZZADMINS)
  6. Start a Qshell session and run the following commands in order:
    1. cd <JazzInstallDirectory>/jazz/server
    2. ./repotools.qsh -createTables
    3. cd /QIBM/ProdData/WebSphere/AppServer/v61/Base/bin
    4. manageProfiles -create -profileName <yourWASInstanceName>
    5. cd /QIBM/UserData/websphere/AppServer/v61/Base/profiles/<yourWASInstanceName>/bin
    6. ./startServer and record your WebSphere Application Server port number for later use.
  7. Open <InstallDirectory>/jazz/server/script_py/RTCi_JVM.qsh and replace #Replace_ME with /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/bin
  8. In the Qshell session, run the following commands in order:
    1. cd <JazzInstallDirectory>/jazz/server/script_py
    2. Log on to the WebSphere Application Server Integrated Solutions console at the following URL: http://<yourServerHostName>:<yourWASAdminPortNumber>/ibm/console expand Environment, select WebSphere Variables, click the right arrow to go to Page: 2 of 2 and record the value fields of WAS_CELL_NAME and WAS_SERVER_NAME.
    3. Navigate to <JazzInstallDirectory>/jazz/server/script_py and run ./RTCI_JVM.qsh to reset Java Virtual Machine parameters using the recorded values for WAS_CELL_NAME and WAS_SERVER_NAME.
    4. cd /QIBM/UserData/WebSphere/AppServer/v61/base/profiles/<yourWASInstanceName>/bin
    5. To set up IBM i authentication, run the ./wsadmin command and perform the next 2 steps.
    6. securityon <yourUserID> <yourPassword>. This UserID will be used to access the WebSphere Application Server Integrated Solutions console.
    7. quit
    8. ./stopServer
    9. ./startServer
  9. Deploy the Jazz.war file by following the steps in Part 3: Installing the Jazz Web archive file .
  10. Expand Servers, click Application, <yourWASInstanceName> and then Ports. Record the port for WC_defaulthost_secure which is <yourJazzServerPortNumber>.
  11. Launch the Jazz server admin page at this URL:
    https://<yourServerHostName>:<yourJazzServerPortNumber>/jazz/admin
    Log in with <yourUserID> and verify that the Server Status summary does not display any error messages and J9VM is listed as the Server JVM.
  12. Click License Key Management and upload Server Activation Kit and Client Access License Activation key(Contributor or Developer).
  13. On IBM i, add user profiles to the groups (JAZZADMINS, JAZZDWADMS, JAZZGUESTS, JAZZUSERS, or JAZZPROJECTADMINS).
  14. On the Jazz server admin page, assign the appropriate client access licenses to the user profiles.

Installing Build System Toolkit for Power Systems Software on IBM i

Install Build System Toolkit for Power on IBM i by completing these steps:

  1. Check that the system value
    QALWOBJRST
    is set to *ALL.
    1. On a 5250 command line, enter this command:
      WRKSYSVAL QALWOBJRST
    2. Select 5 (Display), and check that the value is set to *ALL. If it is set to any other value, record the value on this line:
      QALWOBJRST _____________________________________________
  2. Press Enter to continue.
  3. If QALWOBJRST was set to *ALL, skip to step 4; otherwise, complete the following steps:
    1. On the Work with System Values screen, enter 2 to change the value.
    2. On the Change System Values screen, change the existing value to *ALL.
    3. Press Enter to save the change.
    4. Press F3 to return.
  4. From a 5250 command line, create a library for installation:
    CRTLIB  RTCP_TMP TEXT('RTCP INSTALL LIBRARY')
  5. Create a save file. When you are installing Jazz Team Server Express Edition, use this command:
    CRTSAVF FILE(RTCP_TMP/B5724Z00) TEXT('RTCP INSTALL PRODUCT *BASE')
    For Jazz Team Server Standard and Enterprise Edition, use this command:
    CRTSAVF FILE(RTCP_TMP/B5724Z01) TEXT('RTCP INSTALL PRODUCT *BASE')
    Note:
    The content of the save files for all editions is the same. They have different numbers only for installation and uninstallation purposes.
  6. Copy the save file to the RTCP_TMP library. Depending on which installation medium you are using, there are two methods for copying the save file:

    Method 1: Installing from Passport Advantage files or from a DVD using your PC DVD drive

    Complete these steps to install from your workstation to your IBM i system:

    1. Download the Build System Toolkit for Power save file from Passport Advantage. For Express Edition, use save file B5724Z00, for Standard and Enterprise Edition, use save file B5724Z01. Download the save file to the temporary directory c:\RTCPTMP on your PC workstation. If you have a product DVD, you could insert the DVD into the DVD drive instead.
    2. Start an FTP session by entering the following command in the MS-DOS Command Prompt:
      FTP <yourServerHostName>
      where <yourServerHostName> is the name of the target IBM i system.
    3. When prompted, enter your IBM i system user ID and password.
    4. Enter BIN to change the FTP type to BINARY.
    5. Set the file naming convention to Path by entering the following:
      quote site namefmt 1
    6. Transfer the save file from the Passport Advantage files you downloaded or from the DVD to the IBM i system. For Express Edition use:
      put <YourDirectory>\B5724Z00.sav /qsys.lib/RTCP_TMP.lib/B5724Z00.file
      where <YourDirectory> is your PC DVD drive or the temporary directory c:\RTCPTMP where you downloaded the save file. For Standard and Enterprise Edition use:
      put <YourDirectory>\B5724Z01.sav /qsys.lib/RTCP_TMP.lib/B5724Z01.file
    7. End your FTP session with this command:
      QUIT
    8. Delete c:\RTCPTMP if you downloaded the save file there.

    Method 2: Installing from a DVD using your IBM i DVD drive

    Complete these steps to install from an IBM i DVD:

    1. Insert the DVD into the DVD drive and enter the following command on a 5250 command line:
      WRKLNK OBJ('/qopt')
    2. Where the Work with Object Links screen displays the qopt object link, select 5 (Next Level) to select the next object link, which is the volume ID (volid) of the DVD-ROM. Record the value here for use later during the installation:
      VOL ID _____________________________________________
    3. For Express Edition enter this command. (Command is printed on two lines to fit the page.):
      CPYFRMSTMF FROMSTMF('/QOPT/<volid>/B5724Z00.sav') 
      TOMBR('/qsys.lib/RTCP_TMP.lib/B5724Z00.file') MBROPT (*replace)
      where <volid> is the volume ID of the DVD you recorded above. For Standard and Enterprise Edition enter this command:
      CPYFRMSTMF FROMSTMF('/QOPT/<volid>/B5724Z01.sav') 
      TOMBR('/qsys.lib/RTCP_TMP.lib/B5724Z01.file') MBROPT (*replace)
  7. Install Build System Toolkit for Power for Express Edition by entering this command:
    RSTLICPGM LICPGM(5724Z00) DEV(*SAVF) SAVF(RTCP_TMP/B5724Z00)
    Note:
    If your system is not using English as the primary language, you have to specify value 2924 for the LNG parameter of the RSTLICPGM command.
    When it is restored, this message displays:
    *PGM objects for product 5724Z00 option *BASE release *FIRST restored.
    Install Build System Toolkit for Power for Standard or Enterprise Edition by entering this command:
    RSTLICPGM LICPGM(5724Z01) DEV(*SAVF) SAVF(RTCP_TMP/B5724Z01)
    Note:
    If your system is not using English as the primary language, you have to specify value 2924 for the LNG parameter of the RSTLICPGM command.
    When it is restored, this message displays:
    *PGM objects for product 5724Z01 option *BASE release *FIRST restored.
  8. If you do not intend to install Jazz Team Server Express, Standard, or Enterprise Edition, change the QALWOBJRST value back to the value you recorded earlier in step 1.b and delete the installation library DLTLIB RTCP_TMP.

This completes the installation of Build System Toolkit for Power V2.0 on IBM i. If you want to install Jazz Team Server for Power on IBM i Express Edition, continue with Installing Jazz Team Server for Power Express Edition on IBM i, for Standard Edition continue with Installing Jazz Team Server for Power Standard Edition on IBM i, and for Enterprise Edition, continue with Installing Jazz Team Server for Power Enterprise Edition on IBM i.

Installing Jazz Team Server for Power Express Edition on IBM i

Before starting with the steps in this section, ensure that your installation of Build System Toolkit for Power is complete. Install Jazz Team Server for Power Express Edition by completing these steps:

  1. If you just installed Build System Toolkit, continue with step 5, otherwise verify that the system value QALWOBJRST is set to *ALL.
    1. On a 5250 command line, enter this command:
      WRKSYSVAL
      QALWOBJRST
    2. Enter 5 (Display), and check that the value is set to *ALL. If it is set to any other value, record the value on this line:
      QALWOBJRST _____________________________________________
  2. Press Enter to continue.
  3. If QALWOBJRST was set to *ALL, skip to step 4; otherwise, complete these steps:
    1. On the Work with System Values screen, enter 2 to change the value.
    2. On the Change System Values screen, change the existing value to *ALL.
    3. Press Enter to save the changes.
    4. Press F3 to return.
  4. From a 5250 command line, create a library for installation:
    CRTLIB  RTCP_TMP TEXT('RTCP INSTALL LIBRARY')
  5. Create this save file:
    CRTSAVF FILE(RTCP_TMP/E5724Z00) TEXT('RTCP INSTALL PRODUCT OPTION1')
  6. Copy the save file to the IBM i system library. Depending on which installation medium you are using, there are two methods for copying the save file:
    Method 1: Installing from Passport Advantage files or from a DVD using your PC DVD drive
    Complete these steps to install from your workstation to your IBM i system:
    1. Download the Jazz Team Server for Power Express Edition save file (E5724Z00.sav ) from Passport Advantage to the temporary directory c:\RTCPTMP on your PC workstation, or if you have a product DVD, insert the DVD into the DVD drive.
    2. Start an FTP session by entering the following command in the MS-DOS Command Prompt:
      FTP <yourServerHostName>
      where <yourServerHostName> is the name of the target IBM i system.
    3. When prompted, enter your IBM i system user ID and password.
    4. Enter BIN to change the FTP type to BINARY.
    5. Set the file naming convention to Path by entering the following:
      quote site namefmt 1
    6. Transfer the following save file from the Passport Advantage file you downloaded or from the DVD to the IBM i system:
      put <YourDirectory>\E5724Z00.sav /qsys.lib/RTCP_TMP.lib/E5724Z00.file
      where <YourDirectory> is your PC DVD drive or the temporary directory c:\RTCPTMP where you downloaded the save file.
    7. End your FTP session with this command:
      QUIT
    8. Delete c:\RTCPTMP if you downloaded the save file there.
    Method 2: Installing from a DVD using your IBM i DVD drive
    Complete these steps to install from an IBM i DVD:
    1. Insert the DVD into the DVD drive and enter the following command on a 5250 command line:
      WRKLNK OBJ('/qopt')
    2. Where the Work with Object Links screen displays the qopt object link, select 5 (Next Level) to select the next object link, which is the volume ID (volid ) of the DVD. Record the value here for use later during the installation:
      VOL ID _____________________________________________
    3. Enter the following command. (The command is printed on two lines to fit the page.):
      CPYFRMSTMF FROMSTMF('/QOPT/<volid>/E5724Z00.sav') 
      TOMBR('/qsys.lib/RTCP_TMP.lib/E5724Z00.file') MBROPT (*replace)
      where <volid> is the volume ID of the DVD you recorded above.
  7. Install Jazz Team Server for Power Express Edition by entering this command:
    RSTLICPGM LICPGM(5724Z00) DEV(*SAVF) OPTION(1) SAVF(RTCP_TMP/E5724Z00)
    Note:
    If your system is not using English as the primary language, you have to specify value 2924 for the LNG parameter of the RSTLICPGM command.
    When it is restored, this message displays:
    *PGM objects for product 5724Z00 option 1 release *FIRST restored.
  8. Change the QALWOBJRST value back to the value you recorded earlier in step 1b.
  9. Delete the installation library DLTLIB RTCP_TMP
  10. To complete the installation of Jazz Team Server for Power, see RTC Power: Configuring your installation.

Installing Jazz Team Server for Power Enterprise Edition on IBM i

Before starting with the steps in this section, ensure that your installation of Build System Toolkit for Power is complete. Install Jazz Team Server for Power Enterprise Edition by completing these steps:

  1. If you just installed Build System Toolkit, continue with step 5, otherwise verify that the system value QALWOBJRST is set to *ALL.
    1. On a 5250 command line, enter this command:
      WRKSYSVAL
      QALWOBJRST
    2. Enter 5 (Display), and check that the value is set to *ALL. If it is set to any other value, record the value on this line:
      QALWOBJRST _____________________________________________
  2. Press Enter to continue.
  3. If QALWOBJRST was set to *ALL, skip to step 4; otherwise, complete these steps:
    1. On the Work with System Values screen, enter 2 to change the value.
    2. On the Change System Values screen, change the existing value to *ALL.
    3. Press Enter to save the changes.
    4. Press F3 to return.
  4. From a 5250 command line, create a library for installation:
    CRTLIB  RTCP_TMP TEXT('RTCP INSTALL LIBRARY')
  5. Create this save file:
    CRTSAVF FILE(RTCP_TMP/E5724Z01) TEXT('RTCP INSTALL PRODUCT OPTION1')
  6. Copy the save file to the IBM i system library. Depending on which installation medium you are using, there are two methods for copying the save file:
    Method 1: Installing from Passport Advantage files or from a DVD using your PC DVD drive
    Complete these steps to install from your workstation to your IBM i system:
    1. Download the Jazz Team Server for Power Enterprise Edition save files (E5724Z01.sav ) from Passport Advantage to the temporary directory c:\RTCPTMP on your PC workstation, or if you have a product DVD, insert the DVD into the DVD drive.
    2. Start an FTP session by entering the following command in the MS-DOS Command Prompt:
      FTP <yourServerHostName>
      where <yourServerHostName> is the name of the target IBM i system.
    3. When prompted, enter your IBM i system user ID and password.
    4. Enter BIN to change the FTP type to BINARY.
    5. Set the file naming convention to Path by entering the following:
      quote site namefmt 1
    6. Transfer the following save file from the Passport Advantage file you downloaded or from the DVD to the IBM i system:
      put <YourDirectory>\E5724Z01.sav /qsys.lib/RTCP_TMP.lib/E5724Z01.file
      where <YourDirectory> is your PC DVD drive or the temporary directory c:\RTCPTMP where you downloaded the save file.
    7. End your FTP session with this command:
      QUIT
    8. Delete c:\RTCPTMP if you downloaded the save file there.
    Method 2: Installing from a DVD using your IBM i DVD drive
    Complete these steps to install from an IBM i DVD:
    1. Insert the DVD into the DVD drive and enter the following command on a 5250 command line:
      WRKLNK OBJ('/qopt')
    2. Where the Work with Object Links screen displays the qopt object link, select 5 (Next Level) to select the next object link, which is the volume ID (volid ) of the DVD. Record the value here for use later during the installation:
      VOL ID _____________________________________________
    3. Enter the following command. (The command is printed on two lines to fit the page.):
      CPYFRMSTMF FROMSTMF('/QOPT/<volid>/E5724Z01.sav') 
      TOMBR('/qsys.lib/RTCP_TMP.lib/E5724Z01.file') MBROPT (*replace)
      where <volid> is the volume ID of the DVD you recorded above.
  7. Install Jazz Team Server for Power Enterprise Edition by entering this command:
    RSTLICPGM LICPGM(5724Z01) DEV(*SAVF) OPTION(1) SAVF(RTCP_TMP/E5724Z01)
    Note:
    If your system is not using English as the primary language, you have to specify value 2924 for the LNG parameter of the RSTLICPGM command.
    When it is restored, this message displays:
    *PGM objects for product 5724Z01 option 1 release *FIRST restored.
  8. Change the QALWOBJRST value back to the value you recorded earlier in step 1b.
  9. Delete the installation library DLTLIB RTCP_TMP
  10. To complete the installation of Jazz Team Server for Power, see RTC Power: Configuring your installation.

Installing Jazz Team Server for Power Standard Edition on IBM i

Before starting with the steps in this section, ensure that your installation of Build System Toolkit for Power is complete. Install Jazz Team Server for Power Standard Edition by completing these steps:

  1. If you just installed Build System Toolkit, continue with step 5, otherwise verify that the system value QALWOBJRST is set to *ALL.
    1. On a 5250 command line, enter this command:
      WRKSYSVAL
      QALWOBJRST
    2. Enter 5 (Display), and check that the value is set to *ALL. If it is set to any other value, record the value on this line:
      QALWOBJRST _____________________________________________
  2. Press Enter to continue.
  3. If QALWOBJRST was set to *ALL, skip to step 4; otherwise, complete these steps:
    1. On the Work with System Values screen, enter 2 to change the value.
    2. On the Change System Values screen, change the existing value to *ALL.
    3. Press Enter to save the changes.
    4. Press F3 to return.
  4. From a 5250 command line, create a library for installation:
    CRTLIB  RTCP_TMP TEXT('RTCP INSTALL LIBRARY')
  5. Create this save file:
     CRTSAVF FILE(RTCP_TMP/S5724Z01) TEXT('RTCP INSTALL PRODUCT OPTION2')
  6. Copy the save file to the IBM i system library. Depending on which installation medium you are using, there are two methods for copying the save file:
    Method 1: Installing from Passport Advantage files or from a DVD using your PC DVD drive
    Complete these steps to install from your workstation to your IBM i system:
    1. Download the Jazz Team Server for Power Standard Edition save files (S5724Z01.sav ) from Passport Advantage to the temporary directory c:\RTCPTMP on your PC workstation, or if you have a product DVD, insert the DVD into the DVD drive.
    2. Start an FTP session by entering the following command in the MS-DOS Command Prompt:
      FTP <yourServerHostName>
      where <yourServerHostName> is the name of the target IBM i system.
    3. When prompted, enter your IBM i system user ID and password.
    4. Enter BIN to change the FTP type to BINARY.
    5. Set the file naming convention to Path by entering the following:
      quote site namefmt 1
    6. Transfer the following save file from the Passport Advantage file you downloaded or from the DVD to the IBM i system:
      put <YourDirectory>\S5724Z01.sav /qsys.lib/RTCP_TMP.lib/S5724Z01.file
      where <YourDirectory> is your PC DVD drive or the temporary directory c:\RTCPTMP where you downloaded the save file.
    7. End your FTP session with this command:
      QUIT
    8. Delete c:\RTCPTMP if you downloaded the save file there.
    Method 2: Installing from a DVD using your IBM i DVD drive
    Complete these steps to install from an IBM i DVD:
    1. Insert the DVD into the DVD drive and enter the following command on a 5250 command line:
      WRKLNK OBJ('/qopt')
    2. Where the Work with Object Links screen displays the qopt object link, select 5 (Next Level) to select the next object link, which is the volume ID (volid ) of the DVD. Record the value here for use later during the installation:
      VOL ID _____________________________________________
    3. Enter the following command. (The command is printed on two lines to fit the page.):
      CPYFRMSTMF FROMSTMF('/QOPT/<volid>/S5724Z01.sav') 
      TOMBR('/qsys.lib/RTCP_TMP.lib/S5724Z01.file') MBROPT (*replace)
      where <volid> is the volume ID of the DVD you recorded above.
  7. Install Jazz Team Server for Power Standard Edition by entering this command:
    RSTLICPGM LICPGM(5724Z01) DEV(*SAVF) OPTION(2) SAVF(RTCP_TMP/S5724Z01)
    Note:
    If your system is not using English as the primary language, you have to specify value 2924 for the LNG parameter of the RSTLICPGM command.
    When it is restored, this message displays:
    *PGM objects for product 5724Z01 option 2 release *FIRST restored.
  8. Change the QALWOBJRST value back to the value you recorded earlier in step 1b.
  9. Delete the installation library DLTLIB RTCP_TMP
  10. To complete the installation of Jazz Team Server for Power, see RTC Power: Configuring your installation.

Applying the V2.0.0.2 PTF to Build System Toolkit for Power and Jazz Team Server for Power on IBM i

To update Build System Toolkit for Power and Jazz Team Server for Power Express Edition on IBM i from Version 2.0 to Version 2.0.0.2, apply the required PTFs to licence program 5724Z00.

To update Build System Toolkit for Power and Jazz Team Server for Power Standard Edition and Enterprise Edition on IBM i from Version 2.0 to Version 2.0.0.2, apply the required PTFs to licence program 5724Z01.

Note:
The product 5724Z00 or 5724Z01 must be installed on the IBM i host already.

For detailed step-by-step installation instructions, follow the links below. For all editions, start with Applying V2.0.0.2 PTF to Build System Toolkit for Power on IBM i and complete all steps in that section. Depending on the edition you are using, continue with Applying V2.0.0.2 PTF to Jazz Team Server for Power Express Edition on IBM i , Applying V2.0.0.2 PTF to Jazz Team Server for Power Standard Edition on IBM i, or Applying V2.0.0.2 PTF to Jazz Team Server for Power Enterprise Edition on IBM i.

Applying V2.0.0.2 PTF to Build System Toolkit for Power on IBM i

To update Build System Toolkit for Power Systems Software on IBM i, apply PTF SI38429 to licence program 5724Z00 or PTF SI38446 to licence program 5724Z01

Note:
The product 5724Z00 *BASE for Express Edition or 5724Z01 *BASE for Standard and Enterprise Edition must be installed on the IBM i host already.

To load and apply PTF SI38429 for Express Edition, perform these steps:

  1. Important! Terminate the Jazz Team Server for Power and stop all build engines before loading and applying or removing the PTF.
    1. To stop the server, use the ./stopServer command in
      /QIBM/UserData/WebSphere/AppServer/v61/base/<yourWASInstanceName>/bin or /QIBM/UserData/WebSphere/AppServer/v70/base/<yourWASInstanceName>/bin
    2. To stop all build engines, navigate to /QIBM/ProdData/RTCp/V2.0/BuildExp/jazz/buildsystem/buildengine/eclipse/RTCiLogs and write down all the folder names in this directory.
    3. On a 5250 command line, type WRKACTJOB and end all jobs in subsystem QUSRWRK that match a job name which you wrote down.
    4. Type CL command WRKSPLF SELECT(*ALL) JOB(<theEndedJobName>) and use option 4 to delete the spool files.
  2. Request and send PTF SI38429 to the IBM i host where you want to update Build System Toolkit for Power to V2.0.0.2.
  3. Use command LODPTF LICPGM(5724Z00) SELECT(SI38429) with the additional device specification to load the PTF.
  4. Use command APYPTF LICPGM(5724Z00) SELECT(SI38429) to apply the PTF.

To load and apply PTF SI38446 for Standard and Enterprise Edition, perform these steps:

  1. Important! Terminate the Jazz Team Server for Power and stop all build engines before loading and applying or removing the PTF.
    1. To stop the server, use the ./stopServer command in
      /QIBM/UserData/WebSphere/AppServer/v61/base/<yourWASInstanceName>/bin or /QIBM/UserData/WebSphere/AppServer/v70/base/<yourWASInstanceName>/bin
    2. To stop all build engines, navigate to /QIBM/ProdData/RTCp/V2.0/Build/jazz/buildsystem/buildengine/eclipse/RTCiLogs and write down all the folder names in this directory.
    3. On a 5250 command line, type WRKACTJOB and end all jobs in subsystem QUSRWRK that match a job name which you wrote down.
    4. Type CL command WRKSPLF SELECT(*ALL) JOB(<theEndedJobName>) and use option 4 to delete the spool files.
  2. Request and send PTF SI38446 to the IBM i host where you want to update Build System Toolkit for Power to V2.0.0.2.
  3. Use command LODPTF LICPGM(5724Z01) SELECT(SI38446) with the additional device specification to load the PTF.
  4. Use command APYPTF LICPGM(5724Z01) SELECT(SI38446) to apply the PTF.

As part of applying this PTF, a backup directory containing your 2.0 log files will be created with the name backup-config-v2.0-buildsystemtoolkit-SI38429 for Express Edition or backup-config-v2.0-buildsystemtoolkit-SI38446 for Standard and Enterprise Edition in /QIBM/ProdData/RTCp/. The RTCilogs folder will be copied to this directory, if it exists in QIBM/ProdData/RTCp/V1.0/BuildExp/jazz/buildsystem/buildengine/eclipse. for Express Edition or QIBM/ProdData/RTCp/V1.0/Build/jazz/buildsystem/buildengine/eclipse. for Standard and Enterprise Edition.

After applying this PTF, the backed up folder will not be restored to QIBM/ProdData/RTCp/V1.0/BuildExp/jazz/buildsystem/buildengine/eclipse. for Express Edition or QIBM/ProdData/RTCp/V1.0/Build/jazz/buildsystem/buildengine/eclipse. for Standard and Enterprise Edition. If you want to start all the build engines which you stopped earlier, you can do this using the backed up RTCilogs folder. This folder is for your reference only and you may delete it if the information in it is no longer required.

Applying V2.0.0.2 PTF to Jazz Team Server for Power Express Edition on IBM i

To update Jazz Team Server for Power Express Edition on IBM i to V2.0.0.2, perform these steps:

  1. Important! Terminate the Jazz Team Server for Power and stop all build engines before loading and applying or removing the PTF.
    1. To stop the server, use the ./stopServer command in
      /QIBM/UserData/WebSphere/AppServer/v61/base/<yourWASInstanceName>/bin for WAS6.1 or /QIBM/UserData/WebSphere/AppServer/v70/base/<yourWASInstanceName>/bin for WAS7.0 
    2. To stop all build engines, navigate to /QIBM/ProdData/RTCp/V2.0/BuildExp/jazz/buildsystem/buildengine/eclipse/RTCiLogs and write down all the folder names in this directory.
    3. On a 5250 command line, type WRKACTJOB and end all jobs in subsystem QUSRWRK that match a job name which you wrote down.
    4. Type CL command WRKSPLF SELECT(*ALL) JOB(<theEndedJobName>) and use option 4 to delete the spool files.
  2. Request and send PTF SI38430 to the IBM i host where you want to update Jazz Team Server for Power Express Edition to V2.0.0.2.
    Note:
    The product 5724Z00 *BASE and Option 1 (Build System Toolkit for Powerand Jazz Team Server for Power Express Edition Version 2.0) must be installed on the IBM i host already. PTF SI38429 which updates Build System Toolkit for Power to Version 2..0.0.2 must be applied already.
  3. Use command LODPTF LICPGM(5724Z00) SELECT(SI38430) with the additional device specification to load the PTF.
  4. Use command APYPTF LICPGM(5724Z00) SELECT(SI38430) to apply the PTF.

As part of applying this PTF, a backup directory containing your 2.0 configuration files will be created with the name backup-config-v2.0-express-SI38430 in /QIBM/ProdData/RTCp/.

The following files will be copied to this backup directory:

  • /QIBM/ProdData/RTCp/V2.0/Express/jazz/server/conf,
  • /QIBM/ProdData/RTCp/V1.0/Express/jazz/server/script_py/RTCi_JVM.qsh.

The workitemindex folder, if it exists in /QIBM/ProdData/RTCp/V2.0/Express/jazz/server, will also be copied to the backup directory.

After applying this PTF, the backed up files and folder will be restored to /QIBM/ProdData/RTCp/V2.0/Express/jazz/server. The backed up configuration files will not be deleted. These will be used to restore the server to its previous configuration, if the PTF is removed.

Attention: Do not delete the backup directory. These files are required if you remove the PTF. If the files are not found when the PTF is removed, the server may end up in an unpredictable state.

Applying V2.0.0.2 PTF to Jazz Team Server for Power Enterprise Edition on IBM i

To update Jazz Team Server for Power Enterprise Edition on IBM i to V2.0.0.2, perform these steps:

  1. Important! Terminate theJazz Team Server for Power and stop all build engines before loading and applying or removing the PTF.
    1. To stop the server, use the ./stopServer command in
      /QIBM/UserData/WebSphere/AppServer/v61/base/<yourWASInstanceName>/bin for WAS6.1 or /QIBM/UserData/WebSphere/AppServer/v70/base/<yourWASInstanceName>/bin for WAS7.0 
    2. To stop all build engines, navigate to /QIBM/ProdData/RTCp/V2.0/Build/jazz/buildsystem/buildengine/eclipse/RTCiLogs and write down all the folder names in this directory.
    3. On a 5250 command line, type WRKACTJOB and end all jobs in subsystem QUSRWRK that match a job name which you wrote down.
    4. Type CL command WRKSPLF SELECT(*ALL) JOB(<theEndedJobName>) and use option 4 to delete the spool files.
  2. Request and send PTF SI38447 to the IBM i host where you want to update Jazz Team Server for Power Enterprise Edition to V2.0.0.2.
    Note:
    The product 5724Z01 *BASE and Option 1 (Build System Toolkit for Power and Jazz Team Server for Power Enterprise Edition Version 2.0) must be installed on the IBM i host already. PTF SI38446 which updates Build System Toolkit for Power to Version 2.0.0.2 must be applied already.
  3. Use command LODPTF LICPGM(5724Z01) SELECT(SI38447) with the additional device specification to load the PTF.
  4. Use command APYPTF LICPGM(5724Z01) SELECT(SI38447) to apply the PTF.

As part of applying this PTF, a backup directory containing your 2.0 configuration files will be created with the name backup-config-v2.0-enterprise-SI38447 in /QIBM/ProdData/RTCp/.

The following files will be copied to this backup directory:

  • /QIBM/ProdData/RTCp/V2.0/Enterprise/jazz/server/conf,
  • /QIBM/ProdData/RTCp/V1.0/Enterprise/jazz/server/script_py/RTCi_JVM.qsh.

The workitemindex folder, if it exists in /QIBM/ProdData/RTCp/V2.0/Enterprise/jazz/server, will also be copied to the backup directory.

After applying this PTF, the backed up files and folder will be restored to /QIBM/ProdData/RTCp/V2.0/Enterprise/jazz/server. The backed up configuration files will not be deleted. These will be used to restore the server to its previous configuration, if the PTF is removed.

Attention: Do not delete the backup directory. These files are required if you remove the PTF. If the files are not found when the PTF is removed, the server may end up in an unpredictable state.

Applying V2.0.0.2 PTF to Jazz Team Server for Power Standard Edition on IBM i

To update Jazz Team Server for Power Standard Edition on IBM i to V2.0.0.2, perform these steps:

  1. Important! Terminate the Jazz Team Server for Power and stop all build engines before loading and applying or removing the PTF.
    1. To stop the server, use the ./stopServer command in
      /QIBM/UserData/WebSphere/AppServer/v61/base/<yourWASInstanceName>/bin for WAS6.1 or /QIBM/UserData/WebSphere/AppServer/v70/base/<yourWASInstanceName>/bin for WAS7.0 
    2. To stop all build engines, navigate to /QIBM/ProdData/RTCp/V2.0/Build/jazz/buildsystem/buildengine/eclipse/RTCiLogs and write down all the folder names in this directory.
    3. On a 5250 command line, type WRKACTJOB and end all jobs in subsystem QUSRWRK that match a job name which you wrote down.
    4. Type CL command WRKSPLF SELECT(*ALL) JOB(<theEndedJobName>) and use option 4 to delete the spool files.
  2. Request and send PTF SI38448 to the IBM i host where you want to update Jazz Team Server for Power Standard Edition to V2.0.0.2.
    Note:
    The product 5724Z01 *BASE and Option 2 (Build System Toolkit for Powerand Jazz Team Server for Power Standard Edition Version 2.0) must be installed on the IBM i host already. PTF SI38446 which updates Build System Toolkit for Power to Version 2.0.0.2 must be applied already.
  3. Use command LODPTF LICPGM(5724Z01) SELECT(SI38448) with the additional device specification to load the PTF.
  4. Use command APYPTF LICPGM(5724Z01) SELECT(SI38448) to apply the PTF.

As part of applying this PTF, a backup directory containing your 2.0 configuration files will be created with the name backup-config-v2.0-standard-SI38448 in /QIBM/ProdData/RTCp/.

The following files will be copied to this backup directory:

  • /QIBM/ProdData/RTCp/V2.0/Standard/jazz/server/conf,
  • /QIBM/ProdData/RTCp/V1.0/Standard/jazz/server/script_py/RTCi_JVM.qsh.

The workitemindex folder, if it exists in /QIBM/ProdData/RTCp/V2.0/Standard/jazz/server, will also be copied to the backup directory.

After applying this PTF, the backed up files and folder will be restored to /QIBM/ProdData/RTCp/V2.0/Standard/jazz/server. The backed up configuration files will not be deleted. These will be used to restore the server to its previous configuration, if the PTF is removed.

Attention: Do not delete the backup directory. These files are required if you remove the PTF. If the files are not found when the PTF is removed, the server may end up in an unpredictable state.

RTC Power: Configuring your installation

After successfully installing Build System Toolkit for Power and Jazz Team Server for Power, complete these tasks to configure your installation.

Edit the following items in <JazzInstallDirectory>/jazz/server/conf/jazz/teamserver.properties. Be careful when editing the properties and .ini files. Use WordPad, Rational Developer for Power Remote System Explorer, or EDTF to ensure that you correctly format the files.

  1. Replace jazzDBuser with your user ID, which must have the authority to create and write to a library on the system.
  2. Replace jazzDBpswd with your password.
    Note:
    Do not modify the entry password={password}.
  3. By default, Jazz Team Server for Power will create and use the library JAZZREPO01 in QSYS.LIB as its repository. If you want to use a different library, uncomment the line (remove the pound sign) with com.ibm.team.repository.db.db2i.schema.name, and replace JAZZREPO01 with the name of the library you want to use. See the following example.
    Note:
    The com.ibm.team.repository.db.jdbc.location line has been wrapped in this example. In your code, that setting and the parameters should be on one line. Also, information about commenting lines can usually be ignored, as the relevant lines should already be commented out (or in).
    #
    # DB2i configuration 
    # 
    # Uncomment the following lines, customize the location to use DB2i
    com.ibm.team.repository.db.vendor = DB2i 
    com.ibm.team.repository.db.jdbc.location=//localhost;hold statements=true;
    		user=jazzDBuser;password={password};
    com.ibm.team.repository.db.jdbc.password=jazzDBpswd 
    com.ibm.team.repository.db.db2i.schema.name=MYREPO 
  4. Optional: Rational Team Concert for Power supports IBM i local authentication and LDAP for security. If you are importing user profiles from LDAP to Jazz Team Server Standard or Enterprise Edition, you need to add the following statement to teamserver.properties: com.ibm.team.repository.user.registry.type=LDAP.

Creating Jazz Team Server for Power database tables

The Repository Tools application is a standalone application that provides a way to manage a Jazz Team Server for Power repository database, including creating and migrating the repository database.

By running this application with various parameters, you can perform commands on the repository database. For example, use the -createTables parameter to create the repository database.

With Jazz Team Server for Power you can launch the application using a script from within a QShell session. The repository tools shell script is located in <JazzInstallDirectory>/jazz/server and is called repotools.qsh. Change directory to <JazzInstallDirectory>/jazz/server. Run the command ./repotools.qsh -createTables to create the database tables for a Jazz Team Server for Power repository.

Note:
  1. The path for the log can be passed directly to the command. For example, ./repotools.qsh -createTables logFile=/QIBM/UserData/User1/createRTCiTables.log. By default, this command will create a log file called repotools_createTables.log, which contains information that is recorded when you create the tables, and also a statement about whether you created the tables successfully. This log file is created in the current directory unless you provide a different file path. If you want to use a different log file name, modify the command link in the example above.
  2. By default, this command looks for configuration information in a teamserver.properties file located in <yourInstallDirectory>/jazz/server/conf/jazz and it uses the configuration parameters in that file to create the repository. It uses the user ID and password you specified in that file to create the repository library and tables, and will create the repository in the library using the name you specified (if you changed the default from JAZZREPO01).
  3. Go to Migrating > Migrating the Jazz Team Server > Repository Tools Overview at the Rational Team Concert for Power Information Center for more information about the repository tools application.

Setting up WebSphere Application Server

Before you can set up Jazz Team Server for Power, you must create a WebSphere Application Server runtime environment. This runtime environment is defined by a profile that you can modify, and it includes all of the files that the server processes in the runtime environment. (These are files that you can change.) During WebSphere Application Server installation, a default profile named default is created. The default profile is a standalone application server profile that contains a single application server called server1. You can use this default profile for Jazz Team Server for Power; or to create a new standalone application server, you can create a new profile using the manageprofiles command.

Consult either Frequently asked questions, the WebSphere Application Server 6.1 Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp, or the WebSphere Application Server 7.0 Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp. There you can find information about creating and managing WebSphere Application Server profiles, WebSphere Application Server administration, and WebSphere Application Server security. You can also refer to the manageProfiles command, found in the bin directory of your WebSphere Application Server installation. For example: Command ./manageprofiles -create -profileName WAS4RTCI in directory/QIBM/ProdData/WebSphere/AppServer/V61/Base/bin for WebSphere Application Server 6.1, or /QIBM/ProdData/WebSphere/AppServer/V7/Base/bin for WebSphere Application Server 7.0.

The steps that follow in this guide are intended to provide you only with basic WebSphere Application Server configuration guidance, and not complete instructions for WebSphere Application Server administration. For the following topics, refer to the WebSphere Application Server that you are using for Jazz Team Server for Power. This server might be the default server, or it might be a new server that you created solely for Jazz Team Server for Power. In this document, this server is referred to as <yourWASInstanceName>.

After you have determined whether you will use the default WebSphere Application Server or a new server, deploy Jazz Team Server for Power to your WebSphere Application Server.

The instructions for setting up your WebSphere Application Server with Jazz Team Server for Power are divided into four parts:

Before you continue, run the following command from any directory within QShell to give read and write access from Jazz Team Server for Power to the /tmp directory:

  • chmod -R 777 /tmp
Part 1: Setting Java Virtual Machine parameters

WebSphere Application Server Java Virtual Machine (JVM) properties are required to point to your directories and files. These parameters are automatically set up using a provided script.

To set the JVM parameters, complete the following steps:

  1. Log on to IBM i, and enter the QSH command.
  2. To start the server, navigate to the directory containing the WebSphere Application Server commands and executable files. For example: cd /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/bin.
  3. Start the server using the ./startServer command. When the server has started, the system will provide a port number that you can use to access the WebSphere Application Server Integrated Solutions console. For example:
    CPC1221: Job 107206/QEJBSVR/SERVER1 submitted to job queue QWASJOBQ in
    		library QWAS61.
    CWNATV00I: Application server server1 in profile default has started and is
    		ready to accept connections on admin port 9060. 
  4. To access the WebSphere Application Server console, replace <yourWASAdminPortNumber> with the port number the system provided in the following URL: http://<yourServerHostName>:<yourWASAdminPortNumber>/ibm/console.
    Note:
    Both the <yourServerHostName> and <yourWASAdminPortNumber> variables must be replaced with the name that you chose to assign to your server and your port.
  5. Log on to the WebSphere Application Server Integrated Solutions console. A user ID is not needed because security is not set.
  6. Expand Environment, select WebSphere Variables, and click the right arrow to go to Page: 2 of 2.
  7. From the list of names, copy the information from the Value fields for the following variable names and paste to a text editor file: USER_INSTALL_ROOT, WAS_CELL_NAME, and WAS_SERVER_NAME.
  8. Add /bin to the directory path value you pasted for USER_INSTALL_ROOT. For example: /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/bin.
  9. Navigate to the script directory script_py where your Jazz Team Server for Power is installed on IBM i:
    cd /<JazzInstallDirectory>/jazz/server/script_py.
  10. Modify the RTCi_JVM.qsh with the USER_INSTALL_ROOT value you pasted and modified in a previous step.
  11. In the qsh command line, invoke the script to populate the JVM custom properties using the following command: ./RTCi_JVM.qsh.

    The WebSphere Application Server will prompt you for your WAS_CELL_NAME and WAS_SERVER_NAME.

  12. When you are prompted to indicate a Maximum Heap Size, it is recommended that you select 768 MB; however, you can also choose to set the value to match your available IBM i memory, instead .
Part 2: Securing WebSphere Application Server

Jazz Team Server requires that WebSphere Application Server administrative security and application security are enabled. Jazz Team Server for Power uses the functions of WebSphere Application Server security to validate user IDs and passwords. In addition, WebSphere Application Server security is used to assign Jazz Team Server for Power repository permissions to a particular user ID. This assignment can be done for individual users or groups of users, based on the facilities of the security provider. This mapping of user IDs to repository permissions is discussed further in Part 3: Installing the Jazz Web archive file. For more information about WebSphere Application Server 6.1, go to http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp, for more information about WebSphere Application Server 7.0, go to http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp.

Part 2: Securing WebSphere Application Server and Securing WebSphere Application Server with LDAP introduce information on securing WebSphere Application Server with either IBM i or LDAP authentication.

Securing WebSphere Application Server with IBM i authentication

The following steps describe one way to secure the WebSphere Application Server using IBM i as the security provider.

Note:
Your WebSphere Application Server must be running to complete these steps. The steps in this example are for WebSphere Application Server V6.1, for WebSphere Application Server V7.0 the paths are slightly different.

  1. Navigate to the WebSphere Application Server administration directory using the cd command. For example: cd /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/bin.
  2. Use the wsadmin command to start the WebSphere Application Server administration tool. For example:
    ./wsadmin
      WASX7209I: Connected to process "server1" on node LOTI19 using 
      SOAP connector  ;  The type of process is: UnManagedProcess
      WASX7029I: For help, enter: "$Help help"
    wsadmin>
  3. Secure the WebSphere Application Server profile with a valid user ID and password by entering the following command: securityon <yourUserID> <yourPassword>. This user ID and password will be used to access the secure WebSphere Application Server administrative console, and has authority to stop the application server after it is secured.
  4. Use the quit command to stop the WebSphere Application Server administration tool.
  5. For the changes to take effect, you must stop the server using the ./stopServer command and restart it using the ./startServer command in /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/bin. When the server has restarted, a message displays that is similar to:
    CPC1221: Job 107206/QEJBSVR/SERVER1 submitted to job queue QWASJOBQ in
    		library QWAS61.
    CWNATV00I: Application server server1 in profile default has started and is
    		ready to accept connections on admin port 9060.
Securing WebSphere Application Server with LDAP

If you want to secure your Jazz Team Server for Power by requiring users to authenticate through an LDAP server, you must secure your WebSphere Application Server with LDAP. You can configure your server to use LDAP security in one of several ways. Please review the following articles for information about configuring WebSphere Application Server security using LDAP:

Note:
  1. Ignore any references in these articles to Tomcat or Derby, as these are not applicable to Rational Team Concert for Power on IBM i.
  2. You must be a registered user of jazz.net to access articles on that site.
  3. To use LDAP for security, you must have an LDAP server to use with Jazz Team Server for Power.
  4. To get basic information about setting up IBM Tivoli Directory Server for i (LDAP), go to
    http://publib.boulder.ibm.com/infocenter/systems/topic/rzahy/rzahy.pdf.

After you have secured the WebSphere Application Server with LDAP, you can use user IDs and groups from your LDAP server to grant Jazz Team Server for Power repository permissions, and also to create Jazz Team Server for Power repository users that map to LDAP users.

For information about Rational Team Concert for Power server administration configuration of WebSphere Application Server 6.1, go to http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp, for WebSphere Application Server 7.0, go to http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp.

Note:
You must perform LDAP authentication in the WebSphere Application Server console.
Part 3: Installing the Jazz Web archive file

Jazz Team Server for Power is composed of a Web archive file called jazz.war, along with certain other dependent files. The jazz.war file must be installed on your WebSphere Application Server if you want to be able to use Jazz Team Server for Power. Use the following procedure on the WebSphere Application Server Integrated Solutions console to install the file:

  1. Use a Web browser to log on to the WebSphere Application Server Integrated Solutions console with a URL like http://<yourServerHostName>:<yourWASAdminPort>/ibm/console/. For example,
    http://<yourServerHostName>:9060/ibm/console
    If you followed the setup in Part 2, you have already enabled WebSphere Application Server security, and you will be redirected to a secure port.
  2. Ensure that the WAS security setting Use available authentication data when an unprotected URI is accessed is checked. If you are using the WAS Integrated Solutions Console, you can do this by:
    1. Navigating to Security -> Secure administration, applications, and infrastructure -> Web Security - General Settings.
    2. Selecting the checkbox for Use available authentication data when an unprotected URI is accessed. Click OK to apply the changes and select Save changes to save to the master configuration.
  3. Expand Applications, then click Enterprise Applications
  4. On the Enterprise Applications window, click Install.
  5. For Path to new application, select Remote file system.
  6. Navigate to the jazz.war file at <JazzInstallDirectory>/jazz/server/jazz.war.
  7. Set Context root to /jazz.
  8. Under How do you want to install the application?, select Show me all installation options and parameters and click Next.
  9. Complete each subsequent step, accepting all defaults until you get to Map security roles to users or groups. The security roles and levels of access defined by the Jazz Team Server for Power include:
    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 repository
    JazzProjectAdmins
    Administrators of a Jazz repository with specific permissions to create and modify project areas, team areas, and process templates

    There are two options for mapping security roles. If you have many users, it is more efficient to create group profiles on IBM i and map those groups to Jazz Team Server for Power roles rather than mapping a large number of individual users.

    To map groups of users to Jazz Team Server for Power roles (recommended):
    1. On IBM i, create Group Profiles using names such as JAZZADMINS, JAZZDWADMS, JAZZGUESTS, JAZZUSERS, JAZZPRJADM. (There is a ten-character limit.)
      Note:
      These group profile names are suggestions only. You can choose to assign any group profile name you prefer (up to ten characters in length).
      For more information about creating group profiles on IBM i, go to Frequently asked questions.
    2. Assign users to the appropriate group profiles.
    3. On the WebSphere Application Server Integrated Solutions console, use Look up groups to map those groups of users to their corresponding roles.
      1. Select JazzAdmins and click Look up groups.
      2. On the next screen, click Search, and select at least one group from the Available list and move it to Selected using >>.
        Note:
        The WebSphere Application Server console displays only those groups that have at least one user assigned.
      3. Repeat these steps for JazzDWAdmins, JazzUsers, and JazzGuests, JazzProjectAdmins.
    To map individual users to Jazz Team Server for Power roles:
    1. Select JazzAdmins and click Look up users.
    2. On the next screen, click Search, and select at least one user ID from the Available list and move it to Selected using >>.
    3. Repeat these steps for JazzDWAdmins, JazzUsers, and JazzGuests, JazzProjectAdmins.
    Note:
    This setup is different if you use LDAP security. The users and groups in this case would correspond to user IDs or groups on your LDAP server. For more information on LDAP security and Jazz, see https://jazz.net/jazzdocs/topic/com.ibm.team.install.doc/topics/c_plan_identity_management.html.
  10. Click Finish, then Save directly to the master configuration. When the save is complete, a red x is displayed under Application status for jazz.war.
  11. Select the jazz.war.radio button, and click Start.

The jazz.war file is now installed. At this point, you should re-start the WebSphere Application Server by running the ./stopServer command followed by the ./startServer command when the stop command completes.

Part 4: Verifying the installation

Complete the following steps to ensure the application is installed and set up properly:

  1. The WebSphere Application Server logs provide informational and error messages related to the Jazz Team Server. You must verify that the correct JVM is being used by this application server instance. For example, navigate to /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstanceName>/logs/<yourWASInstanceName> and check the SystemOut.log.
  2. Verify that J9 VM is initiated by ensuring the first few lines of the log include text that refers to the IBM J9 VM. Your log should be similar to the following:
    ************ Start Display Current Environment ************
    WebSphere Platform 6.1 [BASE 6.1.0.23 cf230910.10]  running with process name ........
    Detailed IFix information: No IFixes applied to this build
    Host Operating System is OS/400, version V6R1M0
    Java version = 1.5.0, Java Compiler = j9jit23, Java VM name = IBM J9 VM
    was.install.root = /QIBM/ProdData/WebSphere/AppServer/V61/Base
    . . . . . . . . . . . . .
    Note:
    If you discover that you are not using the IBM J9 VM, you must use the enableJVM command with the std32 option to enable it. For example, in QSH, change the directory to /QIBM/ProdData/WebSphere/AppServer/V61/Base/bin and run the command enableJVM -jvm std32 -profile MYPROFILE.
  3. Access the Jazz Team Server administrative Web interface using the secure port associated with the application server virtual host to which you installed the jazz_war application. In a default application server, this is port 9443. Use this port to access the Jazz Team Server administrative Web interface to verify the server status using a Web browser, for example, https://<yourServerHostName>:<yourJazzServerPortNumber>/jazz/admin. Log in with a user ID that has JazzAdmins permission and verify that the Server Status summary does not display any error messages.
Note:
If you are unsure of the secure port used for your WebSphere Application Server profile, you can determine the port from the IBM i HTTP Server Administration, which you can access at http://<yourServerHostName>:2001/HTTPAdmin. Click Manage > Application Servers, and select your WebSphere Application Server profile. Click Server Ports in the left menu. The Secure HTTP port is where the Jazz server is available. Use this port as the secure port to access the Jazz Team Server.

Alternately, in a typical WebSphere Application Server configuration, you can determine the secure port for the Jazz Team Server for Power as follows:

  1. Log in to the WebSphere Administration Console in the same way that you did to install the Jazz Team Server Web archive file. For example: http://<yourServerHostName>:<yourWASAdminPortNumber>/ibm/console.
  2. Click Servers > Application Servers, then MYPROFILE.
  3. Select the Configuration tab. Under Comunications, expand the Ports section. The port name WC_defaulthost_secure is typically the port used for secure Jazz Team Server for Power access.

Completing the installation

This topic describes how to complete the installation of Rational Team Concert for Power.

Licensing considerations

By default, Rational Team Concert for Power on IBM i is installed with a trial license. If you are evaluating Rational Team Concert for Power, you can skip this section.

To convert a license from trial to permanent, download the Server Activation Key file from Passport Advantage. In Passport Advantage, right-click the file and select Save. Install the key by performing these steps:

  1. In a Web browser, enter the URL for the Jazz Team Server Administrative page. For example: https://<yourHostServerName>:<yourJazzServerPortNumber>/jazz/admin.
  2. Log in with your Jazz administrative user account.
  3. Click Server.
  4. In the Configuration section, click License Key Management.
  5. In the Server Activation Key section, click Edit.
  6. In the dialog that displays, click Browse.
  7. Navigate to the jazz_team_server_express_p-release.jar, jazz_team_server_standard_p-release.jar, or jazz_team_server_enterprise_p-release.jar file, select it, then click Open to upload the key.
    Note:
    If you purchased additional IBM Rational Team Concert for Power Systems Software client licenses from Passport Advantage, download the Contributor and Developer Client Activation Key files from Passport Advantage. Install the keys by performing the steps above, except that in step 5 you must click Add in the Client Access License Types section, not the Server Access License Types section. Make sure to enter the number of Contributor or Developer licenses you have purchased.
  8. Click Finish to save your changes.

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

  • Refer to the Rational Team Concert for Power Information Center for important information about additional administrative tasks, including creating users, creating project areas and teams, configuring e-mail settings, and configuring advanced properties.
  • Some files contain passwords. Those files should be protected so that they are readable only by users who are authorized to know the password for the accounts. The Jazz Team Server for Power requires that the database password is stored in <JazzInstallDirectory>/server/teamserver.properties. You can encrypt the passwords by changing any one of the advanced properties and saving the properties file. To do this:
    1. Go to http://<yourServerHostName>:<yourJazzServerPortNumber>/jazz/admin.
    2. Click Advanced properties on the left side.
    3. Change any one of the properties and save the file. Change the property setting back to its previous value, if you do not wish to keep the new setting.
    By saving the properties file, the passwords are now encrypted. When the properties file is saved, the application always makes a backup copy of the previous version in the same directory. Remove all backup properties files that contain the clear-text password, after configuring the server for the first time. You should also delete the copy of teamserver.properties, if it exists in directory /QIBM/ProdData/RTCp
  • If you configured the application server to use ports other than the defaults, these ports should also be configured in the Jazz Team Server for Power configuration. These port numbers are used for composing URLs for things like feed links and item links in e-mail notifications. To update the defaults, use the Jazz Team Server for Power administrative Web interface. Click Configuration, then Advanced Properties to locate the properties below.
    • com.ibm.team.repository.servlet.internal.ServletConfigurationService
      • Repository HTTPS port
    • com.ibm.team.repository.service.internal.webuiInitializer. ConfigPropertyInitializer
      • URL HTTPS port
    Click Edit to enable the editing of these properties, then click Save to save your changes.
Note:
When using IBM i authentication, giving a user access to Jazz Team Server for Power is a three-step process:
  1. Create the IBM i user ID. If you are using group profiles, add the user to the group, otherwise you need to add the user mapping. See To map individual users to Jazz Team Server roles in Part 3: Installing the Jazz Web archive file for more details.
  2. Create a corresponding user in the Jazz Team Server for Power repository.
  3. Give the Jazz Team Server for Power user the correct user permissions as developer or contributor.

Troubleshooting and getting help

Jazz Team Server for Power logs informational, warning, and error messages that you can use to troubleshoot, and which you might need when you report a problem. The log4j.properties file controls the log file location and format, and you can find this file at <JazzInstallDirectory>/jazz/server/conf/jazz. By default, the Jazz Team Server for Power records messages in the WebSphere Application Server log files, and also in a separate jazz.log file. For WebSphere Application Server V6.1, these log files are located in a directory with a name that is similar to this:

  • /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstance>/logs

This log contains only Jazz Team Server for Power messages and is not automatically cleared, so you should delete it periodically when it gets too large.

The WebSphere Application Server V6.1 files are located in the logs directory for your server profile and server instance, in a directory with a name that is similar to this:

  • /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/<yourWASInstance>/logs/<yourWASInstance>
Note:
For WebSphere Application Server V7.0, these log files are located in a directory with a name that is similar to this:
  • /QIBM/UserData/WebSphere/AppServer/V70/Base/profiles/<yourWASInstance>/logs
  • /QIBM/UserData/WebSphere/AppServer/V70/Base/profiles/<yourWASInstance>/logs/<yourWASInstance>

To troubleshoot, start with the SystemOut.log and the SystemErr.log, although other logs in that directory might also contain helpful information. These logs contain both WebSphere Application Server messages and Jazz Team Server for Power messages. Note, however, that when one of these logs reaches 1024 MB, the WebSphere Application Server automatically closes and saves it as one historical log. You can change this action in the WebSphere Application Server Administration Console by performing the following steps:

  1. Within the WebSphere Administration Console, select TroubleShooting.
  2. Select Logs and Trace.
  3. Select JVM Logs.
  4. Configure the maximum log size and the maximum number of historical files to keep, according to your preferences.
Note:
For guidance on more effective bug reporting, see How to Report Bugs Effectively at

Information about Rational Developer for Power APAR/PTF is available online at

To find more information about any required Power Systems server PTFs, do the following:

  1. Open the Remote System Explorer perspective. The name of the current perspective is displayed in the top left corner of the title bar for the Window. To open the Remote System Explorer perspective, select Window > Open Perspective > Other, then select Remote System Explorer from the list.
  2. Create a connection to IBM i by expanding New Connection > IBM i.
  3. Expand your new connection and right-click IBM i Objects. Select Verify Connection from the menu. This displays a dialog that shows which required PTFs are already installed on the system and which ones are missing.
Frequently asked questions

The following are answers to some of the questions that are frequently asked about installing Rational Team Concert for Power on IBM i.

Question:

Where are the startserver and stopserver files located and how do I use them?

Answer:

Navigate to your WebSphere Application Server bin directory. For example: /QIBM/ProdData/WebSphere/AppServer/V61/Base/bin. Use the ./startserver command to start or the ./stopserver command to stop. If you need to start or stop a WebSphere Application Server instance other than the default WebSphere Application Server instance, you can pass the -profileName parameter to the ./startserver or ./stopserver commands.

Question:

How do I create a WebSphere Application Server profile?

Answer:

To create a WebSphere Application Server profile that you can use to start a new WebSphere Application Server instance, perform these steps:

  1. From QShell, navigate to your WebSphere Application Server installation directory. For example: cd /QIBM/ProdData/WebSphere/AppServer/V61/Base/bin.
  2. Use the manageprofiles command to create a new profile. For example: ./manageprofiles -create -profileName WAS4RTCI.
  3. The manageprofiles command will tell you whether you successfully created the profile, and then direct you to the log file that was generated when you created the profile.
Note:
The process of creating a WebSphere Application Server profile takes several minutes to complete. This delay is normal.

Question:

How do I create IBM i group profiles?

Answer:

  • Here are examples of IBM i commands that you can use to create group profiles on IBM i to be used with the Jazz Team Server for Power:
    • crtusrprf usrprf(JAZZADMINS) password(*none) grpprf(*none) text('Group profile for JAZZADMINS')
    There are four user roles associated with the Jazz Team Server for Power application:
    • JazzAdmins
    • JazzDWAdmins
    • JazzUsers
    • JazzGuests
    • JazzProjectAdmins

    You can create a separate group for each of these roles by repeating the command above with a different usrprf name.

  • To assign a valid user ID to a group, use the command chgusrprf usrprf(MONDIEU) grpprf(JAZZADMINS).
  • You can also assign a supplemental group.

Consult the IBM i Information Center for additional information.

Question:

Where do I find provisioning information for the Jazz Team Server for Power?

Answer:

You can view the results of the provisioning process from the Jazz Team Server for Power administrative Web interface, using a URL similar to https://<yourServerHostName>:<yourJazzServerPortNumber>/jazz/admin#action=com.ibm.team.repository.admin.provisionStatus.

  1. If there are error messages, you can use them to diagnose any problems.
  2. After fixing these problems, reset the Jazz Team Server for Power to reprovision with the new settings.
  3. You can then click to check the Provision Status again.

Installing the Build System Toolkit for Power Systems Software

The Build System Toolkit for Power Systems Software can be installed on the build machines using a .zip file, the IBM Installation Manager or IBM i licensed programs.

Installing the Build System Toolkit for Power Systems Software from the IBM Installation Manager

The Build System Toolkit for Power Systems Software can be installed on the build machines using the IBM Installation Manager.

About this task

  1. Start the launchpad program.

    If the Installation Manager is not running, start it.

    Note:
    You must have administrator privileges to run the launchpad program.
    • If you are using the Installation Manager local install for server, build system toolkit and optional components .zip file, extract the contents of the archive into a temporary directory and run the launchpad program.
      • To run the file on Windows, run this command:
        launchpad.exe
      • To run the file on AIX, run this command:
        sh launchpad.sh
  2. When the launchpad program appears, click on the Rational Team Concert for Power Systems Software - Build System Toolkit to start the installation process.
  3. After the installation is complete, you can configure a build. More information about the Build System Toolkit for Power Systems Software can be found in About Jazz team build.

Installing the Build System Toolkit for Power Systems Software from a .zip file

The Build System Toolkit for Power Systems Software can be installed on the build machines using a .zip file download.

About this task

To install the Build System Toolkit for Power Systems Software from a .zip file:

  1. Download the Build System Toolkit for Power Systems Software .zip file.
  2. Extract the .zip file into the JazzInstallDir directory.
  3. Before running jbe.sh, consider using ls -l to make sure that jbe.qsh has x (executable) permission. If it is -rw-rw-rw-, use chmod a+x jbe.sh to make it executable
  4. After the installation is complete, you can configure a build. More information about the Build System Toolkit can be found in About Jazz team build.

Installing the Build System Toolkit for Power Systems Software on IBM i

The Build System Toolkit for Power Systems Software can be installed on IBM i using the licensed program installation process.

After restoring the licensed program, the Build System Toolkit for Power Systems Software is installed in the following directory: /QIBM/Proddata/RTCp/V2.0/Build or /QIBM/Proddata/RTCp/V2.0/BuildExp. For more information see Installing Build System Toolkit for Power Systems Software on IBM i.

Installing Rational Team Concert for Power Systems Software Connectors

Jazz Team Server for Power Systems Software integrates with Rational ClearQuest® and Rational ClearCase®. However, note that if you are running Jazz Team Server for Power Systems Software on IBM i, integration with these products is provided only as a technical preview on an as-is basis. There is no implied support when running the team server on IBM i. To install the ClearCase Connector and ClearQuest Connector connectors:

Installing Rational Team Concert for Power Systems Software ClearCase Connector

To install the ClearCase Connector:

Installing Rational Team Concert for Power Systems Software ClearCase Connector using the IBM Installation Manager

The ClearCase Connector can be installed on the build machines using the IBM Installation Manager.

About this task

  1. Start the launchpad program.

    If the Installation Manager is not already running, complete the following steps to start it.

    Note:
    You must have administrator privileges to run the launchpad program.
    • If you are using the Full product DVD, insert the disk in the DVD driver and run the launchpad program.
      • To run the file on Windows, run this command:
        launchpad.exe
  2. When the launchpad program appears, click on the ClearCase Connector to start the installation process.
  3. After the installation is complete configure the ClearCase Connector. See Deploying ClearCase Connector.

Installing Rational Team Concert for Power Systems Software ClearCase Connector from a .zip file

The ClearCase Connector can be installed on the build machines using a .zip file download.

About this task

  1. Download the ClearCase Connector .zip file.
  2. Extract the .zip file into the JazzInstallDir directory.
  3. After the installation is complete configure the ClearCase Connector. See Deploying ClearCase Connector.

Installing Rational Team Concert for Power Systems Software ClearQuest Connector

To install the ClearQuest Connector:

Installing Rational Team Concert for Power Systems Software ClearQuest Connector using the IBM Installation Manager

The ClearQuest Connector can be installed on the build machines using the IBM Installation Manager.

About this task

  1. Start the launchpad program.

    If the Installation Manager is not already running, complete the following steps to start it.

    Note:
    You must have administrator privileges to run the launchpad program.
    • If you are using the Full product DVD, insert the disk in the DVD driver and run the launchpad program.
      • To run the file on Windows, run this command:
        launchpad.exe
  2. When the launchpad program appears, click on the ClearQuest Connector to start the installation process.
  3. After the installation is complete configure the ClearQuest Connector. See Deploying ClearQuest Connector.

Installing Rational Team Concert for Power Systems Software ClearQuest Connector from a .zip file

The ClearQuest Connector can be installed on the build machines using a .zip file download.

About this task

To install the ClearQuest Connector from a .zip file:

  1. Download the ClearQuest Connector .zip file.
  2. Extract the .zip file into the JazzInstallDir directory.
  3. After the installation is complete configure the ClearQuest Connector. See Deploying ClearQuest Connector.

Installing Rational Team Concert for Power Systems Software Client

RTC Power: Client installation overview

The Rational Team Concert for Power Systems Software client requires Rational Developer for Power Systems Software to be installed. Both of these products are installed using IBM Installation Manager.

The Jazz Team Server for Power Systems Software, Rational Team Concert for Power Systems Software client, Build System Toolkit for Power Systems Software, ClearCase Connector, ClearQuest Connector and other incubator files can be downloaded from https://jazz.net. To purchase Rational Team Concert for Power Systems Software, go to http://www.ibm.com/software/rational/products/rtcp/, where you can download an installable image or order a DVD. To purchase Rational Developer for Power Systems Software, go to http://www.ibm.com/software/rational/products/rdp/, where you can download an installable image or order a DVD.

If you are a Power Systems developer, download an executable file that will run the IBM Installation Manager launchpad program to guide you through the install process.

If you are not a Power Systems developer or you do not need the Power Systems extensions, you can administer the Jazz Team Server for Power through the Web interface or install the Rational Team Concert client from https://jazz.net.

Note:
The Rational Team Concert for Power Systems Software client must be installed into an existing Rational Developer for Power Systems Software product which. This is done using Installation Manager and is sometimes referred to as shell sharing or installing into the same package group. The Installation Manager simplifies shell sharing by allowing you to choose an existing instance of Rational Developer for Power Systems Software to install the client into. The Rational Team Concert for Power Systems Software client contains the core Rational Team Concert client and RPG and COBOL Collaboration Tools for i. Only when RPG and COBOL Development Tools for i feature in Rational Developer for Power Systems Software is installed, RPG and COBOL Collaboration Tools for i feature in Rational Team Concert for Power Systems Software will be enabled for installation.

RTC Power: Installing the client using the IBM Installation Manager

The client is distributed as a downloadable file via the IBM Installation Manager.

About this task

Note:
You must install the client into an existing Rational Developer for Power Systems Software package group instance using the IBM Installation Manager. The IBM Installation Manager install allows you to select the package group for the Rational Developer for Power Systems Software instance you want to extend and takes care of managing future updates, rollbacks, and modifications.

  1. Download or get one of the following installation packages.

    There are two methods to install the Rational Team Concert for Power Systems Software client.

    • Installation Manager local install for client .zip file: This archive file contains the Installation Manager launchpad program and a local copy of the Rational Team Concert for Power Systems Software client. This is a .zip file that is not self extracting. This method allows the installation to proceed without an Internet connection once the .zip file is downloaded.
    • Full product DVD: This contains the Installation Manager launchpad program and a local copy of all the installable resources including server, client, build system toolkit and optional components. The benefit of using this install is that it allows the installation to proceed without an Internet connection.
  2. Start the launchpad program.

    If the Installation Manager is not already running, complete the following steps to start it.

    Note:
    You must have administrator privileges to run the launchpad program.
    • If you are using the Installation Manager local install for client .zip file, extract the contents of the archive into a temporary directory and run the command:
      launchpad.exe
    • If you are using the Full product DVD, insert the disk in the DVD driver and run the command:
      launchpad.exe
  3. You can install the following clients:
    • To install Rational Team Concert for Power Systems Software client, click Rational Team Concert for Power Systems Software Client link.
    • To install Rational Team Concert for Power Systems Software client for Microsoft Visual Studio, click Rational Team Concert Client for Microsoft Visual Studio IDE link.
      Note:
      The Rational Team Concert Client for Microsoft Visual Studio IDE is available for install if you are using the Full product DVD or it can be downloaded from https://jazz.net.
    The Installation Manager wizard is displayed. The wizard guides you through to install the client.
    Note:
    The Rational Team Concert for Power Systems Software client is an extension of Rational Developer for Power Systems Software. Extensions can be installed into a common package group only and will share a common user interface. You must ensure that you have previously installed Rational Developer for Power Systems Software and then select its package group when you install Rational Team Concert for Power Systems Software.
  4. Start the client by clicking the IBM Rational Team Concert for Power Systems Software shortcut created by the installation or from the Start menu. For example, click Start -> Programs -> IBM Software Delivery Platform -> IBM Rational Team Concert for Power Systems Software.
  5. Connect to the server. The easiest way to connect to a server is using the Team Invitation. If you do not have an invitation you can connect manually.
    1. Click File -> Accept team invitation. The wizard guides you through the process.
      Note:
      If you do not have an invitation you need the URI or URL from your server admin (an example format is: https://example.com:9443/jazz). Click on the connecting to an existing project area hyperlink that appears in the bottom right corner of the Accept Team Invitation window.
    2. Follow the instructions in the wizard to set up your connection.

Example

Trouble Shooting: Here are some suggested problem management techniques.

  • Start with an empty workspace.
  • The client and the server builds must match. Make sure the build ID's match for both the client and server distributions.
  • Make sure the server is up. Confirm using the status URL: https://example.com:9443/jazz.

What to do next

After you have successfully installed the client, you should refer to the following topics to help you get started with Rational Team Concert for Power Systems Software.

Release notes - Rational Team Concert for Power Systems Software V 2.0.0.2

This document contains information about system requirements, installation, and known issues for Rational Team Concert for Power Systems Software V 2.0.0.2. It also provides information about contacting IBM Rational Software Support.

Contents

Description

Rational Team Concert for Power Systems Software V 2.0.0.2 is a team collaboration tool that is built on a scalable, extensible platform that integrates tasks across the software lifecycle. In addition, it also offers the following features:

  • Collaboration and integration across the development lifecycle
  • Process configuration and customization
  • Eclipse client and Web interfaces
  • Powered by the Jazz technology platform
  • Extensions to facilitate team collaboration on IBM i, including:
    Builds:
    • The new IBM i build specification allows you to define what objects to build from an i Project, how to build these objects, which dependencies would require a rebuild of these objects. It also allows you to define inter-project dependencies.
    • There is a new team build definition which uses this new IBM i build specification, which enables you to specify library mappings for IBM i projects, to specify library list search paths when building, and to specify other property and substitution variables to be applied at the time of the build.
    • Individual developers can also submit builds to their own libraries using the IBM i build specification.
    • There is support for loading and building changesets which were delivered after a specified prior snapshot version of the source.
    • There is improved logging of build error messages in the build results.
    • There are additional options for starting the build engine.
    Change Promotion:
    Improved instructions on configuring process, source control and builds for change promotion.
    Auditing:
    There is an enhancement to tag binary objects created from a build (e.g. *PGM objects) with a build identifier, so that these objects can be mapped back to the version of source from which they were created.

System requirements

For information about hardware and software compatibility, see the product Web site for Rational Team Concert for Power Systems Software V 2.0.0.2 at http://www.ibm.com/software/rational/products/rtcp/.

Supported integrations

The following integration environments are supported with Rational Team Concert for Power Systems Software V 2.0.0.2.

Note:
If you are running Jazz Team Server for Power Systems Software on IBM i, integration with these products is provided only as a technical preview on an as-is basis. There is no implied support when running the team server on IBM i.

  • The ClearCase Connector component connects the following versions of IBM Rational ClearCase:
    • 7.0.1
    • 7.1
  • The ClearQuest Connector component connects to the following versions of IBM Ration ClearQuest:
    • 7.0.1
    • 7.1
  • The Subversion importer connects to the following version of Subversion:
    • 1.4.6

Installing Rational Team Concert for Power Systems Software V 2.0.0.2

For step-by-step installation instructions, see these topics in the information center:

Known problems

Known problems are documented in the form of individual technotes in the Support knowledge base. As problems are discovered and resolved, the IBM Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

The following link launch a customized query of the live Support knowledge base:

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml