Cloning Hyperion

Introduction
Strategy to clone this application will be to use Oracle Hyperion LCM (Life Cycle
Management). Lifecycle Management is integrated with Shared Services Console, and
the artifacts are listed under Application Groups and Applications. For example, in
Shared Services Console, an application group called Development is displayed. Under
the Development application group, an HFM Management Reporting application is
displayed. Under the HFM Management reporting application, dimensional and no
dimensional models are displayed (Accounts, Entities, Security, Member Lists, and so
on). Refer to Lifecycle Management and Shared Services Console Integration in
"Lifecycle Management Guide" .The Products which can be migrated with this tool are:
Shared Services
Essbase
Planning
Reporting
HFM
The dimensions housed in EPMA
A fresh instance required to be installed, but following Important Considerations need to
be take care:
Target application can have different name from source Application
The Plan Type in Source and destination should match
o Otherwise it must be changed by editing the files in target
o Target Application plan types should be in same order as source
Application
Start year should be the same (It is not mandatory to match the number of years)
Base time period should be the same
Target Application Currency settings should match Source Application
Standard Dimension names should be match
o Otherwise it can be changed by editing the files

Migration / Cloning
The file system location is on the Shared Services Web application server computer.
The default destination on the Shared Services computer is
MIDDLEWARE_HOME/user_projects/epmsystem1/import_export. Applications or
artifacts exported (or copied) to the file system location are displayed under the File
System node in the View pane. When artifacts are exported to the file system, they
retain the last modified time the artifact was updated in the native product.
Note: On Windows 2003, if Shared Services is started as a Windows service, and the
file system path is defined for a mapped drive, you cannot view the file system contents
using Shared Services Console. If the file system path is a network-accessible location,
ensure that Shared Services is not running as a Windows service

Figure 1: XML Schema Outline of the Migration Definition File
Artifacts to migrate must be defined in a migration definition. EPM System provides
sample files (in EPM_ORACLE_HOME/common/utilities/LCM/11.1.2.0/Sample) for you
to model the migration definition to use during migrations. You can create a migration
definition manually or you can create one automatically in Shared Services Console.
Cloning process will start by opening the specific component i.e. Shared Services, this
can be repeated for all components.
Step 1: Application Groups >Application (in this case Shared Services under
Foundation).
Step 2: Select all Artifacts
Step 3: Press Button Define Migration which is located on bottom of screen. It will
start the Migration wizard.
Step 4: On Source Options screen, enter * in all Filters including Native User Filter,
Native Group Filter, Native Role Filter.
Step 5: Type in a file name for the export. It is advisable that you use a naming
convention for this since you will end up with (possibly multiple) files for each application
Review the destination options & click Next.
Finally, review the Migration summary and click Execute Migration.
This will get to information screen. Click Launch Migration Status Report to actually see
the migration progress.
As long as the migration is running you will get a status of In Progress
Click Refresh to keep checking status (if desired) until you get a status
of Completed or Failed. Refer to Viewing Migration Status in Lifecycle Management
Guide

Errors encountered during migration are defined by logging.xml in the
MIDDLEWARE_HOME/user_projects/epmsystem1/Config/FoundationServices directory
and the log.directory property. Monitor the error log to understand issues encountered
during the migration process.
All of the other applications can be exported this same way, each with slightly different
screen sequences but generally the same process.
After the exports are finished the LCM export files can be copied to the target server
environment, if needed. These export files can be found on the Shared Services server
under \Hyperion\common\import_export\username@directory.

Step 6: Copy the entire directory (in this example, Essadmin@Native Directory) to the
Hyperion\common\import_export directory on the target server.
The import side is where things are more likely to be tricky. Here you will reverse the
process, selecting the export files in proper order (Shared Services, Essbase, Planning
& Reporting) and importing them to whatever target is appropriate.
Step: 7 start the process by logging in to the Shared Services console as the same
username you used in the export process. Under Application Groups>File System,
find the appropriate export files and click Define Migration. Click through the screens,
including the SS screen selecting the target application to import to.
On the destination option screen select Create/Update and increase the Max errors if
desired (default = 100), than execute the migration. Select all the artifacts you want to
import one by one.