Learning Life Cycle Management (LCM): Command Line Security Synchronization

Printer Friendly This purpose of this article is to introduce the command line Life Cycle Management(LCM) utility in Oracle EPM. The LCM tool can be used to export and import objects that can be found within the Oracle EPM Environment. This includes Security, Essbase, Hyperion Planning, Financial Management … etc. As once gets more familiar with LCM, one comes to realize how powerful the tool is and how empty life without LCM was. Without LCM some of the more detailed artifacts within an application were difficult to move between environments. LCM provides a centralized mechanism for exporting and importing nearly all of the objects within an Oracle EPM application or module. The table below is listed to get an idea of all the facets of LCM.

Application Artifacts by Module
Module Shared Services Artifacts User and Group Provisioning Projects/Application Metadata Files (.csc, .rpt, .otl, .rul) Data Filters Partitions Index and Page files (drive letters) Application and Database properties Security Rules Locations Sequences Projects Security Forms Dimensions Application Properties Security Metadata Data Journals Forms/Grids Rules


EAS/Business Rules

Hyperion Planning

Hyperion Financial Management

Lists Security Maps Security Data Metadata Scripts Security Reports Files Database Connections Security

Financial Data Quality Management

Reporting and Analysis (Workspace)

The LCM tool is integrated into the Shared Services Web Interface. If can be found under the Application Groups tab. Within the application groups there are three main areas of interest: 1. Foundation – includes Shared Services security such as Users/Groups and Provisioning. 2. File System - This is where the exported files will go by default. The default location is to be stored server side, on the Shared Services server in the location: E:\Hyperion\common\import_export Under this main folder, the contents are broken out by the user account that performed the export. Within the export folder, there is an “info” folder and a “resource” folder. The info folder provides an xml listing of the artifacts contained within the export. The resource folder contains the actual objects that were exported. The LCM Command line tool provides more flexibility because it can be installed on any machine and the results can be directed to output to any local folder. Sometimes this is very useful if the Shared Services node is a Unix machine, and the LCM users are unfamiliar with Unix. Simply install the LCM Command Line Utility on the Windows machine and redirect its output to a local Windows folder using the –local command line option. 3. Products and Applications – Each registered product will be listed and provide a mechanism to export and import the respective objects for the associated applications, Essbase, Planning…etc.

Going Command Line
The Shared Services LCM GUI is a great way to become familiar with the LCM tool. However, when it is time to start automating LCM tasks and debugging issues, the Command Line LCM utility is very helpful. To get started, the LCM Command Line tool requires a single command line argument, an xml file that contains the migration definition. The quickest way to obtain the

0.xml Attempting to load Log Config File:. “Execute Migration” or “Save Migration Definition”. open a command line and run Utility.Executing package file E:\Hyperion\common\util ities\LCM\9.421 WARN .0./conf/log.xml 2011-03-20 11:50:49.Audit Client has been created for the server h ttp://hyp13:58080/interop/Audit 2011-03-20 11:50:58. That is pretty much all there is to it… move the xml migration definition file to the location you have installed LCM. \Hyperion\common\utilities\LCM\9.968 INFO .0\bin\SampleExport.0\bin>Utility.0.0\bin. Two options are presented.xml >>> Enter username .Going to buffer response body of large or unknow n size. Choose “Save Migration Definition” to save the migration definition to a local file. For instance.bat as indicated: E:\Hyperion\common\utilities\LCM\9.5. .bat SampleExport.015 INFO . select Define Migration to pull up the LCM Migration Wizard.5.xml file is to use the Shared Services LCM Web interface to select the objects you wish.admin >>> Enter Password-----------2011-03-20 11:50:57.5. Using getResponseBodyAsStream instead is recommended.. and follow the prompts until the last step.

