This document describes the additional steps needed to get Aptify Web operational after a 5.5.3 database is restored from Server A to Server B. A typical use case is when implementation team restores the Conversion instance to the TEST/UAT instance multiple times throughout the project life-cycle.
Info
These instructions or use case assume that both source and the destination environments are fully functional before coping the database from source to destination as far as Windows Client and Aptify Web and both environments are on 5.5.3.
Backup the source database and restore it on the destination database using SSMS.
Copy the AptifyWeb553 folder from the source IIS environment to the destination IIS environment.
Only perform this step if absolutely needed.
Please note that usually this step won't be needed. It is only required if JavaScript files have changed or edited which is unlikely in a typical implementation. If you are skipping this step, please proceed directly to Step 7.
- Open/edit AptifyWeb553 folder > AptifyServicesAPI > web.config. Update the URL to match the new environment at 4 places as shown below.
- Open/edit AptifyWeb553 folder > Aptify > script > Aptify > configuration > Aptify.Framework.Configuration.External.js. Update the URL to match the new environment at 3 places as shown below.
- Open/edit AptifyWeb553 folder > Aptify > web.config. Update the database name to match the new environment at 1 place as shown below.
- Open/edit AptifyWeb553 folder > Aptify > ErrorContent > Error.txt. Update the URL to match the new environment at 1 place as shown below.
- Restore or import the Aptify Licenses as needed for the destination database/environment.
- Go to Users Administration and add back the ebizuser and aptifyuser and make sure that they are active and reapply all settings by finishing the User Administration wizard.
- Open Aptify > Web Services > Authentication Providers. Create an All View and Edit #2 Domain User and #6 Domain User (with container) to reflect the new server.
