Hyperion Version 8.5 to Version 9 Migration

version 2010/09/02

This document is based on the Hyperion Version 8.5 to Version 9 migration that Taurus performed internally. The document lists the key steps that were followed during the process.

The main conclusion drawn from the migration exercise is that the available Oracle/Hyperion documentation is complete and that the Version 8 to Version 9 migration itself is straightforward. We found the initial installation and configuration of Version 9 to be more problematic than the migration itself.

The installation of Version 9 and Taurus EAS are well documented in detail elsewhere. Nonetheless, we will itemize and detail all major steps while adding additional observations and recommendations where appropriate.

Our migration made use of separate Windows systems as the Version 8 source and the Version 9 target. It is feasible to configure and use co-located VM slices, although for logistical reasons we did not choose this approach.

Hyperion product documentation for both Version 8 and 9 is available for web download from the following link:

Migration steps

1. Install and create a target database (SQL Server was used).

2. Prepare for Version 9 installation on target

3. Install Version 9 on the target

4. Migrate from Version 8 to Version 9

5. Publish the EAS queries

General Considerations

To configure, alter, and operate the application on the target system you will require administrative privileges as well as the memory and disk requirements specified in the Hyperion Version 9 Release documentation. Many of these hardware requirements are covered below, but please review the Release documentation requirements in order to insure that the target system is Hyperion-ready.

As a general rule, please make sure that any port created for either the migration or longer-term use has been added to the exception list on the target Version 9 system's firewall. An alternate approach to port exceptions is to specify a firewall exception by executable name.

Also, it is very important, with no exceptions, that the identical DSN names that are in use on the Version 8.5 migration source are used in the Version 9 migration target.

1. Install or configure SQL Server on target system

You will require administrator privileges on this system (see SQL Server StandAlone installation documentation for details).

  • Install SQL Server StandAlone edition or use available (we used an existing SQL Server 2003).
  • Accept mixed-mode SQL Server and Windows authentications.
  • Accept all other default settings.
  • Create Hyperion Repository database accepting all default settings, set initial size to 5MB and allow extension.
  • Create required database user.
  • Set the database user's default database to the Hyperion Repository and make sure user is the db_owner.
  • Add database user to the Hyperion Repository database and set it as dbo.

Note : on some systems the default port of 1433 may be already taken. You can use TCPView or another port-scanning tool to find out which server ports are in use. You can also check and alter SQL Server port usage using the SQL Server Configuration Manager.

2. Prepare for Version 9 installation on target (see Hyperion Version 9 Installation documentation):

  • Create the database with a DB name of s9ss and a user/password of s9ssadm/password.
  • Create a database with a DB name s9bi and a user/password of sibiadm/password.
  • Create an ODBC DSN named s9bi mapping to the s9bi database for PR configuration.

3. Install Version 9 (see Hyperion Version 9 Installation documentation)

  • Install the Shared Service and test.
  • Install the BI service.
  • Install the UI service.
  • Run config utility.

NOTE: Always use the fully qualified name when specifying a server by name.

Shared Services

  • Install Shared Services using the previously-defined database DSN and database user.
  • Configure Shared Services in a custom mode, selecting all services except Mail Server.
  • Configure TomCat as a service.
  • Specify the InterOp servlet name and port (58080 in this example).
  • Test Shared Services by opening http:\\localhost:58080/interop/index.jsp, logging in using the literal strings "administrator" and "password".

BI+ Studios

  • Custom install the following BI+ Studio clients : Financial Reporting, Interactive Reporting, Production Reporting, Dashboard.

NOTE: you do not need to run config at the end of this installation Step.

BI+ Services

  • Create a BI repository database for PR configuration, a DSN, and a database user, initial database size 50MB with extend.
  • If FR is to be installed, install Ghostscript.
  • Custom install BI+ Services, enable SDI installation but disable FR services.
  • Install UI Services with a Typical install unless you do not want to install WA or FR web components.
  • Run the config utility.
  • Start Shared Services in the order listed in the document Appendix.
  • Select all BI+ options.
  • Select TomCat, choosing defaults.
  • Login to the Shared Services console using the strings "administrator" and "password".
  • Create a user and provision for BI+ as an Administrator.
  • Login to the default Workspace as this user.
  • Install Hyperion Intelligent designer.
  • Start Hyperion Intelligent Designer.
  • Add new data source in the same manner as adding a system dsn, specifying a SQL user log-in and password as Windows Authentication may not work.
  • Save this as an .oce.
  • Add tables to the query, add attributes to the queries, save the query as .bqy file.
  • BackUp the Version 9 repository database after detaching its database file for a consistent image.
  • Backup C:\Program Files\Hyperion\HPSu\BrioPlatform\server\RM1_[xxxxx]

