Moving to production
Plan and Schedule Production Changes
Once you have successfully tested the new version of aPriori, you can plan your move to production. Schedule the production move for a date and time when you can suspend use of aPriori completely for a period of time. This process typically takes a day, and it is recommended to leave two days in case extra time is needed for unforeseen issues.
Notify all aPriori users about the time-schedule for the move and indicate that the application is unavailable during migration.
The following steps explain how to find the scenarios in the production database that have been updated since the first migration took place. Run this at least two days prior to the production move, and again at the time of the production move. This process minimizes the time for the production move and gives a sense for how long the move takes.
1 Prepare for the production move by importing the upgraded database you migrated previously into a production schema.
IMPORTANT! At this point you still require both the old and the upgraded databases. Therefore, do not import the new database into the same schema as the old!
2 At this point in time all users should stop using aPriori. Any changes made with the old version after this point are lost.
3 The following steps explain how to export the scenarios that have been created or updated since the old database was exported.
• Open the old version
• Select File > Export > Select Scenario(s)
• On the left side of the search box under Time Selection, select From
• Enter the date you last exported the database. (leave the To field empty)
• To find all scenarios created or updated since the chosen date, click the Find button.
• Click on the first scenario to select it, then press CTRL A to select all, then click OK.
4 Save the apriori.scenarios.ap file. The following steps explain how to import the scenarios into the new database.
• Open the new version of aPriori.
• Select File > Import
• Browse to the location you saved the apriori.scenarios.ap file that you exported from the old version. Select the file and click Open.
• This imports those scenarios to the new database and completes the move to the new database.
5 If any VPE changes were made since the initial database export, export those VPEs out of the old version and import them into the new version.
6 If any other changes had been made to the old version such as users or site variables since the initial export, make those same changes in the new version.
7 Once all data in the new database is up to date, disable the old database to ensure no users continue to use it. This can be done by changing the database password or by dropping the database.