Simple disaster recovery

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Simple disaster recovery is managed in primary and secondary data center.

In situations that can tolerate periodic planned system outages, stop the primary system, and ensure that all resources are consistent. Then, copy all the configuration data and runtime data from the primary data center to a secondary data center and restore the data in the secondary data center.

In such a setup (see Figure 1), Business Automation Workflow is configured to communicate with Content Platform Engine. The document object operation that case solutions or other applications request stores objects in the Content Platform Engine. The file storage area stores the related objects for the Content Platform Engine. The shared folder shares the information between the Business Automation Workflow clusters and the Content Platform Engine clusters. During the configuration, the host address information or related information is persisted into the configuration data for the engine to use. After the system is restored in the secondary data center, the servers in the secondary data center must use the same configuration data and use the same hostname to configure the host address or related items. The hostnames and directory locations from the primary data center must be available in the secondary data center.

Figure 1. Simple disaster recovery Simple disaster recovery

Guidance for configuring case components in a disaster recovery setup

When you configure a disaster recovery environment for IBM® Business Automation Workflow, you must perform specific Case configuration tasks depending on whether the primary and failover environments share components.

Shared versus Non-Shared Components
  • Content Platform Engine is considered shared when both environments use the same physical application server or database instance.
  • IBM Content Navigator server is considered shared when both environments use the same physical application server or database instance.
Important: If either the Content Platform Engine or IBM Content Navigator server is shared, skip the corresponding configuration tasks that are listed here.

Tasks to run only when the Content Platform Engine is not shared

If the Content Platform Engine is not shared, complete the following tasks by using the Case configuration tool:

  • Configure the case management object stores
  • Configure the Content Platform Engine Gateway Service
    • Run this task only if the Content Platform Engine application server is also not shared
  • Define the default project area
  • Define the target environment
  • Configure Case Integration with IBM Business Automation Workflow

Tasks to run only when the IBM Content Navigator server is not shared

If the IBM Content Navigator server and its application server are not shared, complete the following tasks:

  • Register the IBM Business Automation Workflow plug-in
  • Register the Case Management Services plug-in
  • Register the Case widgets Package
  • Register the IBM Business Automation Workflow Case administration client plug-in
  • Register the project area
  • Register the case monitor widgets package

Restart the IBM Business Automation Workflow server, the IBM Content Navigator server, and the Content Platform Engine server

Remember:
  • Ensure that all configuration tasks are run in the correct environment (primary or failover) based on the shared status of the components.
  • Document the configuration steps and outcomes for future audits and troubleshooting.
  • Validate the disaster recovery setup by performing failover testing to confirm that case functionality behaves as expected.