Setting up automated Hyperion-Essbase Migrations in 11.1.1.3 with Life Cycle Management

What is LCM?

One of most attractive features of version 11 is Life Cycle Management.  It is by far the biggest step that Oracle has taken in a true migration utility that has made migrating applications from DEV to TEST to PROD easier than ever before. But it does come with its share of nuances.

LCM actually existed in 9.3, but it was more of a command line tool that was integrated with Workspace, and it did not really offer a good solution to security and provisioning.  LCM is now integrated (and installed) with Shared Services with a much easier to use GUI interface.

What it does

LCM migrates entire applications or individual “artifacts” between environments.  If the environments share a common Shares Services, the migration can go directly from application to application.  However, more commonly, the environments use separate Shared Services, so most migrations are done by exporting and importing to/from the file system.

The exports are stored in $HYPERION_HOME/common/import_export/<user>

Each user has directory here that stores their exported LCM artifacts.  The exports are organized into a logical directory structure.  Some use this structure to ZIP up entire applications and use them for version control and release management.

For Essbase, LCM will copy most everything that is needed for an Essbase Application, including

  • Definitions of all databases within the applications
  • Outlines
  • Substitution Variables
  • Rule Files
  • Calculation Scripts
  • Report Scripts
  • Excel Files
  • Location Aliases
  • Security Filters

It does not do

  • Data
  • Versioning
  • MXL files
  • Triggers
  • Partition definitions,
  • custom defined macros/functions

Prerequisites

  • In addition to product provisioning, users must be provisioned to the LCM Administrator Role.  For Essbase, a user needs Server Access, Calc, and Database Manager privileges.
  • Essbase must be in Shared Services Mode
  • Environments must be same software release version
  • LCM does not create applications, so the target app must exist, with the same name
  • During export, the source applications need to be running, and likewise, on import, the target applications need to be running.
  • When performing a migration, if the source artifacts have an earlier time stamp than the destination artifacts, the artifacts will not get migrated.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: