Migrating Essbase to Shared Services

After installation, both Essbase and Administration Services are in native security mode. To use Shared Services, you must migrate to Shared Services security mode. For Essbase, migration is done at the Essbase Server level. Once you have converted to Shared Services security mode,you cannot convert back to native security mode.
Essbase Administration Server can run in Shared Services security mode with Essbase Server running in native security mode. However, if any Essbase Server that you administer from Administration Services Console runs in Shared Services security mode, Essbase Administration Server must also.
To migrate Essbase Server, Essbase Administration Server, and users and groups to Shared Services, use a tool:
Tool
Administration Services
Topic
Converting Essbase Server and Migrating Users to Shared Services
Location
Essbase Administration Services Online Help
Tool
MaxL
Topic
alter system
Location
Essbase Technical Reference

You must be an Essbase Administrator to run a migration. For Essbase Administration Server, if you ran the Oracle's Hyperion® Configuration Utility™ after installation and specified a Shared Services server and login, Essbase Administration Server is converted to Shared Services security mode at that point. 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:
Tool
Administration Services
Topic
Migrating Users to Shared Services
Location
Essbase Administration Services Online Help
Tool
MaxL
Topic
display user,display group,alter user,alter group
Location
Essbase Technical Reference

You must be an Administration Services Administrator to migrate Administration Services users.
Note:
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 once 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). We suggest 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 Shared Services security mode.