Manage Multiple Essbase 21c Servers in Shared Services and Administration Services

Here you can learn how to manage multiple Essbase instances in Shared Services and Essbase Administration Services (EAS Lite).

Optionally, if needed for your site's Essbase and identity provider configuration, you can:

register multiple Essbase servers within one Shared Services instance
manage all Essbase servers together in Essbase Administration Services (EAS Lite)

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 in this configuration, select one of the following workflows.

Install Essbase 21c for the first time. See Install Oracle Essbase.
Stop Essbase services. See Stop, Start, and Check Servers.
If you are using a base installation of Essbase 21.1 or 21.2, use OPatch tool to upgrade to at least the 21.2.1.0.0 patch. See Patch and Restore. If you are using 21.3 or higher, there is no need to apply a patch.
Run configuration to register multiple Essbase servers with Shared Services and EAS Lite (instructions below).
Optionally, set up Essbase to access all servers from one centralized Smart View URL. See Access Multiple Essbase Servers From Smart View.

If you are using a base installation of Essbase 21.1 or 21.2, back up your existing applications. See 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.
Stop Essbase services. See Stop, Start, and Check Servers.
If you are using a base installation of Essbase 21.1 or 21.2, use OPatch tool to apply the 21.2.1.0.0 patch. See Patch and Restore. If you are using 21.3 or higher, there is no need to apply a patch.
Run configuration to register multiple Essbase servers with Shared Services and EAS Lite (instructions below).
Optionally, set up Essbase to access all 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 in your selected workflow above, repeating it for all Essbase server instances you will use.
In your first Essbase server installation, navigate to <Oracle_Home>/essbase/bin and run the configuration tool, config.sh (or config.bat). See 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 LCM import.

Notes

If you have registered multiple Essbase instances with Shared Services using Release 21.2.x or 21.3.x, and you want to rename them -- for example, if you want to create custom names to use instead of EssbaseCluster-1, EssbaseCluster-2, etc, then you must upgrade to Release 21.4 and reconfigure each instance using the Essbase deployment configuration tool, config.sh (or config.bat) in <Oracle_Home>/essbase/bin. In the Identity Provider screen of the configuration tool, you can select a custom name to register with Shared Services.
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.

To register multiple Essbase servers with one Essbase Administration Services (EAS Lite), perform these steps.

Follow steps 1-3 in your selected workflow above, repeating it for all Essbase server instances you will use.
In one of your Essbase server installations, navigate to <Oracle_Home>/essbase/bin and run configuration. See Configure Oracle Essbase.
In the configuration page labeled WebLogic Server Ports, select Enable EAS.
Complete the remaining configuration tasks. As a result, EAS Lite will be enabled for use with this Essbase server.
Complete the instructions to access and use EAS Lite. See Use Essbase Administration Services Lite. The following limitations are removed when you use this configuration: inability to add, remove, and connect to additional Essbase servers.
If you are using a secure Essbase port (HTTPS), see Add External Certificates to Essbase.
To add additional Essbase servers to EAS Lite, see Adding Essbase Servers to Enterprise View.
You must use the Discovery URL host specification format:
```
https://wl_managed_server_host:wl_managed_server_port/essbase/agent
```
where

wl_managed_server_host is the WebLogic managed server host name of the Essbase server.

wl_managed_server_port is the WebLogic managed server port of the Essbase server.

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.
If Essbase Administration Services (EAS Lite) is configured, list the components with type ADMIN_SERVICES_WEB_APP.
```
./epmsys_registry.sh view ADMIN_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.