This topic describes how to set up the
Jazz Team Server for System z to work with WebSphere® Application
Server.
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 System z stores user records with user IDs in
exact case as they are imported. When you log in to the Jazz Team
Server for System z, 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 System z .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:
- Navigating to Security -> Secure administration, applications,
and infrastructure -> Web Security - General Settings.
- Selecting the checkbox for "Use available authentication data
when an unprotected URI is accessed".
- The Jazz Team Server for System z 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 System z 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 System z 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.
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.
- 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).
- Verify or update the WebSphere Application
Server level. See the Detailed System Requirements for the Rational Team
Concert for System z server environments.
- Update the JVM arguments.
The Jazz Team Server
for System z 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 System z 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 System z 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 System z installation directory:
- Click on .
- Click on server1.
- Click on .
- Click on Java Virtual Machine.
- Add the value 100 to the Initial Heap.
- Add the value 1000 to the Maximum Heap Size.
- Click Apply.
- Click Logging and Tracing. Click Change
Log Detail Levels. The Jazz Team Server for System z 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.
- Click Custom Properties
- 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
- Click Save directly to the master
configuration.
- 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.
- Open the Admin console for your WebSphere Application
Server.
- Click on .
- Under Path to new Application,
click Local file system.
- Under Full path enter:
JazzInstallDir/server/jazz.war
- Set Context Root to /jazz.
- Click Next and continue through
the remaining Install New Application steps.
- Click Finish.
- Click Save directly to the master
configuration.
- Click on .
- Select the box next to jazz_war; click Start.
A green arrow should appear indicating the application
started successfully.