This architecture shows a cross‑region, highly available deployment of Oracle WebLogic Server on Oracle Cloud Infrastructure (OCI) with database protection and block volume replication.

A DNS (domain name system) resolves client traffic from mywebapp.example.com to the active region’s load balancer public IP address (111.111.111.111 in Region 1 or 222.222.222.222 in Region 2).

Primary OCI Region 1 contains the region1 VCN (virtual cloud network) with 2 subnets:

• wlsociprefix-wls-0.subnet1.region1vcn.oraclevcn.com subnet
  • OCI Load Balancer accepts client traffic from mywebapp.example.com, which resolves in the domain name system (DNS) to 111.111.111.111, and forwards requests to the WebLogic compute instances in this VCN.
  • wlsociprefix_domain (WebLogic Server domain) contains the Admin Server (wlsociprefix_adminserver) and two managed servers (wlsociprefix_server_1 and wlsociprefix_server_2). The load balancer distributes requests to the managed servers, while the Admin Server manages the domain.
  • Primary DB stores application data and receives metadata service (MDS), java message service (JMS), and transaction logs (TLOGS) from the WebLogic domain.
  • OCI Block Volumes (wlsociprefix-data-block-0, wlsociprefix-mw-block-0) attach to the WebLogic compute instances for data and middleware storage and replicate across regions.
  • A dynamic routing gateway (DRG) connects this VCN to the standby region for Oracle Data Guard and block volume replication.
• wlsociprefix-wls-1.subnet1.region1vcn.oraclevcn.com subnet
  • Shares the WebLogic domain components above. The load balancer distributes traffic across instances in both subnets.

Standby OCI Region 2 contains region2 VCN with 2 subnets:

• wlsociprefix-wls-0.subnet2.region2vcn.oraclevcn.com subnet
  • OCI Load Balancer accepts client traffic from mywebapp.example.com when DNS resolves to 222.222.222.222 and forwards requests to standby WebLogic instances.
  • wlsociprefix_domain (WebLogic Server domain) includes an Admin Server (wlsociprefix_adminserver) and two Managed Servers (wlsociprefix_server_1 and wlsociprefix_server_2) standing by to serve traffic on failover.
  • Standby DB receives redo from the primary database by using Oracle Data Guard.
  • OCI Block Volumes replicas provide cross‑region replicas of the primary region’s volumes for rapid recovery.
  • DRG (dynamic routing gateway) links to the primary region’s DRG for Oracle Data Guard transport and block volume replication.
• wlsociprefix-wls-1.subnet2.region2vcn.oraclevcn.com subnet
  • Shares the standby WebLogic domain components above. The load balancer distributes traffic across instances in both subnets upon failover.

Cross‑region connections:

• Oracle Data Guard continuously ships redo from Primary DB in Region 1 to Standby DB in Region 2 by using the DRG‑to‑DRG connectivity.
• OCI Block Volumes performs block volume replication from Region 1 volumes to Region 2 for disaster recovery readiness.