Page Comparison

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 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 usually keeps a business continuity plan to address such outages. Therefore, Adeptia also recommends installing 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.

...

environment that would ideally keep the business running in case the main production environment is down. This is achieved by backing up the data from production environment's RAID to the RAID of disaster recovery constantly. This helps in copying all the activities created and stored in the RAID of the Production environment to 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.

Use Select existing tables option while configuring backend and log database wizard.
Use Configure the same mail server parameters that you have configured in specified in the production environment.
Use existing Configure the replicated shared path while folder that you have specified in the production environment while enabling clustering.

Post Installation

If you have installed Adeptia Connect in a non-clustered environment, map IP address of Adeptia Suite and Adeptia Connect to DNS in the properties that you have configured while installing Adeptia Connect.

...

Configure the same values in the application.properties file that you have specified in the production environment.

After you have installed Adeptia Connect, stop Kernel, WebRunner, and Tomcat since RAID will automatically update all the activities without running the services.

Image Added