Exporting Shared Services Data from the Earlier Release

To use data from the earlier release of Shared Services, you export the data using a utility, and then copy the resulting file to the machine hosting the new installation. During configuration, EPM System Configurator extracts the necessary data for use in the current release.

Note:

The database, Shared Services, and OpenLDAP must be running before you perform this procedure.

Note:

Before you migrate Shared Services data, ensure that the admin user is provisioned for the Essbase Server. You can remove this provisioning after the upgrade is complete.

  To export Shared Services data from the earlier release:

  1. If you have not already done so, download files for Release 11.1.2.1 and extract the contents of the System Installer ZIP file.

    If you have not yet downloaded the System Installer ZIP file (Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.2.1 for platformName), download it from the Oracle Software Delivery Cloud. See Preparing for Installation.

    Tip:

    Use a zip file extraction program that can handle long path names, such as 7-Zip.

  2. In the SystemInstallerExtractLocation/Migration directory, look for HSSMigrate.zip and extract the contents to the HYPERION_HOME directory on the machine hosting the earlier release of Shared Services.

  3. From a command line, run the following script from the HYPERION_HOME/Migrate directory: 

    hssmigrate.bat|sh

    The utility searches for Shared Services configuration files and prompts you for confirmation.

    Tip:

    To ensure successful export of Lifecycle Management data from Release 11.1.1.3 on UNIX, set executable permissions on set_hyphome_servername_1.sh, in $home/.

  4. At the prompt, review the location from which the utility will extract Shared Services configuration files. If the path is correct, press Enter. If the path is not correct, enter 2, specify the correct path, and then press Enter.

    Tip:

    The path you enter should be the path for the CSS.xml, Domain.xml, and WorkflowEngine.properties files, for example: HYPERION_HOME/AppServer/InstalledApps/WebServerName/WebServerVersion.

    The utility creates a file, hssmigratedata.zip, in HYPERION_HOME/migrate, that stores the Shared Services data.

    Tip:

    If the utility reports errors, review the logs in HYPERION_HOME/migrate/logs, correct any errors, and then re-run the utility to generate a new ZIP file that replaces the existing file.

  5. Copy hssmigratedata.zip from HYPERION_HOME/migrate to the machine on which you plan to host the new release of Shared Services, or make the file available on a shared drive. (If you are installing on the same machine, make sure the location is outside of HYPERION_HOME.)

    You specify the location during configuration.

  6. In a distributed installation, for some products, if products will be installed on a machine or machines other than the machine hosting Shared Services, copy hssmigratedata.zip to each machine and unzip the contents to the MIDDLEWARE_HOME directory.

    This step is required for Essbase Studio, Web Analysis, Administration Services if you are also using Business Rules, and Performance Scorecard.

    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 these files. After installation, unzip hssmigratedata.zip to the MIDDLEWARE_HOME created by EPM System Installer.

For more information about what happens during Shared Services data import, see What Happens During Shared Services Data Import.