To move Essbase Studio from release 11.1.1.3 and earlier to the 11.1.2.1 release, you perform an upgrade. To move from release 11.1.2 to 11.1.2.1, you apply the maintenance release.
Before you begin the upgrade or maintenance release procedures for Essbase Studio, complete the “Upgrading Checklist” tasks in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
Note: | You must complete the upgrade tasks applicable to your environment in the order noted in the checklist. |
After you complete the applicable EPM System environment upgrade tasks, you may begin the Essbase Studio upgrade or applying the maintenance release.
Whether you are upgrading or applying the maintenance release, you must migrate your catalog database to the current version to keep information in the catalog intact. Information such as data source connections, metadata elements, cube schemas, and Essbase models will be functional and deployable after the migration and subsequent upgrade tasks.
Perform the Essbase Studio catalog database upgrade during the EPM System configuration process. The instructions for migrating the Essbase Studio catalog database are included in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
For upgrades (from release 11.1.1.3 and earlier), after configuration, perform these tasks:
If Essbase Studio Server has moved, for deployed applications that reference the old server location, update the cube linkage, as described in Updating Cube Linkage.
If Essbase Server has moved, perform the rehosting procedure so that Essbase connections point to the new server location, as described in Updating References to Rehosted EPM System Products.
For text file data sources:
Oracle recommends that you store the text files in the default directory (EPM_ORACLE_HOME/products/Essbase/EssbaseStudio/Server/datafiles) on the machine where Essbase Studio Server resides. If you choose to store text files in a non-default location, you must add the server.datafile.dir property to the server.properties file, as described in server.datafile.dir.
Also, if you are storing text files in a non-default directory, edit the connection properties for any text file connections to point to the new location of the text files, as described in Editing Data Source Connection Properties.
If Performance Management Architect Dimension Server has moved, edit the connection properties for any Performance Management Architect Dimension Server connections that point to the old server location, as described in Editing Data Source Connection Properties.