281 INFO . it is not as straightforward as simply running an export from one environment and importing into another environment. HSS log file is in E:\Hyperion\common\utilities\LCM\9. a list of items to be deleted must be supplied.5.0\bin> LCM Example: Synchronizing Shared Services Security between Environments LCM often requires moving objects and security between environments. such as from a development environment to a production environment. 4. Step 1 and 4 are the typical import/export operations – where security is exported from one environment and imported into another environment. two additional steps are necessary. removing provisioning too. the users and groups in the target environment are deleted.2011-03-20 11:51:03.Audit Client has been created for the server htt p://hyp13:58080/interop/Audit 2011-03-20 11:51:03. it will not handle removing user provisioning.421 INFO . Below are some sample XML migration definitions for each step: .Success E:\Hyperion\common\utilities\LCM\9.0.0\logs\LCM_2011_0 3_20_11_50_48_0.Migration Status .687 INFO .log 2011-03-20 11:51:32.5. The reason is that LCM imports work in a “create/update” mode. While LCM makes it easy.437 INFO . However. ensuring no residual artifacts remain in the environment. the steps to sync provisioning using LCM would be: 1. removing or changing groups.0. To use the LCM delete operation. This leaves an empty. This is where Step 2 comes in.Message after RemoteMigration execution Succes s. In other words. 3. Export Users/Groups/Provisioning from Source Environment Export Users/Groups from Target Environment Delete Using Step 2 Results the Users/Groups in Target Environment Import Users/Groups/Provisioning into Target Environment Essentially. clean environment to then import security. or essentially removing users from the system. a simple export of the Users and Groups in the Target environment will provide the necessary information to provide to Step 3 – deleting the respective users and groups. the operations performed in LCM are typically additive in nature. This can be an easy oversight. 2. At a high level. In Step 3.MIGRATING ARTIFACTS FROM "Foundation/Shared Serv ices" TO "/SampleExport" 2011-03-20 11:51:32. but it will ensure that the security becomes out of sync over time and can cause issues as well as security implications. While the typical LCM method would capture new users and new application provisioning.

in the Target system.0" encoding="UTF-8"?> <Package name="web-migration" description="Migrating Shared Services to File System "> <LOCALE>en_US</LOCALE> <Connections> <ConnectionInfo name="MyHSS-Connection1" type="HSS" description="Hyperion Shared Service connection" . <?xml version=”1. Simply redirect the results into the local folder. You can use LCM to redirect the output to keep the results all in the same environment (the target system) by using the command line option [-local/-l] (run utility.Step 1 – Export Users/Groups/Provisioning from Source Environment Note: By default the results will be sent to the source Shared Services server in the “import_export” directory. \Hyperion\common\import_export.0” encoding="UTF-8"?> <Package name="web-migration" description="Migrating Shared Services to File System "> <LOCALE>en_US</LOCALE> <Connections> <ConnectionInfo name="MyHSS-Connection1" type="HSS" description="Hyperion Shared Service connection" url="http://sourceSvr:58080/interop" user="" password=""/> <ConnectionInfo name="FileSystem-Connection1" type="FileSystem" description="File system connection" HSSConnection="MyHSS-Connection1" filePath="/Step1ExportFromSource"/> <ConnectionInfo name="AppConnection2" type="Application" product="HUB" project="Foundation" application="Shared Services" HSSConnection="MyHSS-Connection1" description="Source Application"/> </Connections> <Tasks> <Task seqID="1"> <Source connection="AppConnection2"> <Options> <optionInfo name="userFilter" value="*"/> <optionInfo name="groupFilter" value="*"/> <optionInfo name="roleFilter" value="*"/> </Options> <Artifact recursive="false" parentPath="/Native Directory" pattern="Users"/> <Artifact recursive="true" parentPath="/Native Directory/Assigned Roles" pattern="*"/> <Artifact recursive="false" parentPath="/Native Directory" pattern="Groups"/> </Source> <Target connection="FileSystem-Connection1"> <Options/> </Target> </Task> </Tasks> </Package> Step 2 .bat without any command line options to see help for your version of LCM).Export Users / Groups from Target Environment <?xml version="1.

