Deploying and starting the Jazz™ Team
Server begins with the selection of the application server, which
hosts the Jazz Team Server and
its applications. Before you can deploy the Lifecycle Query Engine
war files, you must set up your WebSphere® Application
Server..
Before you begin
- The Java™ 2 Security option
must be turned off. If this option is turned on in WebSphere Application Server, the web application
will not start.
- Click .
- Under Java 2 security, clear
the check box for Use Java 2
security to restrict application access to local resources.
- Ensure that the Enable administrative security and Enable
application security check boxes are selected.
- Ensure that the Use available authentication data when an unprotected
URI is accessed application server security setting is selected.
If you are using the Integrated Solutions Console for the server,
use the following steps to verify this setting:
- Click .
- Click the Use available authentication data when an
unprotected URI is accessed check box.
- Click OK and Save directly to
the master configuration.
- To ensure that the LTPA cookies are secure, enable the Requires
SSL setting:
- In WebSphere Integrated
Solutions Console, click Security > Global security > Web
and SIP security > Single sign-on (SSO).
- Select the Requires SSL check box.
- Click OK and Save directly to
the master configuration.
- There is a WebSphere Application
Server fix that is essential to ensuring consistent user authentication
between applications. APAR PM75942 describes the issue, and provides
a pointer to the patches for V8.0.0.8 and V8.5.5.2 resolving the problem.
Note: - Rational® Engineering
Lifecycle Manager v1.x must share an application server with the Lifecycle
Query Engine.
- Rational Engineering
Lifecycle Manager v4.x can share an application server with the Lifecycle
Query Engine or be deployed to a different application server. However
both applications must be registered to the same Jazz Team Server.
Procedure
- In the WebSphere Application
Server admin console, select
- Select the server on which you will deploy Lifecycle Query
Engine
- On the Configuration page, select Java
and Process Management.
- Select .
- Locate the Generic JVM arguments text
field, and add this environment variable to the JVM startup process:
-Dlqe.config.location=file://drive:\lqe_installation_folder\server\conf\lqe
For
example:
-Dlqe.config.location=file://C:\Program Files\IBM\JazzTeamServer\server\conf\lqe
Click Save to
save your updates.
- Increase the default thread pool to allow for multiple
users. Click .
- Under Additional Properties, click Thread pools.
- Click WebContainer, and increase
the default maximum size from 50 to 200 threads.
- Click Save directly to the master configuration.
- Install the Lifecycle Query Engine WAR file. Select .
- Select Install.
- Choose the Local file system radio
button, and provide the location for the lqe.war file
where it was installed. For example,
C:\Program Files\IBM\JazzTeamServer\server\tomcat\webapps\lqe.war
- Select Next, choose the Fast
Path radio button and select + Choose to generate
default bindings and mappings Click Next.
- Keep all the defaults on the Installation Options page,
and click Next.
- On the Map Modules to Servers page,
specify the target scope on the server for the Lifecycle Query Engine
module. Click Next.
- Add /lqe as the context root. Click Next.
- Review your selections and click Finish. You should receive a message stating Application lqe_war
installed successfully
- Next you will modify the configuration options for the
WAR file you just installed. Select
- Select the lqe.war application.
- Select Manage Modules
- Select lqe
- Locate the Class loader order field
and select Classes loaded with local class loader first
(parent last) Click OK and
save your changes.
- Select the lqe.war application
- Select Class loading and update detection
- Find Class loader order, and select Classes
loaded with local class loader first (parent last) Select Apply,
and Save directly to the master configuration.
- In order for the variable added in step 5 to be applied to WebSphere Application Server, the server
must be restarted. Restart WebSphere Application
Server.
- If the LQE application has not be automatically started,
select the check box for lqe.war and select Start.