FastTrac: RecTrac Server Update
RecTrac Server update | Progress update
Summary
Join Zach Malloch as he reviews how to download and install RecTrac Updates.
Video
Transcript
In this fast track video, we're going to be going over applying the latest RecTrac and Progress updates to the RecTrac server. To do this, you'll need local admin access to the RecTrac server, the latest RecTrac Build, Tomcat updates, and Progress zip file from the FTP site. Please note, it is highly recommended that you download the zipped files in each directory only. In addition, once you have downloaded them, we recommend that you create a C/temp folder to extract the files into. This video will show the folder on the desktop, but this can occasionally cause issues if the file path is too long. You'll need the latest RecTrac and Progress versions and access to reboot the servers several times. You will also need some basic familiarity with IIS approximately 30 minutes to an hour of downtime. And please note that this is not required for Vermont systems hosted customers. The process can be broken down into roughly four steps, preparing the server, running the Progress update, running the RecTrac and Tomcat updates, installing the PA SOE and returning the server to full operation. Please note that a reboot will be required between each of these steps. We'll start by going to the sFTP site and remember that you can always find the current password by going to the knowledge base number 1516. Once logged into the sFTP site, we will go to files updates and drivers. We will go down to RecTrac and from here we will go to 3.1. From here we're going to download the zipped archive from the Progress folder, the Tomcat folder, and then we're going to go to updates find your current RecTrac version and grab the latest Build from that version. Once the files have been downloaded, we can prepare the server first we're going to turn off User Account Control or verify that it is at the lowest possible setting. Secondly, we will go into services. Set the admin service for Progress to a manual start and we will set Apache Tomcat also to be a manual start. We will then open up Internet Information Services and we will stop the VSI websites. We are now ready to reboot the server for the first time. Once the server has come back up we want to verify that we can get to a C:/VSI3 logs location if you've installed your RecTrac on any other drive you will need to manually create these two folders, a VSI3 folder at your root of c and a log folder under the VSI3 folder this will be used during the Progress install. Once we have verified that we will extract all of the Progress zipped files and once that's complete, we will run the Progress.exe file. accept all of the defaults through this procedure.
Once this is complete, it's time to reboot for the second time. Once we have rebooted if you manually created the log file location you can now delete that once you have done so we will now navigate to your VSI3 folder, to your RecTrac folder into your data folder. In each of the Demo and live folders we will want to delete any RecTrac lk files that we find. Once we have deleted those files, we can now run the RecTrac update. Once the RecTrac update is complete, we can go to Tomcat and run this update as well. With Tomcat updated it is now time for our third reboot. Once the server has come back up, we will go back into our VSI3 directory wherever that is on your server and we will go back into the RecTrac databases and we will delete the LK file from both live and from Demo. We're now ready to run our last Progress update. Running Progress. exe we will launch that when we are asked if we wish to add additional components we will add the Progress application server for OpenEdge or PASOE for short, hit next and allow that to install. Once the Progress patch has completed, hit next and finish now it's time to restart our services it's time to set the services back to automatic startup while in Apache Tomcat and set to automatic startup and also change the log on to local system accoun. We will then restart our websites through IIS. We will also need to navigate to our VSI3 slash logs folder and find any A.I.A VIC logs and delete those. And our last reboot should bring the server backup and fully running ready to serve client connections.
Delete