Connect to Multiple Essbase 26ai Servers in Shared Services

If your site uses multiple Essbase Server instances with Shared Services, you can access them all under one centralized Smart View URL.

If needed for your site's configuration, you can register multiple Essbase Servers within one Shared Services instance.

To configure and manage multiple Essbase Server instances with Shared Services identity provider, you will need to run the configuration tool for each Essbase Server, providing the same EPM_ORACLE_HOME and EPM_ORACLE_INSTANCE variables each time. Optionally, all Essbase Servers can share a centralized Smart View URL.

Note:

The following applies only if you opt for the configuration to enable management of multiple Essbase Servers in one EPM Shared Services instance.

This configuration is supported only for independent deployments (not for Marketplace deployment on OCI).
Filter assignments and LCM operations are not supported from Shared Services Console.
After uninstalling an Essbase Server, you need to clean Essbase entries from the EPM registry. Otherwise, removed EssbaseCluster entries remain in Shared Services Console.

Important: Please read all steps before beginning. If you opt for configuring multiple Essbase Servers with a single Shared Services instance, it requires reconfiguration, and you cannot roll back the patch.

Select a Workflow

To deploy multiple Essbase Servers that share one EPM Shared Services as the identity provider, select whichever of the following workflows is most appropriate for your circumstance.

Install Essbase 26ai for the first time, as described in Install Oracle Essbase.
Stop Essbase services, as described in Stop, Start, and Check Servers.
Run configuration to register multiple Essbase Servers with Shared Services (instructions below).
Optionally, set up Essbase to access all Essbase Servers from one centralized Smart View URL, as described in Access Multiple Essbase Servers From Smart View.

If you are performing an upgrade, back up your existing applications. Refer to Back Up and Restore Essbase.
In addition to the backup, perform an LCM export of the applications so they can be re-imported after the reconfiguration. Refer to LcmExport CLI command (or Export LCM job).
Stop Essbase services as described in Stop, Start, and Check Servers.
Run configuration to register multiple Essbase Servers with Shared Services (instructions below).
Optionally, set up Essbase to access all Essbase Servers from one centralized Smart View URL. See Access Multiple Essbase Servers From Smart View.

To register multiple Essbase Servers with one instance of EPM Shared Services, perform these steps.

Follow steps 1-4 from your Select a Workflow path above (backing up applications, then installing or patching the software for each Essbase Server instance).
In your first Essbase Server installation, navigate to <Oracle_Home>/essbase/bin and run the configuration tool, config.sh (or config.bat). Refer to Configure Oracle Essbase for more information about the tool.
In the configuration page labeled Identity Provider, click Enable EPM Shared Services Identity Provider, and provide the path locations for your EPM system variables EPM_ORACLE_HOME and EPM_ORACLE_INSTANCE.
Optionally (also in the Identity Provider screen), provide a name for the Essbase Server you are registering with Shared Services. If you omit a name, the configuration will name it EssbaseCluster-1 (or EssbaseCluster-n).
Complete the remaining configuration tasks. As a result, the configuration registers your Essbase Server with Shared Services as EssbaseCluster-1 (or as the name you optionally provide). Note: This is a single Essbase Server, rather than an actual cluster.
Run configuration again for the second Essbase Server, providing the same EPM system locations you indicated for the first. As a result, the configuration registers the second Essbase Server with Shared Services as EssbaseCluster-2 (or as the name you optionally provide).
Continue to configure all additional Essbase Servers in the same way.
Re-import all of the applications, using the LcmImport CLI command (or Import LCM job).

Notes

Known Issue: In Shared Services Console, under Application Groups, if you double-click an application name under a de-registered EssbaseCluster, it returns a message EPMLCM-13000: Service currently not available.

Manual Steps to Clean EPM Registry

After uninstalling an Essbase Server, you need to clean Essbase entries from the EPM registry. Otherwise, removed EssbaseCluster entries will remain in Shared Services Console.

To clean the EPM registry, perform these steps.

Navigate to <EPM_ORACLE_INSTANCE>/bin.
List the components with type CLUSTER.
```
./epmsys_registry.sh view CLUSTER
```
Note the cluster IDs of your Essbase Server name (for example, EssbaseCluster-1), and the IDs of its children.

Delete the components with those IDs.

./epmsys_registry.sh deletecomponent \#componentID

For every child component of type APPLICATION, remove the corresponding file by replacing extensions .ESB or .ESBAPP with .instance in the ID.

For example,

Child ID: Sample_EssbaseCluster-1_1.ESBAPP

Child ID: Analytic Servers:EssbaseCluster-1:1.ESB

TYPE: APPLICATION
```
./epmsys_registry.sh removefile SYSTEM9/ESSBASE_PRODUCT/@'Analytic Servers:EssbaseCluster-1:1.instance'
```
TYPE: APPLICATION
```
./epmsys_registry.sh removefile SYSTEM9/ESSBASE_PRODUCT/@'Sample_EssbaseCluster-1_1.instance'
```
List the components with type PROJECT.
```
./epmsys_registry.sh view PROJECT
```

Delete the components with those IDs.

./epmsys_registry.sh deletecomponent \#componentID

List the components with type PROVIDER_SERVICES_WEB_APP.
```
./epmsys_registry.sh view PROVIDER_SERVICES_WEB_APP
```
Note the ID of the component that has an instance_home and localhost_name matching your Essbase instance, and delete that component.
Note the ID of the component that has an instance_home and localhost_name matching your Essbase instance, and delete that component.