First-Time Lifecycle Management Migration for Oracle Hyperion Planning 11.1.1 with Hyperion Shared Services Lifecycle Management 11.1.1


Purpose


This tutorial covers a first-time Lifecycle Management (LCM) migration for Oracle Hyperion Planning 11.1.1 applications. This lifecycle management migration utilizes Hyperion Shared Services Lifecycle Management 11.1.1.

Time to Complete


Approximately 2 hours.

Topics


This tutorial covers the following topics:

 Overview
 Scenario
 Prerequisites
 Exporting a Planning Application to the File System in the Source Environment
 Copying Application Artifacts from the Source Environment to the Destination Environment
 Creating a Planning Application in the Destination Environment for Planning Classic Applications
t6Importing a Planning Application from the File System in the Destination Environment
 Summary

Viewing Screenshots


Click icon to show all screenshots 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.

Overview


In this tutorial, you perform a first-time migration with an Oracle Planning 11.1.1 application and Hyperion Shared Services Lifecycle Management 11.1.1 from a source environment to a destination environment.

The Planning application consists of artifacts from various products. For example:

  • Shared Services users, groups, and provisioning artifacts
  • Planning artifacts
  • Enterprise Performance Management Architect (EPMA) artifacts
  • Financial Reporting or Web Analysis documents

Because Planning application artifacts span multiple products, you must migrate the artifacts from each product as it relates 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 Enterprise Performance Management (EPM) Lifecycle Management Administration Guide, Appendix E: Planning and Lifecycle Management. Note, too, that data migration is currently not supported.

Back to Topic List

Scenario


You are tasked with a first-time migration for an Oracle Planning 11.1.1 application from a source environment to a destination environment. The 11.1.1 release is installed and configured on the source and destination environments, which utilize separate Shared Services 11.1.1 instances. Consequently, the file system will be utilized for this migration.

Back to Topic List

Prerequisites


Before starting this tutorial:

1.

Install and configure Planning 11.1.1 and all related 11.1.1 EPM products in the source and destination environments (Hyperion Shared Services, Essbase, Financial Reporting, and so on).

2.

The source environment must contain the Planning application with all metadata loaded.

3.

The source environment user who is performing the lifecycle management activities is provisioned with the following roles:

  • Shared Services LCM administrator role
  • Planning application administrator role
4.

The destination environment user who is performing the lifecycle management activities is provisioned with the following roles:

  • Shared Services LCM administrator role
  • Planning application administrator role
  • Planning application creator role

Back to Topic List

Exporting a Planning Application to the File System in the Source Environment


1.

In the source environment, log on to Shared Services as the user who is provisioned with the appropriate LCM roles.

 

2.

Navigate to Foundation > Shared Services, and select the native directory provisioning artifacts and task flows that are applicable to the Planning application, as follows:

  • Users – Native Directory users
  • Groups – Native Directory groups
  • Assigned Roles – Roles granted to users and groups through the provisioning process. You should select the roles for the associated product artifacts that pertain to the Planning application.

Note: You should choose the assigned roles for all products that contain artifacts for the Planning application.

 

3.

Navigate to the Planning application group, and select the Planning application that you want to migrate; for example, HPSamp.

 

4.

Select the application artifacts that you want to migrate.

 

5.

For EPMA-enabled Planning applications, navigate to Foundation > EPM Architect > Application Metadata > Planning Applications, and select the EPMA artifacts that reside under the Planning application that you are migrating. In the following example, it is HPSamp.

 

6.

Navigate to Reporting and Analysis to select the financial reports.

 

7.

Select the Repository Objects folder, and navigate to the folders that contain the financial reports that are associated with the Planning application.

 

8.

Select the financial reports; for example, Planning HPSamp Reports.

 

9.

On the Selected Artifacts tab, review the set of artifacts that you selected for the Planning application migration.

 

10.

Click the Define Migration button to define the Planning application migration.

 

11.

Select the first product to migrate (for example, Shared Services), and click Next.

 

12.

On the Source Options page, filter the user, groups, and roles as needed, and click Next.

 

