Before You Begin

For a detailed description of all the architectural options and the design considerations, see Design the infrastructure to deploy Oracle Enterprise Performance Management in the cloud.

In this architecture, applications and databases are deployed in a single Google Cloud zone within the same Google Cloud region.

Application users access the EPM application through the EPM Oracle HTTP Server (OHS). The request is resolved by the Windows server application server to the Oracle Database.

Oracle Databases are protected by Oracle Autonomous Recovery services with zero data loss protection.

The architecture in the preceding diagram includes the following components

Table 4-1 Overview of Architecture and it's components

Component	Purpose
Oracle EPM OHS	The Oracle EPM OHS tier consists of web servers that run independently on two Compute Engine VMs .
Oracle EPM Application	The Oracle EPM mid tier consists of Windows Server running independently on Compute Engine VMs.
Virtual Private Cloud (VPC) network	All of the Google Cloud resources in the architecture use a single VPC network. The web servers, mid-tier components, and databases are in separate subnets.
Oracle Database@Google Cloud	Oracle Database@Google Cloud is a database service that lets you to access OCI managed Oracle Exadata infrastructure inside Google Cloud data centers. The Oracle EPM applications read data from and write to Oracle databases in Oracle Exadata Database Service. You provision Oracle Exadata Database Service by using Oracle Database@Google Cloud. You use Google Cloud interfaces like the Google Cloud console, the Google Cloud CLI, and APIs to create Exadata Infrastructure instances. Oracle sets up and manages the required compute, storage, and networking infrastructure in a data center within a Google Cloud region on hardware that's dedicated for your project. To optimize the latency between the application and the database, deploy the application in the same zone where you create the Exadata Infrastructure instances.
Exadata Infrastructure instance	The Exadata Infrastructure instance contains two or more physical database servers and three or more storage servers. These servers, which aren't shown in the diagram, are interconnected using a low-latency network fabric. When you create the Exadata Infrastructure instance, you specify the number of database servers and storage servers that must be provisioned.
Exadata VM Clusters	Within the Exadata Infrastructure instance, you create one or more Exadata VM Clusters. For example, you can choose to create and use a separate Exadata VM Cluster to host the databases that are required for each of your business units. Each Exadata VM Cluster contains one or more Oracle Linux VMs that host Oracle Database instances. When you create an Exadata VM Cluster, you specify the following: The number of database servers. The compute, memory, and storage capacity to be allocated to each VM in the cluster. The VPC network that the cluster must connect to. The IP address ranges of the backup and client subnets for the cluster. The VMs within Exadata VM Clusters are not Compute Engine VMs.
Oracle Database instances	You create and manage Oracle Database instances through the Oracle Cloud Infrastructure (OCI) console and other OCI interfaces. Oracle Database software runs on the VMs within the Exadata VM Cluster. When you create the Exadata VM Cluster, you specify the Oracle Grid Infrastructure version and choose the license type. You can either bring your own licenses (BYOL) or opt for the license-included model.

Table 4-2 Configuration and Architecture Details for Oracle EPM 11.2.23 Deployment on Google Cloud

Google Cloud Setup Process	Details
EPM Architecture	Assign Server Roles to the EPM Applications. Assign application components to the Virtual Machine (VM)s, for example: Virtual Machine (VM) 1: Foundation1, OHS1, Calc1, FR1, FCM1, Tax Gov1, HTP1 Virtual Machine (VM) 2: Foundation2, Calc2, FR2, FCM2, Tax Gov2, HTP2 Virtual Machine (VM) 3: HPCM1, Essbase1, HFM1, FDMEE1, Planning1 Virtual Machine (VM )4: HPCM2, Essbase2, HFM2, FDMEE2, Planning2
Set Up a Shared Storage Location	Windows Network Share: How to create Network Share on Virtual Machine (VM) 1: Example 1:: \\VM1\LCMShare$) Example 2: \\<IP Address>\shared_data
Virtual Machine (VM) Provisioning	Determine the number of VMs needed: Four VMs for the EPM Application (same subnet). One VM for Windows Domain Controller (same subnet).
Virtual Machine (VM) Requirements Summary	Virtual Machine (VM) Requirements Five Windows Server 2019+ Datacenter VMs, each with 8vCPUs and 30GB memory. Set up a Windows Domain Controller on one VM, and join Four EPM application VMs to this domain. Ensure the Windows domain user is a member of the "Administrators" group on all EPM VMs. Install the NFS client, mount an NFS share on all four VMs, and verify that it is accessible by the domain user. The Windows Firewall should be disabled or configured per the EPM Configuration guide. User Account Control (UAC) should be disabled.
Domain Requirements	NOTE: All EPM Application VMs must join a Windows Domain. For each application VM, use a start-up script to: Configure DNS to use Domain Controller first, enable and configure RDP Open firewall ports or adjust firewall settings, Enable needed Windows features (like NFS Client) Set hostname/domains. Before launching application VMs, confirm the Domain Controller is online and reachable within the subnet. Install any required Windows features (For example, NFS Client) on application VMs. Run post-launch scripts on each application VM to: check if Domain Controller is reachable, join the VM to the domain using appepm\epmuser, and restart for changes to take effect. Check that all VMs can communicate, domain authentication works, the network share is mounted and accessible, and RDP access is enabled as per policy.
Domain Setup	On the Windows Domain Controller VM, install and configure Active Directory Domain Services. Create a domain. For example, Domain name: APPEPM.
Domain Credentials	Create and configure a user account (for example: appepm\epmuser with a secure password) Join all EPM Application VMs to this domain
Install and Configure	Oracle EPM Standard Deployment Guide to install EPM components, adjusting for your topology.
Deployment Difference	SSL-Offloader removed. Single OHS front-end.