Preparing to Upgrade Team Studio

Before you install a new version of Team Studio, follow these steps to prepare your server.

Perform this task on the server where you plan to upgrade Team Studio.

Prerequisites

  • Be sure your server meets the system requirements.
  • Back up any previous installations. See Backing up Team Studio for more information.

Procedure

  1. Open the file chorus.properties, and ensure that the property workflow.url is set to http://localhost:9090, rather than an external IP address.
  2. Download the Team Studio installation package and validate it.

    The package is in the form chorus-6.0.0.0.<build number>-<sha>.sh, where <sha> is a hash that maps to a specific code commit.

  3. Put the installation package in a folder where the user chorus has write privileges.
    Note: For installation on a DCA standby master or DCA (UAP Edition) DIA module, this folder should be in the /home/chorus directory.
  4. Run MD5 on the binary.
    This tool generates a string that you can compare to the value provided with the installation package to verify that you downloaded the correct file. For example, run the following.
    # md5sum ~/chorus-6.0.0.0.1549-9d20ac862.sh
    MD5 chorus-6.0.0.0.1549-9d20ac862.sh=
    935d82688591bf0e6f0ba05dc5837fd3

    You can compare 935d82688591bf0e6f0ba05dc5837fd3 with the value provided with the installation package. If the values match, then you downloaded the correct file.

  5. Log in as chorus if you are not already logged in as this user.

    Because only the user who has privileges to start and stop the system can upgrade the software, you must log in as chorus.

  6. Source chorus_path.sh according to the appropriate value for the environment variable $CHORUS_HOME.
    $ echo $CHORUS_HOME
    /usr/local/chorus
    $ source $CHORUS_HOME/chorus_path.sh
  7. Make sure Team Studio is stopped.
    $ chorus_control.sh stop
  8. Write down the Team Studio memory startup settings and Kerberos realm settings.

    You must transfer these settings into the file deploy.properties. See Team Studio Deploy Properties for details.

What to do next

Related tasks