13.

On the Destination page, enter the name of the file system folder where the Shared Services artifacts will be extracted, and click Next.

 

14.

Review the destination options to ensure that the parameters are correct, and click Next.

You are directed back to the beginning of the migration wizard so that you can define other product migrations.

 

15.

Select the next product to migrate (for example, EPM Architect), and click Next.

 

16.

On the Source Options page, click Next.

 

17.

On the Destination page, enter the name of the file system folder where the EPMA artifacts will be extracted, and click Next.

 

18.

Review the destination options to ensure that the parameters are correct, and click Next.

 

19.

Select the next application to migrate (for example, Planning), and click Next.

 

20.

On the Source Options page, and click Next.

 

21.

On the Destination page, enter the name of the file system folder where the Planning artifacts will be extracted, and click Next.

 

22.

Review the Destination Options page, and click Next.

 

23.

Select the next application to migrate (for example, Reporting and Analysis), and click Next.

 

24.

On the Source Options page, select Export with Job Output if you want that information to be migrated, and click Next.

 

25.

On the Destination page, enter the name of the file system folder where the Financial Reporting artifacts will be extracted, and click Next.

 

26.

Review the destination options to ensure that the parameters are correct, and click Next.

 

27.

Review the Migration Summary to ensure that the defined migrations are correct.

 

28.

Click Save Migration Definition.

 

29.

Select Save as XML, and click OK.

 

30.

Click Save.

 

31.

Enter the location and name for the migration definition file, and click Save.

 

32.

In the Download Complete dialog box, click Close.

 

33.

Click Close.

 

34.

Click Execute Migration.

The Planning application migration is executed.

 

35.

Click Launch Migration Status Report.

 

36.

On the Migration Status Report page, review the status of the migration.

When the report status changes to Success, the migration is completed successfully, and the Planning application artifacts are extracted to the file system.

 

37.

Refresh the Migration Status Report to see that the migration is completed.

 

Back to Topic List

Copying Planning Application Artifacts from the Source Environment to the Destination Environment


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.

Note that the default file system location for the life cycle management artifacts is on the Shared Services Web application server at <%hyperion_home%>\common\import_export.

In this example, you copy and paste the artifacts within Windows Explorer.

1.

In the source environment, navigate to Windows Explorer on the file system.

 

2.

Select Tools > Map Network Drive.

 

3.

Enter the parameters for the destination environment file system location.

 

4.

Click Finish.

 

5.

Navigate to the location of the source environment application artifacts.

 

6.

Select the folders, right-click, and select Copy.

 

7.

Navigate to the newly mapped destination location, right-click, and select Paste.

The application artifact folders now reside on the destination server file system location.

 

Back to Topic

Creating the Planning Application in the Destination Environment for Planning Classic Applications


Before migrating a Planning classic application, you must first create the Planning application in destination environment. Prior to beginning this section, ensure that you have created a new relational database for this new application.

Note:

  • If the Planning application is already created in the destination environment or if the Planning application is EPMA-enabled, skip this section.
  • The following dimension-level properties must match in both the source and the destination applications:
    • Start year
    • Base time period (for example, 12 months, Quarters, and Custom)
    • Start month
    • If the source has a “Single Currency” application type, then the destination application should be of the same type
    • Source and destination plan types must match (for example, if the source application has a plan type called Plan1, a Plan1 plan type must exist in the destination application).
1.

Log on to Workspace.

 

2.

Navigate to Administer > Classic Application Administration > Planning Administration.

 

3.

Select Manage Data Source.

 

4.

Click Create Data Source.

 

5.

Enter the parameters, and select Finish.

 

6.

Click Create Application.

 

7.

Enter the application name, description, Shared Services project, and instance, select Sample Application, and click Next.

 

8.

Click Finish.

 

9.

Select File > Open > Applications > Planning > HPSamp

You successfully created the destination application.

 

 

Back to Topic List

Importing a Planning Application from the File System in the Destination Environment


