Deploying and Starting WebSphere

The following explains how to configure the WebSphere™ Application Server using it’s administration console and deploying the Connector web application.

Configure WebSphere Application Server

  1. Start a web browser and login to WebSphere Integrated Solutions Console at (this URL is an example)
  2. 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 Security > Global Security.
  3. To ensure that the Lightweight Third-Party Authentication (LTPA) cookies are secure, enable the Requires Secure Sockets Layer (SSL) setting:
  4. Also ensure that the "Use available authentication data when an unprotected URI is accessed" application server security setting is selected.
  5. Add the following session management custom property to avoid SESN0008E error message when a user logs out without terminating the session:
  6. To improve performance of the operating procedures, change the WebContainer thread pool size settings:
  7. Click Apply, and then click Save directly to the master configuration.
  8. 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:
  9. Click New, enter JAZZ_HOME in the Name field, and enter file:///JazzInstallDir/server/conf in the Value field.
  10. SubstituteJazzInstallDir with the location of Jazz Team Server installation directory. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer/server/conf.
  11. To avoid problems, do not use spaces in file paths. You can use double quotation marks to enclose the path.
  12. Click OK.
  13. Repeat Step 9 and add these custom properties:
  14. Click Save directly to the master configuration.
  15. For changes to take effect, restart the application server.

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

Deploy Web Applications (.WAR files)

  1. Make sure the WebSphere Application Server is installed and started. Obtain the appropriate released version of the oslc-windchill.war file
  2. Go to Application> Application Types> WebSphere enterprise applications to uninstall WebSphere Application Server default applications (DefaultApplication, ivtApp , and query ) if they are installed with the profile. Jazz Team Server and CLM applications do not use these applications and for security and performance reasons they can be removed.
  3. Start a web browser and login to WebSphere Integrated Solutions Console at (this URL is an example).
  4. Within the Console Menu page, Click Applications > New Application > New Enterprise Application.
  5. On the Path to the new application page, select Remote file system and browse to the file location of the appropriate oslc-windchill.war file.
  6. Click Next.
  7. Select Fast Path and then click Next.
  8. Click Next to accept all default options until reaching the Map context roots for web modules page.
  9. In the Map context roots for web modules, set Context Root for OSLC Connect for Windchill to /oslc-windchill
  10. Click Next.
  11. Click Finish.
  12. Verify that your application was installed correctly
  13. Click Save directly to the master configuration
  14. Navigate to Applications > Application Types > Websphere Enterprise Applications
  15. Verify that the application status is started otherwise select the check box next to the OSLC Connect for Windchill war and click Start.

Edit the context parameters for WebSphere.

  1. To configure the servlet’s Context properties again use the WebSphere Administration Console.
  2. Browse to Servers> Server Types > WebSphere application servers> servers > server1 > Server Infrastructure – Java and Process Management – Process Definition > Additional Properties – Java Virtual Machine > Custom Properties
  3. Click New and go to the section Configuring Context Parameters to add the context properties in the Name and Value fields, then click OK.
  4. Repeat this step to add each custom property.