If Essbase and Administration Services are in Essbase native security mode, you can migrate to EPM System security mode. For Essbase, migration is done at the Essbase Server level. After you have converted to EPM System security mode, you cannot convert back to Essbase native security mode.
Essbase Administration Server can run in EPM System security mode with Essbase Server running in Essbase native security mode. However, if any Essbase Server that you administer from Administration Services Console runs in EPM System security mode, Essbase Administration Server must also.
To migrate Essbase Server, Essbase Administration Server, and users and groups to EPM System security, use a tool:
You must be an Essbase Administrator to run a migration.
For Essbase Administration Server, if you ran Oracle Hyperion Enterprise Performance Management System Configurator after installation and specified a Shared Services server and login, at that point, Essbase Administration Server is converted to EPM System security mode. You can view the Shared Services configuration information in the Essbase Administration Server properties window (Configuration tab). You can then choose to migrate Administration Services users to Shared Services.
To migrate Administration Services users or to remigrate any Essbase users and groups that failed migration, use a tool:
You must be an Administration Services Administrator to migrate Administration Services users.
Before migrating users, groups, and applications to Shared Services, ensure that the NETDELAY and NETRETRYCOUNT configuration settings are high enough to allow the migration to complete. Set NETDELAY to at least 3 hours, possibly more, depending on the size of the security file. Return the settings to their original values after the migration is complete. Specify these settings in the client essbase.cfg file, which you place in the ARBORPATH/bin folder of the client computer from which you launch the migration. For example, if you use Administration Services Console to launch the migration, the client essbase.cfg file must be in the ARBORPATH/bin folder on the computer on which Essbase Administration Server is installed. |
Essbase automatically creates a backup of the security file before and after migration (essbase.bak_preUPM and essbase.bak_postUPM). Oracle suggests that you manually back up these files to a safe location.
The Administration Services Essbase Server Properties window displays information on whether the server is in EPM System security mode.