Document: What you should know

Migrating Hyperion Planning Application using LCM

History:
Version 0.1 Description Change Initial Draft Author Amit Sharma Publish Date 01-Dec-2011

www.hyperionguru.com

www.bisptrainings.com

Below are the important points one should remember while working with LCM for migration and backing up Hyperion Planning Application a) When performing a composite application migration like Planning, you must perform the import operation in the following order: Performance Management Architect, Shared Services, Essbase, Reporting and Analysis, Planning, Financial Management, and Profitability. b) The source and destination environments must be on the same release number. Data migration is not supported. c) The following EPM System products are not integrated with LCM: Strategic Finance, FDM, ERP Integrator, Essbase Studio, and Essbase Integration Services. d) Do not use LCM as your only means of backup and recovery. e) Do not migrate artifacts under Shared Services deployment metadata. These artifacts are environment-specific and should not be migrated. f) Direct application-to-application migration can happen only within the same environment such as Development, Test, and Production. Plan for an export to the file system and import from the file system when migrating artifacts across environments. g) Do not use quick edit features (export for edit and import after edit) if you want to export an artifact from one environment and import it into another environment. The quick edit feature is only for editing and replacing the artifact in the same environment

www.hyperionguru.com

www.bisptrainings.com