Setting up WebSphere Application Server
Before you can deploy ELM applications war files, you must set up your WebSphere Application Server.
Before you begin
-
Important: Starting in version 6.0.6.1, the required Java version is 8.
- On UNIX systems, ensure that the Open File Limit value is properly set. For more information, see Planning to install on UNIX and Linux systems.
- The database is created. If you use the default Derby database
for evaluation purposes, ensure the location to the database in the teamserver.properties file
is an absolute path.
- Go to JazzInstallDir/server/conf/app where JazzInstallDir is where you installed Jazz® Team Server and app is a directory for jts, ccm, rm, qm, dcc, gc, lqe, or relm.
- For all applications except for LQE, open teamserver.properties for editing.
- For the LQE application, go to the lqe/template directory. Copy the dbconnection.properties file to the /lqe directory and open the file for editing.
- Locate the Derby database location com.ibm.team.repository.db.jdbc.location=conf/jts/derby/repositoryDB, and change the location with an absolute path. For example, com.ibm.team.repository.db.jdbc.location=C:/Progra~1/IBM/JazzTeamServer/server/conf/jts/derby/repositoryDB.
- 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.
- In WebSphere Integrated Solutions Console, 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.
- To ensure strong security practices, examine and adjust the following settings: Note: If all applications that will be deployed in the same WebSphere Application Server have Jazz Security Architecture SSO enabled, the following steps are unnecessary.
- 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:
- In WebSphere Integrated Solutions Console, 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 .
- Click the Requires SSL check box.
- Also ensure that Set security cookies to HTTPOnly to help prevent cross-site scripting attacks is selected.
- Click OK and Save directly to the master configuration.
- Set the Restrict cookies to HTTPS sessions to ensure that the session
cookies include the secure field. Enabling this feature restricts the exchange of cookies to HTTPS sessions:
- In WebSphere Integrated Solutions Console, click .
- Select the Restrict cookies to HTTPS sessions check box.
- Add the following session management custom property to avoid SESN0008E error message when a
user logs out without terminating the session:
- In WebSphere Integrated Solutions Console, click .
- Click server1 and then in the Container Settings section, click Session management.
- In the Additional Properties section, click Custom properties.
- Click New and enter the following information:
- Name: InvalidateOnUnauthorizedSessionRequestException
- Value: true
- Click Apply and save directly to the master configuration.
- 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:
- To improve performance of the operating procedures, change the WebContainer thread
pool size settings:
- In WebSphere Integrated Solutions Console, click .
- Click server1 and then in the Additional Properties section, click Thread pools.
- In the Thread pools page, click WebContainers.
- Enter 200 in the Minimum Size and Maximum Size fields.
- Click OK and save directly to the master configuration.
- In WebSphere Application Server version 9.0, the Contexts and Dependency Injection (CDI) 1.2 is enabled by default. If CDI is enabled, it might increase unnecessary performance overhead if the application is not using it. ELM applications do not use CDI and to gain performance, you can disable CDI by setting some Java custom properties and manifest attributes. For detailed instructions, see this IBM Support troubleshooting document.
The Jazz web interface requires that authentication be configured in order to perform authorization and personalize the application.
About this task
When increasing the Java heap size, ensure that enough unused physical memory is available on the machine to cover the increase. If sufficient physical memory is not available, either install additional memory or take into account the effect on overall performance that occurs.
It is also important to have more physical memory than is required by all of the processes on the machine combined to prevent paging or swapping. Paging reduces the performance of the system and affects the performance of the Java memory management system.