Shared Services artifacts include projects, applications, user roles, users, and groups. When you assign access to a user or group in Shared Services, you provision the user or group with a role for an application. See the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide.
Shared Services and Essbase both use the term “application.” Essbase uses “application” to refer to a container for databases. Shared Services uses “application” to refer to an artifact for which you provision users. In this topic, “application” refers to a Shared Services application, unless an Essbase application is specifically stated. In most cases, an Essbase application maps to a Shared Services application, so the distinction is unnecessary.
For Essbase, migration is done at the Essbase Server level. When you migrate an Essbase Server to Shared Services, a Shared Services project is created for the Essbase Server. The project is named Essbase:machineName:EssbaseServer#, where machineName is the Essbase Server computer name and EssbaseServer# is the sequence number. The sequence number for the first Essbase Server that is migrated is 1. When migrating multiple Essbase Servers on the same computer, the sequence number is incremented by 1. Also, if you delete the security file and remigrate an Essbase Server, each successful migration creates a new server project with a new sequence number. You can delete unwanted projects in Shared Services Console.
Essbase automatically creates the following applications within the project and automatically registers the applications with Shared Services:
An application named Essbase:machineName:EssbaseServer#, which is the same name as the Shared Services project. This application, which allows you to specify security at the Essbase Server level, is known as the global Essbase Server application. After migration, you can change the name of the global application and application project in Shared Services by using the alter system MaxL statement with the rename global registration name grammar. See the Oracle Essbase Technical Reference.
A Shared Services application for each Essbase application on the Essbase Server. In Shared Services, if an Essbase application contains multiple databases, the databases must have the same user security access levels. (However, users can have different calculation script and database filters assigned for databases within the same application. See Assigning Database Calculation and Filter Access in Shared Services.)
In the following illustration, the first instance of Essbase:JWARD:1 is the Shared Services project for the first Essbase Server migrated on JWARD. The second instance of Essbase:JWARD:1 is the global Essbase Server application.
Projects Essbase:JWARD:1 ASOsamp DMDemo Demo Essbase Servers:JWARD:1 Sampeast Sample Sample_U Samppart
After you have migrated to Shared Services, when you create an application and database in Essbase, a corresponding Shared Services application is created within the Essbase Server project, and the application is automatically registered with Shared Services.