This image is an architecture diagram of the deployment of an Oracle Essbase application in a single instance while ensuring high availability.

OCI Region has a virtual cloud network with the bastion, load balancer, virtual machine, and an autonomous database. The bastion host and load balancer are deployed in a public subnet, and the Oracle Essbase virtual machine (Essbase VM) and Autonomous Database are deployed in a private subnet. The internet gateway connects the on-premises network to the cloud network and the NAT Gateway connects to the internet cloud.

Oracle Services Network includes a Resource Manager, OCI Identity and Access Management, OCI Object Storage, and a SAN with a Config Volume and a Data Volume. There is two-way communication between OCI Identity and Access Management and the SAN. The Bastion Host connects to the Resource Manager.

The following are the connections for the Essbase VM:

The load balancer host receives requests from servers outside of Oracle Cloud through the internet gateway with HTTPS/443 and sends information to the Essbase VM in the private subnet with HTTPS/443
The Bastion Host is connected to the Essbase VM through SSH/22
Information flows from the Essbase VM to the NAT Gateway and Internet Cloud
Information flows from the Essbase VM to the autonomous database through tcp/1521
Information flows from the Essbase VM to OCI Object Storage, OCI Identity and Access Management, and SAN