Deploy Essbase from Marketplace for Federated Cubes

To implement a federated cube, you must deploy Essbase according to specific requirements.

Prerequisites

These instructions assume you have already done the following, as a domain administrator on Oracle Cloud Infrastructure:

• Created a compartment, dynamic group, and policy on the Oracle Cloud Infrastructure tenancy, as described in Before You Begin with Oracle Essbase.

• Created a vault for encryption keys and secrets on the Oracle Cloud Infrastructure tenancy, as described in Create Vault, Secrets, and Encrypt Values.

• Created a confidential application and an initial Essbase system administrator on the Oracle Cloud Infrastructure tenancy, as described in Set Up Essbase Access in Identity Cloud Service. Be sure to save the application's client secret, as well as the Essbase administrator password, in the vault.

• Provisioned an Autonomous AI Lakehouse Serverless as described in Provision Autonomous AI Lakehouse for Federated Cubes. Be sure to save the Database administrator's password in the vault.

  Note:

  You can provision Autonomous AI Lakehouse during the Essbase deployment.

Instructions

From the Marketplace on Oracle Cloud Infrastructure, deploy an Essbase stack to the same tenancy where you have provisioned (or will provision) Autonomous AI Lakehouse.

Follow the instructions in Create Stack, but while completing those steps,

1. If you already provisioned Autonomous AI Lakehouse Serverless previously, ensure that it is up and running first.

2. In the Essbase Instance screen, change the Catalog Storage Type to Object Storage Bucket. This step is mandatory for federated cubes.

   Note:

   • You cannot change Catalog Storage Type back to Local File system after deployment.
   • Any Essbase jobs that require read/write access to files in the Essbase catalog will search for them in (or export them to) the OCI object storage bucket associated with the Essbase stack on OCI.
   • For more information, see Specify Files in a Catalog Path.
3. In the Database Configuration screen, select how you want to configure Autonomous AI Lakehouse Serverless with Essbase. Essbase will use this database as the repository for its RCU schemas.

   1. If you want to provision Autonomous AI Lakehouse Serverless during this Essbase deployment, click Show Advanced Database Options, and from Choose a database workload type, select Autonomous AI Lakehouse.

   2. Or, you can select Use Existing Database to use a previously provisioned Autonomous AI Lakehouse Serverless.

4. Use a vault in the Identity & Security section of OCI Console to encrypt and save the Autonomous AI Database administrator password. Refer to Create Vault, Secrets, and Encrypt Values.

5. Complete the rest of the instructions in Deploy Essbase.

After Essbase Deployment - What's Next?

In the same Autonomous AI Lakehouse that is the repository database for Essbase, you will need to do the following:

• Create a Schema for Federated Cubes. No other database instance or type can be used for this schema.
• Identify the Pivot Dimension and Set up the Fact Table. No other database instance or type can be used for the fact table.

• An administrator with SSH access to the Essbase instance on OCI must set up credentials by running the ./configure-dbms-writeback.sh script. You only need to run the script once per database schema in Autonomous AI Lakehouse. Refer to Set up Credentials for Federated Cubes.