Setting up a test intranet environment to run parallel with your production environment provides the following benefits:
- Test out upgrades or patches prior to applying these updates to production
- Test out new features or functionality changes prior to pushing the changes live
- Allows for pilot testing with select user groups (depending on the change)
- Avoids unwanted surprises in your Production environment (Requires environments to be configured identically)
It's possible to set up a test environment on the same server as the production installation. However, this can cause problems for upgrades and serves as a potential for your production installation to become contaminated with test data. As a result, this is not recommended.
However, if you must set up a test environment on the same server as your production installation, contact Support for assistance before proceeding.
To set up a test environment on a separate server from your production environment:
- Set up the test server and complete the installation as per Intranet Connections Installation Guide article
- When prompted, use the same serial number as your current production environment
- Do not configure this intranet
- Stop Lucee and World Wide Web Publishing services on the test server
- Copy C:\inetpub\wwwroot\intranet from the production server to C:\inetpub\wwwroot\ on the test server overwriting the existing files
- Backup your production database for Intranet Connections (review the Backup the Intranet article)
- Restore your production database for Intranet Connections to the new test Intranet Connections database overwriting the existing database (review the Restore the Intranet article)
- Restart World Wide Web Publishing and Lucee services (in order)
- Log into the test intranet
Add a message box widget to the home page of the test site to denote it as a test site. This also serves as a test to ensure everything is configured correctly and there is no cross-contamination of data between production and test servers.