When using the default deployment option, Essbase and Administration Services are deployed in EPM System security mode.
After configuring Administration Services for EPM System security mode, you must migrate Essbase Administration Server users to Shared Services.
To use EPM System security for Essbase deployments that are in Essbase native security mode, you must migrate any Essbase Server applications and any existing Essbase users and groups to Shared Services, as described in this topic.
Once converted, Essbase Administration Servers and Essbase Servers cannot be converted back to native security mode. When a server runs in EPM System security mode, you use the Shared Services Console to perform all user management tasks.
When you convert Essbase Server, all native Essbase users and groups that do not already exist in an external authentication directory are converted to native Shared Services users and groups in the native Shared Services user directory and are given equivalent roles. Any externally authenticated users are registered with Shared Services but are still stored in their original authentication directory. Users that do not successfully migrate are retained in the Essbase security file (essbase.sec).
If a user’s database permissions changed during migration to Shared Services, information is written to a text file named AccessModifiedUsers_n.txt, where n represents the sequence id for the instance of Essbase that is registered with Shared Services. This file is located in the ARBORPATH/bin directory.
Applications are also registered with Shared Services during this process. For more information about this automatic user migration process, see the Oracle Essbase Database Administrator's Guide.
You must be an Essbase Administrator to convert the server. Also, Essbase Administration Server must be running in EPM System security mode when you convert Essbase Server.
To convert an Essbase Server to EPM System security mode:
From Enterprise View or a custom view, under the Essbase Server node, select the Security node.
Right-click and select Externalize users.
At the confirmation prompt, click Yes to proceed.
Note:
Once converted, the server cannot be converted back to native mode.
In the Conversion Settings dialog box, specify server and port information for an Essbase Administration Server.
Specify how passwords should be created for those users who will be created as native Shared Services users.
Click OK to start the conversion.
If necessary, re-migrate users and groups that failed the initial migration using the Externalize Users Wizard.
“Migrating Essbase to EPM System Security” topic in the “User Management and Security in EPM System Security Mode” chapter in the Oracle Essbase Database Administrator's Guide
alter system (MaxL) in the Oracle Essbase Technical Reference