Caution! | Do not proceed with configuration until you have exported Shared Services data from the earlier release. See Exporting Shared Services Data from the Earlier Release. |
After you install, use EPM System Configurator to configure EPM System products.
Upgrade configuration notes:
You must configure Foundation Services first. Foundation Services must be installed and configured for other products to configure successfully.
In a distributed environment, for Shared Services, perform the Configure Database and Import data from earlier release tasks on each machine on which Shared Services is installed before configuring any other products. For other products, you perform the import data tasks on only one machine in a distributed environment.
Configure Essbase and Essbase products next.
You must perform the Configure Database task at the same time as or before you perform the “Deploy to Application Server” task.
Because you are configuring products one at a time, configure the Web server after each product. (Select the Foundation Services “Configure Web Server” task.) After configuration, restart the Web server and EPM Workspace.
You must deploy all EPM System products to a single WebLogic domain. The only exception to this requirement is documented in Deploying Financial Reporting and Web Analysis on Windows for use with Financial Management.
If you are upgrading multiple instances of Essbase, for each instance that you are upgrading from, you must create a new instance in Release 11.1.2.1. See Configuring and Starting Additional Instances of Essbase Server.
The following table describes the tasks that you must select in EPM System Configurator and describes the tasks EPM System Configurator performs during upgrade. For details about running EPM System Configurator, see Configuring EPM System Products or click Help.
Note: | For all products other than Shared Services, during product database configuration, select Upgrade existing database to the current release from... and select a release number. Then, enter connection information for the existing or replicated database. |
To launch EPM System Configurator, from the Start menu, select Programs, then Oracle EPM System, then Foundation Services, and then EPM System Configurator.
Table 33. Required Configuration Tasks During Upgrade
| Product | Configuration Tasks | What Happens During Upgrade |
|---|---|---|
| All products | Configure a New or Existing EPM Oracle Instance. Typically, if you are installing all products on a single machine, for the first product you configure, you create a new EPM Oracle instance. For each product after that, you modify the existing instance. If you are installing in a distributed environment, create a new instance with a unique name on each machine. | |
| Shared Services |
During Shared Services database configuration, select Perform first- time configuration of Shared Services database, and then enter connection information for a new database. If you are upgrading from Release 11.1.1.3, and you configured all EPM System products to use one database, you are alerted that pre-existing Shared Services tables have been detected in the database. When prompted to drop and recreate the tables, select Yes. For the Deploy to Application Server configuration task, deploy to a new WebLogic domain. For the Import Data From Earlier Release configuration task, specify the location from which to import Shared Services data. You must specify the full path to hssmigratedata.zip, which is created with the Shared Services Upgrade Utility. Caution! Perform this task only once on a machine. In a distributed environment, perform the Configure Database and Import data from earlier release tasks on each machine on which Shared Services is installed before configuring any other products. When you are done with this step, return to the Upgrading Checklist. | Imports Shared Services data from the earlier release. For more information about this process, see What Happens During Shared Services Data Import. Note: You see applications in EPM Workspace and provisioning information in Shared Services only after a product is reregistered and applications are migrated. You see EPM Workspace preferences upgraded from the earlier release only after you have upgraded all EPM System components and you have started Reporting and Analysis Framework. In addition, users must be provisioned with a Reporting and Analysis role other than IR HTML Viewer or IR WebClient Viewer. |
| Essbase |
On the Configure Essbase Server page, for Full path to application location (ARBORPATH), specify the location of the existing or replicated Essbase data. Note: If you replicated data to a new machine, and if you selected Differently-named disk volumes, table spaces, or ARBORPATH on source and target or Consolidated disk volumes or tablespaces on target by exporting data during data replication, you must run a script immediately after configuring Essbase to update the Essbase security file to reflect the disk volumes on the upgraded system. The Essbase Staging Tool provides a script to update the settings in the security file (essbase.sec): Start the Essbase Server and EPM System services. Navigate to ARBORPATH/app on the machine that is hosting the upgraded Essbase Server and run the following script using MaxL: %ARBORPATH%/bin/startMaxl.bat -u userName editagtsec.msh where userName is the Administrator user name to connect to the upgraded Essbase server. The script prompts you to enter the password. Note: editagtsec.msh could be empty in some scenarios. For example, when you launched the Staging Tool, the Staging Tool reports on existing volumes. If no volumes are listed, editagtsec.msh is empty. | Registers applications with Shared Services and upgrades applications. Note: When you upgrade from an earlier release, a backup of the security file for the earlier release is created before the security file is upgraded. The security file backup, Essbase.Bak_preUpgrade, is in ARBORPATH/bin. Unlike the Essbase_timestamp.bak file, which regularly backs up the latest state of Essbase security, this pre-upgrade backup file is kept intact and is not subsequently updated by further operations. |
| Provider Services |
For the Import Data From Earlier Release task, specify the location of the existing or replicated data. | Moves data from the earlier release into the Shared Services Registry. Moves essbase.properties to EPM_ORACLE_INSTANCE/aps/bin and merges its contents with the essbase.properties file installed with Release 11.1.2.1. |
| Administration Services |
For the Import Data From Earlier Release task, specify the location of the existing or replicated data | Moves data from the earlier release into the Shared Services Registry. |
| Essbase Studio |
On the Configure Essbase Studio Server Data File Location page, specify the location of the existing or replicated Essbase Studio data. | Upgrades the Essbase Studio catalog and the database. EPM System Configurator performs the following tasks during the upgrade process:
Note: If database configuration fails during upgrade from Release 11.1.1.3, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide. Maintain the Release 11.1.1.3 environment until the upgrade is complete. |
| Integration Services |
When you are done with this step, return to the Upgrading Checklist. | |
| Performance Management Architect |
When you are done with this step, return to the Upgrading Checklist. | Updates the database. For interface datasources, imports data from the migrated Shared Services data and stores it in the Shared Services Registry. |
| Calculation Manager (for upgrades from Release 11.1.1.3) |
When you are done with this step, return to the Upgrading Checklist. | Updates the database. |
| Reporting and Analysis |
On the Reporting and Analysis Framework Services configuration page, for Repository Directory, specify the location of the existing or replicated data. When you are done with this step, return to the Upgrading Checklist. | Updates Web Analysis application settings. Updates the database. |
| Planning |
When you are done with this step, return to the Upgrading Checklist. | Updates the database. For Planning Release 9.2.1 only, moves the data from HSPJS.properties to the Planning system repository and the file is no longer used. You perform application upgrade later in the upgrade process. |
| Financial Management |
You must select Upgrade applications from earlier release. Note that there is no EPM System Configurator page for this task and you need not enter information. Note: Depending on the number and size of applications you are upgrading, this task can take some time. When you are done with this step, return to the Upgrading Checklist. | Upgrades applications by converting database tables, and registers applications with Shared Services. Note: Perform the application upgrade only once, regardless of how many Financial Management application servers are configured. |
| Performance Scorecard |
On the Performance Scorecard Specify directory to store Performance Scorecard files configuration page, specify the location in which to store files. When you are done with this step, return to the Upgrading Checklist. | Updates the database. |
| Profitability and Cost Management |
When you are done with this step, return to the Upgrading Checklist. | Updates the database and reregisters all upgraded Profitability and Cost Management applications with Shared Services. |
| Strategic Finance |
On the Strategic Finance Configuration configuration page, specify the location of the existing or replicated data. When you are done with this step, return to the Upgrading Checklist. | Updates the database. |
| Disclosure Management | N/A. Use the Apply Maintenance Release option during installation. | |
| Financial Close Management | N/A. Use the Apply Maintenance Release option during installation. | |
| FDM |
When you are done with this step, return to the Upgrading Checklist. | Registers FDM with Shared Services. Updates the ERP Integrator database. You complete configuration in FDM and upgrade applications later in the upgrade process. |