Planning a disaster recovery is a significant aspect of any organization. It is useful to protect assets in the event of a mishap. Protecting the application from accidental circumstances is necessary to make the application functions smoothly and stays unhindered in case of disasters.
You might need to install Adeptia Connect in certain disaster recovery or catastrophic failure. Adeptia recommends you to install Adeptia Connect in a disaster recovery environment also.
Both production environment and Disaster Recovery environment are connected through RAID. All the activities created in the Production environment will get automatically updated in the Disaster Recovery environment through RAID.
You must stop all the Adeptia Suite services (Kernel, WebRunner, and Tomcat) in the Disaster Recovery environment since RAID will automatically update all the activities without running the services.
Installing Adeptia Connect in Production Environment
Follow the instructions described here to install Adeptia Connect in the Production Environment.
While installing Adeptia Connect, you need to maintain the replica of the database and shared drives you are using.
Post Installation
If you are setting a disaster recovery environment then you need to use DNS name instead of IP address for 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.
Installing 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.