Configuring Jazz Team Server and the applications for the Engineering Lifecycle Management to use WebSphere Application Server on z/OS

Edit online

This topic describes how to set up the Jazz® Team Server and the IBM® Engineering Lifecycle Management (ELM) applications to work with the WebSphere Application Server on z/OS. Configuring the WebSphere Application Server on z/OS is similar to other platforms. The primary differences are the security model and the locations of files in the file system.

Before you begin

Before you perform this task, make sure you:
  • See the Hardware and software requirements before you configure.
  • Installed and are running the WebSphere Application Server.
  • Customized and submitted the BLZCP* jobs for the Jazz Team Server and any ELM applications you plan to deploy.
  • Created the DB2® databases and updated the teamserver.properties files with your database settings.
  • Selected and configured Local Operating System, if you are using RACF® security.
  • Established RACF security settings. For more information about RACF security, see Setting up user security on a z/OS system by using RACFSetting up user security on a z/OS system using RACF.
  • Turned off the Java™ 2 security option by following these steps:
    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 check boxes for Enable administrative security and Enable application security are selected.

    If this option is turned on in the WebSphere Application Server, the web application will not start.

  • Selected Use available authentication data when an unprotected URI is accessed. If you are using the Integrated Solutions Console for the server, use the following steps to verify this setting:
    1. Click Security > Global security > Web and SIP security > General settings.
    2. Select the check box for Use available authentication data when an unprotected URI is accessed.
  • Enabled Requires SSL to ensure that the LTPA cookies are secure. If you are using the Integrated Solutions Console for the server, use the following steps to verify this setting:
    1. Click Security > Global security > Web and SIP security > Single sign-on (SSO).
    2. Select the check box for Requires SSL.
    3. Click OK to save the settings.
  • Add the following session management custom property to avoid an SESN0008E error message when a user logs out without terminating the session. If you are using the Integrated Solutions Console for the server, use the following steps to verify this setting:
    1. Click Servers > Server Types > WebSphere application servers > server1.
    2. 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 to save the settings.
  • Verified or updated the WebSphere Application Server level based on the System Requirements from https://jazz.net/wiki/bin/view/Deployment/DeploymentInstallingUpgradingAndMigrating.

About this task

This topic does not list the steps for configuring the WebSphere Application Server authentication on SSL. For detailed information about the various authentication and encryption options you can use, go to the WebSphere Application Server for z/OS product documentation, select the version that you are running, and search for Securing applications and their environment.

Procedure

Perform the following steps to deploy the Jazz Team Server and ELM applications on the WebSphere Application Server. Each step is detailed in its own task.

  1. Define application server JVM custom properties.
  2. Deploy the web applications and restart the application server.
  3. If you are installing the Report Builder (rs), complete the following steps to define the Jazz Reporting Service (JRS) shared libraries. You will reference this shared library when configuring the Report Builder.
    1. In the WebSphere Integrated Solutions Console navigation pane, expand Environment and click Shared libraries.
    2. In the Scope list, select Node=yourNodeName, Server=yourServerName and click New.
    3. Enter the shared library name JRS Shared Library, and add a description. Set the classpath to: @workPath@/rs/WAS_SharedLibrary, where @workPath@ is the path used to configure the work directory for rs. For example, /u/jazz702/rs/WAS_SharedLibrary.
    4. Under Class Loading, select Use an isolated class loader for this shared library, click Apply, and then click Save.

Defining application server JVM custom properties

Edit online

About this task

Notes:
  • There might be minor differences in the WebSphere administrative console depending on your version of the WebSphere Application Server.
  • Substitute @confPath@ with your Jazz Team Server configuration directory as determined when you ran the BLZCPJTS and other BLZCP* sample jobs for the ELM applications.

