Migrating artifacts using Hyperion LCM

1.      Overview

Lifecycle Mangement: Lifecycle Management provides a consistent way to migrate an application, a repository, or individual artifacts across product environments and operating systems.We can migrate application artifacts using Shared Services Console or Lifecycle Management Utility.

Migrating Scenarios:

1. When the source and destination appicaltions are registered with the different instance of Shared Services, i.e. when source and destination servers are on different environments,ex: you are migrating applications from Dev to Test, Test to Prod etc.

2. When the source and destination applications are registered with the same instance of Shared Services, Ex: Copy an application within an environment.

2.      Artifacts

Application Artifacts by Module

Module	Artifacts
Shared Services	User and Group Provisioning  Projects/Application Metadata
Essbase	Files (.csc, .rpt, .otl, .rul) Data Filters Partitions Index and Page files (drive letters) Application and Database properties Security
EAS/Business Rules	Rules Locations Sequences Projects Security
Hyperion Planning	Forms Dimensions Application Properties Security
Hyperion Financial Management	Metadata Data Journals Forms/Grids Rules Lists Security
Financial Data Quality Management	Maps Security Data Metadata Scripts Security
Reporting and Analysis (Workspace)	Reports Files Database Connections Security

3.      Procedure

Lets Migrate the App1 Planning Application from one environment to other: 

3.1.     Select source application and artifacts to be migrated

Log into Shared services, under Application Groups select the application which you want to migrate, once done select the artifacts,

 When you click on define migration it will take you to the migration wizard, Confirm source application to be migrated.

3.2.     Migrate source artifacts to Source File system

Because I want to migrate my application to a different environment I need to take a file system back up of the App1 Application, there is no need to give the location, it will automatically be stored at the pre defined location(we can set this location as well, more in detail later). The default location is: Oracle\Middleware\user_projects\epmsystem1\import_export\<userName>@Native Directory\

 You can save the migration definition file for future use, and click on Define Migration,

 You can click on Launch Migration Status Report to check the status of the migration, it will take you to the following window,

 Migration will take some time and this time depends on the size of the application, you can click on the refresh button to refresh the status of migration. After you see the completed status you can find the file system back up under the File System Folder under Application Group Management,

  If you want to have a look at the folder which is created you can check at location specified above, if you are on distributed environment you will find this folder on the Foundation Services' Server

3.3.     Migrate artifacts from source file system to Target file system

Now lets create a folder and copy the file system backup to destination server at the same location, now if we login to shared services again we will find this folder under File System,.

as per our example: Oracle\Middleware\user_projects\epmsystem1\import_export\admin@Native Directory\DevBkup09092011_11_28AM\

3.4.     Migrate artifacts from Destination File System to Destination environment.

Now we need to perform an import on the destination server, this time select DevBackup0909201111_28AM under the file system, and select all artifacts, 

 Now in Migration Wizard this File System backup will be your source and TgtApp1 will be your target application. You need to be very careful when you choose source and destination otherwise this will screw other applications if you chosen anything wrong.

 Once done you can check Migration summary to ensure the complete migration.

Hyperion Workspace and Shared Services URL without port numbers

When an application is accessible via a network it means that it is using a TCP/IP port. When a port is used by an application, it cannot be used by another one. Even during installation/deployment, we will get an error message stating that a particular port is being used by another application. Therefore, the skill to find out what port is being used by what application comes in very handy.

If you want to find out what is using a specific Port, you can open the COMMAND PROPMT and type in
netstat -aon findstr "6800"

Default port numbers of Hyperion EPM System:

Sr No	Name of Service	Default Port Number
1	Shared Services	28080
2	Workspace	19000
3	Planning	8300
4	Essbase	13080
5	Essbase Agent	1423
6	HFM	80
7	Weblogic	7001

Recently, I have installed and configured one server environment for Hyperion EPM V11.1.2.1. Shared Services and Workspace URL's were accessible using following two URL's 

http://MyServer:19000/workspace/index.jsp

http://MyServer:28080/interop/index.jsp

But, as per the client's requirement, port numbers were not required while accessing final URL's of Hyperion EPM system.

It is possible if we change default port of accessing URL's to 80. To implement the same, complete following steps:

1- Stop all Oracle/Hyperion services
2- Launch EPM System Configurator
3- Choose to modify existing EPM Oracle Instance
4- On configuration tab, uncheck all actions and only check "configure web server" option found below Hyperion Foundation
5- Choose your web server and specify the new port
6- Keep other selections as defaults and press next
7- Continue until your configuration is completed then press finish
8- Start all Oracle/Hyperion services

Now, my URL's are accessible using following URL's

http://MyServer/workspace/index.jsp

http://MyServer/interop/index.jsp