Date: Fri, 29 Mar 2024 12:32:43 +0000 (UTC) Message-ID: <2077123005.12205.1711715563291@catch-kbase-p> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12204_1470823016.1711715563291" ------=_Part_12204_1470823016.1711715563291 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As your ET instance grows it may be necessary to upgrade your se= rver. This article takes you through the steps required when moving to a ne= w server.
About this Article
This article does not cover the steps to provisioning a server. This art= icle assumes that your server is ready to install ET. See the System Requirements article for inform= ation on the supported operating systems, required applications and the rec= ommended specifications. This article assumes that these requirements have = been met.
Back up your ET database and your ET installation directory includin=
g 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;
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 ch= ange the site.root.url setting in the web.config file. If you are sync= hronizing with JIRA and the URL for your ET instance is changing, the URL&n= bsp;in JIRA to the ET requirements, scripts, script runs, and incidents wil= l 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 bat= ching entities by using a filter to reduce the number of entities synchroni= zed.
If you are moving your production system, we recommend contacting&nb= sp;Catch Support in advance to arrange assistance with = providing a new license text.
After setting up your new ET server, run the ET installer matching t= he 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 cont= act the Support team for older installation files.
Copy across to the new server a copy of the backup copy of your orig= inal web.config file to the Enterprise Tester Web folder.
Copy across to the new server a copy of the backup copy of your atta= chment folder to your Enterprise Tester Data folder or if you have changed = the storage of attachments to a non default location (default storage = is =E2=80=A6\Data\Attachments) then you will need to copy over your attachm= ent directory to the new location on the new ET server and update your web.= config file.
Start IIS.
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 indica= te whether the license is for a production or development environment.
<= /li>Apply the license text. You should be able to access Enterprise Test= er now.
If the URL for ET is changing, then you will need to update the sit= e.root.url setting in the web.config file. The site.root.url setting config= ures 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 o= pen this file as Administrator in order to update it.
Locate the section <appSettings>=E2=80=A6= </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=3D"site.root.url" value=3D"http://myapp.com/Ent= erpriseTester/"/>
</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 synchronizatio= n to reduce the load on ET and your external system if you expect a lot of = data to be synchronized.
By default, Enterprise Tester stores all attachments in the Data= directory of the ET installation files (\Data\Attachments). If yo= u 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 attachme= nts.
To do this, you will need to locate or add the attachment.storage.path k= ey 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 liste= d. If so, update the value to the new path. If not, add the following key v= alue pair at the end of the list of appSetting before </appSetti= ngs>.
This should look like:
<appSettings>
<add key=3D"attachment.storage.path" value=3D"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 att= achments and new attachments will also be saved to this directory.