First-Time Lifecycle Management Migration for Oracle Essbase 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 Essbase 11.1.1 databases. 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 an Essbase Database to the File System in the Source Environment
Copying Essbase Database Artifacts from the Source Environment to the Destination Environment
Creating the Essbase Application in the Destination Environment
Modifying Security Artifacts Before Importing
t6 Importing an Essbase Database from the File System in the Destination Environment
Summary
Related Information


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 Essbase 11.1.1 database and Hyperion Shared Services Lifecycle Management 11.1.1 from a source environment to a destination environment.

The Essbase database consists of artifacts from various products. For example:

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

Because the Essbase database artifacts span multiple products, you must migrate the artifacts from each product as it relates to the Essbase database.

In order to use this Lifecycle Management feature with Essbase, you must first convert the Essbase server to Shared Services mode.

For the list of support artifacts that are available for migration with the Shared Services Lifecycle Management functionality, refer to the EPM Lifecycle Management Administration Guide, Appendix C: Essbase and Lifecycle Management. Additionally, note that data migration is currently not supported.

Back to Topic List

Scenario


You are tasked with a first-time migration for an Oracle Essbase 11.1.1 database 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 Oracle Essbase 11.1.1 and all related 11.1.1 EPM products in the source and destination environments (Hyperion Shared Services, Financial Reporting, and so on).
2. The source environment must contain the Essbase database with all metadata loaded.
3. The source environment user who is performing the lifecycle management activities must be provisioned with the following roles:
  • Shared Services LCM administrator role
  • Essbase server level: Server Access role
  • Essbase application level: Calc role
4. The destination environment user who is performing the lifecycle management activities must be provisioned with the following roles:
  • Shared Services LCM administrator role
  • Essbase application level: Database Manager role

Back to Topic List

Exporting an Essbase Database 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 the task flows that are applicable to the Essbase database, 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 Essbase database.

Note: You should choose the assigned roles for all products that contain artifacts for the Essbase database.

 

3.

Navigate to the Essbase application to select the Essbase database that you want to migrate; for example, Sample Basic.

Notice that the Essbase Server level also contains substitution variables that can be selected for migration.

 

4.

Select the database artifacts that you want to migrate.

 

5.

For EPMA enabled Essbase databases, navigate to Foundation > EPM Architect > Application Metadata > Essbase (ASO) Applications, and select the EPMA artifacts that reside under the Essbase database that you are migrating. In the following example, it is Basic.

 

6.

Navigate to Reporting and Analysis to select the financial reports.

 

7.

Expand the Repository Objects folder, and navigate to the folders that contain the financial reports that are associated with the Essbase database.

 

8.

Select the financial reports; for example, Sample Basic Reports.

 

9.

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

 

10.

Click the Define Migration button to define the Essbase database migration.

 

11.

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

 

12.

On the Source Options page, select the user, groups, and role filters, 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 product to migrate (for example, Essbase), and click Next.

 

20.

Review the Source Options page, and click Next.

 

21.

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

 

22.

Review the Destination Options page, and click Next.

 

23.

Select the next product 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 Essbase database 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 Essbase database 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 Essbase Database Artifacts from the Source Environment to the Destination Environment


The source environment database 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 lifecycle management artifacts is on the Shared Services web database 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 database artifacts.

 

6.

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

 

7.

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

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

Back to Topic List

Creating the Essbase Application in the Destination Environment


Before migrating an Essbase database, you must first create the Essbase application in destination environment.

Note: If the Essbase application is already created in the destination environment, skip this section.

1.

Log on to Essbase Administration Services.

 

2.

Navigate to the Essbase Server, right-click, and select Create application with either Using aggregate storage or Using block storage.

Note: If the Source environment application is aggregate storage (ASO), the database can be migrated only to an ASO application. If the Source environment application is block storage (BSO), the database can be migrated only to a BSO application.

 

3.

Enter the application name, select Unicode mode (optional), and click Next.

