About a week and a half ago I wrote at a high level about 2 Essbase Cloud Service (EssCS) command line scripts, the Export Utility and Command Line Tool. Another utility in the mix that I didn’t talk about (due to environment constraints) was the Essbase LCM Utility. I finally got my environment set up to use the tool and played around with an export and import today.
On the EssCS homepage, you will see a green icon named “Utilities”. I clicked on this to download the utility.
In the list, it will be the third item. I clicked the down arrow next to “Life Cycle Management”.
After I downloaded and extracted the tool to my favorite utility location, I read the “README.txt”. Below I have highlight some items I thought were key:
· The supported releases of Essbase are 11.1.2.4.0xx, 11.1.2.4.5xx , and 12c EssCS.
· The command and variables to use when exporting a cube.
· The command and variables to use when importing a cube.
Note that there are also details about how to deal with scenarios (workflow and/or sandbox) and partitions. I’m not using these in my example cube, so I won’t be addressing them in this blog post.
The first thing I want to do is export my on-premises (OP) cube to a zip file. I have highlighted that syntax below in the window. Also, I have supplied it to copy and paste for your environment.
EssbaseLCM export –server {servername}:1423 –user {username} –password {password} –application {appname} –zipFile {FileName}.zip
If all goes successfully, you should get a line for each artifact in your application. You can also choose to not import data by adding “-nodata” at the end of the export command.
Note: The parameters given in the command can be in any order, not just the one shown!
Because I’m curious, I opened the zip file to see how it was organized.
I can see there are folders for the various artifacts.
Now to import the application… I tried the import command for a new cube first, but because I already have the cube in my environment, I was given an error and told to use “-overwrite” in my parameters. So, that’s what I did (shown with the yellow box). The command I used for the import was:
EssbaseLCM –server {servername}:1423 –user {username} –password {password} –application {appname} –zipFile {filename}.zip -overwrite
To double-check to make sure it worked, I logged into EssCS, chose my database name, and clicked “Settings”.
In the Properties tab under Basic, I can see that the expected number of members were loaded as well as data. Perfect!
The data is not aggregated, so I thought it would be a good chance to see if my calc scripts came in…Yep! From here I could execute the scripts if I desired.
And I’m done! That was easy enough…
And to take a step further, this is easily something that could be run routinely via a batch (or shell) script. This would be great for backing up your environment, versioning, or simply moving cubes from one environment to another. …And if you were wondering if you can only download from OP, nope, cloud is an option as shown below:
Command Line:
Folder:
RealTriGeek 
For the cloud cube export, I’m a little confused by the command line screenshot. How did you download the cube from the cloud if the -server parameter says localhost? For a second I thought maybe you might be running it directly from the cloud VM, but it doesn’t look like it since your command line prompt points to a Windows path. Would you instead just point it to the public IP of the Essbase cloud server? Thanks!!!
Correct! I was running it from a VM on a Windows box. And you are also correct that you would point it to the IP of the Essbase cloud server.