The purpose of this document is to provide a high level overview of the process for migrating EPMA enabled Planning applications between two completely separated environments.  I have made a couple assumptions while writing this that I mention below.  All of this information is available in the references mentions.  I have just tried to provide a single concise process.

References

• Oracle EPM 11.1.2.1 Lifecycle Manager Administration Guide
• Oracle Hyperion EPMA 11.1.2.1 Admin Guide
• Oracle Hyperion Planning 11.1.2.1 Admin Guide

Assumptions

• Migrating applications already exist in the target environment.  The purpose is to refresh existing applications.
• The same user will perform the Lifecycle Manager exports and imports in each environment.

Executive Summary

The overall process uses a couple technologies to accomplish the migration of Planning applications, the underlying Essbase database and its artifacts, EPMA metadata, and the Reporting and Analysis repository.

Lifecycle Manager is used to extract all relevant components from the following:

• Foundation
  • Calc Manager
    • Planning applications
• EPMA
  • Application Metadata
  • Shared Library Dimensions
• Planning
  • All artifacts
  • Essbase artifacts
    • Calc Scripts
    • Load Rules, etc.
• Essbase
  • Substitution Variables
• Reporting and Analysis
  • Repository content
    • Relevant folders only

Essbase data is captured by backing up (archiving) the Essbase database in EAS Console.

Metadata is imported first in the target system followed by application components, data, and then reports.  Planning application metadata requires particular attention to the order of import.

Application Refresh

Extract Source Metadata

In Shared Services Console, select the following components of the applications listed:

• EPMA
  • Application Metadata for each Planning application
  • Shared Dimensions
• Calc Manager
  • All artifacts for each Planning application that is migrating.
• Planning
  • All artifacts for each Planning application that is migrating.  This will capture all Essbase artifacts such as calculation scripts, load rules, etc.
• Essbase
  • Substitution variables
• Reporting and Analysis
  • All repository folders that need to be replicated in the target environment.  System folders do not need to be migrated.

LCM will export artifacts to the file system, by default, to <HYPERION_HOME>\user_projects\epmsystem1\import_export\<USER>@<DIRECTORY>\<FOLDER>

• <HYPERION_HOME> is usually <DRIVE>\Oracle\Middleware
• <USER> is the login of the user performing the export.
• <DIRECTORY> is the Shared Services user directory.
• <FOLDER> is the folder specified in during the migration definition.

Backup Essbase databases using the ARCHIVE feature in EAS Console.

Import in Target Environment

Begin by copying the folders created during the LCM export to the same location in the target environment.

The Future of Big Data

With some guidance, you can craft a data platform that is right for your organization’s needs and gets the most return from your data capital.

Get the Guide

Import the EPMA, Calc Manager, and Essbase artifacts first using Lifecycle Manager from Shared Services.  When prompted specify to REPLACE instead of MERGE.

Deploy the Planning application from Lifecycle Manager.  Specify to CREATE the database and FULL deploy.

Import Planning artifacts in the following order.  Each group of items requires an import iteration.

1.  Application Settings under Configuration Properties.

2.  Global Artifacts:

• Spread Patterns
• Smart Lists
• Common Dimensions
• Exchange Rates

3.  All Standard and Attribute Dimensions under Plan Type

4.  Configuration:

• User Variables
• User Preferences

5.  Substitution Variables under Global Artifacts

6.  Plan Type:

• Substitution Variables
• Calc Scripts
• Rules files
• Calculation Manager Rules

7.  Global Artifacts:

• Business Rules
• Custom Menus
• Calculation Manager Rule sets
• Planning Unit Hierarchies
• Report Mappings

8.  Data Forms under Plan Type

9.  Global Artifacts:

• Composite Forms
• Task Lists

10.  Relational Data

Copy the archive files created previously for the Essbase databases to the target system and force restore from within EAS Console.

Re-deploy the application from Application Library.  Specify only to REFRESH the database