You successfully created the Destination application.

 

Back to Topic List

Modifying Security Artifacts Before Importing


Before importing the Shared Services security artifacts, you must modify the Essbase Assigned Roles artifacts so that they contain the correct Destination environment Shared Services Application Group.

1.

In the Destination environment, navigate to the file system location of the Shared Services Essbase Assigned Roles artifacts. In this example, the location is C:\Hyperion\common\import_export\admin@Native Directory\Sample Basic - HSS artifacts\resource\Native Directory\Assigned Roles\Essbase.

 

2.

Select the CSV file (in this example, Sample.csv) and open the file in Microsoft Excel.


 

3.

Change the project_name field to reflect the correct Application Group in the destination environment. For example, change Essbase:LCMDEV:1 to Essbase:LCMTEST:1.

 

4.

Select File > Save.

 

Back to Topic List

Importing an Essbase Database from the File System in the Destination System


You have exported the Essbase database artifacts from the source environment to the file system, copied the artifacts to the destination environment file system, created an Essbase application in the destination environment, and modified the Shared Services Essbase Assigned Role artifact. You now import the artifacts into the destination Essbase database.

1.

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


 

2.

Perform one of the following actions:

  • For Essbase databases that are EPMA-enabled, proceed to step 3.
  • For native Essbase applications, skip to step 18.

 

3.

If the Essbase database is EPMA-enabled, navigate to Application Groups > File System.

 

4.

Select the EPMA file system artifacts that are applicable to the Essbase database.

 

5.

Click Define Migration.

 

6.

View the Source Options page, and click Next.

 

7.

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

 

8.

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

 

9.

Review the Migration Summary, and click Save Migration Definition.

 

10.

Click OK.

 

11.

In the File Download dialog box, click Save.

 

12.

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

 

13.

In the Download Complete dialog box, click Close.

 

14.

Click Close again.

 

15.

Select Execute Migration.

The migration is executed.

 

16.

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

Notice that the migration is completed.

 

17.

Click Cancel to close the Migration Status Report.

 

18.

Navigate to Application Groups > File System, and select the Essbase database artifacts, the Essbase Shared Services artifacts, and the Essbase financial reports.

 

19.

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

 

20.

Click Define Migration.

21.

Select the Essbase Sample Basic artifacts, and click Next.

 

22.

Review the source options, and click Next.

 

23.

Choose the Destination Essbase application that you want the database to import to, and click Next.

 

24.

Select Overwrite Artifact(s) (optional) and the restructure cube option, and click Next.

 

25.

Select the Shared Services artifacts, and click Next.



 

26.

Review the source options, and click Next.

 

27.

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

 

28.

On the Destination Options page, select the Import Operation Type and the number of maximum errors before stopping the import, and click Next.

 

29.

Select the Financial Reporting artifacts, and click Next.

 

30.

Review the Source Options page, and click Next.

 

31.

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

 

32.

On the Destination Options page, select Exclude Job Output on Import (optional), and click Next.

 

33.

Review the Migration Summary, and click Save Migration Definition.

 

34.

Click OK.

 

35.

In the File Download dialog box, click Save.

 

36.

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

 

37.

In the Download Complete dialog box, click Close.

 

38.

Click Close again.

 

39.

Click Execute Migration.

 

40.

Click Launch Migration Status Report.

The migration is completed.

 

Back to Topic List

Summary


Congratulations! You have completed your first migration using Shared Services Lifecycle Management release 11.1.1.

In this tutorial, you have learned how to:

Export the database artifacts from your source environment to the file system.
Copy the database artifacts from your source environment file system to the destination environment file system.
Create an Essbase application in the destination environment.
Modify the Shared Services Essbase Assigned Roles artifact to include the correct destination Shared Services application group.
Import the database artifacts from the destination environment file system to the database.

Back to Topic List

Related Information


To learn more about Essbase you can refer to:

Essbase Online Technical Reference.

Back to Topic List