url="http://targetSvr:58080/interop" user="" password=""/> <ConnectionInfo name="FileSystem-Connection1" type="FileSystem" description="File system connection" HSSConnection="MyHSS-Connection1" filePath="/Step2UsersGroupsTarget"/> <ConnectionInfo name="AppConnection2" type="Application" product="HUB" project="Foundation" application="Shared Services" HSSConnection="MyHSS-Connection1" description="Source Application"/> </Connections> <Tasks> <Task seqID="1"> <Source connection="AppConnection2"> <Options> <optionInfo name="userFilter" value="*"/> <optionInfo name="groupFilter" value="*"/> </Options> <Artifact recursive="false" parentPath="/Native Directory" pattern="Users"/> <Artifact recursive="false" parentPath="/Native Directory" pattern="Groups"/> </Source> <Target connection="FileSystem-Connection1"> <Options/> </Target> </Task> </Tasks> </Package> Step 3 – Delete Users/Groups in Target Environment <?xml version="1.0" encoding="UTF-8"?> <Package name="web-migration" description="Migrating File System to Shared Services"> <LOCALE>en_US</LOCALE> <Connections> <ConnectionInfo name="MyHSS-Connection1" type="HSS" description="Hyperion Shared Service connection" url="http://targetSvr:58080/interop" user="" password=""/> <ConnectionInfo name="AppConnection1" type="Application" product="HUB" description="Destination Application" HSSConnection="MyHSSConnection1" project="Foundation" application="Shared Services"/> <ConnectionInfo name="FileSystem-Connection2" type="FileSystem" HSSConnection="MyHSS-Connection1" filePath="/Step2UsersGroupsTarget" description="Source Application"/> </Connections> <Tasks> <Task seqID="1"> <Source connection="FileSystem-Connection2"> <Options/> <Artifact recursive="false" parentPath="/Native Directory" pattern="Users"/> <Artifact recursive="false" parentPath="/Native Directory" pattern="Groups"/> </Source> <Target connection="AppConnection1"> <Options> <optionInfo name="operation" value="delete"/> .

. can also be manually copied from the source to the target environment without using the redirection to a local folder technique.0" encoding="UTF-8"?> <Package name="web-migration" description="Migrating File System to Shared Services"> <LOCALE>en_US</LOCALE> <Connections> <ConnectionInfo name="MyHSS-Connection1" type="HSS" description="Hyperion Shared Service connection" url="http://targetSvr:58080/interop" user="" password=""/> <ConnectionInfo name="AppConnection1" type="Application" product="HUB" description="Destination Application" HSSConnection="MyHSSConnection1" project="Foundation" application="Shared Services"/> <ConnectionInfo name="FileSystem-Connection2" type="FileSystem" HSSConnection="MyHSS-Connection1" filePath="/Step1UsersGroupsSource" description="Source Application"/> </Connections> <Tasks> <Task seqID="1"> <Source connection="FileSystem-Connection2"> <Options/> <Artifact recursive="true" parentPath="/Native Directory" pattern="*"/> </Source> <Target connection="AppConnection1"> <Options> <optionInfo name="operation" value="create/update"/> <optionInfo name="maxerrors" value="100"/> </Options> </Target> </Task> </Tasks> </Package> Troubleshooting with Command Line LCM LCM can be a great tool when it works flawlessly. it can quickly become part of mission critical activities like promoting artifacts from development to production. Consequently. The respective folder.<optionInfo name="maxerrors" value="100"/> </Options> </Target> </Task> </Tasks> </Package> Step 4 – Import Users and Groups into Clean Target Environment This step assumes that Step 1 was redirected onto the target environment within the import_export directory. it is necessary to learn some troubleshooting skills to maintain business continuity using LCM. <?xml version="1. However. Step1UsersGroupsSource.

