Refresh UAT QA Activate Server from Production
2 min
This article details the steps to refresh/restore a UAT/QA server from a Production copy of Activate.
Steps
- Stop Production server Job Service
- Backup the Activate Production Database - once backed up restart the Production Job Service
- Stop the UAT/QA server Job Service, DO NOT restart until specified
- Backup the existing Activate UAT/QA Database just in case this is needed in the future
- Restore the Production Database to UAT/QA server SQL Server
- Run SQL Administrator for UAT/QA Server
- Run the attached SQL script to set up this database as a QA server. This script performs the following steps
- Changes Organisation name to {Current} - TEST
- Changes the name of the current site to Production
- Creates a new site named "Restored from Prod"
- Sets the new SiteID to the current site
- Updates all non-system parameters to be owned by Production so they don't appear to have been modified locally.
- Disables and unpublishes all schedulers
- Disables email approvals
- Optionally sets the SMTP Server to only save emails to the Activate DB.
- Cleans up some old parameters no longer in use.
- Disables all PollWorkflow parameters
- Clears all emails in a pending state
- Terminates all active jobs
- Disables all FileWatcher connectors
- Removes pending effective groups
- Removes pending flags from Service Instances
- Clears expiry dates and ExpiryStarted flags
- Removes future expiry dates on ADCacheMembers
- Change Organisation/Name to reflect it’s a UAT/QA server. (<Company Name> -UAT for example)
- Change Roles/System Roles/Users to subset of test users, if required.
- Configure OverrideUpdatableOU and OverrideEmailAddress, if required
- Configure Master site, if required
- Restart the UAT/QA Job Service
- Recycle the Activate App Pool in IIS
- Monitor the job log to ensure no Production system jobs have been submitted.