You have exported the Planning application artifacts from the source environment to the file system, copied the artifacts to the destination environment file system, and created a Planning application in the destination environment. You now import the artifacts into the destination Planning application.

Note:

  • Shared Services artifacts must be imported before you import Planning artifacts.
  • Because Lifecycle Management does not support Planning access permissions migrations, use the following Planning command-line utilities (ImportSecurity and ExportSecurity) to export and import Planning security:

HYPERION_HOME\products\Planning\bin\ExportSecurity.cmd HYPERION_HOME\products\Planning\bin\ImportSecurity.cmd

 

1.

In the destination, log on to Shared Services as the user who is provisioned with the appropriate LCM roles.


 

2.

Navigate to the File System node, select the Shared Services artifacts, and click Define Migration.

 

3.

Review the source options, and click Next.

 

4.

In the destination, choose the Shared Services destination, and click Next.

 

5.

On the Destination Options page, select the import operation type and the number of maximum errors before stopping the import, and click Next.

 

 

6.

Click Execute Migration.

The migration is executed.

 

7.

Click Launch Migration Status Report to view the status of the migration.

Notice that the migration is executed.

 

8.

Perform one of the following actions:

  • For Planning applications that are EPMA-enabled, proceed to step 9.

Note: EPMA artifacts must be imported and deployed before non-dimensional Planning artifacts are imported.

  • For Planning classic applications, skip to step 24.

 

9.

If the Planning application is EPMA-enabled, navigate to Application Groups > File System.

Note: The EPMA artifacts must be imported and deployed before you migrate non-dimensional artifacts for Planning application.

 

10.

Select the EPMA file system artifacts that are applicable to the Planning application.

 

11.

Click Define Migration.

 

12.

View the Source Options page, and click Next.

 

13.

Select the destination (in this case, EPM Architect), and click Next.

 

14.

Select the Dimension Import Mode ( Merge or Replace), select Deploy after Import, enter the remaining parameters to deploy the application view to a physical Planning application, and click Next.

 

15.

Review the Migration Summary, and click Save Migration Definition.

 

16.

Click OK.

 

17.

In the File Download dialog box, click Save.

 

18.

Enter the location and migration definition file name, and click Save.

 

19.

In the Download Complete dialog box, click Close.

 

20.

Click Close again.

 

21.

Click Execute Migration.

The migration is executed.

 

22.

Click Launch Migration Status Report to view the status of the migration.

Notice that the migration is completed.

 

23.

Click Cancel to close the Migration Status Report.

 

24.

Navigate to Application Groups > File System, and select the Planning application artifacts and the Planning financial reports.

 

25.

Review the Selected Artifacts tab to view the artifacts that you selected for the migration.

 

26.

Click Define Migration.

 

27.

Select the Financial Report artifacts (FR artifacts), and click Next.

 

28.

Review the Source Options page, and click Next.

 

29.

On the Destination page, select the Reporting and Analysis repository, and click Next.

 

30.

Optional: On the Destination Options page, select Exclude job output on import, and click Next.

 

31.

Select Planning artifacts, and click Next.

 

32.

Review the Source Options page, and click Next.

 

33.

Select the destination Planning application that you want the application to import to, and click Next.

 

34.

Review the Destination Options page, and click Next.

 

35.

Review the Migration Summary page, and click Save Migration Definition.

 

36.

Click OK.

 

37.

In the File Download dialog box, click Save.

 

38.

Enter the location and migration definition file name, and click Save.

 

39.

In the Download Complete dialog box, click Close.

 

40.

Click Close again.

 

41.

Click Execute Migration.

 

42.

Click Launch Migration Status Report.

The migration is completed.

 

Back to Topic List

Summary


Congratulations! You have completed your first migration by using Shared Services Lifecycle Management 11.1.1. To review the steps that you completed:

 Export the application artifacts from your source environment to the file system.
 Copy the application artifacts from your source environment file system to the destination environment file system.
 Create a Planning classic application in the destination environment.

Import the application artifacts from the destination environment file system to the application.

Back to Topic List

Related Information


To learn more about Planning, refer to additional OBEs.

Back to Topic List