LifeCycle ManagementLifeCycle Management

June 27, 2010June 27, 2010

Philip DuPre’, Project LeadPhilip DuPre’, Project LeadRanzal & AssociatesRanzal & Associates

Introductions What is LCM? Configuration Requirements Backup an Entire Environment

Migrate to Dev / Test Tricks and Hacks

Removing an unwanted dimension Rename a Plan Type

Q & A

Agenda

INTRODUCTIONS

Founded in 1996, Ranzal has implemented Hyperion solutions for 500+ companies (800+ projects since the acquisition)

Oracle / Hyperion Platinum Partner - Highest Status

Hyperion “Americas Reseller” & “Partner of the Year” › 1999, 2005 & 2007

Certified EPM Consultants & Instructors

Vertical Expertise with High-Profile Clients from Coast to Coast› East Coast & West Coast Presence

Sound Project Methodology Insures Project Success› Support Business Applications from start to finish

One of the Largest Hyperion Practices in the U.S. 

“Best Planning & Essbase Practices with Best HFM Practice”› Hyperion Development utilizes Ranzal for Planning, Essbase and HFM product direction

About Ranzal

Regarded in the industry as one of the "BEST” at leveraging Regarded in the industry as one of the "BEST” at leveraging

OLAP technology to develop EPM ApplicationsOLAP technology to develop EPM Applications

Our team has been involved in 800+ successful EPM Implementations› Financial Consolidation & Management Reporting› Budgeting & Planning › Profitability Management Solutions› Business Intelligence and Data Warehousing › Infrastructure Planning and Performance Tuning › Business Process and Project Management

Strong client portfolio across leading Industry Sectors including

Certified consultants and instructors› Hyperion Essbase, Hyperion Planning, Hyperion Financial Management, HPCM, Hyperion

Enterprise, Hyperion Strategic Finance, Hyperion BI+ (Web Analysis, Financial Reports, Interactive Reporting, Production Reporting), Hyperion Data Relationship Management, Hyperion Financial Data Quality Management, Data Services (including ETL, Warehousing)

› Financial Services › Insurance› Retail / Consumer Packaged Goods› Manufacturing› Pharmaceutical & Hospital› Hospitality / Travel / Entertainment

› High Technology / E-business › Energy / Utilities› Distribution › Government› Other

Application & Industries

WHAT IS LCM?

Lifecycle Management

The process of moving an application or artifact from one environment to another with the same version

(Development, Test, Production)

Unified Graphical interface

Command Line capabilities

Allows tasks to be repeated via automation

Exported files can be modified to make changes easier

What is LCM?

Lifecycle Management

Allows Planning Database copy within the same environment

Can Backup the Entire Environment Shared Services Security Essbase, Planning, HFM, Reports, HBR, etc. Excel & Text Files within the Essbase DB Folder Dimensions with EPMA

Allows Selective Restores

What is LCM?

Lifecycle Management

Must manually copy files between environments

Some special characters cause errors

Reports naming convention can exceed Windows limitations

User Interface Seems repetitive

Restoration Order causes error May require several iterations to load correctly

No Detailed listing of what was restored

LCM Limitations - Global

CONFIGURATION REQUIREMENTS

Shared Services Provisioning

User ID used must be provisioned appropriately to allow access to the apps being exported or imported

Can only backup / restore what they have access to Provisioning must include LCM Administrator

Environment

Single Shared Services Foundation Multiple Shared Services Foundations

Development Test Production

Configuration Essentials

BACKUP AN ENTIRE ENVIRONMENT

Backup Source and Target Environments

(Including Relational Repository) With simplicity comes an opportunity for confusion Still an early release of this product

Key Dependencies

Install Target Environment Create Planning apps with the same initial setup

Number of years does not matter, but start year does Create the Essbase apps / databases Create HFM database

Pre-Requisites - Global

Configure Artifacts from Shared Services

Shared Services Essbase Planning Reports HFM

Save or Execute Migration Definition File

Saved Definition Files are used in Automation

Migration Definition File

Plan Type must be the same name as Source Multiple Plan Types, must be in the same order

Start Year must be the same # of years does not have to match

Must have the same base time period Months, Quarters, or Years

Currency Setting must match source

Standard dimension names must match Can edit the name in the files

Planning

A Full Planning Migration Requires 4 Areas

Essbase Only if using Substitution Variables for “All Apps”

Shared Services For Group or User Security

Planning Application Contains, Dimensions, Business Rules, etc.

Reporting & Analysis

For Member Formulas with HspUDF attribute Essbase Outline

Planning

For Planning, if you use substitution variables at “(all apps) (all dbs)”, then you will need to export these under Essbase artifact list

All the other substitution variables are contained within the Planning specific LCM artifact list

Planning - Essbase

Order of Export does not matter We are just creating text files

Order of Importing is important Shared Services Security should be 1st

Planning – Shared Services

When Exporting, you usually want to export everything A file is created for each artifact

Planning - Planning

When Exporting Reports, Generally use “Select All” button

Planning - Reports

Help Leads to very good online help from Oracle

Select All or Clear Selections Select all or Deselect all Artifacts on the screen

Define Migration Select this button to Continue

View Audit Report Auditing must be enabled to use this option

LCM Navigation

Choose your options for the Migration Wizard This is similar for each type of LCM export

Migration Wizard

Migration Wizard

Source Used to select which artifact type is active If only one is open, will skip this screen

Source Options Different depending on the type of export

