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 the 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 Use Java 2 security to
restrict application access to local resources check box.
- 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 .
- Select 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: If you are using Lifecycle
Query Engine with Rational® Engineering Lifecycle
Manager,
both applications can share application server or be deployed to different
application servers. However, both applications must be registered
to the same Jazz Team Server.
Procedure
- In the WebSphere Application Server administrative
console navigation, expand Servers and Server Types and click WebSphere
application servers.
- Select the server on which you want to deploy Lifecycle
Query Engine.
- On the Configuration page, under Server
Infrastructure, click Java and Process Management.
- Click .
- In the Generic JVM arguments field,
add the following environment variable to the JVM startup process:
-Dlqe.config.location=file://drive:\lqe_installation_folder\server\conf\lqe
For
example:
- Click Save.
- To increase the default thread pool to allow for multiple
users, in the WebSphere Application Server administrative
console navigation, expand Servers and Server Types and click WebSphere
application servers.
- 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.
- To install the Lifecycle
Query Engine WAR file,
in the WebSphere Application Server administrative
console navigation, expand Applications and Application Types and
click WebSphere enterprise application.
- Click Install.
- Choose the Local file system option,
and provide the location where the lqe.war file
was installed. For example,
C:\Program Files\IBM\JazzTeamServer\server\tomcat\webapps\lqe.war
- Click Next, choose the Fast
Path option, expand Choose to generate default bindings
and mappings, and select the Generate Default Bindings check
box.
- 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.
- In the Context Root field, add /lqe.
- Click Next.
- Review your selections and click Finish. You should receive a message stating Application lqe_war
installed successfully.
- Next, you modify the configuration options for the WAR
file you just installed. Select
- Select the lqe.war application.
- Click 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
- Click 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 Lifecycle
Query Engine application
has not been automatically started, select the check box for lqe.war and
select Start.