Print PreviewThis tutorial contains the following sections:
Click icon to show all screenshots
Note: Alternatively, you can click an individual icon (or image) associated with each step to view (or hide) the screenshot associated with that step.
This tutorial covers a first-time Lifecycle Management migration for Planning 11.1.2 applications. This lifecycle management migration utilizes Shared Services 11.1.2.
Approximately 2 hours.
Lifecycle Management provides a consistent way for Oracle Hyperion Enterprise Performance Management System (EPM System) products to migrate an application, a repository, or individual artifacts across product environments and operating systems.
Artifacts are individual application or repository items; for example, scripts, Web and data forms, rules files, documents, and financial reports. The application and repository artifacts are organized into categories by product.
The Lifecycle Management interface is integrated with Shared Services Console.
In this tutorial, you perform a first-time migration with a Planning 11.1.2 application and Shared Services 11.1.2 from a source environment to a destination environment.
The Planning application consists of artifacts from various products. For example:
Because Planning application artifacts span multiple products, you must migrate the artifacts from each product as they relate to the Planning application. For the list of supported artifacts that are available for migration with the Shared Services Lifecycle Management functionality, refer to the Oracle® Hyperion Enterprise Performance Management System Lifecycle Management Guide.
The following is a list of software requirements:
Oracle Hyperion Planning Plus 11.1.2 includes the following components:
Relational storage database(s) are required in the installation and configuration of Oracle Hyperion Planning Plus 11.1.2. This tutorial requires a a relational storage associated with a Planning data source. See the Oracle Hyperion EPM System Release 11.1.2 - Start Here: Installation Documents and Readmes.
Before starting this tutorial, you should:
1 . |
Have Planning Administrator and Application Creator access to a working installation of Oracle Hyperion Planning 11.1.2, in both source and destination environments. The source and destination environments must use the same release number.
|
|---|---|
2 . |
Have administrator access to Shared Services 11.1.2, in both source and destination environments.
|
3 . |
Have Lifecycle Management Administrator access to Lifecycle Management 11.1.2, in both source and destination environments.
|
4 . |
Have defined a Planning data source in the destination environments.
|
5 . |
Have a working source Planning application with all required metadata loaded.
|
Note: Lifecycle Management does not migrate data.
You must migrate EPM System artifacts, as they relate to Planning.
Before migrating a Planning application, you must migrate the Shared Services Native Directory artifacts (users, groups, and roles). To migrate Shared Services users, groups, and roles:
1. |
Log on to Workspace.
|
|---|---|
2. |
Select Navigate, then Administer, and then Shared Services Console.
|
3. |
In the left pane, expand Application Groups, then Foundation, and then Shared Services.
The content pane opens the Artifact List tab, which contains artifacts that you can export from Shared Services.
|
4. |
Expand Native Directory, and make the following selections:
|
5. |
At the bottom of the page, click Define Migration.
|
6. |
Enter filters for the source users, groups, and roles and click Next. In this example, the default (asterisk wildcard) is accepted.
|
7. |
On the Destination page, enter the name of the file system folder where the Shared Services artifacts will be exported, and click Next. In this example, the file system folder is named hss_ugr.
|
8. |
Review the destination options to ensure that the parameters are correct, and click Next.
|
9. |
Review the migration summary and click Execute Migration.
|
10. |
Click Launch Migration Status Report.
|
11. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration completed successfully. In the left pane, the exported artifacts are displayed under File System.
|
Each EPM System product provides several default roles tailored to various business needs. Each application belonging to an EPM System product inherits these roles. Predefined roles from the applications registered with Shared Services are displayed in Shared Services Console. When you assign a predefined product role to a user, you must migrate the Assigned Roles directory to ensure the same access between source and destination environments.
To export assigned roles:
1. |
In the left pane, expand Application Groups, then Foundation, and then Shared Services.
|
|---|---|
2. |
In the content pane, select the assigned roles for products that contain artifacts for the Planning application and click Define Migration. In this example, assigned roles for the Hyplan Planning application and Foundation Services are selected.
|
3. |
Enter filters for the roles and click Next. In this example, the default (asterisk wildcard) is accepted.
|
4. |
On the Destination page, enter the name of the file system folder where the Shared Services role artifacts will be exported, and click Next. In this example, the file system folder is named hss_roles.
|
5. |
Review the destination options to ensure that the parameters are correct, and click Next.
|
6. |
Review the migration summary, and click Execute Migration.
|
7. |
Click Launch Migration Status Report.
|
8. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration completed successfully. In the left pane, the exported artifacts are displayed under File System.
|
In this tutorial, the Performance Management artifacts are split into two sets: Shared Dimensions and Application. The Shared Dimensions directory contains shared dimensions artifacts, such as entity, account, and year.
To export Shared Library dimensions:
1. |
In the left pane, expand Application Groups, then Foundation, and then EPM Architect..
|
|---|---|
2. |
In the content pane, expand Shared Library Dimensions, select the dimensions that you want to export, and click Define Migration. In this example, all dimensions in the source's Shared Library are selected.
|
3. |
Review the source options and click Next.
|
4. |
On the Destination page, enter the name of the file system folder where the Shared Library artifacts will be exported, and click Next. In this example, the file system folder is named epma_shared.
|
5. |
Review the destination options to ensure that the parameters are correct, and click Next.
|
6. |
Review the migration summary and click Execute Migration.
|
7. |
Click Launch Migration Status Report.
|
8. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.
|
Planning applications require a shell application: either a Classic shell application or Performance Management shell application. In this tutorial, the Planning application was created in Performance Management Architect, which requires you to export its application metadata.
To export Performance Management Architect application metadata:
1. |
In the left pane, expand Application Groups, then Foundation, and then EPM Architect.
|
|---|---|
2. |
In the content pane, expand Application Metadata, then Planning Applications, and then [Your Planning Application.
|
3. |
Select Local Dimensions and Planning Settings and click Define Migration. In this example, local dimensions and planning settings for the Hyplan Planning application are selected.
|
4. |
Review the source options and click Next.
|
5. |
On the Destination page, enter the name of the file system folder where the Performance Management Architect application artifacts will be exported, and click Next. In this example, the file system folder is named epma_hyplan.
|
6. |
Review the destination options to ensure that the parameters are correct, and click Next.
|
7. |
Review the migration summary and click Execute Migration.
|
8. |
Click Launch Migration Status Report.
|
9. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.
|
You can migrate the following Calculation Manager artifacts: rules, rule sets, formulas, scripts, and templates.
To export Calculation Manager artifacts:
1. |
In the left pane, expand Application Groups, then Foundation, and then Calculation Manager.
|
|---|---|
2. |
In the content pane, expand Planning, select [Your Planning Application], and click Define Migration. In this example, the Hyplan Planning application is selected. You can also select specific artifacts under your Planning application if you do not want to export all Calculation Manager artifacts.
|
3. |
Review the source options, and click Next.
|
4. |
On the Destination page, enter the name of the file system folder where the Calculation Manager artifacts will be exported, and click Next. In this example, the file system folder is named calc_hyplan.
|
5. |
Review the destination options to ensure that the parameters are correct, and click Next.
|
6. |
Review the migration summary and click Execute Migration.
|
7. |
Click Launch Migration Status Report.
|
8. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration is successfully completed . In the left pane, the exported artifacts are displayed under File System.
|
You use Lifecycle Management to migrate the following types of Planning artifacts:
To export Planning application artifacts:
1. |
In the left pane, expand Application Groups, then Default Application Group, and then [Your Planning Application]. Note: If you associated your Planning application with a different application group, you must navigate to that application group and select your Planning application.
|
|---|---|
2. |
In the content pane, expand select the artifacts you want to export and click Define Migration. In this example, Configuration, Global Artifacts, Plan Type, and Relational Data are selected. You can also select a subset of artifacts. It is highly recommended that you split the artifact migration. For instance, you can export a separate file system for Security (access permissions).
|
3. |
Review the source options and click Next.
|
4. |
On the Destination page, select File System, enter the name of the file system folder where the Planning artifacts will be exported, and click Next. In this example, the file system folder is named pln_hyplan.
|
5. |
Review the destination options to ensure that the parameters are correct, and click Next.
|
6. |
Review the migration summary and click Execute Migration.
|
7. |
Click Launch Migration Status Report.
|
8. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.
|
You can export repository objects such as financial reports, books, and other attached files.
To export repository objects:
1. |
In the left pane, expand Application Groups, then Reporting and Analysis, and then Reporting and Analysis.
|
|---|---|
2. |
In the content pane, expand Repository Objects, select the artifacts that you want to export, and click Define Migration. In this example, the following objects are selected: financial reports in the root folder, the Hyplan folder and its contents, and the InsFiles folder and its contents.
|
3. |
Review the source options and click Next.
|
4. |
On the Destination page, select File System, enter the name of the file system folder where the repository objects will be exported, and click Next. In this example, the file system folder is named repobj.
|
5. |
Review the destination options to ensure that the parameters are correct, and click Next.
|
6. |
Review the migration summary and click Execute Migration.
|
7. |
Click Launch Migration Status Report.
|
8. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration is successfully completed. In the left pane, the exported artifacts are displayed under File System.
|
The source environment application artifacts that exist on the file system must be moved to the destination environment file system. You can accomplish this task by copying and pasting the artifacts, sending them through FTP, or burning them to a DVD.
The default file system location for the exported artifacts is:
[Middleware Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory
In this topic, you compress the source artifact directory, copy it to the destination environment, and extract the file system folders. To copy source artifacts to the destination environment:
1. |
Navigate to the following directory: [Middleware Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory In this example, you navigate to C:\oracle\Middleware\user_projects\epmsystem1\import_export\admin@Native Directory.
The exported file system folders are displayed.
|
|---|---|
2. |
Navigate two levels up, and copy or compress the import_export directory.
In this example, the import_export directory is compressed with 7-zip.
Typically, in new environments, the import_export directories do not exist until you run a migration.
|
3. |
In the destination environment, navigate to [Middleware Home]\user_projects\epmsystem1.
Notice that the import_export directory does not exist.
|
4. |
Copy and extract the compressed file.
|
5. |
Open the import_export and [admin_user]@Native Directory folders.
|
6. |
Verify that the exported file system folders were extracted in the [Middleware Home]\user_projects\epmsystem1\import_export\[admin_user]@Native Directory directory of the destination environment.
|
You exported the Planning application artifacts from the source environment to the file system and you copied the artifacts to the destination environment file system. In this topic, you run the Lifecycle Management migration in the destination environment.
Importing Guidelines:
To import Planning applications from the file system into the destination environment:
1. |
Log on to Workspace and open Shared Services Console.
|
|---|---|
2. |
In the left pane, expand File System.
|
3. |
In the left pane, select the file system folder that contains the Shared Services users, groups, and roles. In this example, hss_ugr is selected.
|
4. |
On the Artifact List tab, click Select All, verify that the artifacts were selected, and click Define Migration.
|
5. |
Review the source options and click Next.
|
6. |
On the Destination page, verify that Foundation:Shared Services is selected, and click Next.
|
7. |
On the Destination Options page, accept the defaults, and click Next.
|
8. |
Review the migration summary, and click Execute Migration.
|
9. |
Click Launch Migration Status Report.
|
10. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration is successfully completed.
|
11. |
In the left pane, under File System, select the file system folder that contains the Performance Management Architect Shared Library dimensions and members. In this example, epma_shared is selected.
It is recommended that you import Shared Library dimensions and members before importing Planning applications. Some Planning applications require Shared Members, which will cause your migration to fail if they have not been imported to the Shared Library.
|
12. |
On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.
|
13. |
Review the source options and click Next.
|
14. |
On the Destination page, verify that Foundation:Performance Management Architect is selected and click Next.
|
15. |
On the Destination Options page, accept the defaults and click Next.
|
16. |
Review the migration summary and click Execute Migration.
|
17. |
Click Launch Migration Status Report.
|
18. |
On the Migration Status Report page, review the status of the migration. The report status displays Completed when the migration completed successfully. Click Refresh to display the updated job status.
|
19. |
In the left pane, under File System, select the file system folder that contains the Performance Management Architect application metadata. In this example, epma_hyplan is selected.
|
20. |
On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.
|
21. |
Review the source options, and click Next.
|
22. |
On the Destination page, verify that Foundation:Performance Management Architect is selected, and click Next.
|
23. |
On the Destination Options page, select Deploy after Import and Create Outline, enter the remaining required parameters, and click Next. In this example, the following information is entered:
Note: You must have an existing Planning data source ready before you run the import.
|
24. |
Review the migration summary, and click Execute Migration.
|
25. |
Click Launch Migration Status Report.
|
26. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration completed successfully.
|
27. |
In the left pane, under File System, select the file system folder that contains the Calculation Manager artifacts for your Planning application. In this example, calc_hyplan is selected.
|
28. |
On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.
|
29. |
Review the source options, and click Next.
|
30. |
On the Destination page, verify that Foundation:Calculation Manager is selected, and click Next.
|
31. |
Review the destination options, and click Next.
|
32. |
Review the migration summary, and click Execute Migration.
|
33. |
Click Launch Migration Status Report.
|
34. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration completed successfully.
|
35. |
In the left pane, under File System, select the file system folder that contains the Shared Services assigned roles. In this example, hss_roles is selected.
|
36. |
On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.
|
37. |
Review the source options, and click Next.
|
38. |
On the Destination page, verify that Foundation:Shared Services is selected, and click Next.
|
39. |
Review the destination options, and click Next.
|
40. |
Review the migration summary, and click Execute Migration.
|
41. |
Click Launch Migration Status Report.
|
42. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration completed successfully.
|
43. |
In the left pane, under File System, select the file system folder that contains the Planning application artifacts. In this example, pln_hyplan is selected.
|
44. |
On the Artifacts tab, click Select All, verify that all artifacts are selected, and click Define Migration.
|
45. |
Review the source options, and click Next.
|
46. |
On the Destination page, verify that Default Application Group: Hyplan is selected, and click Next.
|
47. |
Review the destination options, and click Next.
|
48. |
Review the migration summary, and click Execute Migration.
|
49. |
Click Launch Migration Status Report.
|
50. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration completed successfully.
|
51. |
In the left pane, under File System, select the file system folder that contains the repository objects. In this example, repobj is selected.
|
52. |
On the Artifact List tab, click Select All, verify that the artifacts were selected, and click Define Migration.
|
53. |
Review the source options, and click Next.
|
54. |
On the Destination page, verify that Reporting and Analysis:Reporting and Analysis is selected, and click Next.
|
55. |
On the Destination Options page, accept the defaults, and click Next.
|
56. |
Review the migration summary, and click Execute Migration.
|
57. |
Click Launch Migration Status Report.
|
58. |
On the Migration Status Report page, review the status of the migration, and click Refresh to display the updated job status.
The report status displays Completed when the migration completed successfully. The migration for all artifacts is completed.
|
59. |
Next, verify that your artifacts imported completely. In the left pane, expand User Directories, then Native Directory, and then Users.
On the Browse tab, click Search, and review the user list.
|
60. |
Repeat the same steps for Groups and Roles. It is also recommended that you review the assigned roles.
|
61. |
Next, open Calculation Manager, and verify that the rules and rule sets for your Planning application are available. In Workspace, select Navigate, then Administer, and then Calculation Manager.
Expand Planning, then [Planning Application], then [Plan Type], and then Rules.
Ensure that the rules associated with your Planning application are listed. Repeat the same steps to verify all nodes under all plan types in the Planning application.
|
62. |
Next, open your Planning application. In Workspace, select Navigate, then Applications, then Planning, and then [Planning Application].
Verify that data forms, menus, smart lists, and other Planning objects have migrated successfully.
|
In this tutorial, you have learned how to:
 |
About
Oracle |  | Careers | Contact
Us | Site Maps | Legal
Notices | Terms of Use | Your Privacy Rights
|
