An Due to any planned or unplanned event, an application may have an unplanned face a downtime in any form and at any time. The inability to keep your application operational during a disaster may result in a This may cause huge data loss and irreversible damage to your business . One solution is to protect your application and data from any planned or unplanned outage. Adeptia recommends you to install 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 and connect production environment and disaster recovery environments through RAID. All the activities created in the Production environment will get automatically updated in the Disaster Recovery environment through RAID. In this way, you can protect your data and application and during disaster, you can continue with your application without any data loss
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.
...
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.
...
- 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.
______________________________________________________________________________________________________________________________
...