Oracle Cloud Infrastructure Documentation

Enterprise Performance Management

The infrastructure provides a reference architecture to help run Enterprise Performance Management applications on Google Cloud Compute Engine VMs with low-latency connectivity to Oracle Database@Google Cloud (Oracle Exadata Database within Google Cloud).

Enterprise Performance Management (EPM) enables you to adapt quickly to changing business and compliance requirements while reducing risk, improving controls, and delivering faster, more accurate insights to your stakeholders.

The intended audience for this document include cloud architects, administrators of Oracle Database, and Enterprise Performance Management application administrators. Familiarity with Enterprise Performance Management applications, Oracle Database, and Google Cloud services is recommended.

Single Availability Domain

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

Application users access the Enterprise Performance Management application through the EPM Oracle HTTP Server (OHS). The request is resolved by the Windows server application server to Oracle Database. Oracle Databases are protected by Oracle Autonomous Recovery services with zero data loss protection.

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.

This screenshot shows the architecture diagram.

The architecture shown in the preceding diagram includes the following components:

Component Purpose
Oracle EPM OHS The Oracle Enterprise Performance Management OHS tier consists of web servers that run independently on two Compute Engine VMs.
Oracle Enterprise Performance Management Application The Oracle Enterprise Performance Management 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 AI Database@Google Cloud

Oracle AI Database@Google Cloud is a database service that lets you to access OCI managed Oracle Exadata infrastructure inside Google Cloud data centers.

The Oracle Enterprise Performance Management applications read data from and write to Oracle Database(s) in Oracle Exadata Database. You provision an Oracle Exadata Database 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, 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 Cluster 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 Exadata VM Cluster. When you create an 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.

Configuration and Architecture Details for Oracle EPM 11.2.23 Deployment on Google Cloud

EPM Architecture
  • Assign Server Roles to the EPM Applications.
  • Assign application components to the Virtual Machine (VM)s such as shown below:
    • 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:

To create Network Share on Virtual Machine (VM) 1, you can use the following:
  • 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 the required Windows features such as NFS Client.
    • Set hostname and domains.
  • Before launching application VMs, confirm the Domain Controller is online and reachable within the subnet.
  • Install any required Windows features such as NFS Client on application VMs.
  • Run the post-launch scripts on each application VM to check if Domain Controller is reachable and then 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 To install EPM components based on your topology, see Oracle EPM Standard Deployment Guide.
Deployment Difference
  • SSL - Off loader removed.
  • Single OHS front-end.

Learn more

For more information about Oracle Enterprise Performance Management System, see Oracle Enterprise Performance Management System - Standard Deployment Guide.