Difference between revisions of "Server Migrations"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
=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 18: | Line 19: | ||
<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> | ||
Revision as of 11:29, 12 July 2022
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.
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.
Application server move
- Review the High Level Design Document for the recommended server specs and required server software components for the latest version of PTS.
- Remote in to the existing application server.
- Make a copy of the PTSWeb directory (usually C:\inetpub\wwwroot\PTSWeb\).
- Copy the directory to the new server. Mount it in IIS as a .NET 4.6 application.
- Test the application.
- Take a backup of the existing PTS database. This backup is for rolling back the update if the need arises.
- Update PTS on the existing server to the latest release.
- Test that the update was successful.
- 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.
- Re-map any networked label printers onto the new server.
- Recreate any patient record lookup data sources.
- Update desktop and intranet shortcuts with the new PTS URL.
- Amend PTS URL setting in the PTS 5 app.
Database server move
- Review the High Level Design Document for the recommended server specs and required server software components for the latest version of PTS.
- Take a backup of the existing PTS database. This backup will be used for the migration.
- Create a new "PharmacyDB" database on the new database server, and then replace it using the backup from the old server.
- Verify that the PTS SQL user carried over properly and has dbo permission over the new database. If not, create it anew.
- Modify the connection string used by PTS in its web.config file so that it points to the new database location.
- Test the application is connecting to the database.
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.