Due to any planned or unplanned event, an application may face a downtime in any form and at any time. This may cause huge data loss and irreversible damage to your business causing a disastrous scenario. ITES industry normally keep business continuity plan that should keep the job running in case of any outage. To address such instance in case of Adeptia Connect, we recommend installation of Adeptia Connect in a disaster recovery environment which ideally will keep the business running in case the production environment is down. This is achieved by constant back of the production data from it's RAID to the RAID of disaster recovery. This creates the copies of all the activities created in the Production environment in the Disaster Recovery environment, protecting the data and application during disaster and keeps the business continuity intact.
To achieve this, you must install another instance of Adeptia connect other than regular production environment. This instance can be termed as Disaster Recovery environment. After you have installed Adeptia Connect in the Production Environment, follow the post installation steps given below:
If you are setting a disaster recovery environment then you need to use DNS name instead of IP address in both front-end (Adeptia Connect) and back-end (Adeptia Suite) applications.
- Clustered Environment
If you have installed Adeptia Connect in a clustered environment then use DNS of the internal load balancer and external load balancer. - Non-Clustered Environment
If you have installed Adeptia Connect in a non-clustered environment then use DNS of Adeptia Suite and Adeptia Connect.
After this, you need to install another instance of Adeptia Connect in Disaster Recovery Environment. Follow the instructions described here to install Adeptia Connect in the Disaster Recovery Environment.
While installing Adeptia Connect, you need to keep in mind the following points.
- Select existing tables option while configuring backend and log database wizard.
- Configure the same mail server parameters that you have specified in the production environment.
- Configure the replicated shared path folder that you have specified in the production environment while enabling clustering.
- Configure the same values in the application.properties file that you have specified in the production environment.
Post Installation
After you have installed Adeptia Connect, stop Kernel, WebRunner, and Tomcat since RAID will automatically update all the activities without running the services.
______________________________________________________________________________________________________________________________
Configuration settings for database and filesystem replication and redundancy.