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.
- Download the tool and use the
lcmexport
commands to export single or multiple applications from source to a zip file. - Use the
lcmimport
command to import single or multiple applications from a zip file to Oracle Essbase.
- Create a new OCI Identity and Access Management (IAM) or Oracle Identity Cloud Service (IDCS) application. See Create a Confidential Identity Application.
- Configure your IAM or IDCS application to point to the same external security provider you used in Oracle Analytics Cloud.
- 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. - Manually re-create, in the new IAM or IDCS instance, any non-federated users (IAM or IDCS local users) that you had in the source instance. This is necessary if you want to use Essbase tools like CLI, MaxL, or REST API.
- 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.