Tuesday, February 3, 2009

Essbase Application Migration


Here we will see how you can migrate an Essbase application from one server to another using Hyperion Shared Services Console Migration Utility version when two systems are not connected to each other.
We will fist create an application on the target Essbase server and then migrate the application to a file system and finally migrating to the target server.

I have named it MSR_TEST for the demo purpose.

Now lets go to shared services console.

Expand the Essbase server to see the list of all available application.
Also notice the 'File System' menu below essbase.
Select the Application you want to migrate. When you select the application, on the right main window you will notice the list of substitution variable and databases.
If you expand the database, you will see the list of all other artifacts like Outline and rule files.

Check all and click the button Define Migration below. The tabs on the left hand side will inform you about the steps involved.

here we are trying to migrate 'Demo' application. Click next to select the destination.

Now specify the name for the folder you want to create in the file system. Just in case you want to migrate this application to another server connected to the network, you will have to add that Essbase server in the administration services console and then those applications will appear here.

This is displaying the details of the destination selected. Click Next to start the migration process.

If you want to see the status of the migration, launch migration status report.

This report will show all the previously conducted migrations. The first migration is the current one and it is showing 'In Progress'. Click on the refresh button to see the current status.

Our migration has been completed sucessfully.
Now let's see where exactly the files have been saved.

The default directory where files are saved is Hyperion_Home/common/import_export/admin@native_directory.

Just refresh the file system list and you will notice the application 'MSR_TEST' under it. The application migration does not export the cube data to the file system. However while migrating from one Essbase server to another Essbase server, Utility gives you an option to migrate the cube data.
For our workshop, now we will have to copy the entire folder 'MSR_TEST' and transfer it to the same directory of Target server though ftp or pendrive or CD or any other media.
Once you do that, it will appear in the file system.
Select the application 'MSR_TEST' and you will again see the list of artifacts on the main window.
Click on Define Migration button.

click next to select the destination. This time you will only see the list of applications and not the file system as we already have the artifacts in the file system.

Select the application 'MSR_TEST' we created in the EAS (Administrative Services) in th first step for this purpose.
Click next to see the destination options.

Here we get the option to restructure the cube and retain the cube data. I did not tried this as of now hence not 100% sure whether it exports the data. I will try to show that some other time.
Click next to proceed.

Click Execute migration to start.

Launch the migration status report.

Click refresh to get the updated status.

Migration is successful. Lets check whether it appeared in the EAS or not.

Yes, it is all there. But there is no data in the cube.
Let's try to export the data as well.
Right click the cube on the source system which has the data and select export.

You can export the cube data to a file in your system. Provide the path where you want to export and provide the file extn as .bin.

on the message panel below, it will display the status. In our case it is successful.
Now go to the target system cube and right click to select load data. Click on find data file.

Locate the file in the file system tab and select it.

click on Ok to import.

It will display the status as success.
Lets check whether it displays the data or not.
Right click the cube and select 'preview data'.

You can see now that we successfully migrated an application and exported the data also using Migration utility from shared services console.

Manohar Rana