As your ET instance grows it may be necessary to upgrade your server. This article takes you through the steps required when moving to a new server.

About this Article

This article does not cover the steps to provisioning a server. This article assumes that your server is ready to install ET. See the System Requirements article for information on the supported operating systems, required applications and the recommended specifications. This article assumes that these requirements have been met.

Before You Begin

  • Back up your ET database and your ET installation directory including all child folders. These will include the web.config file, logging.config file and attachment directory among other files. If you are also exporting your baselines, then we recommend that you also back up this folder.
     

  • The Server Key will change. The server key depends on the following details;

    1. Machine Name
    2. Processor Count
    3. Operating System Name
    4. Operating System Version (Major and Minor)

More details on Server Keys can be found in this article Server Key Generation.

  • If the URL for your ET instance is also changing you will need to change the site.root.url setting in the web.config file. If you are synchronizing with JIRA and the URL for your ET instance is changing, the URL in JIRA to the ET requirements, scripts, script runs, and incidents will not be update in JIRA until the incident is synchronized again. You may wish to initiate a synchronize all. Before doing so, consider how many entities (issues/ requirements) will be synchronized as this may affect the performance of ET and JIRA during peak usage. You may wish to consider batching entities by using a filter to reduce the number of entities synchronized.

  • If you are moving your production system, we recommend contacting Catch Support in advance to arrange assistance with providing a new license text.

The Migration

  1. After setting up your new ET server, run the ET installer matching the version you are currently running on the ET server you are moving from. You can find the latest version of Enterprise Tester on our website or contact the Support team for older installation files.

  2. Copy across to the new server a copy of the backup copy of your original web.config file to the Enterprise Tester Web folder.

  3. Copy across to the new server a copy of the backup copy of your attachment folder to your Enterprise Tester Data folder or if you have changed the storage of attachments to a non default location (default storage is …\Data\Attachments) then you will need to copy over your attachment directory to the new location on the new ET server and update your web.config file.

  4. Start IIS.

  5. In the browser, navigate to the ET website. A new server key should be displayed. You will need to add a new license text in order to access ET. Email the server key to Catch Support requesting a new license and indicate whether the license is for a production or development environment.

  6. Apply the license text. You should be able to access Enterprise Tester now.

Updating the site.root.url

If the URL for ET is changing, then you will need to update the site.root.url setting in the web.config file. The site.root.url setting configures the URL that will be specified in links back to ET in external systems like JIRA.

To update the site.root.url, open the web.config file. You may need to open this file as Administrator in order to update it.

Locate the section <appSettings>… </appSettings>.

There is likely a key value pair for site.root.url already listed. If so, update the value to the new URL. If not, add the following key value pair at the end of the list of app setting before </appSettings>.

This should look like:

<appSettings>

<add key="site.root.url" value="http://myapp.com/EnterpriseTester/"/>

</appSettings>

For more information, please see the article appSettings.

Restart IIS.

If you are synchronizing with an external system you may wish to update your links by initiating a Synchronize All from the project link screen. As noted above, you may wish to consider batching entities for synchronization to reduce the load on ET and your external system if you expect a lot of data to be synchronized.

Updating the Attachment Storage Location

By default, Enterprise Tester stores all attachments in the Data directory of the ET installation files (\Data\Attachments). If you are storing your attachments in a non default location, you will need to update the web.config file to specify the storage location for all attachments.

To do this, you will need to locate or add the attachment.storage.path key to the appsettings in your web.config file.

To update the attachment.storage.path, open the web.config file. You may need to open this file as Administrator in order to update it.

There make be a key value pair for attachment.storage.path already listed. If so, update the value to the new path. If not, add the following key value pair at the end of the list of appSetting before </appSettings>.

This should look like:

<appSettings>

<add key="attachment.storage.path" value="f:\et-attachments"/>

</appSettings>

For more information, please see the article appSettings.

Restart IIS.

Once the web.config file is updated, ET should be able to access all attachments and new attachments will also be saved to this directory.

 

  • No labels