Deploying applications for the IBM Engineering Lifecycle Management on WebSphere Application Server
Use these instructions to deploy the IBM Engineering Lifecycle Management applications on an IBM WebSphere Application Server.
Before you begin
- By default, the web application files (.war) are copied into the JazzInstallDir/server/webapps directory unless during the installation you specified a different location.
- Uninstall WebSphere Application Server default applications (DefaultApplication, ivtApp, and query) if they are installed with the profile. Jazz® Team Server and ELM applications do not use these applications and for security and performance reasons they can be removed.
- If you are using a federated file-based user registry, you must create the Jazz repository groups in WebSphere Application Server before you install any ELM applications. For more information, see Managing users by using a federated file-based registry.
About this task
Note: On UNIX, if WebSphere Application
Server is
installed in a non-root environment, the user who deploys the ELM
applications must have read and write access to the installation directory and all
subdirectories.
In the following command-line examples, the WASInstallDir
variable represents the location where WebSphere Application
Server is
installed on your server.
- The default value for the WebSphere Application
Server
installation directory is as
follows:
C:\Program Files\IBM\WebSphere\AppServer
You can restart the server with these commands on Windows:cd WASInstallDir\bin stopServer.bat server1 [for a secure server, include: -username WAS_USER -password USER_PASSWORD] startServer.bat server1
- The default value for the WebSphere Application
Server
installation directory is as follows:
/opt/IBM/WebSphere/AppServer
You can restart the server with these commands on UNIX:cd WASInstallDir/bin ./stopServer server1 [for a secure server, include: -username WAS_USER -password USER_PASSWORD] ./startServer server1
Procedure
Configure the Lifecycle Query Engine (LQE) application
Procedure
- In WebSphere Integrated Solutions Console click .
- Click lqe_war to open it and then click Manage Modules.
- Click lqe, locate the Class loader order field and select Classes loaded with local class loader first (parent last).
- Click OK and save your changes.
- Go back to the lqe_war application and click Class loading and update detection.
- On the Class loader page, select Classes loaded with local class loader first (parent last).
- Click Apply and Save directly to the master configuration.
Configure the Link Index Provider (LDX) application
Procedure
- In WebSphere Integrated Solutions Console click .
- Click ldx_war to open it and then click Manage Modules.
- Click ldx, locate the Class loader order field and select Classes loaded with local class loader first (parent last).
- Click OK and save your changes.
- Go back to the ldx_war application and click Class loading and update detection.
- On the Class loader page, select Classes loaded with local class loader first (parent last).
- Click Apply and Save directly to the master configuration.
Configure the Report Builder (RS) application
Procedure
- In WebSphere Integrated Solutions Console click .
- On the Enterprise Applications page, in the list of resources, click rs_war.
- On the Configuration page, in the References section, click Shared library references.
- Select the rs_war check box and click Reference shared libraries.
- In the Available list, select JRS Shared Library and click the right arrow. For information about setting up the JRS Shared Library, see Setting up WebSphere Application Server.
- Click OK. Click OK again and then click Save.
- In the list of resources, click rs_war.
- On the Configuration page, under Detail Properties, click Class loading and update detection.
- In the Class loader order group, ensure that Classes loaded with local class loader first (parent last) is selected. Click Apply and then click Save.
Start the server
Procedure
- In WebSphere Integrated Solutions Console click .
- Select the check box next to each installed application,
and then click Start. A green arrow should appear that indicates the application is successfully started.