Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

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 usually keeps a 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 to address such outages. Therefore, Adeptia also recommends installing Adeptia Connect in a disaster recovery environment which that would ideally will keep the business running in case the main production environment is down. This is achieved by constant back of backing up the production data from itproduction environment's RAID to the RAID of disaster recovery constantly. This creates the copies of helps in copying all the activities created and stored in the Production RAID of the Production environment in 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 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:

...

  • 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.

Image Added

______________________________________________________________________________________________________________________________

...