5. I‟ve seen countless LCM issues where bouncing the environment clears the issue up. Substation Variables. you‟ll want to be sure to do that. The configuration ties everything together. 7. Essbase can export a number of objects. With this installment I‟ll review the Installation and Configuration activities necessary for a Hyperion 11. Brinkman | In: Hyperion Enterprise Performance Management · Hyperion Essbase · Hyperion Financial Reporting · Hyperion Planning · Hyperion Workforce Planning · Hyperion Workspace · Best Practices · Upgrades and Migrations Printer Friendly "Installation and Configuration" In installment #1 and #2 of this guide. Rule Files. the Oracle Knowledgebase to search for more information. The installation can takes place first and it only lays out the files to run the system. 8. This will cover both including the following items:  Hyperion Fusion Installer and How it Works . 6. Usually it will provide some detail about the error that was received. Part 3 of 5 Nov 6 2009 Posted by C. Hyperion Release 11 Architecture and Installation. and Security.1. Report Scripts. we reviewed the architecture considerations and preinstallation requirements. The installation and configuration are separate items. and creates services. If you haven‟t read the two previous post or haven‟t read the Hyperion “Installation Start Here” guide. Check release notes in patches for enhancements/bug fixes in LCM.0\conf in log. Turn on debugging for the command line LCM tool. LCM is an emerging technology and can sometimes just be in a bad state. 5. LCM is an emerging technology and is still somewhat buggy (especially older versions). deploys applications. Look for special characters that might be present in your data. 2. For instance. Try only a subset of the initial objects. Restart the environment. There are instances where special characters can mess up the parsing.xml <param name="Threshold" value="info" /> 4.x environment.log in ORACLE_HOME\logs\SharedServices\SharedServices_LCM. Try one at a time to determine which part of the whole is failing. Look for patches – as mentioned previously. creates repositories. Use Google. Location Aliases.T.xml and hss-log. Review the server side Shared_services_LCM. LCM is a java tool and uses xml and text files to transmit data. Review the output of the LCM operation. Outline. Calc Scripts. Change the line “info” to “debug” in the files E:\Hyperion\common\utilities\LCM\9.log 3.0.

1. and HFM.1. Planning. For our example we are going to assume the client is using Foundation. Under the Fusion Installer create a folder called “assemblies”.1. So let‟s get started on this installation already.x Oracle Hyperion Enterprise Performance Management System Manual Deployment Guide Release 11. Hyperion Fusion Installer and How it works. You are probably looking at something in the neighborhood of 4GB to download. The first thing to do is download the Fusion Installer and copy it to each server in your architecture.1.x Fusion Edition is the Fusion Installer.   Preparing the Fusion Installer Using the Fusion Installer Hyperion Configuration Utility The companion Hyperion Documentation for this post is either of the following documents found in the Oracle Documentation Library: Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide Release 11. It is a nice application for guiding you through the installation. One of the great features of Release 11. when unzipped contains a group of folders looking something like this: . Each download.x You probably are not going to read them in their entirety since they are rather lengthy but they are very useful in fully understanding what is going on and priceless for complex environment or when things don‟t go well. Preparing the Fusion Installer You‟ll next need to download the remaining Foundation Services as well as any other applications you are using. The Fusion Installer is only the shell for the rest of the installation.

refer to the Installation and Configuration Guide. If you are missing something. the Fusion Installer will let you know in the status window at the bottom application.Each server will need the appropriate assemblies copied to its own \<FusionInstaller>\assmblies directory. Using the Fusion Installer As you start the Fusion Installer you will see something like this: . whenthe Fusion Installer starts. Some of the common components are needed on each server. it knows what is available to install. This way. For details on which assemblies are required for each application.

creating relational repositories. After the installation is complete. It looks something like this .I like to choose “Choose Components Individually” since it feels like I have a little more granularity. It seems to work pretty well when all the components on a server are chosen together. This application will guide you through the configuration with such things as creating and distributing Java applications. you are committed. each server will have a Configuration Application. The EPM System Configurator displays the installed components and then you can select which components to configure. Once the configuration starts. Configuration The first thing to do is to configure Shared Services. It can be launched on a Windows Server from Start >Oracle EPM Applications > Foundation Services > EPM System Configurator. The last thing to do is to review all the install logs for any errors. It is much easier to catch them now than after the configuration is started before anything is written specific is written to registries and relational databases. The Fusion Installer only lays out the application files. it doesn‟t need any information so the sequence of installation can occur in any order. and building the Windows Services. this is run on every server in the architecture. At this point I‟ll select all of the components I want to install on each server. Once again.