Destination Pick to export to File or within the environment

Destination Options This screen may vary, but is usually repetitive

Migration Summary Summary of your choices

Migration Wizard (Con’t)

Source

Select which Application Artifacts to Define Repeats until all selected Artifacts have been defined

Source

Source Options

Shared Services May Select Groups

Essbase No Selections

Planning No Selections

Reports Uncheck Export Job Output Click Next

Source Options

Destination

When exporting to file, this option is the same for all apps For Planning and Essbase it is possible to export to another database,

more on that later

Destination

Destination Options

This is just a review of the Options chosen for each App

Destination Options

Migration Summary

This is a Review of All the Options Chosen for All Apps

Migration Summary

Click “OK” or “Launch Migration Status Report”

Status Report will show “In Progress” while export is running

Click “Refresh” until job shows “Completed”

Launch Migration

Where did the Export go?

Under Application Groups - File System ODTUG_2010_Essbase ODTUG_2010_SS ODTUG_2010_Planning ODTUG_2010_Reports

On the Shared Services / Foundation Server E:\Hyperion\Common\import_export directory Under the UserID you performed the export as Under the folder we used in the export

LCM Export

Restoring Full Environment

Copy the physical files to the Target environment On the Shared Services / Foundation Server

E:\Hyperion\Common\import_export directory Under the UserID you want to Restore under

Can Create this if it Does Not Exist Copy the exported folder intact

Login to SS using the same UserID which the files were copied under in the files system

Under “Application Groups”, open “File System”

Move Files

The Import Order is Crucial

Create “stub” databases Applications are not created by LCM Planning Application must exist

Multiple Plan Types, must be in the same order Identical Start Year, Currency, Base Time Period Standard Dimension Names must match Source

Load Shared Services Security Essbase Servername is often different than Source

Must modify the files to reflect this difference

Load Essbase Global Substitution Variables “All Apps” – “All DBs”

Import Order

The Import Order is Crucial (Con’t)

Restore Planning HspUDF attribute requires Essbase Outline restore Some Pre-requisites are loaded later, Try Again Error listing only lists what did not load

Restore Essbase Databases Existing Essbase migration tools work better

Restore Reports

Import Order (Con’t)

HFM Migration

Documents (including Folders) Grids, Forms, TaskLists, Custom Documents

System Reports

MetaData (Classic or EPMA)

Rules (Classic or Calc Mgr)

Security

Journal Templates & Groups

Does Not Migrate Data or Journal Entries

HFM Migration

HFM Specific Items

HFM Destination Options

HFM Options

Can Migrate the Dimensions Housed in EPMA

Accessed via Foundation Application Group

LCM can load artifacts

Use Application Library to Deploy Changes

May use EPMA File Generator utility Create .ads files to export dimensions Can Import dimensions from .ads files

LCM - EPMA

LCM – EPMA (Con’t)

Scripting the Backup

Migration Definition

Click Save Migration Definition

Choose Save Select a Location Click Save

Migration Definition

When Download is Complete Click Close

Open the MigrationDefinition File Goto the Shared Services Line Find User=“” Password=“”

Migration Definition (Con’t)

Enter the LCMAdmin UserID and password The password will be encrypted after the first time it is used

The job is run using “Utility.bat” under the LCM directory E:\Hyperion\common\utilities\LCM\9.5.0.0\bin\Utility.bat

Call Utility.bat MigrationDefinition.xml > LCMMigration.Log

Migration Definition (Con’t)

The exports go to the same place

On the Shared Services / Foundation Server E:\Hyperion\Common\import_export directory Under the UserID you performed the export as Under the folder used in the export

You will want to remove these folders before running the script again. LCM does not overwrite export folders

Planning - Exports

TRICKS AND HACKS

Copy a Planning App in the Same Environment

Prepare a “Destination” Stub Planning App Perform an LCM backup

Select All members (Including Security?) Same Source Options …

At Destination, instead of File, Choose the Stub Planning App

Planning Copy

Removing an Unwanted Dimension (Planning) A dimension was added by “accident” and needs to be removed

Backup the current environment using LCM Delete the Current Planning App Recreate the Current Planning Base Application When restoring from LCM do not restore that dimension

Delete a Dimension

Rename a Plan Type (Planning) It is decided a Plan Type should have a different name

Backup the current environment using LCM Delete the Current Planning App Recreate the Current Planning Base Application

Locate the LCM Export Make a Copy of the Files Modify the files to reflect the desired change

Rename a Plan Type

Go to the “Plan Type” directory under the resource structure

Change the “Old_Name” directory to be “New_Name”

Rename a Plan Type (Con’t)

Locate the LCM Export

Modify the listing.xml file Replace “Plan Type/Old_Name” with “Plan Type/New_Name”

Rename a Plan Type (Con’t)

Restore a Single Business Rule

After backing everything up you can restore one or many items

You can move a single form from Dev to Prod using LCM

You can restore a form from backup using LCM Provided your backup includes an LCM export

Restore a Single Artifact

When migrating EPMA HFM application, if the source and target names are different:

Change the name within listing.xml Change the subdirectory name

EPMA Migration

Philip DuPre’Philip DuPre’pdupre@ranzal.compdupre@ranzal.com

Questions

LifeCycle ManagementLifeCycle Management

June 27, 2010June 27, 2010

Philip DuPre’, Project LeadPhilip DuPre’, Project LeadRanzal & AssociatesRanzal & Associates