Setting up WebSphere Application Server for the upgrade

If you are using WebSphere® Application Server for your server, you must manually uninstall the web applications from the server and install the new versions.

Before you begin

About this task

Fast path: If you are using Apache Tomcat, no manual deployment steps are necessary for the application server. Proceed to Configuring the upgraded Design Management Server.

When you installed the Design Management Server, you deployed the web applications using the WebSphere Application Server administrative console. This process is described in Deploying the Design Management Server on WebSphere Application Server. To upgrade the Design Management Server, you must uninstall these applications and install the upgraded versions.

Procedure

  1. Optional: Back up the server profile by running the backupConfig command, which is in the folder serverInstallDir/profiles/profileName/bin. For example, you might run the following command on Linux:
    ./backupConfig /root/was_backups/dm_30_profile.zip
    The following code is the equivalent command on Windows:
    backupConfig.bat C:\was_backups\dm_30_profile.zip
  2. Back up your database.
  3. Log in to the administrative console.
  4. Uninstall the applications jts.war, dm.war, and rdmhelp.war by clicking Applications > Application Types > WebSphere enterprise applications, selecting the applications, and clicking Uninstall.
  5. Save the changes to the master configuration.
  6. In the custom properties for the Java Virtual Machine (Servers > Server Types > WebSphere application servers > serverName > Java and Process Management > Process definition > Java Virtual Machine > Custom properties), update the JAZZ_HOME property so that it points to the conf folder for the new version of the Design Management Server.
  7. Update the log4j.configuration property so that it points to the location of the startup_log4j.properties file.
  8. If you are using a database other than Derby or DB2, verify that the property for the database (such as SQLSERVER_JDBC_DRIVER_FILE or ORACLE_JDBC_DRIVER_FILE) points to the correct JDBC driver file.
  9. Save the changes to the master configuration.
  10. Stop WebSphere Application Server.
  11. Optional: Back up the log files named dm.log and jts.log, which are at serverInstallDir/profiles/profileName/logs/. You can then delete the existing log files so the new version of Design Management Server will start new log files. If you do not back up and remove the files, the new version of the server appends log messages to the existing log files.
  12. Delete the following folders of temporary files:
    • serverInstallDir/profiles/profileName/temp/nodeName/serverName/dm_war/
    • serverInstallDir/profiles/profileName/temp/nodeName/serverName/jts_war/
    • serverInstallDir/profiles/profileName/temp/nodeName/serverName/rdmhelp_war/
    • serverInstallDir/profiles/profileName/temp/wscache/dm_war/
    • serverInstallDir/profiles/profileName/temp/wscache/jts_war/
    • serverInstallDir/profiles/profileName/temp/wscache/rdmhelp_war/
    Use the location of the server, the profile name, the node name, and the server name for serverInstallDir, profileName, nodeName, and serverName.
  13. Start the server.
  14. From the administrative console, install the new versions of the files jts.war, dm.war, and rdmhelp.war as you did when you installed the original version. Use the context roots /dm, /jts, and /rdmhelp as you did in the original installation. Also, make sure to save the master configuration after installing each file. For more information, see Deploying the Design Management Server on WebSphere Application Server.
  15. Map the security roles for the Jazz™ Team Server application to users and groups in your security realm. Setting up security is beyond the scope of this task, but in most cases in which your global security realm uses an LDAP registry, you map groups in the LDAP registry to the following security roles for the application:
    • JazzAdmins
    • JazzDWAdmins
    • JazzProjectAdmins
    • JazzGuests
    • JazzUsers
    1. Click Applications > Application Types > WebSphere Enterprise Applications > jts_war.
    2. Under Detail Properties, click Security role to user/group mapping. This page shows the user groups for the Design Management Server that you must map to users or groups in your security realm.
    3. Select a role and then click Map Groups to map that role to a group in your security realm.
      Note: Do not enable the All authenticated? option.
  16. Verify that the applications installed successfully and then save the changes to the master configuration for WebSphere Application Server.
  17. In the WebSphere Application Server administrative console, click Applications > Application Types > WebSphere Enterprise Applications to confirm all applications are running.

What to do next

Configure the server as described in Configuring the upgraded Design Management Server.

Feedback