Add new applications to an existing

Set up the

Note: In a distrubuted environment that the is not already setup, you must perform these steps on each application server.

Before you begin

Ensure you have completed the following tasks:

• is already installed and running.
• You have the WebSphere administrative user name and password.
• Verify or update the level. For a list of supported versions and fix packs, see the Detailed System Requirements page.
• 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.

Procedure

1. Open a browser and login to WebSphere Integrated Solutions Console at https://hostname.example.com:9043/ibm/console/logon.jsp.
2. The Java 2 Security option must be turned off. If this option is turned on in , the web application will not start.
   1. Click Security > Global security.
   2. Under Java 2 security, clear the check box for Use Java 2 security to restrict application access to local resources.
   3. Ensure that the Enable administrative security and Enable application security check boxes are selected.
3. To ensure that the LTPA cookies are secure, enable the Requires SSL setting:
   1. Click Security > Global security > Web and SIP security > Single sign-on(SSO).
   2. Click the Requires SSL check box.
   3. Also ensure that Set security cookies to HTTPOnly to help prevent cross-site scripting attacks is selected.
   4. Click OK and Save directly to the master configuration.
4. 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:
   1. In WebSphere Integrated Solutions Console, click Server > Server Types > WebSphere application servers > server_name > Session management > Enable cookies.
   2. Select the Restrict cookies to HTTPS sessions check box.
5. Also ensure that the Use available authentication data when an unprotected URI is accessed application server security setting is selected.
   1. Click Security > Global security > Web and SIP security > General settings.
   2. Click the Use available authentication data when an unprotected URI is accessed check box.
   3. Click OK and Save directly to the master configuration.
6. Add the following session management custom property to avoid SESN0008E error message when a user logs out without terminating the session:
   1. Click Servers > Server Types > WebSphere application servers.
   2. Click server1 and then in the Container Settings section, click Session management.
   3. In the Additional Properties section, click Custom properties.
   4. Click New and enter the following information:
      • Name: InvalidateOnUnauthorizedSessionRequestException
      • Value: true
   5. Click Apply and save directly to the master configuration.
7. To improve performance of the operating procedures, change the WebContainer thread pool size settings:
   1. Click Servers > Server Types > WebSphere application servers.
   2. Click server1 and then in the Additional Properties section, click Thread pools.
   3. In the Thread pools page, click WebContainer.
   4. Enter 200 in the Minimum Size and Maximum Size fields.
   5. Click OK and save directly to the master configuration.
8. In 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. 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.
9. requires several specific settings on the Java Virtual Machine in which it runs. To set these properties, click Servers > Server Types > WebSphere application servers > server1.
10. Under Server Infrastructure, click Java and Process Management > Process definition.
11. Under Additional Properties, click Java Virtual Machine.
12. In the Generic JVM arguments field, type the following lines:

    -Xmx4g -Xms4g -Xmn1g
    -Xgcpolicy:gencon -Xnocompressedrefs

    -Xmx4g -Xms4g -Xmn1g
    -XX:MaxPermSize=768M -XX:ReservedCodeCacheSize=512M -XX:CodeCacheMinimumFreeSpace=2M

    -Xmx4g -Xms4g -Xmn1g
    -Xgcpolicy:gencon -Xcompressedrefs
    -Xgc:preferredHeapBase=0x100000000

    Tip: If you need more heap size, then you can use the following setting, replacing {N} with the amount of memory to be used and {N/4} with 1/4 of the total memory. For example, if -Xmx is set to 8g, -Xmn should be set to 2g.
    
    -Xmx{N} -Xms{N} -Xmn{N/4}
    
    For only: The -Xmn value should be 33% of the -Xms value. For example, if the -Xmx size is 4gb, the -Xmn should be 1365m. The following Deployment wiki document contains useful information about sizing and tuning: Sizing and tuning guide for . For only: If application pages become unresponsive as a result of memory issues, see this technote for troubleshooting.

13. Click Apply, and then click Save directly to the master configuration.
14. One of the custom properties you must add is JAZZ_HOME, a system property that specifies where to find certain configuration files. This property uses a URL rather than a simple path, so specify the value as a file-style URL: file:///file_path. Under Java Virtual Machine > Additional Properties, click Custom properties. You must use three forward slashes (///) after file:.

    In a distributed environment, when you are using a separate application server for each web application, you must add these custom properties for each instance of the .

15. Click New, enter JAZZ_HOME in the Name field, and enter file:///Jazz_Install_Dir/server/conf in the Value field. Substitute Jazz_Install_Dir with the location of installation directory. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer/server/conf if the server is installed in /opt/IBM, enter file:////opt/IBM/JazzTeamServer/server/conf.

    To avoid problems, do not use spaces in file paths. You can use double quotation marks to enclose the path.

16. Click OK.
17. Repeat the above steps and add these custom properties:
    • Name: lqe.config.location Value: file:///Jazz_Install_Dir/server/conf/lqe
    • Name: ldx.config.location Value: file:///Jazz_Install_Dir/server/conf/ldx
    • Name: java.awt.headless Value: true
    • Name: org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin Value: true
    • Name: ORACLE_JDBC_DRIVER_FILE Value: Absolute_path_to_the_JDBC_driver/ojdbc8.jar

      Note: The path to the JDBC driver must be an absolute path. Do not use URL path (file:///). For more information about Oracle Java Database Connectivity (JDBC) connections, see Set up the database step.

    • Name: SQLSERVER_JDBC_DRIVER_FILE Value: Absolute_path_to_the_JDBC_driver/sqljdbc42.jar

      Note: The path to the JDBC driver must be an absolute path. Do not use URL path (file:///). For more information about SQL Server JDBC connections, see Set up the database step.

    • Name: log4j.configuration Value: file:///Jazz_Install_Dir/server/conf/startup_log4j.properties

      The settings that the startup_log4j.properties file contains are used at the early stages in the startup process to pass messages to the SystemOut.log file. After the early stages, each Jazz application switches to using the application-specific settings from the Jazz_Install_Dir/server/conf/app_context/log4j.properties file.

18. Click Save directly to the master configuration.
19. In the WebSphere Integrated Solutions Console navigation pane, expand Environment and click Shared libraries.
20. In the Scope list, select Node=MachineNameNode01, Server=server1 and click New.
21. Enter the shared library name JRS Shared Library, add a description, and set the classpath to: JRS_install_dir/server/conf/rs/\server\conf\rs\WAS_SharedLibrary. For example: C:\Progra~1\IBM\JazzTeamServer\server\conf\rs\WAS_SharedLibrary/opt/IBM/JazzTeamServer/server/conf/rs/WAS_SharedLibrary
22. Under Class Loading, select the Use an isolated class loader for this shared library check box, click Apply, and then click Save.
23. For changes to take effect, restart the application server.