Upgrading Team Server and Repository

From TeamServer ER/Studio
Jump to: navigation, search

This Upgrade Guide provides important information regarding the process of upgrading from previous versions using the new Team Server installer which includes Repository.

Notepad blue icon 2.pngNote: Please note that with this new installer, Repository and Team Server will be installed on the same server machine. If in your current installation they are on separate machines, be sure to uninstall both before upgrading. Run the upgrade on the machine that was previously running Team Server.

Preparing the Upgrade

Repository User Preparations

  1. Ensure you have backed up all your .dm1 files.
  2. Check in all your diagrams and objects. If you try to check in a file from the previous version with the same name as a current file, the current file will become corrupted.
  3. Rename all local copies of Repository diagrams in the active file directory as follows:
    1. Choose Repository > Options.
    2. Make note of the Active File Directory.
    3. Switch to the Windows Explorer and rename all the diagrams in the Active File Directory in order to protect them of being overwritten. Example: Backup_DiagramName.dm1.

Repository Administrator Preparations

  1. Ensure no one is logged into the Repository.
  2. Backup the current Repository database.

Notepad blue icon 2.pngNote: If you are upgrading from a Repository version prior to 4.0, you can delete the C:\Program Files\Embarcadero\Repository\Data directory. This directory is not used with Repository versions 4.0 and later.

Upgrading from Team Server 4.0.x, CONNECT 3.0.x or ER/Studio Portal 2.0.x

Make a copy of the license files, for example: license.txt, ao_12345678.txt or .slip until the upgrade has completed. Then copy to the license folder in the installation directory of the new Team Server installation folder.

Depending on your installation location, you can find the license file in the program directory. For example: C:\Embarcadero\ERStudio Portal 2.0\license

  • If you have already used the uninstaller, you may also have a license backup in the following location:
    • 32-bit Windows: C:\Program Files (x86)\Common Files\ersEnterprisePortalBackup\license
    • 64-bit Windows: C:\Program Files\Common Files\ersEnterprisePortalBackup\license

After copying over the license.txt file to the license folder within the installation folder of Team Server, log into Team Server as Admin, select My Settings > Admin > Licenses and click Refresh for Team Server to recognize your licenses.

Notepad blue icon 2.pngNote: We always recommend backing up your data before starting the process. You may have to back up your database and, for Team Server and Connect, export your Glossaries and Terms.

Uninstall the previous version.

Upgrades scenarios

First of all, prepare the upgrade for any scenario.

Upgrades from Team Server 2016 (16.X) which includes Repository 7.0.1

  1. Uninstall Team Server 2016 (16.X).
  2. Install Team Server 2016+ (16.5).

Upgrades from Repository 7.0.X (Standalone)

  1. Uninstall Repository 7.0.X.
  2. Install Team Server 2016+ (16.5).
  3. On the repository setup page, if you were also using Team Server 4.0 or previous, select Specify location for Team Server database..., this will expand the information fields to the ones explained here.

Upgrades from Repository prior to 6.5/6.6/6.7 (Standalone) and Team Server 4.0 or previous

  1. The Repository upgrade must be done incrementally from one major version to the next until the target version is reached. You cannot skip major versions during the Repository upgrade as the installer for each major version only contains the database changes between the new version and the previous one.
    • For example: When upgrading from earlier versions, such as from 5.5, you must first upgrade the Repository to version 6.0 using the repository 6.0 installer, uninstall version 6.0, then upgrade to 6.7 using the Repository 6.7 installer then, unistall and install 7.0.1. Each time you install a major version it will update the database.
  2. Install Team Server 2016+ (16.5).
  3. On the repository setup page, if you were also using Team Server 4.0 or previous, select Specify location for Team Server database..., this will expand the information fields to the ones explained here.

Upgrade Configuration

  • If you are upgrading from Team Server 2016 (16.x) you already have one unique combined database, directly follow the steps on the repository setup.
  • If you have installed Team Server XE7 or any previous version, including CONNECT or Portal you need to specify the information to connect to its database. The new installer will copy the Team Server database tables into the Repository database, after which both Repository and Team Server Web will share the same database. Please, read first Database Server Requirements.
  1. Check the repository setup and introduce repository database information.
  2. Select Specify location for Team Server database..., this will expand the information fields to include Team Server database information.
  3. Fill the fields with the Team Server database information with the same structure than you have introduced previously for repository database.
    Q5TSSelectDBMSSQL.png
  4. If your Portal installation was using a separate Solution database, select Specify the location of Solution database....
  5. Specify Portal Solution database details so the tables can also be copied to the Repository database.

Q5TSDetallePortal.png

Note for Oracle: Once the upgrade is done, the alias in the tnsnames file must be updated to point the new database server in case you had Team Server and Repository old databases in different machines.

Note for DB2: Once the upgrade is done, create a System DSN with the ODBC Data Source Administrator to point the new database server in case you had Team Server and Repository old databases in different machines.

Finishing the Upgrade

  1. Perfom the migration process.
  2. Update the search index.
  3. Update reports.
  4. Click Update Solution Repository in My Settings > Admin > Repository Management.
    Notepad blue icon 2.pngNote: Wait until a message of successful update appears.
  5. Once the Team Server upgrade is complete, you should upgrade your diagrams with the latest version of ER/Studio Data Architect.

Important Notes

  • Always back up databases before upgrading.
  • Upgrading diagrams can be time consuming and memory intensive. The number and size of the diagrams managed in the upgrade dictates how long the upgrade process takes.
  • Regardless of the process that you must follow to back up your licenses, which depends on the previous version that you are upgrading from and other factors, after you restore your licenses in your new installation, you must log in as a super user and use the Manage Users page to assign different types of available licenses to your users.

See Also

Personal tools
Product Videos