4. Migrate from Version 8 to Version 9 (see Hyperion Version 9 Migration documentation)

  • Run the Migration Wizard (Start->Programs->Hyperion System 9BI->Utilities and Administration->Migration Utility and select Hyperion Performance Suite 8+.
  • Select a migration logging directory (C:\Hyperion\Migration Utility\log recommended), specifying Info level logging.
  • Define which database contains the Version 8 repository by database type and host name.
  • Specify Version 8 database port, DSN, database user and password.
  • Search for and remove any circular references in the HPS Version 8 relationships.
  • Select HPS objects by type for migration: User Defined Roles, Users, Groups, User Preferences, Repository Metadata, Repository Files, Events, Authorization. We selected all objects.
  • Define the target Version 9 BI+ database in the same manner as above, by database type, host name, port DSN, database user and password.
  • Define the location of the Shared Services Server by host name, port, user and password.
  • Define how to treat user and group names, user and group descriptions, and their respective passwords.
  • Review these user and group mappings and properties, specifying which should be migrated: we selected all.
  • Define source and target host repository mapping, providing the respective paths to server.xml and repositories themselves.
  • Run the migration in Test Mode, to identify and correct any errors. Run in Test Mode iteratively until all errors have been corrected.
  • Select the HPS objects to migrate by type: User Defined Roles, Users, Groups, User Preferences, Repository Metadata, Repository Files, Events, Authorization. Although the documentation suggests to migrate in stages by type, we migrated all.
  • Consider as a post-migration step to use the Validating Migration Results checklist contained in Hyperion's Version 9 Migration document.
  • BackUp the Version 9 repository database after detaching its database file for a consistent image.
  • Backup C:\Program Files\Hyperion\HPSu\BrioPlatform\server\RM1_[xxxxx]

5. Publish the EAS queries (see Taurus EAS documentation)

  • Start up IE and go to
  • Login as globaladministrator/globaladministrator
  • Change the folder root to HyperionRoot.
  • Add a new Folder and click on show access control to set access level and group that can access the folders.
  • To publish the files, first publish the .oce file then .bqy file. When publishing the .bqy file, select the option to attach the query file with the .oce file.

NOTE: the results are the .oce file and two .bqy files, one is merely a view and another is a live query. The live query needs to have the ActiveX control/plugin installed.

  • By clicking on the icon with the plug-in installed, the installation wizard will come up.

NOTE: in the event of installation failure, the plug-in can be manually installed from the directory C:\Program Files\Hyperion\HPSu\servlets\deployment\zeroadmin\component\Insight

  • Click on the query file, if you receive an error of 2018, then it means that the .oce file is not properly set up on the server.

NOTE: the server name field must match that of the .oce file and the server configuration.

Appendix

A. Starting and stopping the Hyperion Services.

Start the Hyperion Services in the following order:

  1. LDAP
  2. Shared
  3. Apache
  4. Core
  5. Interactive Reporting
  6. Web Analysis
  7. Workspace

Stop the Hyperion Services in the following order:

  1. Workspace
  2. Web Analysis
  3. Interactive Reporting
  4. Core
  5. Shared
  6. LDAP
  7. Apache

B. Re-installation of Version 9 on target after install failure (if necessary)

  • Examine log files in the directory C:\Program Files\Hyperion\HPSu\BrioPlatform\logs.
  • Look at the last modified files.
  • All but obvious errors will require a re-install (best practice).
  • Back up the Version 9 repository database after detaching its database file for a consistent image.
  • Backup C:\Program Files\Hyperion\HPSu\BrioPlatform\server\RM1_[xxxxx]
  • Make a copy of C:\Program Files\Hyperion\HPSu\BrioPlatform\etc\config.dat.
  • Make a copy of C:\Program Files\Hyperion\HPSu\BrioPlatform\etc\server.xml.
  • Make a copy of the BrioPlatForm folder.
  • Uninstall Hyperion Performance Suite.
  • Uninstall executable at C:\Program Files\Hyperion\HPSu\uninstall_server
  • Remove installing directories C:\Program Files\Hyperion and C:\Hyperion.
  • Remove the filevpd.properties from c:\Windows directory.
  • Remove all files named BrioPlatformInstallxxx and InstallHistory from the directory under c:\Documents and Settings of the person who installed the server.
  • Remove registry entries: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services name starting with BPS.
  • Re-install Version 9 exactly as before.
  • Reboot the system.
  • After the rebooting, detach repository database file and copy the saved repository database files over the newly created repository database files.
  • Attach the restored repository database files.
  • Copy the saved config.dat and server.xml files into the C:\Program Files\Hyperion\HPSu\BrioPlatform\etc overwriting the existing ones.
  • Start up the services as per the regular installation.

1