Hyperion Life Cycle Management: A migration tool

Life Cycle Management is a tool that comes loaded with Hyperion Shared Services which can be used to migrate Oracle EPM applications and artifacts from one environment to another.

During the migration using Life Cycle Management (LCM) tool in Hyperion Shared Services, first we export the applications and artifacts from the source environment and then we import them in to the target environment, therefore, we will first perform LCM export.

LCM EXPORT IN SOURCE ENVIRONMENT

While exporting, you could follow any order in terms of application-artifact export, however, I would recommend exporting in the following sequence.

1. Foundation/Shared Services
   1. Source option: leave default
   2. Destination: File System            example: SS_EXPORT_CONTENT
2. Planning/Application name
   1. Destination: File System            example: PLAN_EXPORT_CONTENT
3. Foundation/Calculation Manger (not available in our environment)
   1. Destination: File System            example: CALC_EXPORT_CONTENT
4. EssbaseCluster1/EssbaseCluster1
   1. Destination: File System            example: ESSBASE_EXPORT_CONTENT
5. Report and Analysis/Report and Analysis
   1. Source Option     UNCHECK "export with job output"
   2. Destination: File System            example: RA_EXPORT_CONTENT

 Here are the steps.

1. Log in to Hyperion Shared Services.
2. Under Application Management, expand Application Groups -> Foundation -> Shared Services and double-click Shared Services.
3. Under the Artifact List on the right, expand the Native Directory and choose the artifacts that you want to export. In this case, we can select Groups, Users, EssbaseCluster1, Planning
4. On the left pane, under Application Management, expand Foundation -> Calculation Manager. 
5. On the right, expand Planning and choose the application and artifacts to be exported.
6. Now under Application Management on the left, choose Planning -> Application name (FinSrv in this example). You will see the artifact lists, such as Configuration, Global Artifacts, Plan Type, Relational Data, Security, etc. Select ALL.
7. Under Application Management -> Application Groups, choose EssbaseCluster-1 and double click EssbaseCluster-1 under it. On the right, under Artifact list, Select ALL.



Add caption

8. Reporting and Analysis under Application Management -> Reporting and Analysis.
9. On the right, under Artifact List, expand Repository Objects and choose the ones to be exported. Then expand Security, and select the ones to be exported or select all depending on requirement. Remember to cross check Product Preferences as well. The figure below has everything selected under Repository Objects and Security and since everything could not fit, I have not expanded them. However, if you click the PLUS right before the objects, you will see all the artifacts.
10. Click on DEFINE MIGRATION to start the migration process, and this (following screenshot) is what we will get – the source screen for initiation of migration process. Choose Foundation/Shared Services and click NEXT.
11. On the source screen, like in the following screen, leave the defaults and click NEXT.
12. On the destination screen, give a file name under File System. Your Shared Services artifacts, etc will be exported under this folder/file. Click NEXT.
13. On the Destination options screen, leave the default and click NEXT.
14. We will see the following screen. We can see a green CHECKMARK on the left to Foundation/Shared Services, which means that we have chosen the artifacts under Shared Services that we want to migrate. Lets now go on to Planning by checking the RADIO BUTTON that is to the left of Planning/FinSrv.
15. Click NEXT to start the Migration wizard.
16. Leave the Source Option as default and click NEXT.
17. In the Destination screen, give a file name PLAN_EXPORT_CONTENT under the file system.
18. Leave Defaults on the Destination Options screen and click NEXT.
19. Like in the following screen, choose Foundation/Calculation Manager and click NEXT to start the migration wizard. There are green check marks before Planning/FinSrv as well.
20. On the source options screen, leave the defaults and click NEXT.
21. On the destination options screen, under the file system, give a name CALC_EXPORT_CONTENT and click NEXT.
22. Leave the defaults on the Destination options screen and click NEXT.
23. Now lets start the EssbaseCluster-1 migration process. Choose EssbaseCluster-1/EssbaseCluster-1 in the source screen and hit NEXT.
24. Leave the defaults on the source options screen, and under the Destination screen, enter a file system file name called ESSBASE_EXPORT_CONTENT.
25. Leave default on the Destination Option screen.
26. For Reporting and Analysis migration, choose the radio button on the left of Reporting and Analysis/Reporting and Analysis and click NEXT.
27. On the source options screen, uncheck "EXPORT WITH JOB OUTPUT" and click NEXT.
28. Under Destination screen, enter a file name called RA_EXPORT_CONTENT. Leave defaults under the Destination Options screen.
29. On the Summary Screen, click EXECUTE MIGRATION to execute migration.
30. Click LAUNCH MIGRATION STATUS REPORT in order to view the migration status. Migration STATUS REPORT can also be opened from the menu bar by clicking on Administration -> Migration Status Report.
31. We will see a report page which shows a list of artifacts/ applications that we have migrated from the past in a chronological order.
32. If the status is "IN PROGRESS" it means the migration is in progress. You can click REFRESH at the bottom right. If the migration completes successfully, the status will show COMPLETED. If migration fails due to any reason, we will see FAILED status. If the status is FAILED, we can click on it to get the report as to why the migration failed, like in the following screenshot.

 

