Table of Contents
Introduction
This document will walk you through the steps required to update RecTrac 3.1.10.xx to its latest version.
Updates to RecTrac arecumulative. This means you have todownload and run ONLY the update executable for the Minor Version/Build Versionto which you want to update. For example, you are running RecTrac 3.1.10.02.02 and want to update to RecTrac 3.1.10.04.04. You would download Setup_3.1.10.04.04.exe.However, you must perform ALL pre-update and post-update steps for anyversions you are skipping. Refer to the chart in Pre-Update Steps or Post-Update Steps for further information and examples.
To determine your current RecTrac version, click the Supporticon near the bottom of the sidebar. Version information is displayed as:
Version RecTrac 3.1.10.xx.yy Inthe example below: RecTrac 3.1.10.04.00.
Before starting the update, read this entire documentcarefully.
Time Commitment |
The time commitment varies. Depending on system resources and the size of your RecTrac database, the entire update process, including the creation of a current database backup file, could take anywhere from 30 minutes to several hours. |
The Update |
Perform the update only after reading the attached materials. Pick a date and time that will allow you to be without the RecTrac system for a period of time. |
Who Should Run the Update |
This process is designed to be run by the RecTrac System Administrator. |
How to Reach Vermont Systems |
Preparation Steps
1 Perform a Full Backup of RecTrac beforeyou begin the update. If something goes wrong during the update, you will beable to restore to your backup and revert to the old programs. The VSIdirectory with all its subdirectories must be included in the backup.
2 When you finish the backup, validatethat the backup tape or disks are good. Label the backup media with the currentdate and the following: RecTrac 3.1.10.xx.yy Final Backup Before Update. Savethe backup(s) in a fireproof, waterproof, secure place for at least one year.
3 Disable the screen saver on the dataserver. This will allow you to monitor the update progress as messages aredisplayed on the screen while the process runs.
4 Disable virus scan software on the dataserver for the duration of the RecTrac 3.1.xx.yy.zz install.
5 Close all other Windows applications onthe server while running the update, even those running in the background.
6 Write down the version of RecTrac towhich you are updating. You will need this information to determine the Post-Update Steps that need to be completedlater in this document.
Pre-Update Steps
Unless otherwise noted, Pre-Update steps need to beperformed from one (1) client only. Vermont Systems highly recommends runningPre-Update steps from a client connection on the RecTrac databaseserver, but unless noted, they can be run from any clientconnection. Changes will take place throughout the database.
Any Pre-Update steps that must be performed ona specific server are so noted.
Pre-update steps are Minor Version and Build -specific. Youmust complete the steps for all Minor Versions and Builds impacted by theupdate. Use the examples in the table below for reference:
Example Current Version |
Example Version Updating To |
Pre-Update Steps to Run in this Example |
RecTrac 3.1.10.02.yy |
RecTrac 3.1.10.03.yy |
Run Pre-Update steps for: · RecTrac 3.1.10.03.yy |
RecTrac 3.1.10.01.yy |
RecTrac 3.1.10.04.yy |
Run Pre-Update steps for: · RecTrac 3.1.10.02.yy · RecTrac 3.1.10.03.yy · RecTrac 3.1.10.04.yy
|
RecTrac 3.1.09.03.yy |
RecTrac 3.1.10.04.yy
|
Run Pre-Update steps for: · RecTrac 3.1.09.04.yy · RecTrac 3.1.10.00.yy · RecTrac 3.1.10.01.yy · RecTrac 3.1.10.02.yy · RecTrac 3.1.10.03.yy · RecTrac 3.1.10.04.yy |
Note: Contact Vermont Systems Support to obtain the properupdate documentation in the event you are updating through minor versions (forexample: from 3.1.09.xx.yy to 3.1.10.xx.yy). This documentcontains update steps for RecTrac 3.1.10.xx.yy only.
RecTrac3.1.10.xx.yy Pre-Update Steps
The sub-sections that follow list the mandatory Pre-UpdateSteps needed for a particular version. If a version is NOT listed, then NOpre-Update Steps are required for it.
3.1.10.00.04 Pre-UpdateSteps
1 Required for ALL Customers: Verify that your primary RecTracInterface Parameter is set to "Default."
· Go to SystemManagement • Misc Management • Interface Parameters.
· Select yourRecTrac_1 Interface Parameter (or your equivalent) and click Change.
· Verify the Isthis the Default Parameter for this Interface Type toggle option isenabled. Enable it if it isn't.
· Save changes andexit.
2 Required for ALL ePACT Customers: Contact your ePACT Customer Success Representativebefore updating to RecTrac 3.1.10.00.03.
Based on Customer feedback, ePACT ismaking changes to Group Names. There are a few programs that you need to runprior to updating to 3.1.10.00.03 in order to enjoy a smooth transition fromthe old Group Names to the new ones. ePACT has the files and instructionsyou'll need. Contact your ePACT Customer Success Representative for furtherinformation.
3 Optional: Review the 3.1.10 Differences from PriorVersions.pdf for anoverview of changes in RecTrac 3.1.10.00.03.
3.1.10.01.01 Pre-UpdateSteps
1 Requiredfor ALL Customers:Verify your RecTrac server has .NET Framework 4.7.2 (or higher)installed. If NOT, update your .NET Framework PRIOR to updating RecTrac toversion 3.1.10.01.01.
RecTrac 3.1.10.01.01 includes a new Vermont Systems EventTimer version 3.1.9.2 which requires Microsoft .NET Framework 4.7.2 or higherbe installed on your RecTrac server. If you have an older version of the .NETFramework on your server then the Vermont Systems Event Timer will NOT work. VermontSystems Event Timer is used to schedule events within RecTrac (i.e., sendemails, generate reports, create exports, etc.).
Here are several of useful Microsoft links to assist youwith this process:
· https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies
· https://docs.microsoft.com/en-us/dotnet/framework/install/
3.1.10.03.00 Pre-Update Steps
1 Requiredfor ALL Customers:Install Progress 11.7.5 and PASOE.
The update to 3.1.10.03.00 requires an update to ProgressService Pack 11.7.5. The RecTrac setup.exe installs the Service Packautomatically. However, it requires a restart of your servers.
· PLANACCORDINGLY! This update involves downtime foryour RecTrac Servers.
· Refer to Progress11.7.5 Patch.pdf for installation instructions andcomplete the process as outlined in that document.
THEN
Go directly to 3.1.10.03.00 Post-Update Steps to complete the update process.
3.1.10.04.04 Pre-UpdateSteps
1 Requiredfor ALL Customers:Ensure Progress 11.7.5 and PASOE have been installed.
· If you're updatingfrom RecTrac 3.1.10.03.00 to 3.1.10.04.04 (or greater), then youare good to go!
· If you're updatingfrom RecTrac 3.1.10.02.01 (or previous) to 3.1.10.04.04 (or greater),then you MUST install Progress 11.7.5 and PASOE before you can continue. Refer to Progress11.7.5 Patch.pdf or contact Vermont Systems Supportfor further information.
3.1.10.05.05 Pre-Update Steps
Note: We have identified issues with our WebTrac Facilityand Rental calendar search output on WebTrac that could lead to degradedperformance during heavy load. We have temporarily disabled Facility andRental calendar options in WebTrac while our development team works toremedy performance issues and provide an improved calendar search experience.Other calendars, such as Activity, Event, Ticket, and Trip are not impacted.
1 Required for ALL Users:On the Database Server ONLY:
· Make an OnlineBackup of your current RecTrac database.
· Stop All AppServer and WebSpeed Brokers. On ALL servers, includingDatabase/Transaction/AppServer. Log into OpenEdge Explorer and stop ALLAppServer and WebSpeed Brokers.
THEN
· Stop both the LIVE and DEMO databasesrunning.
· Before proceeding with the RecTrac_3.1.10.05.05.exe,Verify that all brokers have a status of Not Running. Theseinclude the following:
AppServers:
· EVENTlive
· EVENTdemo
· VIClive
· VICdemo
WebSpeed:
· Clientlive
· Clientdemo
· WEBlive
· WEBdemo
THEN
· Verify that all databases have a status of NotRunning These include the following:
· <servername>.LIVE
· <servername>.DEMO
3.1.10.07.04 Pre-Update Steps
Note: If you are running a version of 3.1.10.07.xx (i.e..07.00, .07.01, etc.), then skip this step. You do not need to stop thedatabase to go from a version of 3.1.10.07.xx to 3.1.10.07.04.
1 Requiredfor ALL Users Running 3.1.10.06.03 or Previous:
PLANACCORDINGLY:The 3.1.10.07.04 Update requires you to stop your RecTrac Database as wellas ALL AppServer and WebSpeed brokers connected to the database. This meansall RecTrac and WebTrac processing will be suspended while the update runs. Inother words: your RecTrac and WebTrac operations will be "down."
Depending on system resources, theentire update process, including the creation of a current database backupfile, could take up to two (2) hours or more.
Please plan accordingly. The 3.1.10.07.04update is NOT a build that can be performed while thesystem remains online.
· Make an OnlineBackup of your current RecTrac database.
· Stop All AppServer and WebSpeed Brokers. On ALL servers, includingDatabase/Transaction/AppServer. Log into OpenEdge Explorer and stop ALLAppServer and WebSpeed Brokers.
THEN
· Stop both the LIVE and DEMO databasesrunning.
· Before proceeding with the RecTrac_3.1.10.07.04.exe,Verify that all brokers have a status of Not Running. Theseinclude the following:
AppServers:
· EVENTlive
· EVENTdemo
· VIClive
· VICdemo
WebSpeed:
· Clientlive
· Clientdemo
· WEBlive
· WEBdemo
THEN
· Verify that all databases have a status of NotRunning These include the following:
· <servername>.LIVE
· <servername>.DEMO
3.1.10.08.00 Pre-Update Note
Whenthis build is applied all users will be redirected to the Next Gen UserInterface (UI) for RecTrac even if you were previously using the Classic UI.This change is automatic for all users.
NOTE:This change is for RecTrac only. All customers are able to use both theClassic and Next Gen UI for WebTrac.
3.1.10.09.02 Pre-Update Steps
Note: If you are running a version of 3.1.10.09.xx (i.e. .09.00,.09.01, etc.), then skip this step. You do not need to stop the database to gofrom version 3.1.10.09.xx to 3.1.10.09.02.
1 Required for ALL UsersRunning 3.1.10.08.00 or Previous:
PLANACCORDINGLY:The 3.1.10.09.00 Update requires you to stop your RecTrac Database as wellas ALL AppServer and WebSpeed brokers connected to the database. This meansall RecTrac and WebTrac processing will be suspended while the update runs. Inother words: Your RecTrac and WebTrac operations will be "down" whilethe update runs.
Depending on system resources, theentire update process, including the creation of a current database backupfile, could take up to two (2) hours or more.
Please plan accordingly. The 3.1.10.09.00Update is NOT a build that can be performed while thesystem remains online.
· Make an OnlineBackup of your current RecTrac database.
· Stop All AppServer and WebSpeed Brokers on ALL servers, includingDatabase/Transaction/AppServer. Log in to OpenEdge Explorer and stop ALLAppServer and WebSpeed Brokers.
THEN
· Stop both the LIVE and DEMO databases.
· Before proceeding with the RecTrac_3.1.10.09.02.exe,verify that all brokers have a status of Not Running. Theseinclude the following:
AppServers:
· EVENTlive
· EVENTdemo
· VIClive
· VICdemo
WebSpeed:
· Clientlive
· Clientdemo
· WEBlive
· WEBdemo
THEN
· Verify that all databases have a status of NotRunning. These include the following:
· <servername>.LIVE
· <servername>.DEMO
3.1.10.10.05 Pre-Update Note
WebTrac version 3.1.10.10.00 and higher requiresthat reCAPTCHA be configured for your WebTrac site. Numerous WebTrac workflowsnow will require reCAPTCHA, including sales with credit card processing.PayTrac, CardConnect, and ETS/Elavon credit card integrations now require thatreCAPTCHA be added to the WebTrac checkout screen. PlugNPay/WebXPress solutionsdo NOT require reCAPTCHA as reCAPTCHA should be implemented on the PlugNPayhosted payment page.
This change requiring reCAPTCHAconfiguration is for WebTrac only. See theRecTrac 3.1.10.10_Modification Listing.pdf for additional information. Pleaserefer to the following Knowledge Base entry for information on how to acquirereCAPTCHA keys and the steps needed to implement reCAPTCHA for WebTrac: KA-01399.
3.1.10.10.05 Pre-Update Steps
Note: If you are running a version of 3.1.10.09.xx (i.e..09.00, .09.01, etc.) or 3.1.10.10.xx (i.e. .10.00, .10.01, .10.02, .10.03,.10.04), then skip this step. You do not need to stop the database to go fromversion 3.1.10.09.xx or 3.1.10.10.xx to 3.1.10.10.05.
1 Required for ALL UsersRunning 3.1.10.08.00 or Previous:
PLANACCORDINGLY:The 3.1.10.10.05 Update requires you to stop your RecTrac Database as wellas ALL AppServer and WebSpeed brokers connected to the database. This meansall RecTrac and WebTrac processing will be suspended while the update runs. Inother words: Your RecTrac and WebTrac operations will be "down" whilethe update runs.
Depending on system resources, theentire update process, including the creation of a current database backupfile, could take up to two (2) hours or more.
Please plan accordingly. The 3.1.10.10.05Update is NOT a build that can be performed while thesystem remains online.
· Make an OnlineBackup of your current RecTrac database.
· Stop All AppServer and WebSpeed Brokers on ALL servers, includingDatabase/Transaction/AppServer. Log in to OpenEdge Explorer and stop ALLAppServer and WebSpeed Brokers.
THEN
· Stop both the LIVE and DEMO databases.
· Before proceeding with the RecTrac_3.1.10.10.05.exe,verify that all brokers have a status of Not Running. Theseinclude the following:
AppServers:
· EVENTlive
· EVENTdemo
· VIClive
· VICdemo
WebSpeed:
· Clientlive
· Clientdemo
· WEBlive
· WEBdemo
THEN
· Verify that all databases have a status of NotRunning. These include the following:
· <servername>.LIVE
· <servername>.DEMO
3.1.10.11.03 Pre-UpdateNote
WebTrac version 3.1.10.10.00 and higher requiresthat reCAPTCHA be configured for your WebTrac site. Numerous WebTrac workflowsnow will require reCAPTCHA, including sales with credit card processing.PayTrac, CardConnect, and ETS/Elavon credit card integrations now require thatreCAPTCHA be added to the WebTrac checkout screen. PlugNPay/WebXPress solutionsdo NOT require reCAPTCHA as reCAPTCHA should be implemented on the PlugNPayhosted payment page.
This change requiring reCAPTCHA configurationis for WebTrac only. See the RecTrac3.1.10.10_Modification Listing.pdf for additional information. Please refer tothe following Knowledge Base entry for information on how to acquire reCAPTCHAkeys and the steps needed to implement reCAPTCHA for WebTrac: KA-01399.
3.1.10.11.03 Pre-UpdateSteps
Note: If you are running a version of 3.1.10.11 (3.1.10.11.00,3.1.10.11.01, 3.1.10.11.02), then skip these Pre-Update Steps. You do notneed to stop the database to go from version 3.1.10.11.00, 3.1.10.11.01, or3.1.10.11.02 to 3.1.10.11.03. If you are running 3.1.10.10.05 (orprevious), then perform all Pre-Update Steps listed here. You must stopyour database and resources to move from 3.1.10.10.05 (or previous) to3.1.10.11.03.
1 Required for ALL UsersRunning 3.1.10.10.05 or Previous:
PLANACCORDINGLY:The 3.1.10.11.03 Update requires you to stop your RecTrac Database as wellas ALL AppServer and WebSpeed brokers connected to the database. This meansall RecTrac and WebTrac processing will be suspended while the update runs. Inother words: Your RecTrac and WebTrac operations will be "down" whilethe update runs.
Depending on system resources, theentire update process, including the creation of a current database backupfile, could take up to two (2) hours or more.
Please plan accordingly. The 3.1.10.11.03Update is NOT a build that can be performed while thesystem remains online.
· Make an OnlineBackup of your current RecTrac database.
· Stop All AppServer and WebSpeed Brokers on ALL servers, includingDatabase/Transaction/AppServer. Log in to OpenEdge Explorer and stop ALLAppServer and WebSpeed Brokers.
THEN
· Stop both the LIVE and DEMO databases.
· Before proceeding with the RecTrac_3.1.10.11.03.exe,verify that all brokers have a status of Not Running. Theseinclude the following:
AppServers:
· EVENTlive
· EVENTdemo
· VIClive
· VICdemo
WebSpeed:
· Clientlive
· Clientdemo
· WEBlive
· WEBdemo
THEN
· Verify that all databases have a status of NotRunning. These include the following:
· <servername>.LIVE
· <servername>.DEMO
3.1.10.12.01 Pre-Update Note
WebTrac version 3.1.10.10.00 and higher requiresthat reCAPTCHA be configured for your WebTrac site. Numerous WebTrac workflowsnow will require reCAPTCHA, including sales with credit card processing.PayTrac, CardConnect, and ETS/Elavon credit card integrations now require thatreCAPTCHA be added to the WebTrac checkout screen. PlugNPay/WebXPress solutionsdo NOT require reCAPTCHA as reCAPTCHA should be implemented on the PlugNPayhosted payment page.
This change requiring reCAPTCHAconfiguration is for WebTrac only. See theRecTrac 3.1.10.10_Modification Listing.pdf for additional information. Pleaserefer to the following Knowledge Base entry for information on how to acquirereCAPTCHA keys and the steps needed to implement reCAPTCHA for WebTrac: KA-01399.
3.1.10.12.01 Pre-Update Steps
Note: If you are running a version of 3.1.10.11 (3.1.10.11.00,3.1.10.11.01, 3.1.10.11.02, 3.1.10.11.03) or version 3.1.10.12.00, thenskip these Pre-Update Steps. You do not need to stop the database to go from aversion of 3.1.10.11 or version 3.1.10.12.00 to 3.1.10.12.01. If youare running 3.1.10.10.05 (or previous), then perform all Pre-Update Stepslisted here. You must stop your database and resources to move from 3.1.10.10.05(or previous) to 3.1.10.12.01.
1 Required for ALL UsersRunning 3.1.10.10.05 or Previous:
PLANACCORDINGLY:The 3.1.10.12.01 Update requires you to stop your RecTrac Database as wellas ALL AppServer and WebSpeed brokers connected to the database. This meansall RecTrac and WebTrac processing will be suspended while the update runs. Inother words: Your RecTrac and WebTrac operations will be "down" whilethe update runs.
Depending on system resources, theentire update process, including the creation of a current database backupfile, could take up to two (2) hours or more.
Please plan accordingly. The 3.1.10.12.01Update is NOT a build that can be performed while thesystem remains online.
· Make an OnlineBackup of your current RecTrac database.
· Stop All AppServer and WebSpeed Brokers on ALL servers, includingDatabase/Transaction/AppServer. Log in to OpenEdge Explorer and stop ALLAppServer and WebSpeed Brokers.
THEN
· Stop both the LIVE and DEMO databases.
· Before proceeding with the RecTrac_3.1.10.12.01.exe,verify that all brokers have a status of Not Running. Theseinclude the following:
AppServers:
· EVENTlive
· EVENTdemo
· VIClive
· VICdemo
WebSpeed:
· Clientlive
· Clientdemo
· WEBlive
· WEBdemo
THEN
· Verify that all databases have a status of NotRunning. These include the following:
· <servername>.LIVE
· <servername>.DEMO
3.1.10.13.02 Pre-Update Note
WebTrac version 3.1.10.10.00 and higher requiresthat reCAPTCHA be configured for your WebTrac site. Numerous WebTrac workflowsnow will require reCAPTCHA, including sales with credit card processing.PayTrac, CardConnect, and ETS/Elavon credit card integrations now require thatreCAPTCHA be added to the WebTrac checkout screen. PlugNPay/WebXPress solutionsdo NOT require reCAPTCHA as reCAPTCHA should be implemented on the PlugNPayhosted payment page.
This change requiring reCAPTCHAconfiguration is for WebTrac only. See theRecTrac 3.1.10.10_Modification Listing.pdf for additional information. Pleaserefer to the following Knowledge Base entry for information on how to acquirereCAPTCHA keys and the steps needed to implement reCAPTCHA for WebTrac: KA-01399.
3.1.10.13.02 Pre-Update Steps
Note: If you are running a version of 3.1.10.13(3.1.10.13.00, 3.1.10.13.01), then skip these Pre-Update Steps. You do notneed to stop the database to go from a version of 3.1.10.13 to 3.1.10.13.02.If you are running version 3.1.10.12.01 (or previous), then performall Pre-Update Steps listed here. You must stop your database and resources tomove from 3.1.10.12.01 (or previous) to 3.1.10.13.02.
1 Required for ALL UsersRunning 3.1.10.12.01 or Previous:
PLANACCORDINGLY:The 3.1.10.13.02 Update requires you to stop your RecTrac Database as wellas ALL AppServer and WebSpeed brokers connected to the database. This meansall RecTrac and WebTrac processing will be suspended while the update runs. Inother words: Your RecTrac and WebTrac operations will be "down" whilethe update runs.
Depending on system resources, theentire update process, including the creation of a current database backupfile, could take up to two (2) hours or more.
Please plan accordingly. The 3.1.10.13.02Update is NOT a build that can be performed while thesystem remains online.
· Make an OnlineBackup of your current RecTrac database.
· Stop All AppServer and WebSpeed Brokers on ALL servers, includingDatabase/Transaction/AppServer. Log in to OpenEdge Explorer and stop ALLAppServer and WebSpeed Brokers.
THEN
· Stop both the LIVE and DEMO databases.
· Before proceeding with the RecTrac_3.1.10.13.02.exe,verify that all brokers have a status of Not Running. Theseinclude the following:
AppServers:
· EVENTlive
· EVENTdemo
· VIClive
· VICdemo
WebSpeed:
· Clientlive
· Clientdemo
· WEBlive
· WEBdemo
THEN
· Verify that all databases have a status of NotRunning. These include the following:
· <servername>.LIVE
· <servername>.DEMO
Update Instructions
Downloadthe Setup.exe from the Vermont Systems SFTP Site
1 Log in to the Vermont Systems SFTPsite and browse to: ftp://ftp.vermontsystems.com/File Updates AndDrivers/RecTrac/3.1/Updates/3.1.10/Builds.
2 Refer to Vermont Systems KnowledgeBase entry 1516 or contact Vermont Systems Support for current SFTP logincredentials.
3 Save to a local temp directory.
Updates arecumulative. This means you have todownload and run ONLY the update executable for the Minor Version/Build Versionto which you want to update. For example, you are running RecTrac 3.1.10.07.04and want to update to RecTrac 3.1.10.09.02, you would download Setup_3.1.10.09.02.exe.However, you must perform ALL pre-update and post-update steps for anyversions you are skipping. Refer to the chart in Pre-Update Steps or Post-Update Steps for further information and examples.
Where to Run the RecTracUpdate Script
RecTrac 3.1 updates are run on every server you use forRecTrac. Depending on your configuration, this can be one (1) server ormultiple servers. If you run WebTrac, you must run the update on the WebServer. If you have a separate Transaction Server, you must run the update onthat server. If you have a separate VIC AppServer, you must run the update onthe server. Post update steps are performed on the database server. RecTrac 3.1is browser-based. There is no client install/update.
Run theUpdate
Note: ContactVermont Systems Support to obtain the proper update documentation in the eventyou are updating through minor versions (for example: from 3.1.09.xx.yyto 3.1.10.xx.yy). This document contains update steps for RecTrac3.1.10.xx.yy only.
1 Perform all Pre-UpdateSteps for the buildto which you are updating, if there are any.
2 Ensure allusers are logged out of RecTrac.
3 Log into theRecTrac Database Server as an Administrator.
4 In Windows,browse to the setup.exe you downloaded above. Right-click on theSetup_3.1.10.xx.yy.exe and select Run as Administrator.
5 The updateruns automatically. You will be prompted with the following. Answer Yes.
6 Be Patient!Let the installscript run. This may take anywhere from 10 minutes to an hour (or more),depending on your server's resources and the size of your database.
7 At theInstallation Complete screen, click Next.
8 Click Finish.
9 Repeat Steps3-11 on every server you use for RecTrac. Refer to Where toRun the RecTrac Update Scriptfor details.
10 Log into RecTrac and perform allmandatory and required Post-Update Steps for the Minor Version/Build Version towhich you updated.
11 IF you are updating through multiplebuilds, you must perform all applicable Post-Update Steps. Refer to the Post-UpdateSteps Chart forexamples.
Notes: This document is written with the assumption thatyou are updating to the latest version of RecTrac within a day or two of itsrelease. However, if the release has been available for a while, then it ispossible that patch files have been released for critical bug fixes.
To test whether patch files are available, return to the FTP Siteand go to the directory from which you downloaded the RecTrac update.exe.(Refer to Download the Setup.exe from theVermont Systems FTP Site above, if needed.) If patch files are available,there will be a /_3.1.10.xx.yy_Patch_Files sub-directory, where 3.1.10.xx.yyrefers to folder from which you downloaded the update.exe.
Open that sub-directory and read the Readme.txt file. Refer toVermont Systems Knowledge Base #3250.
Post-Update Steps
Unlessotherwise noted, Post-Update steps need to be performed from one (1) clientonly. Vermont Systems highly recommends running Post-Update steps from a clientconnection on the RecTrac database server, but unless noted, theycan be run from any client connection. Changes will take placethroughout the database.
Post-Update steps that mustbe performed on a specific server are so noted.
Post-Update steps are MinorVersion and Build -specific. You must complete the steps for all Minor Versionsand Builds impacted by the update. Use the examples in the table below forreference:
Example Current Version |
Example Version Updating To |
Post-Update Steps to Run in this Example |
RecTrac 3.1.10.03.yy |
RecTrac 3.1.10.04.yy |
Run Post-Update steps for: · RecTrac 3.1.10.04.yy |
RecTrac 3.1.10.01.yy |
RecTrac 3.1.10.04.yy |
Run Post-Update steps for: · RecTrac 3.1.10.02.yy · RecTrac 3.1.10.03.yy · RecTrac 3.1.10.04.yy
|
RecTrac 3.1.09.03.yy |
RecTrac 3.1.10.04.yy
|
Run Post-Update steps for: · RecTrac 3.1.09.04.yy · RecTrac 3.1.10.00.yy · RecTrac 3.1.10.01.yy · RecTrac 3.1.10.02.yy · RecTrac 3.1.10.03.yy · RecTrac 3.1.10.04.yy |
Note:Contact Vermont Systems Support to obtain the proper update documentationin the event you are updating through minor versions (for example: from 3.1.09.xx.yyto 3.1.10.xx.yy). This document contains update steps for RecTrac3.1.10.xx.yy only.
RecTrac3.1.10 Post-Update Steps
The sub-sections that follow list the mandatory Post-UpdateSteps.
3.1.10.00.03 Post-Update Steps
1 Requiredfor ALL Users: Verifythat all AppServer and WebSpeed agents were trimmed/restarted in OpenEdgeExplorer by looking at the Server Pool Control • Started date for running ASand WS agents. If some agents were NOT automatically restarted by the script,manually trim these agents or manually stop and restart the broker.
2 Requiredfor ALL Users: Oncethe build has been applied to ALL Servers, instruct ALL your users to log outof RecTrac completely and then log back in. Logging out and then logging backin will eliminate the risk of newly changed business logic attempting to useolder (mismatched) javascripts and screendata, which can cause significant errorswith Daily Processing functions.
3 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
4 Optional:Enable the RecTracNext Gen User Interface (UI). RecTrac Next Gen provides a simpler, faster, andmore intuitive UI designed to improve your User Experience (UX). Screens areeasier to read, and a "Favorites" menu has been added that allowsusers to get to commonly used programs in a single click. There are NO changesto existing workflow. At this point, the only change is to look, feel, andnavigation.
The classic UI will be phased out at some future release,so Vermont Systems highly encourages you to try the Next Gen UI as early aspossible. Here are two (2) good options:
· Option 1:Enable RecTrac Next Gen in your Demo Database. This option allows you to get familiarwith the new UI using your own data but in a non-production environment.
· Go to the Loginscreen for Demo, but don't log in.
· At the classic UIlogin screen, place your cursor in the URL bar. Overwrite"InterfaceParameter=RecTrac_1" with
"InterfaceParameter=NextGen"
· Press<Enter> on your keyboard. The new UI will be enabled for that session,and you'll see the Next Gen login screen, as shown below.
· Option 2: Usethe RecTrac Next Gen Interface Parameter in your Live Database. This option allows you to toggle backand forth between the new UI and the classic UI, on a per session basis, inyour Live database while in production.
· Go to the Loginscreen in Live, but don't log in.
· At the classic UIlogin screen, place your cursor in the URL bar. Overwrite"InterfaceParameter=RecTrac_1" with "InterfaceParameter=NextGen
· Press<Enter> on your keyboard. The new UI will be enabled for that session,and you'll see the Next Gen login screen, as shown below.
When you're ready to go "full time" with the NextGen UI, simply turn on the Enable Modern UI option on your RecTrac_1Interface Parameter!
Note: If using Option 2, Vermont Systems recommendsrunning one session at time per workstation only. Do not run concurrentsessions on a single workstation where one session uses the classic UI and theother uses the Next Gen UI. Oddities may occur, such as receipts and reportsnot previewing, etc.
3.1.10.01.01 Post-Update Steps
1 Requiredfor ALL Users: Verifythat all AppServer and WebSpeed agents were trimmed/restarted in OpenEdgeExplorer by looking at the Server Pool Control • Started date for running ASand WS agents. If some agents were NOT automatically restarted by the script,manually trim these agents or manually stop and restart the broker.
2 Requiredfor ALL Users: Oncethe build has been applied to ALL Servers, instruct ALL your users to log outof RecTrac completely and then log back in. Logging out and then logging backin will eliminate the risk of newly changed business logic attempting to useolder (mismatched) javascripts and screendata, which can cause significanterrors with Daily Processing functions.
3 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
4 Requiredfor ALL Users: Verifythe Vermont Systems Event Timer is running. On your servers, go to Services. Atthe top, you should see "(VSI) Event Timer." Ensure the Servicerunning.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
Note: In 3.1.10.01.01 Pre-Update Steps, you verifiedMicrosoft .NET version 4.7.2 or higher is installed (or you installed it). Ifyou missed that step, then the Vermont Systems Event Timer will error out. Goback to the Pre-Update steps and follow the links to install .Net Framework.
3.1.10.02.01 Post-Update Steps
1 Requiredfor ALL Users: Verifythat all AppServer and WebSpeed agents were trimmed/restarted in OpenEdgeExplorer by looking at the Server Pool Control • Started date for running ASand WS agents. If some agents were NOT automatically restarted by the script,manually trim these agents or manually stop and restart the broker.
2 Requiredfor ALL Users: Oncethe build has been applied to ALL Servers, instruct ALL your users to log outof RecTrac completely and then log back in. Logging out and then logging backin will eliminate the risk of newly changed business logic attempting to useolder (mismatched) javascripts and screendata, which can cause significanterrors with Daily Processing functions.
3 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
4 Requiredfor ALL Users: Verifythe Vermont Systems Event Timer is running. On your servers, go to Services. Atthe top, you should see "(VSI) Event Timer." Ensure the Servicerunning.
If the service is not running, navigate to OpenEdge Explorerand restart the EVENTlive AppServer. Afterwards, verify in Services that the(VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
Note: In 3.1.10.01.01 Pre-Update Steps, you verifiedMicrosoft .NET version 4.7.2 or higher is installed (or you installed it). Ifyou missed that step, then the Vermont Systems Event Timer will error out. Goback to the Pre-Update steps and follow the links to install .Net Framework.
3.1.10.03.00 Post-Update Steps
1 Requiredfor ALL Users: Verify you installed PASOE.
· On your RecTracserver(s), go to Start • OpenEdge 11.7 • License Info.
· Scroll down andverify "Product Name: Progress ProdAS for OE."
· If you HAVEthe Progress ProdAS for OE, then continue to step 2 below.
· If you DO NOThave Progress ProdAS for OE, then install it before you continue. Refer to Progress11.7.5 Patch.pdf for installation instructions.
2 Requiredfor ALL Users: Verifythat all AppServer and WebSpeed agents were trimmed/restarted in OpenEdgeExplorer by looking at the Server Pool Control • Started date for running ASand WS agents. If some agents were NOT automatically restarted by the script,manually trim these agents or manually stop and restart the broker.
3 Requiredfor ALL Users: Oncethe build has been applied to ALL Servers, instruct ALL your users to log outof RecTrac completely and then log back in. Logging out and then logging backin will eliminate the risk of newly changed business logic attempting to useolder (mismatched) javascripts and screendata, which can cause significanterrors with Daily Processing functions.
4 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
5 Requiredfor ALL Users: Verifythe Vermont Systems Event Timer is running. On your servers, go to Services. Atthe top, you should see "(VSI) Event Timer." Ensure the Servicerunning.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.04.04 Post-UpdateSteps
Note: If you're updating from 3.1.10.03.00 to3.1.10.04.04 (or greater), then continue with the Post-Update Steps below.
If you're updating from 3.1.10.02.01 (or previous) to3.1.10.04.04 (or greater), then verify you installed PASOE before you continue.Refer to 3.1.10.03.00 Post-UpdateStep No. 1 or contact Vermont Systems Support for further information.
1 Requiredfor ALL Users: Verifythat all AppServer and WebSpeed agents were trimmed/restarted in OpenEdgeExplorer by looking at the Server Pool Control • Started date for running ASand WS agents. If some agents were NOT automatically restarted by the script,manually trim these agents or manually stop and restart the broker.
2 Requiredfor ALL Users: Oncethe build has been applied to ALL Servers, instruct ALL your users to log outof RecTrac completely and then log back in. Logging out and then logging backin will eliminate the risk of newly changed business logic attempting to useolder (mismatched) javascripts and screendata, which can cause significanterrors with Daily Processing functions.
3 Requiredfor ALL Users: Verifythe Vermont Systems Event Timer is running. On your servers, go to Services. Atthe top, you should see "(VSI) Event Timer." Ensure the Servicerunning.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.05.05 Post-Update Steps
1 Requiredfor ALL Users: Use the Vermont Systems Database Uility.exe to Truncatethe Bi file for both the your LIVE and DEMO databases.
· In Windows, go to Start •All Programs •VSI3 •DB_Utilities.
· Select Truncate Bi and click Next.
· Select Progress 11.7.
· Click Browse and browse to your LIVE Database File.
· Click Process.
· Click Next when the process completes.
· Opt to Run Another Utility and repeat these steps for yourDEMO database file.
2 Requiredfor ALL Users: InOpenEdge Explorer 11.7.5: Restart the RecTrac Live and Demo databases.
3 Requiredfor ALL Users: InOpenEdge Explorer 11.7.5: Restart all AppServer and WebSpeedbrokers.
4 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
5 Requiredfor ALL Users: Verifythe Vermont Systems Event Timer is running. On your servers, go to Services. Atthe top, you should see "(VSI) Event Timer." Ensure the Servicerunning.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.06.03 Post-Update Steps
1 Required for ALL Users: Verify that all AppServer andWebSpeed agents were trimmed/restarted in OpenEdge Explorer by looking at theServer Pool Control • Started date for running AS and WS agents. If some agentswere NOT automatically restarted by the script, manually trim these agents ormanually stop and restart the broker.
2 Requiredfor ALL Users: Oncethe build has been applied to ALL Servers, instruct ALL your users to log outof RecTrac completely and then log back in. Logging out and then logging backin will eliminate the risk of newly changed business logic attempting to useolder (mismatched) javascripts and screendata, which can cause significanterrors with Daily Processing functions.
3 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
4 Requiredfor ALL Users: Verifythe Vermont Systems Event Timer is running. On your servers, go to Services. Atthe top, you should see "(VSI) Event Timer." Ensure the Servicerunning.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.07.04 Post-Update Steps
Note: If you are updating from a version of 3.1.10.07.xx(i.e. .07.00, .07.01, etc.) to 3.1.10.07.04 then skip to Post UpdateStep 5. If you are updating from 3.1.10.06.03 (or previous), then perform allPost Update Steps listed here.
1 Important Information for ALL Users: 3.1.10.07.04is the last RecTrac release to support the RecTrac Classic User Interface (UI).3.1.10.08.00 and later will support the Next Gen UI only.
2 Requiredfor ALL Users who are updating from 3.1.10.06.03 (or previous) to 3.1.10.07.04:Use the Vermont Systems Database Utilities.exe to Truncate the Bi file forboth the your LIVE and DEMO databases.
· In Windows, go to Start •All Programs •VSI3 •DB_Utilities.
· Select Truncate Bi and click Next.
· Select Progress 11.7.
· Click Browse and browse to your LIVE Database File.
· Click Process.
· Click Next when the process completes.
· Opt to Run Another Utility and repeat these steps for yourDEMO database file.
3 Requiredfor ALL Users who are updating from 3.1.10.06.03 (or previous) to 3.1.10.07.04: In OpenEdge Explorer 11.7.5: Restartthe RecTrac Live and Demo databases.
4 Requiredfor ALL Users who are updating from 3.1.10.06.03 to 3.1.10.07.04: In OpenEdge Explorer 11.7.5:Restart all AppServer and WebSpeed brokers.
5 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
6 Requiredfor ALL Users:Verify the Vermont Systems Event Timer is running. On your servers, go toServices. At the top, you should see "(VSI) Event Timer." Ensure theService running.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.08.00 Post-Update Steps
Whenthis build is applied all users will be redirected to the Next Gen UserInterface (UI) for RecTrac even if you were previously using the Classic UI.This change is automatic for all users.
NOTE:This change is for RecTrac only. All customers are able to use both the Classicand Next Gen UI for WebTrac.
1 Required for ALL Users: Verify that all AppServer and WebSpeed agents weretrimmed/restarted in OpenEdge Explorer by looking at the Server Pool Control •Started date for running AS and WS agents. If some agents were NOTautomatically restarted by the script, manually trim these agents or manuallystop and restart the broker.
2 Required for ALL Users: Once the build has been applied to ALL Servers,instruct ALL your users to log out of RecTrac completely and then log back in.Logging out and then logging back in will eliminate the risk of newly changedbusiness logic attempting to use older (mismatched) javascripts and screendata,which can cause significant errors with Daily Processing functions.
3 Required for ALL Users: Ensure Tomcat is running. On your servers, go toServices. Scroll down the list and find "Apache Tomcat." Ensure theService running. If not, right-click and select "Start."
4 Required for ALL Users: Verify the Vermont Systems Event Timer is running. Onyour servers, go to Services. At the top, you should see "(VSI) EventTimer." Ensure the Service running.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, inRecTrac Scheduled Events Management, verify that scheduled events are runningwhen they should (i.e., the Scheduled Program Business/EmailQueue.r should runevery minute or two based on configuration).
3.1.10.09.02 Post-Update Steps
Note: If you are updating from a version of 3.1.10.09.xx(i.e. .09.00, .09.01, etc.) to 3.1.10.09.02, then skip to Post UpdateStep 5. If you are updating from 3.1.10.08.00 (or previous), then perform allPost Update Steps listed here.
1 ImportantInformation for ALL Users: Release 3.1.10.08.00 and future releasessupport the Next Gen UI only.
2 Requiredfor ALL Users who are updating from 3.1.10.08.00 (or Previous): Use theVermont Systems Database Utilities.exe to Truncate the Bi file for both theLIVE and DEMO databases.
· In Windows, go to Start • All Programs • VSI3 • DB_Utilities.
· Select Truncate Bi and click Next.
· Select Progress 11.7.
· Click Browse and browse to your LIVE Database File.
· Click Process.
· Click Next when the process completes.
· Opt to Run Another Utility and repeat these steps for yourDEMO database file.
3 Requiredfor ALL Users who are updating from 3.1.10.08.00 (or Previous): In OpenEdge Explorer 11.7.5: Restartthe RecTrac Live and Demo databases.
4 Requiredfor ALL Users who are updating from 3.1.10.08.00: In OpenEdge Explorer 11.7.5: Restartall AppServer and WebSpeed brokers.
5 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
6 Requiredfor ALL Users:Verify the Vermont Systems Event Timer is running. On your servers, go toServices. At the top, you should see "(VSI) Event Timer." Ensure theService running.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.10.05 Post-Update Steps
Note: If you are updating from a version of 3.1.10.09.xx(i.e. .09.00, .09.01, etc.) or 3.1.10.10.xx (i.e. .10.00, .10.01,.10.02, .10.03, .10.04), then skip to Post Update Step 5. If you are updatingfrom 3.1.10.08.00 (or previous), then perform all Post Update Steps listedhere.
1 ImportantInformation for ALL Users: Release 3.1.10.08.00 and future releasessupport the Next Gen UI only.
2 Requiredfor ALL Users who are updating from 3.1.10.08.00 (or Previous): Use theVermont Systems Database Utilities.exe to Truncate the Bi file for both theLIVE and DEMO databases.
· In Windows, go to Start • All Programs • VSI3 • DB_Utilities.
· Select Truncate Bi and click Next.
· Select Progress 11.7.
· Click Browse and browse to your LIVE Database File.
· Click Process.
· Click Next when the process completes.
· Opt to Run Another Utility and repeat these steps for yourDEMO database file.
3 Requiredfor ALL Users who are updating from 3.1.10.08.00 (or Previous): In OpenEdge Explorer 11.7.5: Restartthe RecTrac Live and Demo databases.
4 Requiredfor ALL Users who are updating from 3.1.10.08.00: In OpenEdge Explorer 11.7.5: Restartall AppServer and WebSpeed brokers.
5 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
6 Requiredfor ALL Users:Verify the Vermont Systems Event Timer is running. On your servers, go toServices. At the top, you should see "(VSI) Event Timer." Ensure theService running.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.11.03Post-Update Steps
Note: If you are updating from a version of 3.1.10.11(3.1.10.11.00, 3.1.10.11.01, 3.1.10.11.02), then skip to Post-UpdateStep 5. If you are updating from 3.1.10.10.05 (or previous), thenperform all Post-Update Steps listed here.
1 ImportantInformation for ALL Users: Release 3.1.10.08.00 and future releasessupport the Next Gen UI only.
2 Requiredfor ALL Users who are updating from 3.1.10.10.05 (or Previous): Use theVermont Systems Database Utilities.exe to Truncate the Bi file for both theLIVE and DEMO databases.
· In Windows, go to Start • All Programs • VSI3 • DB_Utilities.
· Select Truncate Bi and click Next.
· Select Progress 11.7.
· Click Browse and browse to your LIVE Database File.
· Click Process.
· Click Next when the process completes.
· Opt to Run Another Utility and repeat these steps for yourDEMO database file.
3 Requiredfor ALL Users who are updating from 3.1.10.10.05 (or Previous): In OpenEdge Explorer 11.7.5: Restartthe RecTrac Live and Demo databases.
4 Requiredfor ALL Users who are updating from 3.1.10.10.05: In OpenEdge Explorer 11.7.5: Restartall AppServer and WebSpeed brokers.
5 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
6 Requiredfor ALL Users:Verify the Vermont Systems Event Timer is running. On your servers, go toServices. At the top, you should see "(VSI) Event Timer." Ensure theService running.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.12.01 Post-Update Steps
Note: If you are updating from a version of 3.1.10.11(3.1.10.11.00, 3.1.10.11.01, 3.1.10.11.02, 3.1.10.11.03) or version 3.1.10.12.00,then skip to Post-Update Step 5. If you are updating from 3.1.10.10.05 (orprevious), then perform all Post-Update Steps listed here.
1 ImportantInformation for ALL Users: Release 3.1.10.08.00 and future releasessupport the Next Gen UI only.
2 Requiredfor ALL Users who are updating from 3.1.10.10.05 (or Previous): Use theVermont Systems Database Utilities.exe to Truncate the Bi file for both theLIVE and DEMO databases.
· In Windows, go to Start • All Programs • VSI3 • DB_Utilities.
· Select Truncate Bi and click Next.
· Select Progress 11.7.
· Click Browse and browse to your LIVE Database File.
· Click Process.
· Click Next when the process completes.
· Opt to Run Another Utility and repeat these steps for yourDEMO database file.
3 Requiredfor ALL Users who are updating from 3.1.10.10.05 (or Previous): In OpenEdge Explorer 11.7.5: Restartthe RecTrac Live and Demo databases.
4 Requiredfor ALL Users who are updating from 3.1.10.10.05: In OpenEdge Explorer 11.7.5: Restartall AppServer and WebSpeed brokers.
5 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
6 Requiredfor ALL Users:Verify the Vermont Systems Event Timer is running. On your servers, go toServices. At the top, you should see "(VSI) Event Timer." Ensure theService running.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
3.1.10.13.02 Post-Update Steps
Note: If you are updating from a version of 3.1.10.13(3.1.10.13.00, 3.1.10.13.01) to 3.1.10.13.02, then skip to Post-Update Step5. If you are updating from 3.1.10.12.01 (or previous), then perform allPost-Update Steps listed here.
1 ImportantInformation for ALL Users: Release 3.1.10.08.00 and future releasessupport the Next Gen UI only.
2 Requiredfor ALL Users who are updating from 3.1.10.12.01 (or Previous): Use theVermont Systems Database Utilities.exe to Truncate the Bi file for both theLIVE and DEMO databases.
· In Windows, go to Start • All Programs • VSI3 • DB_Utilities.
· Select Truncate Bi and click Next.
· Select Progress 11.7.
· Click Browse and browse to your LIVE Database File.
· Click Process.
· Click Next when the process completes.
· Opt to Run Another Utility and repeat these steps for yourDEMO database file.
3 Requiredfor ALL Users who are updating from 3.1.10.12.01 (or Previous): In OpenEdge Explorer 11.7.5: Restartthe RecTrac Live and Demo databases.
4 Requiredfor ALL Users who are updating from 3.1.10.12.01 (or Previous): In OpenEdge Explorer 11.7.5: Restartall AppServer and WebSpeed brokers.
5 Requiredfor ALL Users: EnsureTomcat is running. On your servers, go to Services. Scroll down the list andfind "Apache Tomcat." Ensure the Service running. If not, right-clickand select "Start."
6 Requiredfor ALL Users: Verifythe Vermont Systems Event Timer is running. On your servers, go to Services. Atthe top, you should see "(VSI) Event Timer." Ensure the Servicerunning.
If the service is not running, navigate to OpenEdgeExplorer and restart the EVENTlive AppServer. Afterwards, verify in Servicesthat the (VSI) Event Timer is running.
If the Vermont Systems Event Timer is running, in RecTracScheduled Events Management, verify that scheduled events are running when theyshould (i.e., the Scheduled Program Business/EmailQueue.r should run everyminute or two based on configuration).
Appendix A – Copying the Live Database to Demo
For training purposes, you may want to copy your livedatabase files to the DEMO directory and have it initialized to the Demodatabase. The Refresh utility provides that functionality without requiring ashutdown of your Live database.
Note: In all instances of <x>:\vsi\..., <x>refers to the mapped partition on which RecTrac is installed. For example:c:\VSI3\RecTrac\Data\LIVE
Note: Refresh has to be run on your RecTrac databaseserver.
Running the Refresh Utility in On Demand Mode
The Refresh utility primarilywas designed to automate the "copy live to demo" process for trainingpurposes. When used in this capacity, the utility will run the TrainingDatabase Init/Restore program automatically.
1 On the RecTrac database server, launchRefresh. In Windows go to Start • All Programs • VSI3 • DB_Utilities.Right-click and choose Run as Administrator, if the option exists.
2 Read the message on the Welcome tothe Database Utilities screen and click Next. You will proceed tothe Database Utilities program selection screen.
3 Select the Refresh Databaseradio set and click Next>. You will proceed to the Refresh Databasescreen.
4 Accept the default Database Name (RecTrac)and toggle On Demand as the Restore Type. This option performs aProgress online backup of the source database prior to the restore. This willensure that your target database is as up to date as possible. However onlinebackups can be resource-intensive and can take some time to complete. End usersmay notice a temporary drop in performance while the backup is being performed.
Note: When an ON DEMAND restore is utilized, an onlinebackup is made of the SOURCE database. This online backup will be kept in theVSI\backup folder until the next time an ON DEMAND refresh is run, at whichtime it will be overwritten with the new backup.
5 Click the Browse button andselect your RecTrac structure file (rectrac.st). By default, the structure fileis located in <x>:\VSI3\RecTrac\Data\LIVE
6 Click the Browse button andselect your RecTrac database (rectrac.db). By default, the database file islocated in <x>:\VSI3\RecTrac\Data\LIVE
Note: Never change the name of your database without beinginstructed to do so by a Vermont Systems Representative (i.e. if you'rerestoring a RecTrac database, do not select FinTrac). Changing a database namewithout appropriate planning and implementation can have unexpected results.
7 Click Next>. You willproceed to the Refresh Location screen.
8 Accept the default location(<x>:\VSI3\RecTrac\Data\Demo, where <x> is the drive partition onwhich RecTrac is installed) or click the Browse button to select analternate destination, if desired.
Note: If there is a database present in this directory, itmust have the same name as the intended target. For example: You are restoringa RecTrac database (rectrac.db), and the directory you choose has a database init. The database in the directory you choose must be rectrac.db and not someother database name, such as fintrac.db.
9 Click Next>. You willcontinue to the Options screen.
10 Acceptthe Default options on this screen.
11 Initialize Demo. This restores the database inDemo/Training mode. The utility runs the Training Database Init program on thetarget database automatically when the restore is complete but before thedatabase and AppServers are started.
12 RecTrac and WebTrac Password Options: These options will set the passwordfor all User IDs in the database to demo. Passwords in RecTrac 3.1 arecase-sensitive.
13 Clear all HH and FM info? Select this option if you would liketo mask last names for Households and Family Members when the database isinitialized.
Thisoption changes the last name for a Household (and family members) to the beginningletter of the Primary Guardian's/Sponsor's Last Name and random number. Addressand phone number information is deleted as well.
ForExample: With this toggle enabled, the last name of the Penny Lane household(and all Family Members) would become something like L12300. Address and phonenumber data will be deleted from the household.
14 Skip interface parameter clear?: Select this option to avoid deletingall interface parameters from the Demo database. This is not recommended.
15 Tenants: Accept the default VermontSystems entry, unless you are a Vermont Systems-Hosted customer.
Note: If you are a Vermont Systems-Hosted customer,contact Vermont Systems Support for your Tenant name.
17 Click Next>. You willcontinue to the Confirmation screen.
18 Determine whether you wish to createan input file for refresh automation. The recommended option is to leave thistoggle de-selected when refreshing On Demand.
Note: Input files should be created only if you areperforming Refresh as a Scheduled Task in Windows.
19 Confirmedthe settings are accurate and click Process. The Refresh utility willrun.
Bepatient! Depending on the size of your database, this process may take a fewminutes to complete. Processes will be displayed in a DOS window. Additionally,the utility will present you with a message similar to the following:
20 At completion, click Next and Finish.
21Select Yes whenasked to Run Another Utility. Click Done.
22Select UpdateInterface Parameters and then click Next.
23Click Browse,locate your \DEMO\RecTrac.db and then click Open.
24Click Process.
25Click Next. SelectNo to Run Another Utility. Click Done.
26 (Optional)Browse to yourdefault logs directory (i.e. \VSI3\logs), if desired, to review the log file (V3_Utilities.log)that details the processes which were run.
Additional Notes
As a byproduct of running the Refresh.exe program, thefollowing profiles are unlinked automatically from Profile Hierarchy:
· Backup profiles - To ensure valid LIVE backups are notoverwritten
· Credit Card profiles - To ensure that credit cards are notprocessed during demo sales.
· Email profiles - To ensure that emails are not sent to customersas a result of running some program in Demo, such as Installment Billing,Statements, etc….
Appendix B:Determine Your VIC Version
To determine your VIC Version, click the Support icon nearthe bottom of the sidebar. Version information is displayed as shown below.This image is an EXAMPLE only andmay not reflect the current VIC Version.
Manually Determine Your VIC Version
Refer to the following steps in the event you want tomanually determine/verify the version of VIC you are currently running on aparticular workstation.
1 On the workstation for which you wishto verify VIC version, start the Windows Task Manager.
2 Click the Processes tab.
3 Scroll down to VICService.exe.Highlight/select it, right-click and choose Open File Location. WindowsExplorer will launch.
4 In Windows Explorer, highlight/selectVICService.exe, right-click and select Properties. The VICService.exeProperties dialog will open.
5 Click the Details tab. Theproduct version will be listed.
6 Click OK to close theProperties window.
7 If you are using VIC as a Service onlyon this workstation, exit back to the desktop. If you are also running/usingVIC as an EXE, continue to the next step below.
8 Highlight/select VICexe.exe,right-click and select Properties. The VICService.exe Properties dialogwill open.
9 Click the Details tab. Theproduct version will be listed.
10 Verify that the product version of theService and EXE match.
11 Click OK to exit theProsperities dialog and exit back to the desktop.
Note: VIC Admin Service and VIC EXE versions should alwaysbe in synch. In the event of a product version mismatch, contact VermontSystems Support for assistance.
Appendix C: Howto Contact Vermont Systems
Toll-Free Customer Support: (877)883-8757 Monday-Friday
08:00am–08:00pmEastern Time
Weekend hoursand after-hours weekday available at extra cost
Our Website www.vermontsystems.com/
Login usingyour Vermont Systems ID & create a support ticket
Sales: (877)883-8757 or sales@vermontsystems.com
Mailing Address: 12Market Place
Essex Junction,Vermont 05452
USA
FAX: (802)879-5368
Contact Vermont Systems Supportfor the current login or refer to Knowledge Base entry 1516.