RegisterLog In to Jazz.net dW
Download 4.0.6 Release
February 28, 2014

Rational Software Architect Design Manager &
Rational Rhapsody Design Manager

Analysis Design change management Lifecycle traceability

Design Management 3.0.0.1

Product Release Trial | October 17, 2011
This is not the most recent version. We recommend Design Management 4.0.6 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Upgrading Design Management Server

If you have version 3.0 of Design Management Server installed already, you can upgrade that version to the latest version. Plan on 1 to 2 hours to complete the upgrade process; depending on the number of project areas stored on your server, the upgrade process might take longer.

If you are upgrading Design Management Server while using IBM® WebSphere® Application Server as your application server, see the instructions at the bottom of this page. You can also follow these instructions, substituting the WAR files mentioned in step 3 of the topic with the WAR files that are specific to Design Management Server: jts_war, dm_war, and rdmhelp_war.

For detailed upgrade instructions, see Upgrading Design Management Server in the product information center. For high-level instructions that provide an overview of the upgrade process, read the following steps:

  1. On the All Downloads tab, download the following .zip files based on the Rational modeling product that you use:
  • IBM Rational Software Architect Design Manager Upgrade repositories
  • IBM Rational Rhapsody Design Manager Upgrade repositories
  1. Extract the upgrade installation media; a DM_Server directory is created that contains a diskTag.inf file.
  2. In IBM Installation Manager, using File > Preferences, add diskTag.inf as a repository.
  3. Install the Design Management Server 3.0.0.1 update.
  4. After the upgrade is complete, exit the wizard and close IBM Installation Manager.
  5. For the exact steps that explain how to install the server upgrade, see Installing the Design Management Server upgrade package in the product information center.

Important: You must also complete manual upgrade steps; therefore, do not start the Jazz Team Server until later in the upgrade process. Also, do not run the setup process for Design Management Server 3.0.0.1 at this time.

  1. After you install the upgrade, you must copy several specific directories and files from the root directory in Design Management 3.0 and overwrite those files in the version 3.0.0.1 root directory.
  2. After you update the directories and files, you must run several batch files to update the database. For detailed instructions for steps 6 and 7, see Overwriting key directories to upgrade Design Management Server.
  3. After you upgrade Design Management Server and overwrite the appropriate files, you must configure the upgraded server. This process involves provisioning the server, requesting to reset the server, and shutting down and restarting the Design Management Server as well as your computer. After the server restarts, you must also import several process templates that are specific to version 3.0.0.1. Detailed steps are located in Configuring the upgraded Design Management Server.
  4. After you upgrade the Design Management Server, you must update each Design Management Server project area with correct resource permissions. For detailed instructions, see Specifying Design Management Server resource link permissions.

Upgrading Design Management Server on IBM WebSphere Application Server

  1. Install the Design Management Server upgrade in a different directory than Design Management Server 3.0, but do not run, set up, or configure the server.
  2. Back up the WebSphere Application Server profile:
  • Open a command prompt and change the directory to WAS_Install/bin (Example: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin).
  • Run the following command: ./backupConfig <path to a new .zip file to create a backup of profile> (Example: ./backupConfig /root/was_backups/dm_30_profile.zip)

Tip: You can restore the backed up profile by running this command: ./restoreConfig (Example: /restoreConfig /root/was_ backups/dm_30_profile.zip)

  1. Uninstall the Design Management 3.0 applications from WebSphere Application Server.
  • Write down the security role mapping of the following jts_war applications; then, stop and uninstall jts_war, dm_war, and rdmhelp_war. Note the security role mapping because you need it later in this process.
  • Remember to save your changes.
  1. Modify the Java Virtual Machine (JVM) settings in WebSphere Application Server to point to the new Design Management installation directory.
  • Go to the JAZZ_HOME link and update the value to file:///3.0.0.1_installation_directory/server/conf (for example, file:///opt/IBM/DesignManagement_3.0.0.1/server/conf)
  • Go to the jfs.home.configuration link and update the value to file:///3.0.0.1_installation_directory/server (for example, file:///opt/IBM/DesignManagement_3.0.0.1/server)
  • When prompted, remember to save the JVM settings to the master configuration.
  1. Stop WebSphere Application Server.
  2. Delete the following Design Management-related artifacts from the wstemp and temp directories in the profile: dm_war, jts_war, and rdmhelp_war.
  3. Delete the Design Management-related log files from the logs directory in the profile.
  4. If using Derby, move the Derby database from 3.0 to 3.0.0.1.
  5. Copy the JFS/text indices from 3.0 to 3.0.0.1:
    cp -R 3.0_installation_directory/server/conf/jts/indices 
          3.0.0.1_installation_directory/server/conf/jts
  6. Copy your application configuration files from 3.0 to 3.0.0.1:
     cp 3.0_installation_directory/server/conf/jts/teamserver.properties
        3.0_installation_directory/3.0.0.1/server/conf/jts
        3.0_installation_directory/server/conf/dm/dm.properties 
        3.0_installation_directory/server/conf/dm
    
  7. Copy the SQL or Oracle JDBC drivers to 3.0.0.1_installation_directory/server/sqlserver folder or 3.0.0.1_installation_directory/server/oracle folder, as appropriate.
  8. Run the repotools -addTables command to make sure the database has the correct tables:
    cd 3.0.0.1_installation_directory/server
    ./repotools-jts.sh -addTables noPrompt
    
  9. If you have a data warehouse configured, run the repotools -createWarehouse command to update the data warehouse schema to 3.0.0.1.
    cd <3.0.0.1 install dir>/server
    ./reportools-jts.sh -createWarehouse
    
  10. Restart the WebSphere Application Server; then, install and start the 3.0.0.1 WAR files: dm_war, rdmhelp_war, and jts_war. Remember, map the security roles, as appropriate.
  11. After you upgrade Design Management Server and overwrite the appropriate files, you must configure the upgraded server. This process involves provisioning the server, requesting to reset the server, and shutting down and restarting the Design Management Server as well as your computer. After the server restarts, you must also import several process templates that are specific to version 3.0.0.1. Detailed steps are located in Configuring the upgraded Design Management Server.
  12. After you upgrade the Design Management Server, you must update each Design Management Server project area with correct resource permissions. For detailed instructions, see Specifying Design Management Server resource link permissions.