Migrate Applications Using Command Line Interface

You can use Command-Line Interface (CLI) to migrate source applications and artifacts across Essbase cloud deployments and releases. The utility is used to migrate applications.

The standard migration workflow using the Command Line Interface (CLI) is as follows:
  1. Download the tool and use the lcmexport commands to export single or multiple applications from source to a zip file.
  2. Use the lcmimport command to import single or multiple applications from a zip file to Oracle Essbase.
Use the following workflow when the source deployment is from Oracle Analytics Cloud (either Oracle Cloud Infrastructure or Oracle Cloud Infrastructure Classic) using Oracle Identity Cloud Service Federated Security.
  1. Create a new Identity Cloud Service application. See Create a Confidential Identity Cloud Service Application.
  2. Configure your Identity Cloud Service instance to point to the same external security provider used in Oracle Analytics Cloud.
  3. Download CLI, and using the lcmexport command, export applications from source to a zip file.

    Specify the --include-server-level option to include server-level roles.

    Use option --application to export a single application to a zip file. Use option (case-sensitive) --allApp (or -aa), from Essbase 21.4 and higher, instead of --application, to export all applications to a single zip file. Both options, --application and --allApp, do not support export of users and groups.

  4. Manually re-create, in the new Identity Cloud Service instance, any non-federated users (Identity Cloud Service local users) that you had in the source instance. This is necessary if you want to use tools like CLI, MaxL, or REST API.
  5. Using the CLI lcmimport command, it can accept single-application zip files or multiple-application zip files, to Oracle Essbase.

When partitions exist in the source between a source application or database, and a target application or database, only partitions from the target are exported to the file system. When partitions exist between cubes being migrated, you must import the data source before the data target. Otherwise, partition definitions may not be restored.