Difference between revisions of "Server Migrations"

From TMS Support Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
PTS server migrations are not that different to fresh installations of the PTS server software. The crucial difference, of course, is the use of a database backup from your existing PTS database server so your data carries over.
This document aims to briefly summarise the steps involved in a PTS server migration.
This document aims to briefly summarise the steps involved in a PTS server migration.
=Summary of a server migration=
=Summary of a server migration=
In reality a TMSi technician will take the lead on many of these steps but they are included here for the sake of completeness.
In reality a TMSi technician will take the lead on many of these steps but they are included here for the sake of completeness.
[[File:HLD_OnPremise.png|center]]
==Application server move==
==Application server move==
<ol>
<ol>
Line 11: Line 10:
<li>Copy the directory to the new server. Mount it in IIS as a .NET 4.6 application.</li>
<li>Copy the directory to the new server. Mount it in IIS as a .NET 4.6 application.</li>
<li>Test the application.</li>
<li>Test the application.</li>
<li>Take a backup of the existing PTS database. This backup is for rolling back the update if the need arises.</li>
<li>On each PC hosting PTS barcode scanners, uninstall the PTS Comms Client software, and then [[PTS Comms Client Installation|download and re-install]] the appropriate PTS Comms version, being sure to enter the new URL when prompted.</li>
<li>Update PTS on the existing server to the latest release.</li>
<li>Test that the update was successful.</li>
<li>On each PC hosting PTS barcode scanners, uninstall the PTS Comms Client software, and then [[PTS Comms Client Download Page|download]] and [[PTS Comms Client Installation|re-install]] the appropriate PTS Comms version, being sure to enter the new URL when prompted.</li>
<li>[[Label Printer Installation|Re-map any networked label printers onto the new server]].</li>
<li>[[Label Printer Installation|Re-map any networked label printers onto the new server]].</li>
<li>Recreate any [[Patient Record (PAS) Lookup|patient record lookup data sources]].</li>
<li>Recreate any [[Patient Record (PAS) Lookup|patient record lookup data sources]].</li>
<li>Update desktop and intranet shortcuts with the new PTS URL.</li>
<li>Update desktop and intranet shortcuts with the new PTS URL.</li>
<li>Amend PTS URL setting in the PTS 5 app.</li>
</ol>
</ol>


Line 29: Line 26:
<li>Modify the connection string used by PTS in its web.config file so that it points to the new database location.</li>
<li>Modify the connection string used by PTS in its web.config file so that it points to the new database location.</li>
<li>Test the application is connecting to the database.</li>
<li>Test the application is connecting to the database.</li>
<li>Login to the SSRS portal as an administrator and modify the PTS data source with the new connection string.</li>
</ol>
</ol>


Latest revision as of 11:45, 5 August 2024

This document aims to briefly summarise the steps involved in a PTS server migration.

Summary of a server migration

In reality a TMSi technician will take the lead on many of these steps but they are included here for the sake of completeness.

HLD OnPremise.png

Application server move

  1. Review the High Level Design Document for the recommended server specs and required server software components for the latest version of PTS.
  2. Remote in to the existing application server.
  3. Make a copy of the PTSWeb directory (usually C:\inetpub\wwwroot\PTSWeb\).
  4. Copy the directory to the new server. Mount it in IIS as a .NET 4.6 application.
  5. Test the application.
  6. On each PC hosting PTS barcode scanners, uninstall the PTS Comms Client software, and then download and re-install the appropriate PTS Comms version, being sure to enter the new URL when prompted.
  7. Re-map any networked label printers onto the new server.
  8. Recreate any patient record lookup data sources.
  9. Update desktop and intranet shortcuts with the new PTS URL.
  10. Amend PTS URL setting in the PTS 5 app.

Database server move

  1. Review the High Level Design Document for the recommended server specs and required server software components for the latest version of PTS.
  2. Take a backup of the existing PTS database. This backup will be used for the migration.
  3. Create a new "PharmacyDB" database on the new database server, and then replace it using the backup from the old server.
  4. Verify that the PTS SQL user carried over properly and has dbo permission over the new database. If not, create it anew.
  5. Modify the connection string used by PTS in its web.config file so that it points to the new database location.
  6. Test the application is connecting to the database.
  7. Login to the SSRS portal as an administrator and modify the PTS data source with the new connection string.

Patient record (PAS) application move

See the Patient Record (PAS) Lookup page.

SSRS server move

Only TMSi can configure SSRS for use with PTS. Contact us to arrange this.

Retrieved from ‘https://tmsinsight.com/TMSWiki/index.php?title=Server_Migrations&oldid=2440’