Update the JVM arguments. The Jazz Team
Server needs
some specific settings on the Java Virtual
Machine in which it is run.
First, it needs to know where to
find the configuration files for the server and for log4j, the logging
framework used by the server. This is done by setting the system properties
com.ibm.team.server.configURL and log4j.configuration. These properties
use 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 is
running. A typical medium-size team can use a value of -Xmx1000M,
providing 1000 MB of heap memory for the Jazz Team
Server process.
If
you are connecting to an Oracle database then you need to add a property
named "ORACLE_JDBC". Set the property to the absolute file path (not
a URL) to the Oracle 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 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 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.
- Click Save directly to the master
configuration.