HFM Application Migrating

HFM application Migrating using LCM
Created By : Amit Sharma
Contact Point : bisp.consulting@gmail.com
http://learnhyperion.wordpress.com
Introduction
In every Hyperion Financial Management application we need to define following
things to specify and define the Application
1. HFM Application Dimensions
2. Documents associated with the HFM application
3. The Data Forms are created by the developer for the Business Users
4. Intercompany Transactions
5. Journals
6. Member lists
7. Rules
8. Security
For every application it don’t restrict itself only in single server or only in developers
machine. We need the backup of application in case the server face any technical
crisis or we need to move the application from development environment to
testing environment.
We use “HFM application Migration” for two major operation

1) Moving Application from one environment to another.
(Development to Testing Environment)
2) Taking Application Backup/Restore .
This process is performed by LCM ( Life Cycle Management).
Life Cycle Management
Lifecycle Management (LCM) provides a consistent way for Hyperion
products to migrate an application, cube, repository, or individual artifacts
across product environments and operating systems. The LCM interface is
integrated with Oracle's Hyperion® Shared Services Console. LCM also
supports a command-line utility.
LCM features:
 Browsing applications and folders
 Searching for artifacts
 Comparing applications and folders
 Migrating an entire application or repository or individual artifacts
 Application Migration Wizard:
 Application to Application
 Application to Server File System
 Exported Application to Application
 Saving and loading a package file
 Migration Status Report
 Migration Audit Report
 Security—LCM Administrator role
 Command-Line Utility
 API
Artifacts
An artifact by definition is an object that has been created for a practical
purpose. In this case any pieces of your EPM that contain meta-data
or data. When we use the LCM tool we are able to select individual
objects or artifacts during the migration. However, one cannot move an
individual report object via LCM.
How does the LCM utility work?
It’s all XML based. That is to say that once we define our migration (i.e.: select which
artifacts are to be moved) an XML, file-system based directory structure is created. It
is created under the Shared Services directory on the server for which Shared Services
resides. After we define the migration and your XML-based file structure is created,
one whom has LCM administrator permissions must then manually move the file-
structure from one server environment to the other. That can be done either by
copying and pasting or via FTP.
Login to Shared service
http://<servername>:28080/interop
Browse to Application Management > Application Group
Select the server type according to the that we select the server type.
WE SELECT THE APPLICATION WHICH WE

WANT TO MIGRATE or TAKE BACKUP.
All the artifacts are displayed.
All the artifacts are displayed. We select the required artifacts. For complete
migration or back up we select all.
Next we define the Migration properties by launching DEFINE MIGRATION
We define the Source application.
First the source application defined is shown.
NEXT WE need to define the Destination
Here we define the destination option.
Either we select another application or we can take its xml backup to file system.
Here we first choose to take the xml backup to File system
Displayed source application and target application group.
Migration Summary.
When we decide that all the steps for migration has been successfully
Performed , we Execute migration
We launch the Migration Status Report for status of Migration

Migration Status
Report for status of
Migration
Path where the application stored in file system.
When we browse through the folder structure we find that each and every
object is stored in xml format i.e. the DIMENSION members , The Custom
Documents.
In Hyperion product suit every components can be backed up in xml format.
We browse to see the folder structure and components in xml format.
List of all dimension HFM application has available in xml format.

Document available in xml format
The best way to migrate or taking backup of application is these xml files. After
We get all these files in xml we can use it either for backup purpose to another
Server or we can move it to another server that runs Hyperion Suits.
Restoring the HFM Application.
Now we will work on restoring the HFM application into another server
This time we will move it from FILE SYSTEM to HFM APPLICATION
This time we are going to do the other way around.

The application backup we have taken last time, we are going to restore it in
a empty application. Before restoring it you can modify the respected xml files.
In the below example I have added a new Web form named as LCM Web form.
Create new classic blank HFM application in Workspace.

The workspace URL http://<servername >:19000/workspace
PROVIDE THE FOLLOWING INFORMATIONS
Empty Application created successfully

Next we return back to Shared Service.
This time we navigate to File System and open file system application
backup we have taken previously.
Define Migration [Source is file system]. This time we will move the backed up file
To the blank application we just created.
Define the target application. Our target application is newly created blank application.
Specify merging dimension/phase submission or replacing depending upon
requirement.
Execute Migration
After successful migration. We can check it from the status bar.
Check whether the application objects [Dimension, Data from, data grid got moved
into new application]
Finally the new application is mirror copy of the ClasHFM1 application.
This way we can have application back up as well as we can move to another server
and migration too.
Conclusion
If you’ve been on several EPM projects you will know that migrating from
development into QA or PROD for the very first time with LCM is no problem at all.
This is where the tool, despite its limitations with versioning and its not knowing
artifact dependencies, actually makes migration a snap.
THANK YOU
To learn more about hyperion please visit

http://learnhyperion.wordpress.com

HFM Application Migrating

Uploaded by

Copyright:

Available Formats

HFM Application Migrating

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HFM Application Migrating

Uploaded by

Copyright:

Available Formats

HFM application Migrating using LCM

Created By : Amit Sharma

Contact Point : bisp.consulting@gmail.com

We use “HFM application Migration” for two major operation

WE SELECT THE APPLICATION WHICH WE

We launch the Migration Status Report for status of Migration

List of all dimension HFM application has available in xml format.

Document available in xml format

This time we are going to do the other way around.

Create new classic blank HFM application in Workspace.

PROVIDE THE FOLLOWING INFORMATIONS

Empty Application created successfully

To learn more about hyperion please visit

You might also like