launch Shared Services and verify that it is working appropriately. You will want to be careful with each screen to make certain every component is configured as you planned. This needs to be done by itself and before any other components are configured. The Oracle . When I‟m comfortable with the configuration. The documentation also says that some of the repositories need to be separate. If it isn‟t.The first thing to do is configure Shared Services. it is also probably best to go ahead and configure any external authentication provider at this time. you can move from server to server configuring all the components. The last thing to do is to redeploy Workspace so it is configured to proxy all the remaining Web Applications. I usually start with all the Foundation Services and then make sure Workspace functions before moving on to the EPM application like Planning and Financial Management. Better to catch an error now than later. I prefer to do it one at a time to be certain I can keep all the relational repositories separate and I can validate each component as it is competed. As soon as this is complete. I shut everything down and bring it back up. The documentation says that you can configure all the components at once but this will attempt to configure all the selected products in the same relation schema/table. When Shared Services is complete and verified. If you are able to log in to Shared Services. The start order is quite finicky. I like to review all the configuration logs on each server very carefully. it‟s will be a long day. As with the installation. It is easy to keep hitting „NEXT‟ only to find out you mixed your Calculation Manager Repository in with your Shared Services repository.

Print Server Hyperion Financial Reporting . 15. Hyperion Annotation Service 4. we‟ll discuss validation in the next part. 27.NET JNI Bridge Performance Management Architect Web Services Essbase Server Administration Services Application Server Smart Search Application Server Essbase Studio Server Provider Services Application Server Hyperion Financial Reporting .Task Manager 10. Shared Services OpenLDAP 2. 24. 13.Report Server Hyperion Financial Reporting . 21. EPM Workspace UI (CMC UI) 6.Installation and Configuration Guide has specifics regarding the start order but I usually do something like this: 1. 18. 12. EPM Workspace Web Server 7. EPM Workspace Agent (CMC Agent) 5. Shared Services Application Server 3. Assuming everything starts. Hyperion RMI Registry 9. 26.Web Application Calculation Manager Planning Application Server Financial Management Hyperion Financial Management DME Listener Hyperion Financial Management Web Service Manager Hyperion Financial Data Quality Management .Event Manager Hyperion EPM Architect . 16. 17. 25. 22. 11. 23.Scheduler Server Web Analysis Application Server Performance Management Architect Application Server Performance Management Architect Data Synchronizer Application Server Financial Reporting . 29. . 19. Performance Management Architect Services Process Manager automatically starts the following services:     Hyperion EPM Architect .Job Manager Hyperion EPM Architect .Engine Manager Hyperion EPM Architect ..Java RMI Registry Hyperion Financial Reporting . EPM Workspace Application Server 8. 20. 14. 28.

