Although the primary source for the content displayed by Application Server is stored within the InterAction database, the Application Server should be included in your overall disaster recovery plans. The Application Server stores numerous configuration files that your organization has likely customized. Re-creating these files from scratch would be a time-consuming process.
A disaster recovery plan for Application Server should include two components – version control for the configuration files and a full backup of the files.
Using Version Control for the Configuration Files
Version control systems, such as Microsoft Visual SourceSafe, help guard against mistaken changes to the files. In a typical version control system, you must check out the files you want to work on, then check them back in when you are finished making changes.
Checking in a file creates a new version in the system and makes the file on the computer read-only. This helps prevent making changes without properly checking out a file first. If you discover that changes were made in error, you can “roll back” to a previous version.
This sort of system is very useful when working with Application Server configuration files. You can experiment with different settings, while keeping the ability to roll back to an earlier setting. All Application Server configuration files are text files; most version control systems work well with text files and include features that allow comparing and merging the files.
At a minimum, add the following files to the version control system:
- All the files in the directories configured as the IRIS_ETC_DIR and IRIS_TEMPLATES_DIR.
- The InterAction.cfg file.
Backing Up the Application Server
In addition to the version control system, you should perform regular backups of the Application Server. These backups should include all configuration files.
Back up the server on a regular basis, as with the other servers in your organization. Since you will likely change the configuration files frequently during the initial deployment, backup the server more often at first.