Copying Files for Temporary Use During Configuration

If you are upgrading Provider Services, Administration Services, or Planning, some files from the earlier release of EPM System are required during configuration of the new release. You must make the files available on a shared drive or copy them from the earlier release installation to the machine hosting the new installation for use during configuration with EPM System Configurator.

During configuration with EPM System Configurator, this data is moved to the Shared Services Registry and the files are no longer used.

  To copy the files required for configuration:

  1. On the machine hosting the new release installation, prepare a temporary location to store files from the earlier release.

    During configuration, you specify the location of these files.

  2. Copy the following files from the earlier release installation to the directory that you just created:

Table 31. Files for Temporary Use During Configuration

ProductFiles to Copy for Temporary Use

Provider Services

If you are upgrading from Release 9.3.3 or Release 11.1.1.3, copy all Provider Services files to a single folder, for example:
ProviderServicesDataLocation/
	domain.db
	essbase.properties

If you are upgrading from Release 9.2.1, the directory structure that you copy to must be:

ProviderServicesDataLocation/
	ahas/domain.db
	svp/domain.db
	essbase.properties
	svp.properties

Copy the following files:

  • essbase.properties, located in:

    • Release 9.2.1: HighAvailabilityServicesInstallationDirectory/bin OR SmartViewProviderInstallationDirectory/bin

    • Release 9.3.3: HYPERION_HOME/APS/bin

    • Release 11.1.1.3: HYPERION_HOME/products/Essbase/aps/bin

  • datasources.xml (for upgrades from Release 11.1.1.3 only), located in: HYPERION_HOME/products/Essbase/aps/bin

  • svp.properties, for upgrades from Release 9.2.1 only if you are using SmartView Provider, located in SmartViewProviderInstallationDirectory/bin

  • domain.db, located in:

    • Release 9.2.1: HighAvailabilityServicesInstallationDirectory/data AND SmartViewProviderInstallationDirectory/data

      If you have High Availability Services and SmartView provider, copy both files.

    • Release 9.3.3: HYPERION_HOME/APS/data

    • Release 11.1.1.3: HYPERION_HOME/products/Essbase/aps/data

  • Smart slice definitions (for upgrades from Release 11.1.1.3 only) located in HYPERION_HOME/products/Essbase/aps/data/cubeviews. Copy the entire cubeviews directory structure.

For upgrade from Release 9.2.1, during configuration, EPM System Configurator merges the contents of the two domain.db files if both files exist and the contents of essbase.properties and svp.properties if both files exist.

Administration Services and Business Rules

  • Copy the entire storage directory structure located at: HYPERION_HOME/products/Essbase/eas/storage. For Release 9.3.3, the directory structure is HYPERION_HOME/AnalyticAdministrationServices/storage.

  • HBRServer.properties (for Release 9.2.1 and 9.3.3 using Planning); the default location is HYPERION_HOME/products/Essbase/eas. For Release 9.3.3, the directory structure is HYPERION_HOME/AnalyticAdministrationServices. Copy the file to MIDDLEWARE_HOME/EPMData/eas on the new machine, which in a default installation is c:/oracle/middleware/EPMData/eas.

    You must specify this MIDDLEWARE_HOME during installation.

    Tip:

    If you do not want to create the MIDDLEWARE_HOME directory in advance, you can create a temporary folder to store the file. After installation, copy HBRServer.properties to the MIDDLEWARE_HOME created by EPM System Installer.

    For Release 11.1.1.3 using Planning, to replicate HBRServer.properties, perform the following steps:

    1. On the source machine hosting Release 11.1.1.3, use Lifecycle Management to export Business Rules Server-related properties (HBRServer.properties): In the Shared Services Console, go to Application Groups, then Foundation, then Deployment Metadata, select Essbase under Shared Services Registry and perform a migration to the file system by clicking Define Migration.

      The data is exported to: HYPERION_HOME/common/import_export/admin@Native Directory/Export_File_Name.

    2. Copy the exported folder structure (info and resource folders) to the target machine hosting Release 11.1.2.1 to any folder, such as MIDDLEWARE_HOME/EPMData/eas.

      Oracle recommends that you copy the exported folder structure under MIDDLEWARE_HOME/EPMData/eas along with the storage folder required for the Administration Services upgrade.

      You must specify this MIDDLEWARE_HOME during installation.

      Tip:

      If you do not want to create the MIDDLEWARE_HOME directory in advance, you can create a temporary folder to store the file. After installation, copy HBRServer.properties to the MIDDLEWARE_HOME created by EPM System Installer.

      Make note of the location to which you replicate the data. During configuration with EPM System Configurator, you enter this location on the Import Data From Earlier Release configuration page for Administration Services.

Reporting and Analysis

server.xml, located in:

  • Release 9.2.1 and 9.3.3: BIPLUS_HOME/common/config, where BIPLUS_HOME by default is HYPERION_HOME/BIPlus

  • Release 11.1.1.3: HYPERION_HOME/common/workspacert/9.5.0.0/common/config/dynamic/UUID, where UUID is the dynamic ID for the folder.

    If there is more than one UUID folder, retrieve server.xml from the folder that contains irdas_default.txt.

Make note of the location to which you replicate the data. During postconfiguration tasks for Interactive Reporting, you specify the location of this file when you import DAS data sources.

Planning

HspJSHome.properties (for Release 9.2.1 only, in HYPERION_HOME/AppServer/InstalledApps/Web_application_server/HyperionPlanning/WEB-INF/classes)

Note:

The file required for Planning Release 9.2.1 must be copied to MIDDLEWARE_HOME/EPMData/planning, which in a default installation is c:/oracle/middleware/EPMData/planning. You are not prompted for this location during configuration. Create the MIDDLEWARE_HOME directory if it does not exist.

You must specify this MIDDLEWARE_HOME during installation.

Tip:

If you do not want to create the MIDDLEWARE_HOME directory in advance, you can create a temporary folder to store the file. After installation, copy HspJSHome.properties to the MIDDLEWARE_HOME created by EPM System Installer.