you guessed it. In version 11. outlines. it still stores numbers. including its data and all of its objects. Typed Measures Essbase now stores text! Well. Technically. as well as a full API for those who want to customize the process even further. Varying Attributes Attributes have been around for a while now in Essbase. assume we have an attribute that identifies our customers into tiers based on their credit score. functional additions that might peak your interest. This console gives administrators the ability to compare applications. . As with most product releases. an option in EAS exists to backup the entire database. Essbase now includes the option to log transactions and replay them. this is a nice feature to ensure you don‟t lose valuable work. that number is converted to the associated text value in the enumerated list.Upgrade to Essbase 11 and enjoy a host of new features There are a host of new features in version 11. and calculate measures for attributes that vary over multiple dimensions. and stability. One limitation has been the inability to walk forward attributes over time. which is what is in the database. A member in the measures dimension can have a text attribute. somewhat. First. It comes with a command line tool to automate tasks. Members can also be tagged as Date. Secondly. Lifecycle Management Shared Services now provides a consistent way to manage environments. But. and perform artifact migrations. Now. there are some new options for BSO databases. which changes the formatting to. but it represents a string. If a customer‟s score changes such that they move to a higher or lower tier. This member is associated with an enumerated list. For example. With this option turned on. very notable. there are some other. When changing things rapidly through the day. there are the typical improvements related to memory. Not anymore. Backup and Recovery I have seen many methods to making sure Essbase applications are secured. the history is lost because their attribute is the same for all time periods. search for artifacts. a date. a database can be restored to a specific point in time. The entire database can easily be restored. Text measures give administrators a way of storing a value other than a number in a data intersection. Some people hate them and some love them. scripting. and reports) and keeping data exports. Essbase applications can be restored with the option to replay all transactions that occurred after the backup occurred. When reporting is done. This is much quicker than manually archiving all the objects (calc scripts. Varying attributes adds the capability of Essbase to store. load rules. Each member in that list has an index number. They definitely have their place in the design of a database. to one file.

Now. The first and most obvious is to remove the values from the database. This can be very helpful when using partitions. Override Implied Shares Essbase now includes an option in the outline management section to ignore the default setting for implied shares. DATEDIFF will take the difference between two dates at the interval designated. Version 11 has access to not only Essbase variables. Monitoring Environment Reponses Many environments take advantage of partitioning. DATEPART will pull the time period (week. etc) from any date.cfg file. with a folder for each of the Hyperion products. in previous releases of Essbase. Common Log Locations Version 11 organizes all log files in one location. administrators can log transaction response times. but operating system environment variables as well. they are now located in one common folder. DATEROLL will increase a value based on a specific time interval. . Using the ENABLE_DIAG_TRANSPARENT_PARTITION configuration setting in the essbase. there are a host of functions that open up a whole new realm of possibilities. Rather than searching through each products‟ directory tree for the area logs are stored. These operations were difficult at best. month. resulting in a total of zero. day. This is a very nice improvement. as well as a host of other situations. Notable Calculations Additions Now that members can carry a text or date value. The use of Environment Variables If your process management uses variables to decrease maintenance tasks from. this might be something that will intrigue you. there is a way to evaluate the cost of using partitions.ASO Data Management ASO now includes Maxl scripting to enable administrators to clear data from regions of a database in two ways. The second is the ability to copy the data into another member as the inverse.

As part of any installation. and the distribution of Hyperion components 2. and the core BI applications. the Hyperion architecture establishment and installation activities in our organization cover the following five areas. Installation – Running the installation and configuration utilities 4. 1.NET Configuration I‟ll start with the Web Application Server Specification. we reviewed the architecture considerations and defined a simplistic architecture to use as a reference moving forward. For the sake of simplicity I will be using the example of a common installation. Hyperion Financial Management (HFM). some items need to take place before the Fusion Installer is started. Provide Pre-Installation Requirements – Provide the client with a detailed list of activities prior to the installation 3. I like to create a checklist of things that need to be done.        Web Application Server Specifications Relational Repository Information General System Administration Network Information Additional Components DCOM Configuration IIS and . software. and other System Administrators. Often times these things are out of my control and I will rely on Database Administrator.1.1. Once the web application server platform is chosen from the table below. In this post. I will go through step 2 that the Hyperion architect.pdf (128 pages)” from the Oracle Documentation Library. Network Administrators. I recommend you read the previous post before you pick up this one. Validation – Perform all functional activities necessary to validate the environment readiness 5. Defining an Architecture – Work with the client to define the hardware. should deliver. Documentation – Provide the client with all the details of the environment as it is configured.2. Steps 3-5 will be available in the coming weeks. primarily Hyperion Planning. Part 2 of 5 “Pre-Installation Requirements” In installment #1 of this guide. the installation and configuration often falls on System . This checklist contains the following elements. To reiterate our general approach.Hyperion Release 11 Architecture and Installation. I also recommend reading “Oracle Hyperion Enterprise Performance Management System Installation Start Here Release 11.

5. Standard One.17 is the embedded Java container that is installed automatically on all platforms.0. You can obtain this patch at the BEA web site. Includes support for Oracle Application Server Single Sign-On.1. Apache Tomcat 5. Apache Tomcat is supported only in this capacity.x) a Oracle WebLogic Server 9. I‟ll get admin access and manage it myself. I request the URL and authentication information since this will be needed during the deployment. Standard & Enterprise.1. This is directly from Oracle Enterprise Performance Management System .3.1.x C Embedded Java container d a Notes If Oracle Application Server is used as the Web application server.xb IBM WebSphere 6. Oracle HTTP Server is also required. Fusion Edition Release 11. Items such as clustering. I will request contact information from the web application server administrator and work in collaboration on the deployment. If future EPM System releases embed different Java application servers. Supports these editions: Java.Administrators. Server Oracle Application Server 10g (10.17 / 6. Oracle recommends using a commercially supported Web application server that supports high availability and failover. nonbase versions are supported only via manual deployment. and JVM setting are managed outside of the Hyperion installation.3.Supported Platforms Matrices “Oracle Enterprise Performance Management System. . I recommend reviewing this document. If I am doing a manual deployment.1. Shared Services requires WebLogic Server patch CR283953” for all platforms. system account management. b WebLogic Express is supported for each supported version of WebLogic Server. Other times.1. The first item to do is to validate the application server is certified. Apache Tomcat will no longer be supported. d For this release.2 (MP1 minimum) / 9. c WebSphere Express.1.2)” in the Oracle document library. Profitability and Cost Management supports only Oracle Application Server 10.2.x. It can change from release to release.3. ND and XD are supported only via manual deployment. and XD Editions are supported for each supported version of WebSphere. For deployments that require high availability or failover. ND.