FOOD FOR THOUGHT

In order to import the artifacts/applications in the target environment, we will make use of the applications/artifacts that we just exported in the above steps.

Since we have exported the artifacts and application in the FILE SYSTEM, they will be saved under the IMPORT_EXPORT folder in the middleware home. So if we want to see where they are in the source environment, we can go to the Middleware home. The path would be something like D:\Oracle\Middleware\User_projects\epmsystem1\import_export.

Lets look at the contents under import_export folder and we will see folders such as admin@native_directory, etc. The files that we saved during migration will be found here. For example, while doing the Shared Services migration, we had entered a name SS_EXPORT_CONTENT under the file system. So, the file will be available in this folder.

Copy these folders (the exported ones) and paste it in the same folder in the target environment and then we will go ahead with the LCM import process in the target environment.

LCM IMPORT IN TARGET ENVIRONMENT

The steps:

1. Log in to Shared Services.
2. In Shared Services, under Application Management, expand File System. Select CALC_EXPORT. On the right pane with Artifact Lists, Select ALL.
3. One by one, select all the artifacts/applications (that we have exported earlier) on the left and Select ALL on the right.
4. Now click the SELECTED ARTIFACTS tab and you will see a screen similar to the following:
5. Click the DEFINE MIGRATION tab to start the import migration process.
6. On the source screen, select the Shared Services source (File System\SS_EXPORT) and click NEXT.
7. Leave the defaults on the Source Options screen.
8. Leave defaults on the Destination screen as well as the Destination Options screen. Click Next and then it will go back to the source screen again where we will choose the GlobalSubstitutionVariables, as in the following screen.
9. On the source option, destination (EssbaseCluster-1:EssbaseCluster-1), and destination options screens, leave the defaults. Click Next.
10. On the source screen, choose the Planning Application File System (File System\PLAN_EXPORT).
11. On source options, leave the defaults.
12. On the destination screen, select the application that you want to migrate to. For example, if you want to migrate to the application called SAMPLE, you can choose SAMPLE in this case.
13. On the destination options screen, leave the defaults. Click next and it will take you again to the Source screen.
14. Select File System\RA_EXPORT and click NEXT.
15. Source screen, destination screen (Reporting and Analysis: Reporting and Analysis), and destination options screen should have defaults. Click Next to return to source screen again.
16. On the source screen, select the File System Calculation Manager artifacts (File System\CALC_EXPORT). Click NEXT.
17. Source options should be left default and also the destination (Foundation: Calculation Manager) and destination option screens. Click NEXT.
18. Click EXECUTE MIGRATION in the Summary Screen to execute the migration process.
19. If you want to save the migration definition as a file, you can do so by clicking the SAVE MIGRATION DEFINITION tab. It will create an .XML file in the location of your choice.
20. After the migration is executed, we can check the status in the Migration Status Reoport.

 
Foundation/Shared Services
Summary screen before executing migration.
Need to click on EXECUTE MIGRATION tab in order to perform migration. The SAVE MIGRATION DEFINITION saves the file in the location of choice.

 
DataLoad after migration
After successfully exporting application/artifacts from source environment and importing them in the target, we can load data to the Essbase cube.