1. Lifecycle Management Guide
  2. Getting Started With Lifecycle Management
  3. Lifecycle Management Requirements

Lifecycle Management Requirements

Prerequisites to Using

  • Install and configure Oracle Hyperion Shared Services and Oracle Enterprise Performance Management System products and verify that they are running.

  • Ensure that the user performing Oracle Hyperion Enterprise Performance Management System Lifecycle Management operations is assigned the LCM Administrator role.

  • Assign additional product-specific roles as required. See the appendixes at the end of this guide.

Source and Destination Considerations

  • The source and destination environments must use the same user directory.

  • During Lifecycle Management export and import operations, the product services must be up and running.

File System Considerations

  • When migrating to and from a file system, the file system should be accessible to Oracle Hyperion Shared Services Console or the Lifecycle Management Utility on the network.

  • The default destination for the file system is on the Shared Services Java web application server computer; ensure that space is allocated on the Shared Services computer.

    The default file system destination on the Shared Services computer is MIDDLEWARE_HOME/user_projects/epmsystem1/import_export. The file system location is defined in the migration properties. This can also be customized to use a shared disk. See Editing Migration Properties.

Upgrade Considerations

When upgrading from the previous release, the content exported from Lifecycle Management must be extracted in the import_export location.

Applications and Application Groups

  • If the application being imported does not exist in the target environment, Lifecycle Management creates an application shell.

  • Applications must be assigned to an application group or belong to the Default Application Group before migrations can occur. You cannot migrate applications belonging to the Default Application Group if two applications with the same name exist.

    Note:

    Only the Default Application Group can have multiple applications with the same name. However, artifact migration cannot occur unless they are assigned to another Application Group.

  • If the application being imported belongs to an application group that does not exist in the target environment, Lifecycle Management will create the application group.

Availability of the EPM System Environment During Lifecycle Management Migration

Lifecycle Management operations for incremental migration of artifacts can be performed during normal usage of the application with the following exceptions:

  • For complete migration of an application or a repository from one environment to another, Oracle recommends that the systems be in maintenance window.

  • In Oracle Hyperion Financial Management, if the dimension metadata artifact is imported, the current user sessions of that application are invalidated, and users must reopen the application.

Note:

There are no limitations for Oracle Hyperion Planning, Oracle Hyperion Calculation Manager, Oracle Essbase, and Oracle Hyperion Financial Reporting.

Other Important Points

  • Do not use Lifecycle Management as your only means of backup and recovery. See Backup and Recovery.

  • Deployment metadata artifacts contain physical server names and configuration information for the deployment. This information should not be migrated from one environment to another (for example, from Dev to Test). Migrating this data would corrupt the configuration information on the destination environment and would make the system unusable. See Deployment Metadata and Lifecycle Management.

  • Lifecycle Management migration fails for artifacts and folders with the same name as a Windows-reserved name; for example, CON, PRN, AUX, NUL, and so on. (For a complete list of reserved names, refer to the vendor's site for your operating system.)

  • Single-artifact export should only be used with artifacts that can be modified on the file system. See the product appendixes for information on which artifacts can be modified on the file system.