and re-read.NET Configuration. Based upon some Q&A. This is mostly straightforward.NET account information if HFM or FDM are to be installed Next. This can be GhostScript or Acrobat distiller. I like to provide step-by-step information with screen shots since DCOM is often confusing…well it is to me at least. we should be ready to start laying out the binaries and start the Hyperion Installation.The next item on my checklist is to get the Relational Repositories Information set up. I‟ll make initial size recommendations. Planning. and validate it is the appropriate version. validation of name resolution. I identify the Network Information necessities for appropriate communication between servers. and IP address. In addition to the Hyperion Software. and FDM. or OID if applicable) Drive/Volume information identified for installation of the Hyperion software. This is made of the following items. This includes the DCOM account information. and authentication information. etc). subnet configuration. etc. In general. Essbase Admin Services / Business Rules. EPMA. This is vital so the components can communicate via Fully Qualified Domain Name. DCOM and . This includes IP addresses. Although it may not be strictly necessary. Web Application Servers. EPMA.pdf reports in Workspace. IIS is often not installed as part of a standard OS build. and Relational Repositories there are a few Additional Components that need to be installed. A PDF writer is needed for Reports Server to render . For our purposes. Although this is spelled out in detail in the “Start Here” manual. Short Name. . For the Windows Administration. It can always change and your installation may have some caveats that I have not covered. I suggest referring to the “Start Here” documentation to see what is currently supported but we often go with GhostScript due to its cost. The last thing we review is the IIS and . we provide the DCOM Configuration information needed to support FDM. LDAP. with all the above activities completed and validated.NET is installed. permissions. As with any installation. I say „better safe than sorry‟. trace between servers. Financial Management. For the installation and deployment. the Hyperion Manuals on there own rather than relying on this information or intuition. We will review the Fusion Installer and Hyperion Configuration Utility in our next installment. ensuring .      Operating Systems version/build Account on each server to run the Hyperion services and account requirements External Authentication information (MSAD. We make sure this requirement is specified. the documentation does not seem to be clear on the matter. DNS information. I recommend the Installation Architect read. I like to create a tablespace/database for each component ((Hyperion Foundation. A distinct tablespace/database for each component makes it easier to manage in my opinion. The target installation servers have a General System Administration checklist containing the information that I‟ll need to execute the installation. Some components use different variations of name resolution probably because the components were developed separately and have not been fully standardized. I‟ll need credentials for each table.

All the security users and groups need to be created. display database all. and load rules have to be considered. 2. If 4 Essbase servers exist. create all the applications and databases assign all relevant application and database settings rebuild and update security filters replicate all server variables This Maxl can be executed on the destination server to setup the new environment. or creating a backup strategy. All the Maxl and EssCmd scripts need to be copied and changed to reflect the new server and security model.NET application accepted the results of the following Maxl display commands.NET application that significantly reduces the work involved. reports. this effort might have to occur 12 times! Doing the same work 3 times for every server is obviously redundant.Migrating/Upgrading Essbase to a New Server There are many considerations that must be carefully planned when addressing an upgrade to version 9 or 11. it can be time consuming. display application all. . display variable all. alter system load application all. to version 9 or 11). display filter row all. Now factor in the number of Essbase servers and the fact that the security model might have to be consolidated to one (this occurs when upgrading from anything before 9. /* Create Application: BUDGET */ . I developed a small . Don‟t forget that there is only a very small window for the current production servers to be down. 3. As with any endeavor of this capacity. display privilege group all. display partition all advanced. The .NET application below. Essbase calc scripts. Examples of the scripts generated from the . but JAVA. It virtually eliminates the need for any manual or redundant effort. Server variables need to be moved. The benefits of the improved stability and features far outweigh the efforts. Manually moving all the components involved can take days and is extremely error prone. Completing this for one server is tough enough.NET was selected because it was the quickest for me to develop the application. or any other similar development language could be used. There is more to it than moving Essbase databases. 4. Imagine if corporate policy dictates that everything has to be done in a QA and/or test environment before it is moved to the new production area. Security filters need to be copied and altered slightly if moving to a new version of Essbase. Perl. Maxl scripts were created from the process to 1.

alter database 'BUDGET'.'Budget' set retrieve_buffer_size 102400.'Budget'."Working Budget". alter database 'BUDGET'. alter database 'BUDGET'. alter application 'BUDGET' enable updates.'Budget' set retrieve_buffer_size 102400.'Budget' enable aggregate_missing. and Maxl and EssCmd scripts from the source server to the destination server. alter database 'BUDGET'. /* Create Filter: MRP100206310000 */ create or replace filter 'BUDGET'.'Budget' set retrieve_sort_buffer_size 102400. alter application 'BUDGET' set lock_timeout after 300.'Budget' set io_access_mode buffered.'Budget' disable create_blocks.'Budget' set note ''.'Budget' set data_file_cache_size 1024000000.'Budget' set implicit_commit after 10000 blocks.@DESCENDANTS("Total Audit"). alter database 'BUDGET'. alter database 'BUDGET'. alter database 'BUDGET'.'Budget' enable autostartup.@DESCENDANTS("Expenses")'.create or replace application 'BUDGET' type nonunicode_mode."Input". alter database 'BUDGET'. alter database 'BUDGET'.'Budget' set minimum permission no_access.'Budget' set data_cache_size 512000000. alter database 'BUDGET'.'Budget' set retrieve_buffer_size 102400. alter database 'BUDGET'. alter database 'BUDGET'. /* Create Database: BUDGET */ create database 'BUDGET'. groups.'Budget' set compression bitmap. . data files. The program also created all the files to import into Version 9 and System 11 to add users. alter database 'BUDGET'. DOS and UNIX scripts were generated to copy all of the database objects. alter application 'BUDGET' set minimum permission no_access.'Budget' disable committed_mode.'Budget' set index_cache_size 76800000. alter database 'BUDGET'.'Budget' enable compression.'Budget' disable cache_pinning. alter database 'BUDGET'. alter application 'BUDGET' set max_lro_file_size unlimited. alter system unload application 'BUDGET'. alter database 'BUDGET'.'Budget'. alter database 'BUDGET'. alter application 'BUDGET' disable autostartup. alter application 'BUDGET' enable commands.@DESCENDANTS("Product").'Audit' write on '@DESCENDANTS("Time"). alter database 'BUDGET'. alter database 'BUDGET'. alter database 'BUDGET'. and replicate the security model.@DESCENDANTS("Year").'Budget' enable two_pass_calc. alter application 'BUDGET' enable connects.'Budget' enable startup. alter application 'BUDGET' enable startup. alter application 'BUDGET' enable security.

file paths.) were updated so they could be executed on the new servers. This process makes it extremely simple to migrate.All the Maxl and EssCmd scripts (username. . etc. or move. The entire process could be completed in hours. server names. password. What would be budgeted to take weeks with several resources can take less than a day. and eliminates the possibility of human error. rather than days. any Essbase application from one server to another.

Sign up to vote on this title
UsefulNot useful