This image shows two Oracle Cloud Infrastructure regions, the Phoenix region and the Ashburn region. The Phoenix region contain two availability domains (AD), AD 1 and AD 2, with a virtual cloud network (VCN) spanning those domains. The Ashburn region contains a single AD, AD 1 with a VCN spanning that AD.

AD 1 and AD 2 contain three private subnets and a Bastion VM. AD 3 is empty in this diagram. In addition to the private subnets, AD 1 also contains a load balancer.

The first private subnet in both AD 1 and AD 2 contains a Siebel AI server. The load balancer in AD 1 distributes traffic to both Siebel AI servers, as necessary.

The second private subnet in both AD 1 and AD 2 contains two Siebel app server instances, a three-node cluster of a Siebel Cloud Gateway, and a Siebel filesystem. The Siebel Cloud Gateway cluster in AD 2 is depicted as inactive in this diagram.

The third private subnets in both AD 1 and AD 2 contains databases, a primary in AD 1 and a standby in AD 2. Traffic between them is protected by a Dataguard sync operation.

External web clients access the region via an Internet Gateway while internal web clients must go through a VPN, then a dynamic routing gateway to the Siebel AI server in the AD 1 private subnet. Object storage is independent of any AD but within the VCN.

The AD in the Ashburn region contains three private subnets and a Bastion VM and load balancer, mirroring the topology of the ADs in the Phoenix region.

The first private subnet contains a Siebel AI server. The load balancer in AD 1 distributes traffic to the Siebel AI servers.

The second private subnet contains two Siebel app server instances, a three-node cluster of a Siebel Cloud Gateway, and a Siebel filesystem.

The third private subnet contains a standby database in AD 2. Traffic between this database and the primary database in the Phoenix regions is protected by an asynchronous Dataguard operation.

Object storage is independent of the AD but within the VCN.