Description of the Illustration multi_availability_domain_jd_edwards_domain_withCallouts.png

This image is an architectural diagram of the deployment of a JD Edwards EnterpriseOne application across two availability domains while ensuring high availability and disaster recovery.

The architecture consists of a virtual cloud network (VCN) within an Oracle Cloud Infrastructure region. The region is connected to the Internet, the customer's existing network, and a web client. Within the VCN, there are two virtually identical availability domains. The VCN is linked to the region via a NAT gateway, an Internet gateway, and a dynamic routing gateway, which ensures the connectivity of the availability domains. Each availability domain contains a bastion and load balancer.

The administration tier within the availability domain contains Fault Domain. Fault Domain contains provisioning server, deployment server, and development server.

The presentation tier within the availability domain contains Fault Domain 1 and Fault Domain 2. Each Fault Domain contains Java application server, application interface services server, business services server, real-time events server, BI publisher server and application development framework server.

The middle tier within the availability domain contains Fault Domain 1 and Fault Domain 2. Each Fault Domain contains enterprise server.

The database tier within the availability domain contains database server. The database tier for Availability Domain 2 is disabled in this illustration.

The bastion host receives requests through the dynamic routing gateway (DRG) and internet gateway. The DRG is the gateway that connects your on-premises network to your cloud network. To enable communication between the DRG and the customer-premises equipment, use IPSec VPN or Oracle Cloud Infrastructure FastConnect. To access your bastion host from the internet, set up an internet gateway (IGW). An IGW is a software-defined router that provides a path for network traffic from your VCN to the internet. You can access the instances in private subnets over port 22 through the bastion host or the DRG if you have set up an IPSec VPN tunnel between your data center and Oracle Cloud Infrastructure DRG.

There are five numbered callouts on the illustration:
  1. Active-Active components across ADs
  2. Regional subnets across ADs
  3. Load-balancing across ADs
  4. Storage synchronization across ADs
  5. Database DR across ADs
Each callout is described in the surrounding text.