1. Essbase Stack Deployment on Oracle Cloud Infrastructure
  2. Migrate Applications and Users
  3. Migrate Essbase Cloud Service Applications and Users
  4. Prepare to Migrate Cloud Service Applications and Users

Prepare to Migrate Cloud Service Applications and Users

Here are some considerations and requirements when migrating cloud service applications from Oracle Analytics Cloud - Essbase.

You can use the Essbase command-line tool (CLI) to migrate your source application and artifacts across Oracle Analytics Cloud - Essbase deployments and releases. This is used to migrate applications one-at-a-time.

You can use Migration Utility tool to migrate multiple applications, artifacts, and users at one time, across Essbase cloud services.

  • If you're migrating across Essbase cloud deployments and releases, from v17.3.3 (or earlier), use the scripts for migrating to Essbase. See Scripts for Administration Tasks. This also applies to export and import of provisioned application roles and scripts.

  • Restoring an application or database from a prior backup, after the application or database was re-created using LCM import, isn't supported.

  • Global variables, email configuration settings, and file scanner settings must be set on the target instance before using any of the migration tools.
  • Oracle Identity Cloud Service roles aren't supported in Essbase.
  • After migration from Oracle Analytics Cloud - Essbase, Identity Cloud Service provisioning doesn't continue to be honored. However, Essbase server/application level role assignments are migrated.
  • All Identity Cloud Service users and groups listed in the Security provisioning page in the Essbase web interface can be provisioned with one of the Essbase roles: User, Power User, and Service Administrator.
  • Migration Utility can migrate users and groups from embedded LDAP (or from Identity Cloud Service) to Identity Cloud Service in addition to all Essbase applications.
  • If you're migrating users and groups from an LDAP source to an Essbase instance, Identity Cloud Service doesn't support nested groups. Therefore, group associations to other parent groups, from an LDAP source instance, aren't migrated to Identity Cloud Service targets, when using Migration Utility.
  • Any users or groups that exist with the same name in the target environment as in the source environment, aren't updated in the target.
  • To run Essbase CLI or Migration Utility, use the Identity Cloud Service user that you provisioned to be the initial Essbase Service Administrator during the Essbase deployment and setup.
  • When you run Migration utility for SSL connection, include the host (-Dhttps.proxyHost) and port (-Dhttps.proxyPort) proxy settings in the command line.

The required user roles are as follows:

  • For exporting: Application manager for the application created. In addition, the following roles can use LCM utility and CLI tool: Service Administrator for all applications; Power User for all applications created by the Power User.
  • For importing: Power User or Service Administrator, for creating new applications during import. If you use the Power User role, then the target applications are owned by the Power User used in the migration.