HFM Application Migrating
HFM Application Migrating
HFM Application Migrating
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.
HFM application Migrating using LCM
All the artifacts are displayed. We select the required artifacts. For complete
migration or back up we select all.
HFM application Migrating using LCM
Next we define the Migration properties by launching DEFINE MIGRATION
HFM application Migrating using LCM
We define the Source application.
First the source application defined is shown.
NEXT WE need to define the Destination
HFM application Migrating using LCM
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
HFM application Migrating using LCM
Displayed source application and target application group.
HFM application Migrating using LCM
Migration Summary.
HFM application Migrating using LCM
When we decide that all the steps for migration has been successfully
Performed , we Execute migration
Migration Status
Report for status of
Migration
HFM application Migrating using LCM
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.
HFM application Migrating using LCM
We browse to see the folder structure and components 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.
HFM application Migrating using LCM
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
Check whether the application objects [Dimension, Data from, data grid got moved
into new application]
HFM application Migrating using LCM
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.
HFM application Migrating using LCM
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