EPM System Security Migration and Upgrade Considerations

When migrating Essbase from Essbase native security to EPM System security, users that do not successfully migrate are retained in the Essbase security file.

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. (The sequence ID is incremented each time Essbase is externalized.) This file, which is located in the ARBORPATH/bin directory, contains the following information:

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). During migration to Shared Services, if a user has different access levels for two databases in the same application, the user is given the more restrictive access level for both databases.

When migrating Shared Services users with the option to have user passwords automatically generated, those user names and passwords are written to a text file named MigratedUsersPassword.txt, which is located in the ARBORPATH/bin directory. If the Administrator designated a specific password for the migrated users, the password is not listed in the file. This file is created when performing an upgrade or migration.