Procedure

  1. Log in to the WebSphere Application Server administrative console.
  2. Select Servers > Application Servers.
  3. Select server1 or your server name.
  4. Expand Container Services.
  5. Select ORB Service.
  6. Select z/OS Additional Settings.
  7. Set Workload Profile to LONGWAIT. Monitor thread pool usage to determine if adjustments are needed.
  8. Click OK and save the changes.
  9. Select Servers > Application Servers.
  10. Select server1 or your server name.
  11. Select Java and Process Management > Process Definition > Servant.
  12. Select Java Virtual Machine.
  13. Set the value for the Initial Heap Size to 4096.
  14. Set the value for Maximum Heap Size to 4096.
    This is a suggested value. Set the value according to your environment. A typical medium-sized team can use a value of 4096, providing 4 GB of heap memory for the Jazz Team Server process using a 64-bit JVM.
  15. Set the value for Generic JVM arguments to -Xmn512m.
  16. Click Apply.
  17. Select Custom Properties.
  18. Add the following properties by clicking New. Click OK after you add each one.
    Name: java.awt.headless
    Value: true
    Name: org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin
    Value: true
    Name: JAZZ_HOME
    Value: file:///etc/jazz702 or whatever value you have used for @confPath@ during initial set up.
    Name: jazz.auditDir
    Value: u/jazz702/audit or the value you set for @workPath@ during initial set up, followed by /audit.
    Name: DB2Z_JDBC
    Value: /@db2PathPrefix@/db2a10_jdbc/classes or /@db2PathPrefix@/db2b10/jdbc/classes, or /@db2PathPrefix@/db2c10/jdbc/classes
    Note: Replace @db2PathPrefix@ with the path to the Db2 V11.1 or V12.1 JDBC license and JDBC jar files on your system. These files are named db2jcc_license_cisuz.jar and db2jcc.jar and are located by default at /usr/lpp/ plus the version-specific path.
    Name: log4j.configuration
    Value: file:///etc/jazz702/startup_log4j.properties
    Note: The settings contained in startup_log4j.properties are used at the early stages in the startup process to print messages to the WebSphere Application Server SystemOut.log file. After the early stages, each Jazz application will switch to using the application-specific settings from /etc/jazz702/<app context>. If you use a configuration path other than /etc/jazz702, adjust this path accordingly.
  19. Select Save directly to the master configuration.

Deploying the web applications and restarting the WebSphere Application Server

Edit online

Procedure

  1. From the WebSphere Application Server administrative console, select Applications > Install New Application (or Applications > New Application > New Enterprise Application).
  2. Under Path to new Application, select Remote file system.
  3. Under Full path, browse to @pathPrefix@/usr/lpp/jazz/v7.0.2/server/jts.war, where @pathPrefix@ is any prefix you specified when you installed the SMP/E.
  4. Set the context root to /jts.
  5. Click Next, then continue with the remaining Install New Application steps as prompted by that editor.
    Note: For Lifecycle Query Engine (LQE) and Link Index Provider (LDX) only: Expand Choose to generate default bindings and mappings, and then select Generate Default Bindings.
  6. Click Finish.
  7. Select Save directly to the master configuration.
  8. Repeat the previous steps for the clmhelp.war with context root/clmhelp.
  9. If you are installing the CCM application, repeat the previous steps for the ccm.war with context root /ccm.
  10. If you are installing the QM application, repeat the previous steps for the qm.war with context root /qm.
  11. If you are installing the RM application, repeat the previous steps for the rm.war with context root /rm.
  12. If you are installing the LQE application, repeat the previous steps for the lqe.war with context root /lqe.
    Continue with the procedure in Configure the Lifecycle Query Engine (LQE) application
  13. If you are installing the DCC application, repeat the previous steps for the dcc.war with context root /dcc.
  14. If you are installing the GC application, repeat the previous steps for the gc.war with context root /gc.
  15. If you are installing the LDX application, repeat the previous steps for the ldx.war with context root /ldx.
    Continue with the procedure in Configure the Link Index Provider (LDX) application
  16. If you are installing the RS application, repeat the previous steps for the rs.war with context root /rs.
    Continue with the procedure in Configure the Report Builder (RS) application
  17. If you are installing the IBM Engineering Lifecycle Optimization - Engineering Insights (ENI) application, repeat the previous steps for the relm.war with context root /relm.
  18. Restart the application server.
  19. Check the servant logs and system console for errors.

Configure the Lifecycle Query Engine (LQE) application

Edit online

Procedure

  1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
  2. Click lqe_war to open it and then click Manage Modules.
  3. Click lqe, locate the Class loader order field and select Classes loaded with local class loader first (parent last).
  4. Click OK and save your changes.
  5. In the lqe_war application, click Class loading and update detection.
  6. On the Class loader page, select Classes loaded with local class loader first (parent last).
  7. Click Apply and Save directly to the master configuration.

Configure the Link Index Provider (LDX) application

Edit online

Procedure

  1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
  2. Click ldx_war to open it and then click Manage Modules.
  3. Click ldx, locate the Class loader order field and select Classes loaded with local class loader first (parent last).
  4. Click OK and save your changes.
  5. In the ldx_war application, click Class loading and update detection.
  6. On the Class loader page, select Classes loaded with local class loader first (parent last).
  7. Click Apply and Save directly to the master configuration.

Configure the Report Builder (RS) application

Edit online

Procedure

  1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
  2. On the Enterprise Applications page, in the list of resources, click rs_war.
  3. On the Configuration page, in the References section, click Shared library references.
  4. Select the rs_war check box and click Reference shared libraries.
  5. 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 .
  6. Click OK.
  7. Click OK again and then click Save.
  8. In the list of resources, click rs_war.
  9. On the Configuration page, under Detail Properties, click Class loading and update detection.
  10. In the Class loader order group, ensure that Classes loaded with local class loader first (parent last) is selected.
  11. Click Apply and then click Save.

What to do next

After you start the server, review this topic: Running the setup by using Custom setup in the setup wizard.