Migrate an Essbase 11g On-Premises Application Using LCM Utility

Use the Life Cycle Management (LCM) standalone utility to migrate Essbase 11g On-Premise applications from versions 11.1.2.3.0nn, 11.1.2.4.0nn, 11.1.2.4.5nn, 12.2.1, and later.

The workflow to migrate using the LCM utility is as follows:

Download the LCM utility: In the Essbase web interface, click Console, expand Command Line Tools, and download the Life Cycle Management utility (EssbaseLCMUtility.zip). The downloaded utility must be copied to and run on the same machine as the Essbase 11g On-Premise or 12.2.1 installation, for Enterprise Performance Management (EPM) roles to be exported.
Set up the LCM utility: In the uncompressed downloaded file, run EssbaseLCM.bat (Windows) or EssbaseLCM.sh (Linux), based on the platform on which you want to run the utility.
Run the export: To export each Essbase 11g On-Premise or 12.2.1 application and its artifacts to the specified .zip file, use the LCM utility with the parameters below, and run the export command.
At the LCM utility command prompt, enter the following command syntax to export the application to a .zip file:
```
export -server <hostname> <port> -user username -password password -application appname -zipFile zipfilename [-nodata] [-include-server-level] -exportepmroles [-generateartifactlist]
```
Specify these options:

-exportepmroles : (optional) Export Enterprise Performance Management (EPM) roles

-include-server-level : (optional) If you want to include server-level artifacts, such as server-level substitution variables or server-level roles

-generateartifactlist : (optional) Generate artifact list

For example:
```
EssbaseLCM.sh export -server localhost:1423 -user admin -password password -application Sample -zipfile Sample.zip -include-server-level -exportepmroles -generateartifactlist
```
This export additional artifacts: user and group server-level roles, application-level roles, calculations, and filter associations.
Run the import: To import the application, use the Essbase command-line tool (CLI) to upload the .zip file to target application.
The syntax for the CLI lcmimport command is as follows:
```
lcmImport [-verbose] -zipfilename filename [-overwrite] [-targetappName targetApplicationName] [-artifactlist artifactList]
```
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.

Roles are set only if the users are available in Oracle Identity Cloud Service. You can override default role mapping by changing the mapping in CSSMappings.xml provided with LCM utility.
Upgrade Aggregate Storage Cube outline version: After import of Aggregate Storage Cube applications, the outline must be converted to Unicode using ESSCMDQ. See Upgrade Aggregate Storage Cube Outline Version.
Validate: Log in to the Essbase web interface to see the application and cube on the Applications page.