OpenEdge 11 Migrating to a New Database / Transaction Server
RecTrac 3.1
Table of Contents
Migrating to a New Database/TransactionServer
The Migration process has numerous steps and should beperformed only by someone who has experience and is comfortable with RecTracserver and VIC installation procedures. If you are not comfortable with theprocess, we recommend having Vermont Systems assist with the process.
Note: Server Migration is not covered under the normalsupport contract, so hourly phone rates will apply. Please contact sales@vermontsystems.com for pricing andscheduling. Most 3.1 server migrations can be done by a Vermont Systemsrepresentative in about four (4) hours.
Summary
This document will assist you in migrating a Vermont Systems3.1 product (i.e. RecTrac 3.1) from its existing database/transaction server to a new database/transaction server. The document outlines the steps required for most customers, including possible WebTrac steps that may be needed.
Throughout this document, the term "old server" will refer to your existing/current server. The term "new server"refers to the new server onto which you are moving your Vermont Systems-product database (i.e. RecTrac 3.1).
Note: The following steps outline the recommended procedure for moving a database from one server to another (i.e. old to new).This document uses RecTrac examples (i.e. RecTrac 3.1, data, etc.); however,this document can be used for MainTrac or FinTrac, as well, by substitutingnames from those products (i.e. FinTrac 3.1, etc.).
Before You Proceed
Vermont Systems recommends reading through this entiredocument in order to better understand the processes and scope of workinvolved. Vermont Systems also recommends you settle on a naming solution forthe new server prior to beginning the migration process. You will need theRecTrac install files. These are typically on the Vermont Systems sFTP site(sftp.vermontsystems.com).
Install RecTrac 3.1
Install Progress 11.3/RecTrac 3.1 on the new server. Referto RecTrac 3.1 Live Installations Instructions for assistance, if needed. This document is available in the Downloads section of our website. Downloads • RecTrac 3.1Documents • RecTrac 3.1 Installation and Upgrade Documents.
When installing RecTrac 3.1, Vermont Systems recommends:
· Installing the same version/build of RecTrac 3.1 on both servers.Doing this ensures your programs and data match. For example: if you're runningRecTrac 3.1.05.03 on the old server, install RecTrac 3.1.05.03 on the newserver.
Note: If you opt to install a different version of RecTracon the new server than is running on the old server, additional post migration steps willbe necessary.
If running VIC through an AIA configuration on the RecTracDB server, follow steps in the AIA VIC Configuration 3.1 document. ContactVermont Systems Support for a copy.
Migrate Files
Ensure all users are logged out of RecTrac. On the oldserver, set the Admin service for OpenEdge 11.3 to manual and restart it. This will ensure users cannot a log into RecTrac and access the environment duringthe migration. It also ensures that patrons cannot access WebTrac.
If using an SSL on current server, have your IT departmentmake arrangements to install SSL on new server.
Note: Vermont Systems support does NOT install or move SSLs – This must be done by the customer.
DATA Files and Update of interface parameter
1 Copy the entire <x>:\VermontSystems3\Rectrac\Data\Live folder from the old server to the new server, where<x> is the mapped partition on which \vsi is installed on both servers.Overwrite all files when prompted.
2 On the new server, browse to<x>:\Vermont Systems3\Rectrac\Data\Live Right-click on rectrac.st andopen with Notepad. Verify all paths are correct. Make corrections, ifnecessary.
3 On the new server, repair yourRecTrac 3.1 database using the \Vermont Systems3\Misc\Utilities.exe program.Right-click and run the Utilities.exe as Administrator
4 On the new server, start the LiveDatabase in Open Edge Explorer
5 On the new server, update theRecTrac interface parameter using the \Vermont Systems\Misc\Utilities.exeprogram if migrating to a server with a new name. This step is not necessary ifnew server has same name as old server.
ConfigurationRequired Based on New Server's Name
This document assumes three (3) potential scenarios fornaming your new server. How you choose to name your new server will dictatewhat configuration steps you need to perform on the server and clientworkstations once the migration is complete.
Find the scenario that best reflects the approach you wishto take (or are taking) and follow the instructions.
· Scenario I The new server has a name that is differentfrom the old server (i.e. the old server is named rectrac_server_2008 and thenew server is named rectrac_server_2012).
· Scenario II The new server will have the same name as theold server and is being set up off the domain (i.e. the old server is namedrectrac_server, and the new server is named rectrac_server). The new serverwill not join the domain until the old server is removed from it.)
· Scenario III The new server will have the same name as theold server once production starts but is being set up on the domain using atemporary name (i.e. the old server is named rectrac_server, and the new serverwill be named rectrac_server. Both machines are on the domain, so during setup, the new server has a temporary name, such as rectrac_server_temp).
ScenarioI: New Server's Name Is Different from the Old Server's Name
If your new server has a different name than the old server(i.e. the old server is named rectrac_server_2008 and the new server is namedrectrac_server_2012), then the Interface Parameters and VIC need to be updated.VIC would need to be uninstalled from the each client workstation and thenreinstalled once new server is configured.
Refer to VICInstallation using Windows Installer.
Scenario II: New Server's NameIs Identical to the Old Server's Name
If the new server will have the same name as the old server,you can opt to set up the new server while it is off the domain (i.e. the oldserver is named rectrac_server, and the new server is named rectrac_server).The new server will not join the domain until the old server is removed fromit.
Since you can’t have the same computer name twice on adomain, you might wish to set up your new server off the domain. Doing thisallows you to keep your old server in production while setting up the newserver. When you "make the switch," you remove the old server fromthe domain (thus freeing up its name for use) and add the new server to it.
This makes the transition easier, particularly if the sameinstallation drive and directory is used. VIC would not need to be uninstalledand reinstalled. Client URLs would also stay the same.
ScenarioIII: New Server's Name Will Eventually Be Identical to the Old Server's Name
If the new server will have the same name as the old serveronce production starts, you can opt to set up the new server on the domainusing a temporary name (i.e. the old server is named rectrac_server, and thenew server will be named rectrac_server. Both machines are on the domain, soduring set up, the new server has a temporary name, such asrectrac_server_temp).
Since you can’t have the same computer name twice in adomain, you might wish to set up your new server using a temporary name. Whenyou "make the switch," you remove the old server from the domain(thus freeing up its name for use), and rename the new server (i.e. remove the_temp and name the server rectrac_server).
Mandatory Optionfor Selected Server Migration Scenarios
IF the new server has a new name (Naming Scenario Iabove), you MUST uninstall VIC on all of your client workstations.
Refer to VICInstallation using Windows Installer.
Database Configuration
Once the migration is complete, login to RecTrac
The following must be checked:
· VIC profile (Management Ribbon • System Management •Users/Menu/Profile Management group • Profile Assignments)
· Additional Interface Parameters (i.e. Demo) (Management Ribbon •System Management •Misc Management group)
Install VIC on clients if it was uninstalled earlier
Refer to VICInstallation using Windows Installer
Post Migration Steps for WebTrac
1 If you use WebTrac, follow theappropriate steps in the WebTrac Installation section of the RecTrac 3.1 LiveInstallations Instructions to configure your new server for WebTrac.
Note: WebTrac customers may need to make changes on theirweb server if it was not possible to use the old database server name/IP addressfor the new database server. Some customers may need to edit the webtrac.wscfile to reflect the new server name or IP address. As a general rule, this isnecessary only if Naming Scenario I above was used (new server, new servername).
2 If you use CardConnect as your CreditCard Gateway: Log in to yourHPPv2 on the CardConnect site and ensure thefollowing URLs are correct. Use the CardConnectHosted Payment Page for WebTrac doc, if necessary.
· Return to Website URL
· Webhook url