HYPERION® REPORTING AND ANALYSIS MIGRATION UTILITY

RELEASE 11.1.1

MIGRATION GUIDE

Reporting and Analysis Migration Utility Migration Guide, 11.1.1 Copyright © 2002, 2008, Oracle and/or its affiliates. All rights reserved. Authors: EPM Information Development Team This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS: Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

Contents

Chapter 1. Overview and Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Overview of the Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Migration Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 What Happens During Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Prerequisites for Using the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Other Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Special Symbols in Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Invalid Characters in Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 SmartCuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Migrating SAP Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Chapter 2. Migrating from Brio Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 About Migrating from Brio Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Defining the Database Used by the Portal Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Defining the Location of the Portal Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . 23 Location of Portal Repository Database Defined by Host and Name . . . . . . . . . . . . . . 23 Location of Portal Repository Database Defined by JDBC Driver and URL . . . . . . . . . 24 Identifying Portal Groups with Circular References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . . . . . . . . . . . 30 Location of the Hyperion Registry Database by Host and Name . . . . . . . . . . . . . . . . . 31 Location of the Hyperion Registry Database by JDBC Driver and URL . . . . . . . . . . . . 31 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . . 33 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . 34 Location of Reporting and Analysis Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Contents

iii

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . 39 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Adding Users/Groups Assigned in Portal to the Native Shared Services Group . . . . . . 47 Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Chapter 3. Migrating from BrioONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 About Migrating from BrioOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Running the Brio Portal Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Defining the Database Used by the OnDemand Server Repository . . . . . . . . . . . . . . . 55 Defining the Location of the OnDemand Server Repository Database . . . . . . . . . . . . . 56 Defining the Location of the OnDemand Server Installation Files . . . . . . . . . . . . . . . . 59 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Defining Target Row Level Security Repository Database Information . . . . . . . . . . . . 62 Defining the Location of the Target Row Level Security Repository Database . . . . . . . 63 Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . 66 Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . . . . . . . . 68 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . 71 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . 72 Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . 75 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Defining User/Group Names, Descriptions, and Passwords . . . . . . . . . . . . . . . . . . . . 77 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
iv
Contents

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Starting the Migration Utility Wizard . . . . . . . . . . 105 Defining Content Filtering for Broadcast Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Selecting the Objects to Migrate . . . . . . . . . . . . 117 Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . 115 Chapter 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Running the Migration . . . . . . . . . . . . . . . . 117 About Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Defining the Database Used by the Analyzer Repository . . . . . . . . 88 Defining the Database Used by the Broadcast Server Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Defining User/Group Descriptions and Passwords . . 87 About Migrating from the Brio Intelligence Server . . . . . . . . . . . . 126 Defining the Location of the Hyperion Registry Database . . . . . . . . . . . Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating from the Brio Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . .Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Location of the Hyperion Registry Database by JDBC Driver and URL . . . . . 128 Contents v . . . . . . . . . . . . . . 121 Location of Analyzer Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Location of Analyzer Repository Database Defined by Host and Name . . . . . . . . . . . . 108 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . 87 Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Running the Broadcast Server Migration . . . . 94 Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Defining the Location of the Broadcast Server Repository Database . . . . . . . . . . . . . . . . . 118 Entering Logging Details . . . . . . . . . . . . . . 125 Defining Hyperion Registry Database Information . . . . . . . . . . . 98 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . . . . . . 97 Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . . 100 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . . . . . . . . 81 Running the Migration . . . . . . . . . . . . . . . . 90 Defining the Broadcast Server Name and the Location of the Broadcast Server Initialization File . . . . . . . . . . . . . . . . . . . 84 Chapter 4. . . . . . . . . . . . 120 Defining the Location of the Analyzer Repository Database . . . 127 Location of the Hyperion Registry Database by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Defining the Location of the Shared Services Server . . .

145 Starting the Migration Utility Wizard . . . . . . 131 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . 136 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Updating User Name Information . 134 Reviewing User Names . . . . . . . . . . . . . . . 149 Location of Hyperion Performance Suite Repository Database Defined by Host and Name . . . . . 146 Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Editing User Name Properties . . . . . . . . . . . . . . . 155 Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . 141 Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Setting the Migration Action . . . . . . . . . . . . . 146 Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Location of the Hyperion Registry Database by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Defining the Location of the Hyperion Performance Suite Repository Database . . . . . . . . . . . . . . . 141 Chapter 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Searching for User Names . . 150 Identifying Hyperion Performance Suite Groups and Roles with Circular References . . . . . . . . . . 145 About Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . 130 Location of Reporting and Analysis Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Defining the Hyperion Shared Services Registry Type . . . . . . . . . . 138 Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Verifying Group Name Mapping . . . . . . . . Descriptions and Passwords . . . . . . . . . . . 149 Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . .Defining Reporting and AnalysisDatabase Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . 140 Adding Users/Groups Assigned in Analyzer to the Native Shared Services Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Defining User/Group Names. . . . . . . . . . . . . . . . . . . . . . 157 vi Contents . . . . . . . . . . . . . . . . . . . 130 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . Migrating from Hyperion Performance Suite 8 . . . . . . . . . 147 Defining the Database Used by the Hyperion Performance Suite Repository . . . . . . . . . 141 Running the Migration . . . . . . . . . 129 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Defining User/Group Names. . . . 184 Defining the Hyperion Reports Administrator . . . . . . . . . . . . . . . 179 About Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Adding Users/Groups Assigned in Hyperion Performance Suite to the Native Shared Services Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Location of the Hyperion Registry Database by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . 180 Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Defining Reporting and Analysis Repository Database Information . . 173 Updating Group Name Information . . . . . . . . 160 Location of Reporting and Analysis Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Contents vii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Defining the Location of the Reports Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Reviewing Group Names . . . 171 Editing Group Name Properties . . 173 Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Verifying Group Name Mapping . . . . . . 174 Running the Migration . . . . . . . 169 Setting the Migration Action . . . . . . . . . . . . . . . . . . 183 Location of Reports Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . 179 Selecting a Migration Path . . . . . 165 Reviewing User Names . . . . . 180 Defining the Database Used by the Reports Repository . . . . . . . . . . . . . . . . . 172 Setting the Migration Action . . . . . . 170 Searching for Group Names . . . . 186 Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . 185 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Chapter 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Location of Reports Repository Database Defined by Host and Name . . . . . Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . 193 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . 205 Adding Users/Groups Assigned in Reports to the Native Shared Services Group . . . . . . . . . . 203 Reviewing Group Names . . . 200 Searching for User Names . . . . . . . . . . . . . . . . . . . 206 Index . . . . . . . . . . . 189 Location of the Hyperion Registry Database by Host and Name . . . . . . . . . . .Defining the Location of the Hyperion Registry Database . . . . . . . . . 202 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Searching for Group Names . . . . . . . . . . . Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Updating User Name Information . . . . 197 Defining User/Group Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Editing User Name Properties . . . . . . . 190 Location of the Hyperion Registry Database by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Location of Reporting and Analysis Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . 190 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . 206 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 viii Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . .

........ and native users maintained in an Open LDAP database........ groups.............2................. 7......15 Overview of the Migration Process Migration involves migrating information from the source system to Oracle's Hyperion® Shared Services and the Oracle's Hyperion Reporting and Analysis Repository.6.......0.....5 or later BrioONE (Brio Portal 7............ Reporting and Analysis Repository—Stores information about the mapping between the users and groups in the source system and the users and groups in Shared Services......................5 or later and OnDemand Server 6.x Hyperion Reports 7.............1............. or 7..........6...4 or later) Brio Intelligence Server (OnDemand Server and Broadcast Server 6. roles.........0...................... Review the following topics for information on the migration process... ● ● Migration Components What Happens During Migration Migration Components Each migration involves the following components: ● Source system—Users.. repository content..........................x ● Shared Services—Defines both external users and groups in external directory systems..........13 Other Migration Considerations.....1 Hyperion Performance Suite 8.... and the database used by one of the following source products: ❍ ❍ ❍ ❍ ❍ ❍ Brio Portal 7.... 7........0.........2.. 9 Prerequisites for Using the Migration Utility . ● Overview of the Migration Process 9 ...4 or later) Hyperion Analyzer 6.........0.......1 In This Chapter Overview and Prerequisites Overview of the Migration Process.............2....................x or 7...5.............

For users and groups in the source system that do not map to existing users and groups in Shared Services. Review the following topics for information on migrating each of these objects. Based on roles assigned. do not provision the World group. and the information on this mapping is stored in the Reporting and Analysis Repository. users can perform specific tasks and access content in various applications. ● ● Provisioning of Users and Groups During Migration Provisioning is the process of granting roles and access control to users of Hyperion applications. and this role is mapped to role y in the Reporting and Analysis Repository. This means that every user/group is granted these roles. You can provision the World group after migration if desired. When you provision the World group. During user provisioning. new native users and groups are created in Shared Services. the user/ group is not explicitly provisioned. the user will be provisioned with role y. and every user/group is at least implicitly provisioned. ● If a user/group is not explicitly assigned any roles (or is only assigned default roles). For example. keep in mind the following: ● If a user/group is explicitly assigned roles by the source product (other than default roles). All users and groups that are migrated are provisioned for the application that is registered during product installation and configuration. ● ● ● “Migrating Users and Groups” on page 10 “Migrating Roles” on page 11 “Migrating Repository Content” on page 13 Migrating Users and Groups During migration: ● Users and groups in the source system are mapped to users and groups in Shared Services. All users/groups that are migrated (with the exception of the World group) are assigned as members of the new native group (for example. if a user is assigned role x in the source product. ● ● ● 10 Overview and Prerequisites . all users displayed in Shared Services can login. roles. and repository content.What Happens During Migration Migration involves users. the user/group is explicitly provisioned with these roles subject to the mapping of the roles in the Migration Utility. The World group is not explicitly provisioned. If you want only a subset of the users to be able to login. AnalyzerGroup) regardless of whether they were explicitly assigned roles. groups. The new native group is provisioned for the application and is assigned the default roles.

You only need to explicitly provision new user/groups if you want to assign them additional roles. add any new user/s groups to the native group (for example. Hyperion Analyzer Role Administrator Reporting and Analysis or EPM System Role Reporting and Analysis Global Administrator. When you migrate user-defined roles. new roles are created in Shared Services. The mapping determines how users and groups are provisioned. if a user is granted a pre-configured role in the source system. Provisioning Manager Analyst Data Source Publisher Content Manager Reporting and Analysis Global Administrator Content Manager Personal Parameter Editor Personal Parameter Editor Content Publisher Analyst Report Designer Data Editor Data Source Publisher Explorer Deprecated Deprecated Content Publisher Information Consumer Interactive User Power User permission-administer-users permission-create-links permission-create-pv permission-create-pov permission-create-report permission-cube-navigator permission-design-report permission-edit-data permission-manage-database permission-open-report permission-user-preferences permission-print-report permission-save-report Overview of the Migration Process 11 . Oracle's Hyperion® Performance Suite™. pre-configured roles in the source system are mapped to new roles in Shared Services.● To keep the same behavior for users/groups created after migration. By doing this. The following tables correlate legacy roles for Hyperion Analyzer. the user will be provisioned with new Reporting and Analysis roles based on this mapping. AnalyzerGroup). and Hyperion Reports to Reporting and Analysis and Oracle Hyperion Enterprise Performance Management System roles. For example. Directory Manager . Hyperion Metrics Builder. Migrating Roles During migration. the new users/ groups inherit the same roles and are implicitly provisioned.

and Provisioning Manager Directory Manager Explorer Analyst Analyst Dynamic Viewer Interactive Reporting Viewer Job Manager Job Publisher Job Runner Scheduler Content Manager Reporting and Analysis Administrator Data Source Publisher Directory Manager and Provisioning Manager Personal Page Editor Personal Page Publisher Browser Content Administrator Content Publisher Event Services Administrator Global Administrator Group Administrator Group Locator iHTML Viewer Intelligence Analyzer Intelligence Dynamic Viewer Intelligence Viewer Job Administrator Job Publisher Job Runner Job Scheduler MIME Type Administrator Name Service Administrator OCE Publisher Organizational Administrator Personal Page Personal Page Publisher 12 Overview and Prerequisites . Directory Manager.Hyperion Metrics Builder Role Administrator HTML End User Editor Java End User Reporting and Analysis or EPM System Role Reporting and Analysis Administrator Metrics Viewer Metrics Editor Metrics Analyst Oracle's Hyperion® Performance Suite™ Role Administrator Reporting and Analysis or EPM System Role Reporting and Analysis Administrator. Directory Manager. Provisioning Manager Explorer Content Manager Content Publisher Schedule Manager Reporting and Analysis Global Administrator.

Prerequisites for Using the Migration Utility Prerequisites include tasks that you must complete for the Migration Utility to run properly. Directory Manager. Provisioning Manager Explorer Migrating Repository Content All repository content/metadata is migrated from the source system to the Reporting and Analysis Repository. Directory Manager. fulfill the prerequisites in Table 1. regardless of system configuration or content migrated. Personal Page Editor Directory Manager Explorer Viewer Viewer Favorites Distributor Hyperion Reports Role Designer Security Administrator System Administrator Viewer Reporting and Analysis or Oracle Hyperion Enterprise Performance Management System Role Scheduler. Report Designer Reporting and Analysis Global Administrator. Prerequisites for Using the Migration Utility 13 .Oracle's Hyperion® Performance Suite™ Role Physical Resource Administrator Related Content Viewer Role Administrator Role Locator Schedule Administrator Session Administrator System Crawler System Viewer Trusted Application User User Administrator User Locator View Manager View Manager Administrator View Manager Content Publisher Reporting and Analysis or EPM System Role Job Manager Deprecated Provisioning Manager Explorer Schedule Manager Reporting and Analysis Administrator Trusted Application Explorer Trusted Application Explorer. Provisioning Manager Reporting and Analysis Global Administrator. Before using the Migration Utility on a test or production system.

start vncserver so that it uses (at a minimum) HiColor. Have user ID. For example. it triggers the Event Service and creates faulty job output. If this parameter is set too small. password. such as updating last run date and decreasing the number of remaining times for the job to run. Fusion Edition. If a job is scheduled to run during the time of the migration. you may get a “Virtual storage or database resource is not available” error. Log onto Oracle Enterprise Performance Management Workspace. see “Fonts for Unix” in the Hyperion Workspace Administrator’s Guide.) For UNIX systems. and connectivity information for the repository databases. and ensure that Enable Harvesting is not selected. there may be some changes to the BRIOJOBS table. ● If your target system is DB2. set the LOCKTIMEOUT parameter to a finite value. vncserver -depth 15 or vncserver -depth 16. If jobs run during migration. select the Reporting and Analysis Repository database in the DB2 Administration tool. nls_length_semantics=char Brio Portal In addition to the General prerequisites: ● If you are using a DB2 data direct driver. set the APPLHEAPSZ parameter of the target database to a large value for the migration. Turn off the services on the source and target systems. ● Disable the Harvester service. and restart the database. Review the list of users and groups in Shared Services to confirm that they are the external users and groups to which you want to map the source system users and groups. ● Note: Scheduled jobs are migrated as part of the Broadcast Server migration. choose Administrator. then General. choose database parameters and change the LOCKTIMEOUT parameter value to a finite value (instead of the default NULL. if your source system uses external authentication. set the NLS_LENGTH_SEMANTICS parameter to char. Table 1 Prerequisites for Using the Migration Utility Details ● ● ● ● ● Prerequisite Type General Have a working Avalanche installation on the target system. ● Brio Intelligence In addition to the General prerequisites: ● Turn off the services on the source system. For example. (The services on the target system should stay running. add the BQ_FONT_PATH to the services. then you must configure Shared Services with the same external directory services. Have an administrator user ID and password for the source and target systems. ● If your target system is Oracle. screen resolutions set to 800x600 or lower are not supported. Have access to the old and new Repository databases. ● For systems using X-Windows on UNIX. The BQ_FONT_PATH environment variable is needed by the Interactive Reporting Service on the target system to ensure that BQY jobs and documents are rendered properly in the new environment. and a migrated 14 Overview and Prerequisites . For additional information on BQ_FONT_PATH. To do this.Note: When using the Migration Utility. Configure Shared Services for external authentication. or -1).sh file located in the <brio>/BrioPlatform/bin directory and restart the services.

Prerequisite Type

Details job might run an extra time in the migrated system than it needs to run. These changes do not affect migration.

BrioONE

In addition to the General prerequisites:
● ●

Complete all prerequisites for the Brio Portal and Brio Intelligence migrations. Complete the Portal migration, including all pre-migration steps, before running the OnDemand Server migration. Ensure that Portal categories (folders) have been correctly migrated before starting the OnDemand Server migration.

Hyperion Analyzer Hyperion Performance Suite 8

Complete the general prerequisites. In addition to the general prerequisites:

If you are using a DB2 data direct driver, set the APPLHEAPSZ parameter of the target database to a large value for the migration. If this parameter is set too small, you may get a “Virtual storage or database resource is not available” error. Turn off the services on the source and target systems.

Hyperion Reports

Complete the general prerequisites.

Other Migration Considerations
In addition to understanding the general migration process and reviewing the migration prerequisites, review the following topics for some additional issues to consider before migration.
● ● ● ●

Special Symbols in Users and Groups Invalid Characters in Workspace SmartCuts Migrating SAP Database Connections

Special Symbols in Users and Groups
There are certain symbols in a user’s first name, a user’s last name, a user’s login ID, and a group name that are not allowed in Reporting and Analysis. If the Migration Utility encounters any of these symbols, it replaces them with an acceptable symbol. Table 2 shows the symbol in the source system and the symbol it is replaced with in Reporting and Analysis.
Note:

These symbols also apply to roles migrated from the Hyperion Performance Suite 8 source system.

Other Migration Considerations

15

Table 2

Special Symbols Symbol in Reporting and Analysis _ * [ ] [ ] : / ` ~ Note: The '#' symbol is replaced with the ‘~’ symbol only if the '#' symbol is in the first position.

Symbol in Source System , = + < > ( ) ; \ " #

Example During migration, a user name of Smith,Alex is changed to Smith_Alex.
Note:

User login IDs and group names are trimmed for space symbols in the first and last positions.

Invalid Characters in Workspace
The following characters are not supported for objects in Workspace. Rename objects or folders containing these characters before migrating from the source system to the Reporting and Analysis Repository.

Invalid Name Characters
● ● ● ● ● ●

\ / % ? + <>

16

Overview and Prerequisites

● ● ● ● ●

| ' * : "

Invalid Path Characters
● ● ● ● ● ● ● ● ● ●

\ % ? + <> | ' * : "

SmartCuts
SmartCuts for object names with unsupported characters will not be displayed in EPM Workspace after migration. To ensure that your SmartCuts appear in Oracle Enterprise Performance Management Workspace, Fusion Edition, update any SmartCuts in your source system to use supported characters. For information on supported characters for SmartCuts, see “Managing SmartCuts” in the Hyperion Workspace Administrator's Guide.

Migrating SAP Database Connections
To migrate SAP database connections, do the following before running the Migration Utility:

UNIX: Copy SAPLOGON.INI to the $HOME directory, or ensure that the file location is specified in the $SAPLOGON_INI_FILE environment variable. Windows: Copy SAPLOGON.INI to the %WINDIR% directory, or ensure that file location is specified in the %SAPLOGON_INI_FILE% environment variable on the server where SAP is installed.

Note:

The SAPLOGON_INI_FILE environment variable should be a directory.

Other Migration Considerations

17

18

Overview and Prerequisites

...............................50 About Migrating from Brio Portal Use the Brio Portal option in the Migration Utility Wizard to migrate users...................................0................................................................................................................ and repository content from a Brio Portal 7....33 Defining the Location of the Reporting and Analysis Repository Database .............................................................................. Descriptions and Passwords........27 Defining the Hyperion Shared Services Registry Type ......................................................................................................................39 Reviewing User Names ................................................................2 In This Chapter Migrating from Brio Portal About Migrating from Brio Portal .......................................20 Selecting a Migration Path ....................................................................................................21 Defining the Database Used by the Portal Repository.......................................................... “Overview and Prerequisites.................47 Defining Additional Migration Options ......... Before performing the migration..............................22 Defining the Location of the Portal Repository Database .......................................29 Defining the Location of the Hyperion Registry Database..........................................................................41 Reviewing Group Names ..30 Defining Reporting and Analysis Repository Database Information ...............38 Defining User/Group Names................ review the information in Chapter 1................................................................... groups.........................................................................................................................................................................................................” About Migrating from Brio Portal 19 ........................................................................................................20 Entering Logging Details...............23 Identifying Portal Groups with Circular References .............................................................5 or later installation to Shared Services and the Reporting and Analysis Repository....................................................................................................19 Starting the Migration Utility Wizard............................................... roles..............................................................34 Defining the Location of the Shared Services Server ..............29 Defining Hyperion Registry Database Information ..26 Selecting the Objects to Migrate ............................................................................................................................................................................48 Running the Migration ..............................44 Mapping Hosts ............

then Oracle EPM System.bat file is located in: C:\Hyperion\products\Foundation\workspace\MigrationUtility\bin If you are using Windows.sh (UNIX) in the bin folder where you installed the Migration Utility. click migrator. Figure 1 Welcome Screen 20 Migrating from Brio Portal . Selecting a Migration Path Select Brio Portal on the Welcome screen and click Next. the migrator. then Workspace.bat (Windows) or migrator.Starting the Migration Utility Wizard ➤ To start the Migration Utility Wizard. If you installed to the default location. you can also start the Migration Utility Wizard by choosing Start. and then Run Migration Utility. then Programs.

Warn—Warning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. you can ignore this message if deleting that user is part of your migration plan. and potential problems. which may or may not be important for your particular migration scenario. Info—Informational messages notify you of structural changes made between the old and new systems. ● ● Entering Logging Details 21 . Figure 2 Logging Details Table 3 Logging Details Description Specify the log level by selecting one of the following options: ● ● Field Log Level Fatal—Fatal messages cause the migration process to stop. For example. an error message may tell you that a particular user does not exist in the source system. differences encountered between the old and new systems.Entering Logging Details Select the log level for messages and specify the directory in which to write the log files. Oracle recommends this level for most migrations. Logging information is important since this is the only place where you can see errors relating to the migration. Error—Error messages notify you of potential problems.

Debug level messages are numerous because they give a row-by-row account of all migration steps. Figure 3 Database Used by the Portal Repository Table 4 Database Type Information Description Select one of the following databases. Log Directory Specify the directory where you want to write the log file. click Browse. Oracle recommends this level for testing. Defining the Database Used by the Portal Repository Define which database contains the Brio Portal source repository and select how to specify the database location.Field Description ● Debug—Debug level messages include all types of messages and produces a very large log file. To search for a specific directory. ● ● Field Database Type SQL Server Oracle 22 Migrating from Brio Portal .

If your source system is installed on DB2 version 8. you can use data direct drivers. the wizard prompts you to provide full driver information. enter the information discussed in Table 5. Location of Portal Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Portal Repository” on page 22). JDBC Driver and URL—When you select this option. Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. click Test Connection to test the connection to the database. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information. use IBM native drivers to connect. you use data direct drivers.x . Defining the Location of the Portal Repository Database Define the connection to the Portal repository database on your existing system.x. Defining the Location of the Portal Repository Database 23 . The fields that appear on the next screen in the wizard depend on the option selected here.Field Description ● ● ● DB2 Informix Sybase Note: If your source system is installed on DB2 version 7.

Enter the database username used to set up a database connection. In most cases. 24 Migrating from Brio Portal . Enter the database port number. Field Host Port Database Name User ID Password Owner Location of Portal Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Portal Repository” on page 22). Optional: Enter the table owner/schema name. Enter the password for the database. Enter the name of the database. the owner is the same as the database username. enter the information discussed in Table 6.Figure 4 Location of Portal Repository Database Defined by Host and Name Table 5 Host and Name Information Description Enter the name of the database host.

If you wish to load a different external JDBC driver.DB2Driver and click Next to load it. Defining the Location of the Portal Repository Database 25 . if you selected Sybase. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.jdbc. Either type in the path. you must restart the Migration Utility. or click Browse to define the path.jar.SybaseDriver. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server. you cannot load another external JDBC driver with the same name.sybase. you cannot click Back and select another driver. the Migration Utility would enter hyperion.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. Figure 5 Location of Portal Repository Database Defined by JDBC Driver and URL Table 6 JDBC Driver and URL Information Description Enter the path to the native JDBC driver.db2. use sqljdbc. Note: Once you have loaded an external JDBC driver. For example.jdbc. For example. if you enter hyperion.

Field JDBC URL Description The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. In most cases. remove the references in the source Portal system before continuing with the migration. 3 Click Remove Relationship and Recheck. jdbc:hyperion:sybase://<host>:5000. which contains Group A. ➤ To search for circular references in Portal groups. 2 Select the relationship that contains the circular references under Select a Relationship to Remove From. It is important to remove circular references in Portal groups since Portal allows for circular references in groups and Shared Services does not. For example. they appear under “Circular References Found. Group A contains Group B. If the Migration Utility finds any circular references.” After all circular references are identified. the owner is the same as the database username. For example. Circular references are groups that contain other groups in a cyclical relationship. which contains Group C. User ID Password Owner Enter the database username used to set up a database connection. in the Sybase JDBC URL below. Modify this JDBC URL by personalizing the bracketed information. ➤ To remove a circular reference: 1 Select the circular reference under Circular References Found. Identifying Portal Groups with Circular References Search for and remove any existing circular references in Portal groups.DatabaseName=<dbname> remove <host> and <dbname> and replace them with the actual name of your host and database. click Start. 26 Migrating from Brio Portal . Enter the password for the database. Optional: Enter the table owner/schema name.

that you must migrate the objects in the order shown in the wizard. You can select individual objects to migrate here or on the final Run Migration screen. click the checkbox next to the object. To select an object. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. Selecting the Objects to Migrate 27 . however. The objects selected here determine what Portal migration screens appear next.Figure 6 Circular References Selecting the Objects to Migrate Select the Portal objects to migrate. Note.

and files.Figure 7 Portal Objects to Migrate Table 7 Portal Objects to Migrate Description Account owners identified by a user ID and user name. Descriptions of the repository data. Repository content is the largest object to migrate. The content of the system. jobs. Named collections of users. parameter lists for jobs. documents. and exceptions. the metadata could display the name of the content. folders.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices. Access control information for folders. To make the folder accessible. For example. the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. User-specific settings (such as an email address). Note: If a folder in the repository contains more than 80 to 90 items. Field Users Groups User Preferences Repository Metadata Events Authorization Repository Content 28 Migrating from Brio Portal . permissions etc.bat script and restart Common Services. User subscriptions and notifications of events involving subscriptions. and resources. add -DPerformance.

define which database is used by the Hyperion Registry and select how to specify the database location. Defining the Hyperion Shared Services Registry Type 29 .0. Defining Hyperion Registry Database Information If you selected to define a new Shared Services Registry (see “Defining the Hyperion Shared Services Registry Type” on page 125). the Migration Utility takes the required Shared Services and Foundation connection parameters (host names and ports) from the registry. New—Two additional wizard screens are displayed where you can enter data source connection details.0.5. ● Once a registry connection is established.Defining the Hyperion Shared Services Registry Type Define the Oracle's Hyperion Shared Services Registry to use by selecting an option: ● Default—The Migration Utility takes the connection from the local registry properties file in hyperion_home\common\config\9.

click Test Connection to test the connection to the database. you use data direct drivers. After you enter the requested information. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). 30 Migrating from Brio Portal . Defining the Location of the Hyperion Registry Database Define the location of the Hyperion Registry database.Table 8 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. The fields that appear on the next screen in the wizard depend on the option selected here. the wizard prompts you to provide full driver information. JDBC Driver and URL—When you select this option.

Enter the password for the Hyperion Registry database. Table 9 Hyperion Registry Database Host and Name Information Description Enter the name of the Hyperion Registry database host. Enter the Hyperion Registry database port number.Location of the Hyperion Registry Database by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion Registry Database Information” on page 126). enter the information in Table 58. Enter the name of the Hyperion Registry database. (see “Defining Hyperion Registry Database Information” on page 126). enter the information in Table 57. Enter the database username used to set up a Hyperion Registry database connection. Defining the Location of the Hyperion Registry Database 31 . Field Host Port Database Name User ID Password Location of the Hyperion Registry Database by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard.

<dbname>. For example. you must restart the Migration Utility. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. JDBC URL The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. in the DB2 JDBC URL below. database.db2. and <package> and replace them with the actual names of your server. you cannot click Back and select another driver.db2. Modify this JDBC URL by personalizing the bracketed information. For example. 32 Migrating from Brio Portal .DB2Driver and click Next to load it.DB2Driver. or click Browse to define the path. If you wish to load a different external JDBC driver.DatabaseName=<dbname>.Table 10 Hyperion Registry Database JDBC Driver and URL Information Description Enter the path to the native JDBC driver. and DB2 package. the Migration Utility would enter hyperion. jdbc:hyperion:db2://<server>: 50000.jdbc. you cannot load another external JDBC driver with the same name. For example. if you selected DB2. Either type in the path. Note: Once you have loaded an external JDBC driver. if you enter hyperion.jdbc. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen.PackageName=<package> remove <server>. User ID Enter the database username used to set up a Hyperion Registry database connection.

Defining Reporting and Analysis Repository Database Information Define which database contains the target Reporting and Analysis Repository and select how to specify the database location.Field Password Description Enter the password for the Hyperion Registry database. Figure 8 Database Used by the Reporting and Analysis Repository Table 11 Database Type Information Description Select one of the following databases: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: Defining Reporting and Analysis Repository Database Information 33 .

you use data direct drivers. enter the information discussed in Table 12. click Test Connection to test the connection to the database. After you enter the requested information. The fields that appear on the next screen in the wizard depend on the option selected here. Location of Reporting and Analysis Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 33). 34 Migrating from Brio Portal . Defining the Location of the Reporting and Analysis Repository Database Define the location of the Reporting and Analysis Repository database on the target system. the wizard prompts you to provide full driver information. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). JDBC Driver and URL—When you select this option.Field Description ● ● Host and Name—When you select this option.

manually copying your source tables to the target database is much quicker than allowing the Migration Utility to copy them over a network. Enter the name of the Reporting and Analysis Repository database. Optional: Enter the table owner/schema name. Select this option if you manually copied your source tables to the target database. Enter the database username used to set up a Reporting and Analysis Repository database connection.Figure 9 Location of Reporting and Analysis Repository Database Defined by Host and Name Table 12 Host and Name Information Description Enter the name of the Reporting and Analysis Repository database host. Enter the password for the Reporting and Analysis Repository database. In most cases. In most cases. the owner is the same as the database username. Enter the Reporting and Analysis Repository database port number. This is Field Host Port Database Name User ID Password Owner Source tables have been copied to the target database Defining the Location of the Reporting and Analysis Repository Database 35 .

If all of the tables are located in the same database before migration. use sqljdbc. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server. thus resulting in a much faster migration. If you manually copy your source tables to the target database. make sure to have both the source tables and the target tables accessible in one database user account. The following tables are affected: V7_CONTAINER V7_CONT_VERSION V7_DATA_CONTAINER V7_SPF_OUT_OPTS V7_COLLECTION_MBRS V7_COLLECTION V7_CONTNR_KEYWORDS V7_FOLDER V7_FOLDER_TREE V7_TASK VY_JOBINPUTVALUES V7_INPUT_PARAMETER Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 33). enter the information discussed in Table 13. Having your source and target tables in the same database user account can speed up large migrations by allowing you to use another utility to import large V7 tables into your target database. 36 Migrating from Brio Portal . however. the Migration Utility issues one command to move all of the rows in the table.jar. Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection.Field Description because the Migration Utility normally issues multiple commands to separately move each database row from the source database to the target database.

Figure 10 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL Table 13 JDBC Driver and URL Information Description Enter the path to the native JDBC driver. Note: Once you have loaded an external JDBC driver. For example. For example. If you wish to load a different external JDBC driver. Defining the Location of the Reporting and Analysis Repository Database 37 .jdbc. JDBC URL The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. in the DB2 JDBC URL below. if you selected DB2. or click Browse to define the path. Either type in the path.db2. you must restart the Migration Utility. Modify this JDBC URL by personalizing the bracketed information. For example.db2. you cannot click Back and select another driver.jdbc. if you enter hyperion. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen.DB2Driver and click Next to load it. you cannot load another external JDBC driver with the same name.DB2Driver. the Migration Utility would enter hyperion.

See description in Table 12. and <package> and replace them with the actual names of your server. After you enter the requested information. 38 Migrating from Brio Portal . and DB2 package. click Test Connection to test the connection to the server. Password Owner Source tables have been copied to the target database Defining the Location of the Shared Services Server Define the location of the Shared Services Server on the target system.PackageName=<packa ge> remove <server>. In most cases. User ID Enter the database username used to set up a Reporting and Analysis Repository database connection. the owner is the same as the database username. <dbname>. Optional: Enter the table owner/schema name. database.Field Description jdbc:hyperion:db2://<server>: 50000.DatabaseName=<dbname>. Enter the password for the Reporting and Analysis Repository database.

Field Host Port User ID Password Defining User/Group Names. Enter the login ID for the user in Shared Services. and authentication when creating new users in Shared Services. Descriptions and Passwords Define how to treat user descriptions. Enter the Shared Services Server port number. Defining User/Group Names. group names. Enter the password for the User ID. Descriptions and Passwords 39 . The user must have an administrative role in Shared Services. passwords.Figure 11 Location of Shared Services Server Table 14 Shared Services Server Information Description Enter the name of the Shared Services Server host.

If you select this option: ❍ ● Specify how the names in the source description fields are separated by selecting Space. Specify how to add middle names inShared Services by selecting an option for Add Middle Name to. ❍ ❍ 40 Migrating from Brio Portal . you can specify whether to add the middle name as part of the first name or as part of the last name. if the name appears starting with the last name. if a user name consists of more than two names. Shared Services User First and Last Name Fields—Copies the Portal User First and Last Name fields to the Shared Services User First and Last Name fields. Tab.Figure 12 User/Group Descriptions and Passwords Table 15 Information on User/Group Descriptions and Passwords Description Define how to copy the User Descriptions from Portal when creating new native Shared Services users. select Other and specify the delimiter. you would select Last Name. Semi-colon. Select one of the following options: ● Field User Descriptions Shared Services User Description—Copies the Portal User Description fields to the Shared Services User Description fields. Note that you can select more than one option. or Comma. Specify how the user names appear in Portal by selecting an option for Name Starts With. For example. If the names in the source description fields have a different delimiter. For example.

Reviewing User Names 41 . Alternate Group Name—Migrates the native Portal group name to a native Shared Services group name with a prefix or suffix added to the name.Field Group Names Description Define how to treat group names when migrating native groups by selecting one of the following options: ● Same Group Name —Migrates the native Portal group name to a native Shared Services group name and keeps the group name the same. The administrator can use this information to email users their new passwords. click the checkbox next to Portal Uses External NT Authentication and enter the default NT authentication domain. select a user name and click Properties (see “Editing User Name Properties” on page 42). Authentication If Portal currently uses external NT authentication to authenticate users. Enter the desired prefix or suffix in the Prefix or Suffix field. autogenerated password. the Migration Utility creates a file that lists the new native users along with their login ID. Most of the properties for each user name display next to the user name. ● Passwords Define how to handle passwords when creating new Shared Services users by selecting one of the following options: ● ● ● Auto-generated Same as user ID Get from Source Note: If the password is auto-generated. and email address. Reviewing User Names Review the user mappings and properties and set the migration action for each user. For a complete list of properties for a user.

The user names that meet the search criteria display. After you search for a user name.Figure 13 User Names Searching for User Names ➤ To search for a user name: 1 Click Search. 42 Migrating from Brio Portal . you can display all the user names again by clicking Show All. Editing User Name Properties ➤ To edit user name properties: 1 Select the desired user name and click Properties or double-click the user name. The Properties dialog box displays. 2 Define how to conduct the search in the Search dialog box and click Search again.

you would select the user name. 2 Edit the desired properties and click OK. Verifying User Name Mapping When you run the Migration Utility. the first and last name fields are automatically entered in the User Management User information. it queries the source system for users and attempts to automatically map them to existing Shared Services users based on the following criteria: ● ● ● login ID email address first name/last name If a mapping cannot be made. you can change the user name.The user name properties from both systems (source and target) are displayed. then during migration. You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. however. the Migration Utility creates a new native user. you cannot edit any of the Shared Services User properties. In the above screen. Some properties are read-only and some can be edited. click Properties. to map a Portal user name to a different Shared Services user name. Reviewing User Names 43 . For example. Note: For existing users. If you change the user name. and change the Shared Services user name in the Properties dialog box. the user is mapped to another Shared Services user or a new user is created with the new name. then during migration.

44 Migrating from Brio Portal . you must delete the user directly from Shared Services. click Properties. all new native users whose action is set to Migrate are migrated to Shared Services. and select the desired option in the Action field. Users who are not migrated lose all access control information associated with them as well as any assigned user properties. This setting cannot be changed. Most of the properties for each group name display next to the group name. you can set the migration action property to Migrate or Do Not Migrate. Discard Changes (restore original values)—Retrieves the user names from each system. To do this. To set the action for more than one user. instead.Setting the Migration Action For each user. you must manually activate the user in the source system before performing the migration. When specifying whether to migrate users from Portal to Shared Services. press [Shift] and select the desired user names. use one of the following options: ● ● Select the user. and restores mapping and property information to the original values. Select the user and click the checkbox next to Migrate User Name from Portal to Shared Services. select a group name and click Properties (see “Editing Group Name Properties” on page 45). the Migration Utility does not remove the previously-migrated user from Shared Services. or click Select All to select all the user names. To migrate a deactivated user. keep in mind the following: ● When you perform a migration. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the user names from each system and keeps any changes made to the mapping and property information. If you later change a user’s action to Do Not Migrate and perform another migration. The default setting for inactive users is Do Not Migrate. For a complete list of properties for a group. ● Reviewing Group Names Review the group mappings and properties and set the migration action for each group. ● ● Updating User Name Information If you wish to refresh the automatic mapping on the User Names screen. discards any changes made to the mapping or properties.

2 Define how to conduct the search in the Search dialog box and click Search again. Reviewing Group Names 45 . After you search for a group name. The group names that meet the search criteria display. you can display all the group names again by clicking Show All.Figure 14 Group Names Searching for Group Names ➤ To search for a group name: 1 Click Search. Editing Group Name Properties ➤ To edit group name properties: 1 Select the desired group name and click Properties or double-click the group name. The Properties dialog box displays.

You can view these mappings on the Group Names screen and manually adjust or change the mappings as necessary. Select the group and click the checkbox next to Migrate Group Name from Portal to Shared Services. you can set the Action property to Migrate or Do Not Migrate. the Migration Utility creates a new native group. To do this. To set the action for more than one group. click Properties. When specifying whether to migrate groups from Portal to Shared Services. Verifying Group Name Mapping When you run the Migration Utility. or click Select All to select all the group names. it queries the source system for groups and attempts to automatically map them to existing Shared Services groups based on the group name. you cannot edit any of the properties in the Shared Services Group section of the dialog box. Some properties are read-only and some can be edited. If a mapping cannot be made. and change the Shared Services group name in the Properties dialog box.The group name properties from both systems (source and target) are displayed. keep in mind the following: 46 Migrating from Brio Portal . If the group is set to Do Not Migrate. Setting the Migration Action For each group. For example. click Properties. then during migration. 2 Edit the desired properties and click OK. press [Shift] and select the desired group names. use one of the following options: ● ● Select the group. to map a Portal group name to a different Shared Services group name. you would select the group name. and select the desired option in the Action field.

This setting cannot be changed. If you want to migrate a deactivated group. set the Action property of the native parent group to Migrate. set the Action property to Migrate for the all users belonging to the group that have already been migrated. For example. When you migrate content. When you migrate groups. or click Select All to select all the group names. This ensures that user properties and access control information referring to the users and groups migrates correctly.● The default setting for inactive groups is Do Not Migrate. this new native group is created and any users and groups assigned to the group in the source system are assigned to the group in the target system. you must manually activate the group in the source system before performing the migration. and restores mapping and property information to the original values. you must map each source job factory to a new Reporting and Analysis Repository host. 2 Click the checkbox next to Add Users/Groups Assigned in Portal to the Native Shared Services Group. This ensures that user/group relationships migrate correctly. ● Mapping Hosts Define the mapping for the Portal hosts and the Reporting and Analysis Repository hosts. ● ● ● Adding Users/Groups Assigned in Portal to the Native Shared Services Group ➤ To add users and groups assigned in Portal to the native Shared Services group: 1 Press [Shift] and select the desired group names. If you migrate a group that is a member of a native parent group (that is going to be migrated or was already migrated). Updating Group Name Information If you wish to refresh the automatic mapping on the Group Names screen. discards any changes made to the mapping or properties. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the group names from each system and keeps any changes made to the mapping and property information. Mapping Hosts 47 . then upon migration. Note: When you select this option. if a group in Portal is going to be mapped to a new native group in Shared Services. set the Action property to Migrate for all users and groups that have already been migrated. This ensures that group-to-group associations migrate correctly. Discard Changes (restore original values)—Retrieves the group names from each system.

Defining Additional Migration Options Select additional Portal options to provide advanced control of the migration process. ➤ To remove a mapped pair of hosts.Figure 15 Host Mapping ➤ To map a host. The hosts display in the Mapped Hosts text box. 48 Migrating from Brio Portal . select a Portal Host and a Reporting and Analysis Repository Host and click Map Hosts. select the hosts in the Mapped Hosts text box and click Remove Mapped Host.

Repository Content Enter the Source Path and the Target Path for the repository content.x “Write” or “Write and Execute” permissions to the Reporting and Analysis Repository “Full Control” role. which does not allow deletion. As a result. In Portal 7. Full Control in the Reporting and Analysis Repository—Select this option to map "Write" or "Write and Execute" to the “Full Control” access control.Figure 16 Additional Migration Options Table 16 Additional Migration Options Description Define how to translate the Write access control in Portal by selecting one of the following options: ● Field Authorization Modify in the Reporting and Analysis Repository—Select this option to map "Write" or "Write and Execute" to the "Modify" access control. you could delete an object if you had permission to write to the object.x. The “Write” permission in 7. Publishing masks are permissions that the output gets when it runs in the Reporting and Analysis Repository. Either type in the path or click Browse to select a path. Job Group Publishing Masks only apply if you are doing authorization. ● Select Setup job publishing mask group permissions to use job group publishing masks when migrating jobs to the Reporting and Analysis Repository.x maps to the “Modify” role in the Reporting and Analysis Repository. you must map the version 7. Defining Additional Migration Options 49 . if you want permission to delete an object in the Reporting and Analysis Repository.

After you complete the pre-migration test and fix all the outstanding errors. define the version of the files in the Reporting and Analysis Repository. it reports them in the log files. You should fix any potential errors encountered in the pre-migration process before performing an actual migration. you must re-compile all your Production Reporting jobs. After all the users migrate successfully. 50 Migrating from Brio Portal .3 as 83. you could begin by selecting Users. Note. ➤ To migrate each object type separately: 1 Select the desired object type. you may want to backup the target database after you successfully migrate each object type. Unless addressed. If the Migration Utility finds any problems. the Migration Utility goes through the migration process without actually moving objects from the source system to the target system. select Test Only as the Run Mode. Note: After you complete the migration. Note: After you complete the migration. enter Version 8. During a pre-migration test. (The Migration Utility updates both the target database and the OpenLDAP database. Hyperion strongly recommends that you run a pre-migration process before completing an actual migration. and so on. to run a test migration that will help determine any migration issues. you should also backup the OpenLDAP database. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object.) 5 Return to the wizard and select the next object to migrate. ➤ To run a pre-migration process. 3 Check to make sure the object migrated correctly and fix any errors. For example.) This step is optional. and to run the actual migration.0 as 90. As an extra precaution. 4 Backup your target database (and your OpenLDAP database if you are migrating users and groups. When you migrate users and groups.Field Repository Job Factory Description If you plan to migrate Production Reporting files. however. you would select Groups. Version 9. you must re-compile all your Production Reporting jobs. that you must migrate the objects in the order shown in the wizard. 2 Select Perform Migration as the Run Mode and click Start. For example. errors may cause the actual migration to stop or remain incomplete. Running the Migration The final screen of the Migration Utility Wizard allows you to review the objects selected to migrate.

Progress Displays information about the progress of the migration such as successes. Note: Oracle recommends that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object. Field Select the Objects to Migrate Run Mode Select one of the following options: ● ● Test Only—Runs a pre-migration process to help identify any migration issues. errors may cause the actual migration to stop or remain incomplete.Figure 17 Run Migration Table 17 Run Migration Options Description Review the objects selected to migrate. Unless addressed. the number of objects remaining to be migrated. Displays information messages about the migration. Perform Migration—Runs the actual migration. Status Messages Running the Migration 51 . warnings. and the number of objects migrated. Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. The objects that are enabled are the objects selected on the Select Objects to Migrate screen earlier in the wizard (see “Selecting the Objects to Migrate” on page 27). errors.

52 Migrating from Brio Portal .

....... groups..... “Overview and Prerequisites.. If desired.... you can migrate both Brio Portal information and OnDemand Server information....................................................... BrioONE consists of the following components: ● ● Brio Portal 7........ After you have selected a migration path and entered logging details.......... however..................54 About Migrating from BrioOne Use the BrioONE option in the Migration Utility Wizard to migrate users........... you must run the Portal wizard before you run the OnDemand Server wizard.......3 In This Chapter Migrating from BrioONE About Migrating from BrioOne .0.....” Running the Brio Portal Migration To run Brio Portal information following directly by OnDemand Server information........5 or later OnDemand Server 6. review the information in Chapter 1...................... To run the Brio Portal wizard steps separately......... Checking both options on the Welcome screen directs the Migration Utility to run the Portal steps in the wizard followed directly by the OnDemand Server steps in the wizard..4 or later When you run a BrioONE migration...... select the Portal option under BrioONE... running the Brio Portal migration involves: ● Defining the Database Used by the Portal Repository About Migrating from BrioOne 53 ..................... roles....53 Running the OnDemand Server Migration ....53 Running the Brio Portal Migration ........... and repository content from a BrioONE installation to Shared Services and the Reporting and Analysis Repository................................. select BrioONE on the Welcome screen (this checks both the Portal and the OnDemand Server options)...... you can run the Portal and OnDemand Server wizard steps separately. Before performing the migration.......6....................................

“Migrating from Brio Portal ” for detailed information on migrating information from Brio Portal.● ● ● ● ● ● ● ● ● ● ● ● Defining the Location of the Portal Repository Database Identifying Portal Groups with Circular References Selecting the Objects to Migrate Defining Reporting and Analysis Repository Database Information Defining the Location of the Reporting and Analysis Repository Database Defining the Location of the Shared Services Server Defining User/Group Names. If you selected both Portal and OnDemand Server under BrioOne on the Welcome screen. Running the OnDemand Server Migration Before you migrate OnDemand Server information. ● If you already ran the Portal migration and exited from the wizard. you can start the OnDemand Server migration by checking the OnDemand Server option under BrioOne. make sure that you have already migrated Brio Portal information. ● After you have selected a migration path and entered logging details. the OnDemand Server wizard screens automatically appear after the Portal wizard screens. Descriptions and Passwords Reviewing User Names Reviewing Group Names Mapping Hosts Defining Additional Migration Options Running the Migration See Chapter 2. running the OnDemand Server migration involves: ● ● ● ● ● ● “Defining the Database Used by the OnDemand Server Repository” on page 55 “Defining the Location of the OnDemand Server Repository Database” on page 56 “Defining the Location of the OnDemand Server Installation Files” on page 59 “Selecting the Objects to Migrate” on page 60 “Defining Target Row Level Security Repository Database Information” on page 62 “Defining the Location of the Target Row Level Security Repository Database” on page 63 “Defining the Hyperion Shared Services Registry Type” on page 66 “Defining Hyperion Registry Database Information” on page 67 “Defining the Location of the Hyperion Registry Database” on page 68 “Defining Reporting and Analysis Repository Database Information” on page 71 ● ● ● ● 54 Migrating from BrioONE .

Figure 18 Database Used by the OnDemand Server Repository Running the OnDemand Server Migration 55 .● ● ● ● ● ● ● “Defining the Location of the Reporting and Analysis Repository Database” on page 72 “Defining the Location of the Reporting and Analysis Repository Server” on page 75 “Defining the Location of the Shared Services Server” on page 76 “Defining User/Group Names. Descriptions. and Passwords” on page 77 “Reviewing User Names” on page 78 “Reviewing Group Names” on page 81 “Running the Migration” on page 84 Defining the Database Used by the OnDemand Server Repository Define which database contains the OnDemand Server source repository and select how to specify the database location.

56 Migrating from BrioONE . use IBM native drivers to connect. click Test Connection to test the connection to the database. The fields that appear on the next screen in the wizard depend on the option selected here. JDBC Driver and URL—When you select this option. you use data direct drivers. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). you can use data direct drivers. enter the information discussed in Table 19. the wizard prompts you to provide full driver information. ● ● ● ● ● ● Field Database Type SQL Server Oracle DB2 Informix Sybase Redbrick Note: If your source system is installed on DB2 version 7. Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option.x.Table 18 Database Type Information Description Select one of the following databases. Defining the Location of the OnDemand Server Repository Database Define the connection to the OnDemand Server repository database on your existing system. If your source system is installed on DB2 version 8. After you enter the requested information. Location of OnDemand Server Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the OnDemand Server Repository” on page 55).x .

Enter the table owner/schema name. Enter the database username used to set up a database connection. enter the information discussed in Table 20. Enter the name of the database. Field Host Port Database Name User ID Password Owner Location of OnDemand Server Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the OnDemand Server Repository” on page 55). Enter the database port number. Running the OnDemand Server Migration 57 .Figure 19 Location of OnDemand Server Repository Database Defined by Host and Name Table 19 Host and Name Information Description Enter the name of the database host. In most cases. Enter the password for the database. the owner is the same as the database username.

you cannot click Back and select another driver. or click Browse to define the path. For example. 58 Migrating from BrioONE . For example. the migration utility would enter hyperion. if you selected DB2. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. If you wish to load a different external JDBC driver.db2. Either type in the path.db2.DB2Driver. use sqljdbc. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server.jar.DB2Driver and click Next to load it. if you enter hyperion.jdbc.jdbc. Figure 20 Location of OnDemand Server Repository Database Defined by JDBC Driver and URL Table 20 JDBC Driver and URL Information Description Enter the path to the native JDBC driver.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection. you cannot load another external JDBC driver with the same name. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen. Note: Once you have loaded an external JDBC driver. you must restart the Migration Utility.

<dbname>.PackageName=<package> remove <server>. In most cases. in the DB2 JDBC URL below.pwd file. jdbc:hyperion:db2://<server>: 50000. Enter the table owner/schema name. Figure 21 OnDemand Server Installation Files Running the OnDemand Server Migration 59 .ini file and the ODS. Modify this JDBC URL by personalizing the bracketed information.DatabaseName=<dbname>. database.Field JDBC URL Description The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. Defining the Location of the OnDemand Server Installation Files Enter the location of the ODS. and <package> and replace them with the actual names of your server. For example. Enter the password for the database. the owner is the same as the database username. and DB2 package. User ID Password Owner Enter the database username used to set up an OnDemand Server database connection.

Selecting the Objects to Migrate Select the OnDemand Server objects to migrate.pwd file. that you must migrate the objects in the order shown in the wizard. Note. enter the following information: ● Mapped OCE Path—Map the OCE directory on the installation machine to the OCE directory on the source system. ● Mapped BQY Path—Map the BQY directory on the installation machine to the BQY directory on the source system. click the checkbox next to the object.ini File ODS.ini file. map Z:\ on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \Program\Documents on the source system. This file is usually found under: <drive>:/Program Files/Brio/Brio Intelligence Server/Server Field ODS. The objects selected here determine what OnDemand Server migration screens appear next. map Z:\ on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \Program\Open Catalog Extensions on the source system. however. This file is usually found under: <drive>:/Program Files/Brio/Brio Intelligence Server/Server Migration Utility is Not Running on the OnDemand Server Select this option if you are running the migration utility from a machine other than the source system.Table 21 OnDemand Server Installation Files Description Enter the path for the location of your ODS. For example.pwd File Enter the path for the location of your ODS. If running on a machine other than the source. You can select individual objects to migrate here or on the final Run Migration screen. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. 60 Migrating from BrioONE . For example. To select an object.

The default parent group is / BrioODSGroup. Running the OnDemand Server Migration 61 . Note: If a folder in the repository contains more than 80 to 90 items. click the checkbox and select an option from the list that appears. When you migrate groups. To select a User Insight Privilege.bat script and restart Common Services. the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. To make the folder accessible. Folders are similar to the directories or folders of your operating system.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices. A folder can contain subfolders. you must enter a Parent Group. User Insight Privileges include: ● ● ● Field Users Insight Quickview Freeview Groups Named collections of users. Folders Items are organized into folders.Figure 22 OnDemand Server Objects to Migrate Table 22 OnDemand Server Objects to Migrate Description Account owners identified by a user ID and user name. add -DPerformance. or both. items. and are arranged in a hierarchical structure.

the network address of the database server. Managers do not need to know payroll information for other departments within the organization. When you migrate OCE files. click the checkbox next to Enable Thin Client Version. database software. etc.oce. managers need payroll information on their direct reports.). An OCE file is required for a Hyperion Intelligence document to use a database. To view BQY documents in the Shared Services thin-client. and your database user name. Row Level Security Data Data containing row-level security. Row-level security gives users access to only the information they need to make informed decisions. Note: This screen appears only if you selected Row Level Security Data on the Objects to Migrate wizard screen. The default is / Open Catalog Extensions.Field OCE Files Description Files that encapsulate and store connection information used to connect Hyperion applications to a database. SQL*Net. For example. the next page in the migration utility wizard prompts you to configure the target row level security repository. BQY Documents Files created by Hyperion Intelligence and published into the Repository as files or as jobs. OCE files specify the database API (ODBC. you must enter the OCE folder on Target. When you select this object. 62 Migrating from BrioONE . The file extension is . Defining Target Row Level Security Repository Database Information Define which database contains the target Row Level Security Repository and select how to specify the database location. Once created. a user can specify the OCE file and database password and logon.

The fields displayed vary depending on the database location specified on previous screen (Host and Running the OnDemand Server Migration 63 . the wizard prompts you to provide full driver information. you use data direct drivers.Figure 23 Database Used by the Target Row Level Security Repository Table 23 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. Defining the Location of the Target Row Level Security Repository Database Define the location of the Row Level Security Repository database on the target system. JDBC Driver and URL—When you select this option. The fields that appear on the next screen in the wizard depend on the option selected here.

Enter the name of the Row Level Security Repository database. Enter the password for the Row Level Security Repository database.Name or JDBC Driver and URL). Figure 24 Location of Row Level Security Repository Database Defined by Host and Name Table 24 Host and Name Information Description Enter the name of the Row Level Security Repository database host. Enter theRow Level Security Repository database port number. Enter the username used to set up a Row Level Security Repository database connection. After you enter the requested information. Field Host Port Database Name User ID Password 64 Migrating from BrioONE . Location of Target Row Level Security Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 71). click Test Connection to test the connection to the database. enter the information discussed in Table 24.

enter the information discussed in Table 25.Field Owner Description Optional: Enter the table owner/schema name. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server. use sqljdbc. the owner is the same as the database username. In most cases. Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection. Location of Target Row Level Security Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 71).jar. Figure 25 Location of Row Level Security Repository Defined by JDBC Driver and URL Running the OnDemand Server Migration 65 .

jdbc:hyperion:SQLSERVER://<host>: 1433. For example. Optional: Enter the table owner/schema name. you cannot click Back and select another driver.0.jdbc. If you wish to load a different external JDBC driver. 66 Migrating from BrioONE .Table 25 JDBC Driver and URL Information Description Enter the path to the native JDBC driver. ● Once a registry connection is established. Modify this JDBC URL by personalizing the bracketed information.SQLServerDriver. in the SQL Server JDBC URL below. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. you must restart the Migration Utility. the migration utility would enter hyperion. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen. or click Browse to define the path.db2. For example. For example.5.sqlserver.DB2Driver and click Next to load it. Enter the password for the Row Level Security Repository database. the owner is the same as the database username. Note: Once you have loaded an external JDBC driver. the Migration Utility takes the required Shared Services and Foundation connection parameters (host names and ports) from the registry.0. JDBC URL The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. New—Two additional wizard screens are displayed where you can enter data source connection details. Password Owner Defining the Hyperion Shared Services Registry Type Define the Shared Services Registry to use by selecting an option: ● Default—The Migration Utility takes the connection from the local registry properties file in hyperion_home\common\config\9. if you enter hyperion.SelectMethod=cursor remove <host> and <dbname> replace them with the actual host and database names. In most cases. User ID Enter the database username used to set up a Row Level Security Repository database connection. Either type in the path.DatabaseName=<dbname>.jdbc. if you selected SQL Server. you cannot load another external JDBC driver with the same name.

define which database is used by the Hyperion Registry and select how to specify the database location. Running the OnDemand Server Migration 67 .Defining Hyperion Registry Database Information If you selected to define a new Shared Services Registry (see “Defining the Hyperion Shared Services Registry Type” on page 125).

68 Migrating from BrioONE . After you enter the requested information. the wizard prompts you to provide full driver information. you use data direct drivers. click Test Connection to test the connection to the database. Defining the Location of the Hyperion Registry Database Define the location of the Hyperion Registry database. JDBC Driver and URL—When you select this option. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). The fields that appear on the next screen in the wizard depend on the option selected here.Table 26 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option.

Enter the Hyperion Registry database port number. Enter the database username used to set up a Hyperion Registry database connection. Enter the password for the Hyperion Registry database. enter the information in Table 57. Enter the name of the Hyperion Registry database. enter the information in Table 58. Field Host Port Database Name User ID Password Location of the Hyperion Registry Database by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard. Running the OnDemand Server Migration 69 . (see “Defining Hyperion Registry Database Information” on page 126). Table 27 Hyperion Registry Database Host and Name Information Description Enter the name of the Hyperion Registry database host.Location of the Hyperion Registry Database by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion Registry Database Information” on page 126).

User ID Enter the database username used to set up a Hyperion Registry database connection.jdbc. Note: Once you have loaded an external JDBC driver. For example. you cannot click Back and select another driver. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. database.PackageName=<package> remove <server>. JDBC URL The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. the Migration Utility would enter hyperion. <dbname>. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. or click Browse to define the path.DB2Driver. you cannot load another external JDBC driver with the same name. If you wish to load a different external JDBC driver.db2. For example. Either type in the path. For example. Modify this JDBC URL by personalizing the bracketed information.db2. 70 Migrating from BrioONE . and <package> and replace them with the actual names of your server.Table 28 Hyperion Registry Database JDBC Driver and URL Information Description Enter the path to the native JDBC driver.jdbc. if you enter hyperion. if you selected DB2. you must restart the Migration Utility. in the DB2 JDBC URL below.DB2Driver and click Next to load it. and DB2 package. jdbc:hyperion:db2://<server>: 50000.DatabaseName=<dbname>.

Field Password Description Enter the password for the Hyperion Registry database. Figure 26 Database Used by the Reporting and Analysis Repository Table 29 Database Type Information Description Select one of the following databases: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: Running the OnDemand Server Migration 71 . Defining Reporting and Analysis Repository Database Information Define which database contains the target Reporting and Analysis Repository and select how to specify the database location.

Defining the Location of the Reporting and Analysis Repository Database Define the location of the Reporting and Analysis Repository database on the target system. JDBC Driver and URL—When you select this option. The fields that appear on the next screen in the wizard depend on the option selected here. click Test Connection to test the connection to the database. Location of Reporting and Analysis Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 71). After you enter the requested information. you use data direct drivers. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). enter the information discussed in Table 30. the wizard prompts you to provide full driver information. 72 Migrating from BrioONE .Field Description ● ● Host and Name—When you select this option.

Enter the password for the Reporting and Analysis Repository database. Running the OnDemand Server Migration 73 . Enter the name of the Reporting and Analysis Repository database.Figure 27 Location of Reporting and Analysis Repository Database Defined by Host and Name Table 30 Host and Name Information Description Enter the name of the Reporting and Analysis Repository database host. Field Host Port Database Name User ID Password Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 71). enter the information discussed in Table 31. Enter the username used to set up a Reporting and Analysis Repository database connection. Enter the Reporting and Analysis Repository database port number.

Either type in the path. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen. if you selected DB2. Figure 28 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL Table 31 JDBC Driver and URL Information Description Enter the path to the native JDBC driver.jar. if you enter hyperion. If you wish to load a different external JDBC driver.db2. Note: Once you have loaded an external JDBC driver. 74 Migrating from BrioONE .DB2Driver.jdbc. or click Browse to define the path. For example. For example.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.db2.DB2Driver and click Next to load it. you must restart the Migration Utility. use sqljdbc. the migration utility would enter hyperion.jdbc. you cannot load another external JDBC driver with the same name. you cannot click Back and select another driver. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server.

and <package> and replace them with the actual names of your server. For example.DatabaseName=<dbname>. and DB2 package. User ID Enter the database username used to set up a Reporting and Analysis Repository database connection. Modify this JDBC URL by personalizing the bracketed information. Enter the password for the Reporting and Analysis Repository database. Figure 29 Location of Target Reporting and Analysis Repository Server Running the OnDemand Server Migration 75 . in the DB2 JDBC URL below. Password Defining the Location of the Reporting and Analysis Repository Server Define the connection to the Reporting and Analysis Repository Server on the target system. click Test Connection to test the connection to the server. <dbname>.PackageName=<package> remove <server>. database. After you enter the requested information.Field JDBC URL Description The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. jdbc:hyperion:db2://<server>: 50000.

Enter the user ID of a user with Global Administrator. After you enter the requested information. Field Host Port User ID Password Defining the Location of the Shared Services Server Define the location of the Shared Services Server on the target system. click Test Connection to test the connection to the server.Table 32 Reporting and Analysis Repository Server Information Description Enter the name of the Reporting and Analysis Repository Server host. Directory Manager. Enter the password for the user ID. and Provisioning Manager roles. Field Host 76 Migrating from BrioONE . Enter the Reporting and Analysis Repository Server port number. Figure 30 Location of Target Shared Services Server Table 33 Shared Services Server Information Description Enter the name of the Shared Services Server host.

Password Defining User/Group Names. Running the OnDemand Server Migration 77 . Descriptions. Enter the password for the User ID.Field Port User ID Description Enter the Shared Services Server port number. The user must have an administrative role in Shared Services. and Passwords Define how to treat group names and passwords when creating new users in the Shared Services Server. Enter the login ID for the user in Shared Services. Figure 31 User/Group Descriptions and Passwords Table 34 Information on Group Descriptions and Passwords Description Define how to treat group names when migrating native groups by selecting one of the following options: ● Field Group Names Same Group Name—Migrates the native Intelligence group name to a native Shared Services group name and keeps the group name the same.

Most of the properties for each user name display next to the user name. The administrator can use this information to email users their new passwords. autogenerated password. Figure 32 User Names 78 Migrating from BrioONE . Enter the desired prefix or suffix in the Prefix or Suffix field.Field Description ● Alternate Group Name—Migrates the native Intelligence group name to a native Shared Services group name with a prefix or suffix added to the name. Reviewing User Names Review the user mappings and properties and set the migration action for each user. Passwords Define how to handle passwords when creating new Shared Services users by selecting one of the following options: ● ● ● Auto-generated Same as user ID Other Note: If the password is auto-generated. select a user name and click Properties (see “Editing User Name Properties” on page 79). and email address. the migration utility creates a file that lists the new native users along with their login ID. For a complete list of properties for a user.

then during migration. The Properties dialog box displays. the user is mapped to another Shared Services user or a new user is created with the new name. Editing User Name Properties ➤ To edit user name properties: 1 Select the desired user name and click Properties or double-click the user name. After you search for a user name. you can display all the user names again by clicking Show All. however. Some properties are read-only and some can be edited. Note: For existing users. it queries the source system for users and attempts to automatically map them to existing Shared Services users based on the following criteria: ● login ID Running the OnDemand Server Migration 79 . The user names that meet the search criteria display. Verifying User Name Mapping When you run the migration utility.Searching for User Names ➤ To search for a user name: 1 Click Search. you can change the user name. you cannot edit any of the Shared Services User properties. 2 Edit the desired properties and click OK. The user ID properties from both systems (source and target) are displayed. 2 Define how to conduct the search in the Search dialog box and click Search again. If you change the user name.

press [Shift] and select the desired user names.● ● email address first name/last name If a mapping cannot be made. you must manually activate the user in the source system before performing the migration. This setting cannot be changed. use one of the following options: ● ● Select the user. click Properties. and restores mapping and property information to the original values. the migration utility creates a new native user. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the user names from each system and keeps any changes made to the mapping and property information. then during migration. you can set the migration action property to Migrate or Do Not Migrate. For example. ● 80 Migrating from BrioONE . Setting the Migration Action For each user. and change the Shared Services user name in the Properties dialog box. ● ● Updating User Name Information If you wish to refresh the automatic mapping on the User Names screen. you must delete the user directly from the target Shared Services. you would select the user name. instead. When specifying whether to migrate users from Intelligence to Shared Services. Users who are not migrated lose all access control information associated with them as well as any assigned user properties. You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. and select the desired option in the Action field. The default setting for inactive users is Do Not Migrate. to map an Intelligence user name to a different Shared Services user name. To set the action for more than one user. or click Select All to select all the user names. click Properties. Discard Changes (restore original values)—Retrieves the user names from each system. If you later change a user’s action to Do Not Migrate and perform another migration. To do this. the migration utility does not remove the previously-migrated user from target Shared Services system. To migrate a deactivated user. discards any changes made to the mapping or properties. keep in mind the following: ● When you perform a migration. Select the user and click the checkbox next to Migrate User Name from Intelligence to Shared Services. all new native users whose action is set to Migrate are migrated to the target Shared Services.

Running the OnDemand Server Migration 81 . select a group name and click Properties (see “Editing Group Name Properties” on page 82). Figure 33 Group Names Searching for Group Names ➤ To search for a group name: 1 Click Search.Reviewing Group Names Review the group mappings and properties and set the migration action for each group. After you search for a group name. The group names that meet the search criteria display. For a complete list properties for a group. you can display all the group names again by clicking Show All. Most of the properties for each group name display next to the group name. 2 Define how to conduct the search in the Search dialog box and click Search again.

The Properties dialog box displays. and change the Shared Services group name in the Properties dialog box. You can view these mappings on the Group Names screen and manually adjust or change the mappings as necessary. The group names properties from both systems (source and target) are displayed. 2 Edit the desired properties and click OK.Editing Group Name Properties ➤ To edit group name properties: 1 Select the desired group name and click Properties. click Properties. to map an Intelligence group name to a different Shared Services group name. then during migration. if a group in the source system is going to be mapped to a new native group in Shared Services. you would select the group name. 82 Migrating from BrioONE . Some properties are read-only and some can be edited. If the group is set to Do Not Migrate. it queries the source system for groups and attempts to automatically map them to existing Shared Services groups based on the group name. this new native group is created and any users and groups assigned to the group in the source system are assigned to the group in the target system. then upon migration. you cannot edit any of the properties in the User Management Group section of the dialog box. Note: When you select this option. the migration utility creates a new native group. For example. Verifying Group Name Mapping When you run the migration utility. If a mapping cannot be made.

or click Select All to select all the group names. set the Action property to Migrate for the all users belonging to the group that have already been migrated. then upon migration. To set the action for more than one group. click Properties.Setting the Migration Action For each group. this new native group is created and any users and groups assigned to the group in the source system are assigned to the group in the target system. if a group in Intelligence is going to be mapped to a new native group in Shared Services. 2 Click the checkbox next to Add Users/Groups Assigned in Intelligence to the Native Shared Services Group. To migrate a deactivated group. Note: When you select this option. keep in mind the following: ● The default setting for inactive groups is Do Not Migrate. This ensures that user properties and access control information referring to the users and groups migrates correctly. When specifying whether to migrate groups from Intelligence to Shared Services. To do this. and select the desired option in the Action field. press [Shift] and select the desired group names. If you migrate a group that is a member of a native parent group (that is going to be migrated or was already migrated). or click Select All to select all the group names. you must manually activate the group in the source system before performing the migration. When you migrate groups. you can set the Action property to Migrate or Do Not Migrate. Running the OnDemand Server Migration 83 . set the Action property of the native parent group to Migrate. Select the group and click the checkbox next to Migrate Group Name from Intelligence to Shared Services. When you migrate content. use one of the following options: ● ● Select the group. This ensures that user/group relationships migrate correctly. set the Action property to Migrate for all users and groups that have already been migrated. This ensures that group-to-group associations migrate correctly. ● ● ● Adding Users/Groups Assigned in Intelligence to the Native Shared Services Group ➤ To add users and groups assigned in Intelligence to the native Shared Services group: 1 Press [Shift] and select the desired group names. This setting cannot be changed.

You should you fix any potential errors encountered in the pre-migration process before performing an actual migration. and to run the actual migration. errors may cause the actual migration to stop or remain incomplete. After you complete the pre-migration test and fix all the outstanding errors.) This step is optional. 4 Backup your target database (and your OpenLDAP database if you are migrating users and groups. however. ➤ To run a pre-migration process. If the migration utility finds any problems. to run a test migration that will help determine any migration issues. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. that you must migrate the objects in the order shown in the wizard. 84 Migrating from BrioONE . ● Running the Migration The final screen of the Migration Utility wizard allows you to review the objects selected to migrate. the migration utility goes through the migration process without actually moving objects from the source system to the target system. ➤ To migrate each object type separately: 1 Select the desired object type. When you migrate users and groups. it reports them in the log files. 3 Check to make sure the object migrated correctly and fix any errors. you would select Groups. select Test Only as the Run Mode. Note. After all the users migrated successfully. you should also backup the OpenLDAP database. you may want to backup the target database after you successfully migrate each object type. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the group names from each system and keeps any changes made to the mapping and property information. As an extra precaution.Updating Group Name Information If you wish to refresh the automatic mapping on the Group Names screen. you could begin by selecting Users. Hyperion strongly recommends that you run a pre-migration process before completing an actual migration. During a pre-migration test. Discard Changes (restore original values)—Retrieves the group names from each system.) 5 Return to the wizard and select the next object to migrate. discards any changes made to the mapping or properties. 2 Select Perform Migration as the Run Mode and click Start. and restores mapping and property information to the original values. For example. (The Migration Utility updates both the target database and the OpenLDAP database. Unless addressed.

errors may cause the actual migration to stop or remain incomplete. warnings. Unless addressed. the number of objects remaining to be migrated. Displays information messages about the migration. Progress Displays information about the progress of the migration such as successes. and the number of objects migrated. Perform Migration—Runs the actual migration. Status Messages Running the OnDemand Server Migration 85 . The objects that are enabled are the objects selected on the Select Objects to Migrate screen earlier in the wizard (see “Selecting the Objects to Migrate” on page 60). Note: Oracle recommends that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object.Figure 34 Run Migration Table 35 Run Migration Options Description Review the objects selected to migrate. Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. errors. Field Select the Objects to Migrate Run Mode Select one of the following options: ● ● Test Only—Runs a pre-migration process to help identify any migration issues.

86 Migrating from BrioONE .

. To run the OnDemand Server wizard steps separately. select the OnDemand Server option under Brio Intelligence Server. After you have selected a migration path and entered logging details...... groups.........6............................ you can run the OnDemand Server and Broadcast Server wizard steps separately... however.............. Before performing the migration... you can migrate both OnDemand Server information and Broadcast Server information........... roles........ If desired..... select Brio Intelligence Server on the Welcome screen (this checks both the OnDemand Server and the Broadcast Server options)........................................4 or later Broadcast Server 6.........................” Running the OnDemand Server Migration To run OnDemand Server information following directly by Broadcast Server information..... running the OnDemand Server migration involves: ● Defining the Database Used by the OnDemand Server Repository About Migrating from the Brio Intelligence Server 87 ........4 or later When you run a Brio Intelligence Server migration...87 Running the OnDemand Server Migration ....................... and repository content from a Brio Intelligence Server installation toShared Services and the Reporting and Analysis Repository............................4 In This Chapter Migrating from the Brio Intelligence Server About Migrating from the Brio Intelligence Server ........6... “Overview and Prerequisites........... The Intelligence Server consists of the following components: ● ● OnDemand Server 6...........87 Running the Broadcast Server Migration.... Checking both options directs the Migration Utility to run the OnDemand Server steps in the wizard followed directly by the Broadcast Server steps in the wizard........ review the information in Chapter 1.... you must run the OnDemand Server wizard steps before you run the Broadcast Server wizard steps....88 About Migrating from the Brio Intelligence Server Use the Brio Intelligence Server option in the Migration Utility Wizard to migrate users...

Running the Broadcast Server Migration Before you migrate Broadcast Server information.● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Defining the Location of the OnDemand Server Repository Database Defining the Location of the OnDemand Server Installation Files Selecting the Objects to Migrate Defining Target Row Level Security Repository Database Information Defining the Location of the Target Row Level Security Repository Database Defining the Hyperion Shared Services Registry Type Defining Hyperion Registry Database Information Defining the Location of the Hyperion Registry Database Defining Reporting and Analysis Repository Database Information Defining the Location of the Reporting and Analysis Repository Database Defining the Location of the Reporting and Analysis Repository Server Defining the Location of the Shared Services Server Defining User/Group Names. ● If you already ran the OnDemand Server migration and exited from the wizard. and Passwords Reviewing User Names Reviewing Group Names Running the Migration See “Running the OnDemand Server Migration” on page 54 for detailed information on migrating information from the OnDemand Server. you can start the Broadcast Server migration by checking the Broadcast Server option under Brio Intelligence Server. ● After you have selected a migration path and entered logging details. the Broadcast Server wizard screens automatically appear after the OnDemand Server wizard screens. running the Broadcast Server migration involves: ● ● ● “Defining the Database Used by the Broadcast Server Repository” on page 89 “Defining the Location of the Broadcast Server Repository Database” on page 90 “Defining the Broadcast Server Name and the Location of the Broadcast Server Initialization File” on page 93 “Selecting the Objects to Migrate” on page 94 “Defining the Hyperion Shared Services Registry Type” on page 66 ● ● 88 Migrating from the Brio Intelligence Server . If you selected both OnDemand Server and Broadcast Server under Brio Intelligence Server on the Welcome screen. Descriptions. make sure that you have already migrated OnDemand Server information.

● ● ● ● ● ● ● ● ● “Defining Hyperion Registry Database Information” on page 67 “Defining the Location of the Hyperion Registry Database” on page 68 “Defining Reporting and Analysis Repository Database Information” on page 100 “Defining the Location of the Reporting and Analysis Repository Database” on page 101 “Defining the Location of the Shared Services Server” on page 105 “Defining User/Group Descriptions and Passwords” on page 108 “Reviewing User Names” on page 109 “Reviewing Group Names” on page 112 “Running the Migration” on page 115 Defining the Database Used by the Broadcast Server Repository Define which database contains the Broadcast Server source repository and select how to specify the database location. Figure 35 Database Used by the Broadcast Server Repository Running the Broadcast Server Migration 89 .

After you enter the requested information. ● ● ● ● ● ● Field Database Type SQL Server Oracle DB2 Informix Sybase Redbrick Note: If your source system is installed on DB2 version 7.Table 36 Database Type Information Description Select one of the following databases. the wizard prompts you to provide full driver information. The fields that appear on the next screen in the wizard depend on the option selected here.x. Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). If your source system is installed on DB2 version 8. 90 Migrating from the Brio Intelligence Server . JDBC Driver and URL—When you select this option. enter the information discussed in Table 37. you can use data direct drivers. you use data direct drivers. Defining the Location of the Broadcast Server Repository Database Define the connection to the Broadcast Server repository database on your existing system. click Test Connection to test the connection to the database. use IBM native drivers to connect. Location of Broadcast Server Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Broadcast Server Repository” on page 89).x.

Enter the password for the database. Field Host Port Database Name User ID Password Owner Location of Broadcast Server Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Broadcast Server Repository” on page 89). Optional: Enter the table owner/schema name. Running the Broadcast Server Migration 91 . Enter the database username used to set up a database connection. the owner is the same as the database username. In most cases.Figure 36 Location of Broadcast Server Repository Database Defined by Host and Name Table 37 Host and Name Information Description Enter the name of the database host. Enter the name of the database. enter the information discussed in Table 39. Enter the database port number.

db2. Figure 37 Location of Broadcast Server Repository Database Defined by JDBC Driver and URL Table 38 JDBC Driver and URL Information Description Enter the path to the native JDBC driver.jdbc. you must restart the Migration Utility. or click Browse. JDBC URL The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. in the DB2 JDBC URL below. Modify this JDBC URL by personalizing the bracketed information. you cannot click Back and select another driver. Either type in the path. For example. if you selected DB2.jar. For example. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. the migration utility would enter hyperion. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen.jdbc. 92 Migrating from the Brio Intelligence Server .DB2Driver. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server.DB2Driver and click Next to load it. Note: Once you have loaded an external JDBC driver. use sqljdbc. For example. if you enter hyperion. If you wish to load a different external JDBC driver.db2. you cannot load another external JDBC driver with the same name.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection.

User ID Password Owner Enter the database username for a Broadcast Server Repository database connection.DatabaseName=<dbname>. the owner is the same as the database username. In most cases. <dbname>.PackageName=<package> remove <server>.Field Description jdbc:hyperion:db2://<server>: 50000.ini). database. Enter the password for the Broadcast Server Repository database. Optional: Enter the table owner/schema name. and DB2 package. Figure 38 Broadcast Server Configuration Running the Broadcast Server Migration 93 . Defining the Broadcast Server Name and the Location of the Broadcast Server Initialization File Enter the name of the Broadcast Server and the location of the Broadcast Server initialization file (BQServ1. and <package> and replace them with the actual names of your server.

To select an object.Table 39 Broadcast Server Configuration Information Description Enter the path for the location of the BQServ1.ini Field BQServ1.ini BCS Server Name Enter the name of the Broadcast Server. If you select this option. ● Mapped Job Storage Path—Map the job storage directory on the installation machine to the job storage directory on the source system. 94 Migrating from the Brio Intelligence Server . Select this option if you are running the migration utility from a machine other than the source system. Selecting the Objects to Migrate Select the Broadcast Server objects to migrate. or click Browse to search for the file. For example. Note. that you must migrate the objects in the order shown in the wizard. you can find it in the Broadcast Server Administrator utility. map Z:\on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \BCS_Jobs on the source system. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. If you do not know the name. enter the mapped job storage path and enter the following information: ● Migration Utility is Not Running on the Broadcast Server Mapped OCE Path—Map the OCE directory on the installation machine to the OCE directory on the source system. however. The objects selected here determine what Broadcast Server migration screens appear next. click the checkbox next to the object.ini file (the ini file for the Broadcast Server). You can select individual objects to migrate here or on the final Run Migration screen. Either type in the path to the file. For example. map Z:\ on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \Program\Open Catalog Extensions on the source system. This file is usually found under: <drive>:/winnt/BQServ1.

the network address of the database server. and your database user name. OCE files specify the database API (ODBC. The default is /Open Catalog Extensions. database software. a user can specify the OCE file and database password and logon. Events in the Broadcast Server. A named collection of users. etc. user name. When you migrate OCE files. The file extension is .Figure 39 Broadcast Server Objects to Migrate Table 40 Broadcast Server Objects to Migrate Description Account owners identified by a user ID. and sample).).oce. Field Users Groups Calendar Events Printer Paths Paths OCE Files Files that encapsulate and store connection information used to connect Hyperion applications to a database. Calendars used to schedule jobs in the Broadcast Server. Sample. Path definitions in the Broadcast Server. Note: If you have Broadcast Server output directories names (paths) that differ only in case (for example SAMPLE . Once created. An OCE file is required for a Hyperion Intelligence document to use a database. Printer path definitions in the Broadcast Server. you must enter the OCE folder on Target. Running the Broadcast Server Migration 95 . and password. SQL*Net. only the first path is migrated.

You enter the criteria for filtering on the Content Filter screen that appears later on in the wizard.0. jobs are migrated to the root. Note: Select Filter Content to filter BQY job content upon migration.5. Enter the job category on target and click the checkbox to run the job in the background.Field BQY Jobs Description Files created by Hyperion Intelligence and published into the Repository as files or as jobs. If you leave the Job Category on Target field empty. Defining the Hyperion Shared Services Registry Type Define the Shared Services Registry to use by selecting an option: ● Default—The Migration Utility takes the connection from the local registry properties file in hyperion_home\common\config\9. New—Two additional wizard screens are displayed where you can enter data source connection details. ● Once a registry connection is established. 96 Migrating from the Brio Intelligence Server . the Migration Utility takes the required Shared Services and Foundation connection parameters (host names and ports) from the registry.0.

Defining Hyperion Registry Database Information If you selected to define a new Shared Services Registry (see “Defining the Hyperion Shared Services Registry Type” on page 125). The fields that appear on the next screen in the wizard depend on the option selected here. JDBC Driver and URL—When you select this option. you use data direct drivers. the wizard prompts you to provide full driver information. Table 41 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. Running the Broadcast Server Migration 97 . define which database is used by the Hyperion Registry and select how to specify the database location.

Enter the name of the Hyperion Registry database. click Test Connection to test the connection to the database.Defining the Location of the Hyperion Registry Database Define the location of the Hyperion Registry database. Field Host Port Database Name User ID Password 98 Migrating from the Brio Intelligence Server . enter the information in Table 57. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). Enter the Hyperion Registry database port number. Enter the database username used to set up a Hyperion Registry database connection. After you enter the requested information. Location of the Hyperion Registry Database by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion Registry Database Information” on page 126). Table 42 Hyperion Registry Database Host and Name Information Description Enter the name of the Hyperion Registry database host. Enter the password for the Hyperion Registry database.

if you selected DB2. enter the information in Table 58. Note: Once you have loaded an external JDBC driver.PackageName=<package> Running the Broadcast Server Migration 99 .Location of the Hyperion Registry Database by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard. jdbc:hyperion:db2://<server>: 50000.db2. you cannot load another external JDBC driver with the same name. If you wish to load a different external JDBC driver.db2.DB2Driver.jdbc. if you enter hyperion. For example. in the DB2 JDBC URL below. Modify this JDBC URL by personalizing the bracketed information. you cannot click Back and select another driver. For example. Either type in the path. For example.jdbc. (see “Defining Hyperion Registry Database Information” on page 126). Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen.DatabaseName=<dbname>. the Migration Utility would enter hyperion. JDBC URL The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Table 43 Hyperion Registry Database JDBC Driver and URL Information Description Enter the path to the native JDBC driver. you must restart the Migration Utility.DB2Driver and click Next to load it. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. or click Browse to define the path.

and <package> and replace them with the actual names of your server.Field Description remove <server>. and DB2 package. Enter the password for the Hyperion Registry database. database. <dbname>. Figure 40 Database Used by the Reporting and Analysis Repository Table 44 Database Type Information Description Select one of the following databases: ● Field Database Type SQL Server 100 Migrating from the Brio Intelligence Server . User ID Password Enter the database username used to set up a Hyperion Registry database connection. Defining Reporting and Analysis Repository Database Information Define which database contains the target Reporting and Analysis Repository and select how to specify the database location.

Location of Reporting and Analysis Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 100). you use data direct drivers. enter the information discussed in Table 45. Running the Broadcast Server Migration 101 . JDBC Driver and URL—When you select this option. click Test Connection to test the connection to the database. After you enter the requested information.Field Description ● ● Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). The fields that appear on the next screen in the wizard depend on the option selected here. the wizard prompts you to provide full driver information. Defining the Location of the Reporting and Analysis Repository Database Define the location of the Reporting and Analysis Repository database on the target system.

Figure 41 Location of Reporting and Analysis Repository Database Defined by Host and Name Table 45 Host and Name Information Description Enter the name of the Reporting and Analysis Repository database host. Enter the password for the Reporting and Analysis Repository database. Field Host Port Database Name User ID Password Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 100). 102 Migrating from the Brio Intelligence Server . Enter the Reporting and Analysis Repository database port number. enter the information discussed in Table 46. Enter the database username used to set up a Reporting and Analysis Repository database connection. Enter the name of the Reporting and Analysis Repository database.

Note: Once you have loaded an external JDBC driver. For example.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection.jar. Figure 42 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL Table 46 JDBC Driver and URL Information Description Enter the path to the native JDBC driver. For example.db2. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server.db2.DB2Driver. you cannot load another external JDBC driver with the same name. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen.DB2Driver and click Next to load it.jdbc.jdbc. you must restart the Migration Utility. you cannot click Back and select another driver. if you selected DB2. if you enter hyperion. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. use sqljdbc. the migration utility would enter hyperion. Either type in the path. If you wish to load a different external JDBC driver. Running the Broadcast Server Migration 103 . or click Browse to define the path.

database. Modify this JDBC URL by personalizing the bracketed information. For example. Password Defining the Location of the Reporting and Analysis Repository Server Define the connection to the Reporting and Analysis Repository Server on the target system. User ID Enter the database username used to set up a Reporting and Analysis Repository database connection. and <package> and replace them with the actual names of your server. and DB2 package. click Test Connection to test the connection to the server. Figure 43 Location of Target Reporting and Analysis Repository Server 104 Migrating from the Brio Intelligence Server . Enter the password for the Reporting and Analysis Repository database.PackageName=<package> remove <server>. <dbname>. jdbc:hyperion:db2://<server>: 50000.DatabaseName=<dbname>. After you enter the requested information.Field JDBC URL Description The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. in the DB2 JDBC URL below.

Enter the username of a user with Global Administrator. click Test Connection to test the connection to the server. Field Host Running the Broadcast Server Migration 105 . Enter the password for the User ID. and Provisioning Manager roles. Enter the Reporting and Analysis Repository Server port number.Table 47 Reporting and Analysis Repository Server Information Description Enter the name of the Reporting and Analysis Repository Server host. After you enter the requested information. Figure 44 Location of Target Shared Services Server Table 48 Shared Services Server Information Description Enter the name of the Shared Services Server host. Directory Manager. Field Host Port User ID Password Defining the Location of the Shared Services Server Define the location of the Shared Services Server on the target system.

When you map jobs to folders that do not currently exist in the target system. When you use content filtering. the folders are created during migration. Defining Content Filtering for Broadcast Server Jobs Content filtering involves selectively moving content to different folders in the Reporting and Analysis target system. type. Enter the login ID for the user in Shared Services. Figure 45 Content Filtering 106 Migrating from the Brio Intelligence Server . Use this screen to verify the location of content items.Field Port User ID Password Description Enter the Shared Services Server port number. The Content Filtering screen displays each content item with its location. Enter the password for the User ID. You can map Broadcast Server jobs to existing or non-existing folders. you can map Broadcast Server jobs to multiple folders in the target system during a single migration run. view or change the mapping. owner. and migration action. and set the migration action for each item.

Searching for Content Items ➤ To search for a content item: 1 Click Search. ➤ To set the migration action for more than one content item. Running the Broadcast Server Migration 107 . click Save. select the content item and select or clear the checkbox next to Do not migrate. Clicking Save is optional. Setting the Migration Action By default. You can also make changes in the external file and load it into the Migration Utility. You can successfully run a migration without saving content filtering settings to an external file. 2 Define how to conduct the search in the Search dialog box and click Search again. Mapping Content Items ➤ To change mapping information: 1 Select the desired BCS jobs(s). ➤ To change the migration action. Saving Content Filtering Changes to an External File ➤ To save content filtering changes to an external file. you can load the file if you close and then re-open the Migration Utility. After you search for a content item. however. If you do decide to save settings to an external file. press [Shift] and select the desired content items. or click Select All to select all the content items. 2 Click Map to and select a folder in the Browse Target File System dialog box. you can display all the content items again by clicking Show All. The content items that meet the search criteria display. the migration action for each content item is set to Migrate.

Loading Content Filtering Changes from an External File
➤ To load content filtering changes from an external file and display them on the Content Filtering
screen, click Load.

Defining User/Group Descriptions and Passwords
Define how to treat group names and passwords when creating new users in the Shared Services Server.

Figure 46

User/Group Descriptions and Passwords

Table 49

Information on User/Group Descriptions and Passwords Description Define how to treat group names when migrating native groups by selecting one of the following options:

Field Group Names

Same Group Name—Migrates the native Intelligence group name to a native Shared Services group name and keeps the group names the same. Alternate Group Name—Migrates the native Intelligence group name to a native Shared Services group name with a prefix or suffix added to the name. Enter the desired prefix or suffix in the Prefix or Suffix field.

108 Migrating from the Brio Intelligence Server

Field Passwords

Description Define how to handle passwords when creating new Shared Services users by selecting one of the following options:
● ● ●

Auto-generated Same as user ID Other

Note: If the password is auto-generated, the migration utility creates a file that lists the new native users along with their login ID, autogenerated password, and email address. The administrator can use this information to email users their new passwords.

Reviewing User Names
Review the user mappings and properties and set the migration action for each user. Most of the properties for each user name display next to the user name. For a complete list of user name properties, click Properties (see “Editing User Name Properties” on page 110).

Figure 47

User Names

Running the Broadcast Server Migration 109

Searching for User Names
➤ To search for a user name:
1 Click Search. 2 Define how to conduct the search in the Search dialog box and click Search again.
The user names that meet the search criteria display. After you search for a user name, you can display all the user names again by clicking Show All.

Editing User Name Properties
➤ To edit user name properties:
1 Select the desired user name and click Properties or double-click the user name.
The Properties dialog box displays.

The user name properties from both systems (source and target) are displayed. Some properties are read-only and some can be edited.

2 Edit the desired properties and click OK.
Note:

For existing users, you cannot edit any of the Shared Services User properties; however, you can change the user name. If you change the user name, then during migration, the user is mapped to another Shared Services user or a new user is created with the new name.

Verifying User Name Mapping
When you run the migration utility, it queries the source system for users and attempts to automatically map them to existing Shared Services users based on the following criteria:

login ID

110 Migrating from the Brio Intelligence Server

● ●

email address first name/last name

If a mapping cannot be made, then during migration, the migration utility creates a new native user. You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. For example, to map an Intelligence user name to a different Shared Services user name, you would select the user name, click Properties, and change the Shared Services user name in the Properties dialog box.

Setting the Migration Action
For each user, you can set the migration action property to Migrate or Do Not Migrate. To do this, use one of the following options:
● ●

Select the user, click Properties, and select the desired option in the Action field. Select the user and click the checkbox next to Migrate User Name from Intelligence to Shared Services. To set the action for more than one user, press [Shift] and select the desired user names, or click Select All to select all the user names.

When specifying whether to migrate users from Intelligence to Shared Services , keep in mind the following:

When you perform a migration, all new native users whose action is set to Migrate are migrated to the target Shared Services. If you later change a user’s action to Do Not Migrate and perform another migration, the migration utility does not remove the previously-migrated user from target Shared Services system; instead, you must delete the user directly from the target Shared Services. The default setting for inactive users is Do Not Migrate. This setting cannot be changed. To migrate a deactivated user, you must manually activate the user in the source system before performing the migration. Users who are not migrated lose all access control information associated with them as well as any assigned user properties.

Updating User Name Information
If you wish to refresh the automatic mapping on the User Names screen, click Update Names and select one of the following options:

Keep Changes (use new values)—Validates the user names from each system and keeps any changes made to the mapping and property information. Discard Changes (restore original values)—Retrieves the user names from each system, discards any changes made to the mapping or properties, and restores mapping and property information to the original values.

Running the Broadcast Server Migration 111

The group names that meet the search criteria display. you can display all the group names again by clicking Show All. select a group name and click Properties (see “Editing Group Name Properties” on page 113).Reviewing Group Names Review the group mappings and properties and set the migration action for each group. For a complete list properties for a group. Most of the properties for each group name display next to the group name. 2 Define how to conduct the search in the Search dialog box and click Search again. After you search for a group name. 112 Migrating from the Brio Intelligence Server . Figure 48 Group Names Searching for Group Names ➤ To search for a group name: 1 Click Search.

Editing Group Name Properties ➤ To edit group name properties: 1 Select the desired group name and click Properties. Running the Broadcast Server Migration 113 . and change the Shared Services group name in the Properties dialog box. click Properties. If the group is set to Do Not Migrate. The Properties dialog box displays. If a mapping cannot be made. To do this. you would select the group name. then during migration. and select the desired option in the Action field. you can set the Action property to Migrate or Do Not Migrate. Verifying Group Name Mapping When you run the migration utility. you cannot edit any of the properties in the User Management Group section of the dialog box. Select the group and click the checkbox next to Migrate Group Name from Intelligence to Shared Services. the migration utility creates a new native group. You can view these mappings on the Group Names screen and manually adjust or change the mappings as necessary. For example. Setting the Migration Action For each group. to map an Intelligence group name to a different Shared Services group name. Some properties are read-only and some can be edited. it queries the source system for groups and attempts to automatically map them to existing Shared Services groups based on the group name. The group name properties from both systems (source and target) are displayed. use one of the following options: ● ● Select the group. 2 Edit the desired properties and click OK. click Properties.

keep in mind the following: ● The default setting for inactive groups is Do Not Migrate. ● 114 Migrating from the Brio Intelligence Server . discards any changes made to the mapping or properties. When specifying whether to migrate groups from Intelligence to Shared Services. or click Select All to select all the group names. and restores mapping and property information to the original values. set the Action property of the native parent group to Migrate. or click Select All to select all the group names.To set the action for more than one group. Discard Changes (restore original values)—Retrieves the group names from each system. ● ● ● Adding Users/Groups Assigned in Intelligence to the Native Shared Services Group ➤ To add users and groups assigned in Intelligence to the native Shared Services group: 1 Press [Shift] and select the desired group names. then upon migration. If you migrate a group that is a member of a native parent group (that is going to be migrated or was already migrated). Updating Group Name Information If you wish to refresh the automatic mapping on the Group Names screen. if a group in Intelligence is going to be mapped to a new native group in Shared Services. this new native group is created and any users and groups assigned to the group in the source system are assigned to the group in the target system. 2 Click the checkbox next to Add Users/Groups Assigned in Intelligence to the Native Shared Services Group. This setting cannot be changed. To migrate a deactivated group. Note: When you select this option. When you migrate groups. set the Action property to Migrate for all users and groups that have already been migrated. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the group names from each system and keeps any changes made to the mapping and property information. set the Action property to Migrate for the all users belonging to the group that have already been migrated. press [Shift] and select the desired group names. you must manually activate the group in the source system before performing the migration. This ensures that group-to-group associations migrate correctly. This ensures that user/group relationships migrate correctly. This ensures that user properties and access control information referring to the users and groups migrates correctly. When you migrate content.

Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object.) This step is optional. errors may cause the actual migration to stop or remain incomplete. After all the users migrated successfully. the migration utility goes through the migration process without actually moving objects from the source system to the target system. it reports them in the log files.) 5 Return to the wizard and select the next object to migrate. Unless addressed. 3 Check to make sure the object migrated correctly and fix any errors. After you complete the pre-migration test and fix all the outstanding errors. 4 Backup your target database (and your OpenLDAP database if you are migrating users and groups. If the migration utility finds any problems. you may want to backup the target database after you successfully migrate each object type. however. When you migrate users and groups.Running the Migration The final screen of the Migration Utility wizard allows you to review the objects selected to migrate. you would select Groups. 2 Select Perform Migration as the Run Mode and click Start. select Test Only as the Run Mode. that you must migrate the objects in the order shown in the wizard. As an extra precaution. Note. you should also backup the OpenLDAP database. Hyperion strongly recommends that you run a pre-migration process before completing an actual migration. you could begin by selecting Users. ➤ To run a pre-migration process. and to run the actual migration. ➤ To migrate each object type separately: 1 Select the desired object type. (The Migration Utility updates both the target database and the OpenLDAP database. During a pre-migration test. to run a test migration that will help determine any migration issues. You should fix any potential errors encountered in the pre-migration process before performing an actual migration. For example. Running the Broadcast Server Migration 115 .

Progress Displays information about the progress of the migration such as successes. Field Select the Objects to Migrate Run Mode Select one of the following options: ● ● Test Only—Runs a pre-migration process to help identify any migration issues. Note: Oracle recommends that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object. Displays information messages about the migration. Unless addressed. the number of objects remaining to be migrated. and the number of objects migrated. The objects that are enabled are the objects selected on the Select Objects to Migrate screen earlier in the wizard (see “Selecting the Objects to Migrate” on page 94). Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. errors may cause the actual migration to stop or remain incomplete.Figure 49 Run Migration Table 50 Run Migration Options Description Review the objects selected to migrate. Perform Migration—Runs the actual migration. warnings. errors. Status Messages 116 Migrating from the Brio Intelligence Server .

............................ Descriptions and Passwords................................................. 121 Selecting the Objects to Migrate .............. 134 Reviewing User Names ...............................sh (UNIX) in the bin folder where you installed the migration utility......................................... 130 Defining the Location of the Shared Services Server .................... groups.... 118 Entering Logging Details.............. 126 Defining the Location of the Hyperion Registry Database.................................................. click migrator......................... 120 Defining the Location of the Analyzer Repository Database ........................................ 7................................................................................ 117 Starting the Migration Utility Wizard.........1................................................................... 135 Reviewing Group Names ............................................................................. Before performing the migration................................................................bat file is located in: C:\Hyperion\products\Foundation\workspace\MigrationUtility\bin About Migrating from Hyperion Analyzer 117 .......... review the information in Chapter 1..................................................................................... roles..2............................................” Starting the Migration Utility Wizard ➤ To start the Migration Utility Wizard................................................................................ 7................................................................................................... and repository content from a Hyperion Analyzer 6.. 124 Defining the Hyperion Shared Services Registry Type ...........................5........................ 117 Selecting a Migration Path .................................0... 127 Defining Reporting and AnalysisDatabase Information. If you installed to the default location...... 129 Defining the Location of the Reporting and Analysis Repository Database .... 133 Defining User/Group Names.................. 125 Defining Hyperion Registry Database Information ................................................... 118 Defining the Database Used by the Analyzer Repository...... 138 Running the Migration ....... “Overview and Prerequisites..........................1 installation to Shared Services and the Reporting and Analysis Repository................bat (Windows) or migrator......... 141 About Migrating from Hyperion Analyzer Use the Hyperion Analyzer option in the Migration Utility Wizard to migrate users.....................................................................5 In This Chapter Migrating from Hyperion Analyzer About Migrating from Hyperion Analyzer ............................................................................................................................................. the migrator....2.............. or 7....................................

then Oracle EPM System.If you are using Windows. and then Run Migration Utility. Logging information is important since this is the only place where you can see errors relating to the migration. 118 Migrating from Hyperion Analyzer . then Workspace. Selecting a Migration Path Select Hyperion Analyzer on the Welcome screen and click Next. you can also start the Migration Utility Wizard by choosing Start. Figure 50 Welcome Screen Entering Logging Details Select the log level for messages and specify the directory in which to write the log files. then Programs.

which may or may not be important for your particular migration scenario. Warn—Warning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. Entering Logging Details 119 .Figure 51 Logging Details Table 51 Logging Details Description Specify the log level by selecting one of the following options: ● ● Field Log Level Fatal—Fatal messages cause the migration process to stop. To search for a specific directory. Debug—Debug level messages include all types of messages and produces a very large log file. and potential problems. an error message may tell you that a particular user does not exist in the source system. you can ignore this message if deleting that user is part of your migration plan. Oracle recommends this level for testing. For example. Debug level messages are numerous because they give a row-by-row account of all migration steps. ● ● ● Log Directory Specify the directory where you want to write the log file. Error—Error messages notify you of potential problems. Info—Informational messages notify you of structural changes made between the old and new systems. click Browse. differences encountered between the old and new systems. Oracle recommends this level for most migrations.

use IBM native drivers to connect. Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. JDBC Driver and URL—When you select this option.x.x. the wizard prompts you to provide full driver information.Defining the Database Used by the Analyzer Repository Define which database contains the Analyzer source repository and select how to specify the database location. you can use data direct drivers. ● ● ● ● Field Database Type SQL Server Oracle DB2 MySQL Note: If your source system is installed on DB2 version 7. Figure 52 Database Used by the Analyzer Repository Table 52 Database Type Information Description Select one of the following databases. 120 Migrating from Hyperion Analyzer . If your source system is installed on DB2 version 8. you use data direct drivers.

Figure 53 Location of Analyzer Repository Database Defined by Host and Name Defining the Location of the Analyzer Repository Database 121 . Location of Analyzer Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Analyzer Repository” on page 120). click Test Connection to test the connection to the database. Defining the Location of the Analyzer Repository Database Define the connection to the Analyzer repository database on your existing system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). enter the information discussed in Table 53. After you enter the requested information.Field Description The fields that appear on the next screen in the wizard depend on the option selected here.

122 Migrating from Hyperion Analyzer . enter the information discussed in Table 54. Field Host Port Database Name User ID Password Location of Analyzer Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Analyzer Repository” on page 120). use sqljdbc. Enter the database username used to set up a database connection.jar. Enter the database port number.Table 53 Host and Name Information Description Enter the name of the database host. Enter the name of the database. Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server. Enter the password for the database.

you cannot load another external JDBC driver with the same name. jdbc:hyperion:SQLSERVER://<host>: 1433.Figure 54 Location of Analyzer Repository Database Defined by JDBC Driver and URL Table 54 JDBC Driver and URL Information Description Enter the path to the native JDBC driver.sqlserver. Defining the Location of the Analyzer Repository Database 123 . the migration utility would enter hyperion.jdbc. If you wish to load a different external JDBC driver. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen. in the SQL Server JDBC URL below. you cannot click Back and select another driver. For example. JDBC URL The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen.DatabaseName=<dbname>.DB2Driver and click Next to load it. you must restart the Migration Utility. For example.SQLServerDriver. or click Browse to define the path.db2. User ID Enter the database username used to set up a database connection. if you enter hyperion.jdbc. if you selected SQL Server. Modify this JDBC URL by personalizing the bracketed information. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. Note: Once you have loaded an external JDBC driver.SelectMethod=cursor remove <host> and <dbname> and replace them with the actual name of your host and database. Either type in the path. For example.

Note.Field Password Description Enter the password for the database. To select an object. that you must migrate the objects in the order shown in the wizard. Selecting the Objects to Migrate Select the Analyzer objects to migrate. however. Groups—Named collections of users. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. Figure 55 Hyperion Analyzer Objects to Migrate Table 55 Hyperion Analyzer Objects to Migrate Description Users—Account owners identified by a user ID and user name. The objects selected here determine what Analyzer migration screens appear next. You can select individual objects to migrate here or on the final Run Migration screen. Field Users and Groups 124 Migrating from Hyperion Analyzer . click the checkbox next to the object.

5. URLs. which consists of files in the native file system and metadata for each object in a database in a Relational Database Management System (RDBMS). ● Once a registry connection is established. Note: If a folder in the repository contains more than 80 to 90 items. add -DPerformance. Defining the Hyperion Shared Services Registry Type Define the Shared Services Registry to use by selecting an option: ● Default—The Migration Utility takes the connection from the local registry properties file in hyperion_home\common\config\9. To make the folder accessible. New—Two additional wizard screens are displayed where you can enter data source connection details.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices. Repository content is the largest object to migrate. jobs.bat script and restart Common Services. namely: folders. the Migration Utility takes the required Shared Services and Foundation connection parameters (host names and ports) from the registry. and shortcuts. the folder is inaccessible in Shared Services and the Reporting and Analysis Repository.Field Repository Content Description The content of the system. The content resides in the repository. Defining the Hyperion Shared Services Registry Type 125 .0. and their metadata (properties). files.0.

126 Migrating from Hyperion Analyzer . The fields that appear on the next screen in the wizard depend on the option selected here.Defining Hyperion Registry Database Information If you selected to define a new Shared Services Registry (see “Defining the Hyperion Shared Services Registry Type” on page 125). JDBC Driver and URL—When you select this option. Table 56 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. the wizard prompts you to provide full driver information. you use data direct drivers. define which database is used by the Hyperion Registry and select how to specify the database location.

The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). Location of the Hyperion Registry Database by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion Registry Database Information” on page 126). Enter the password for the Hyperion Registry database. Table 57 Hyperion Registry Database Host and Name Information Description Enter the name of the Hyperion Registry database host. Enter the Hyperion Registry database port number. Enter the name of the Hyperion Registry database. Field Host Port Database Name User ID Password Defining the Location of the Hyperion Registry Database 127 . click Test Connection to test the connection to the database. enter the information in Table 57.Defining the Location of the Hyperion Registry Database Define the location of the Hyperion Registry database. Enter the database username used to set up a Hyperion Registry database connection. After you enter the requested information.

you cannot load another external JDBC driver with the same name. Note: Once you have loaded an external JDBC driver. For example. For example. If you wish to load a different external JDBC driver.jdbc. if you selected DB2.Location of the Hyperion Registry Database by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard. Either type in the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. if you enter hyperion. For example. Modify this JDBC URL by personalizing the bracketed information. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen.db2. JDBC URL The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. in the DB2 JDBC URL below.DB2Driver and click Next to load it. 128 Migrating from Hyperion Analyzer . enter the information in Table 58. Table 58 Hyperion Registry Database JDBC Driver and URL Information Description Enter the path to the native JDBC driver. (see “Defining Hyperion Registry Database Information” on page 126).jdbc. you cannot click Back and select another driver. you must restart the Migration Utility. or click Browse to define the path. the Migration Utility would enter hyperion.db2.DB2Driver.

Enter the password for the Hyperion Registry database. Figure 56 Database Used by the Reporting and Analysis Repository Table 59 Database Type Information Description Select one of the following database drivers: ● Field Database Type SQL Server Defining Reporting and AnalysisDatabase Information 129 .PackageName=<package> remove <server>.DatabaseName=<dbname>. and <package> and replace them with the actual names of your server. Defining Reporting and AnalysisDatabase Information Define which database contains the target Reporting and Analysis Repository and select how to specify the database location. <dbname>. User ID Password Enter the database username used to set up a Hyperion Registry database connection.Field Description jdbc:hyperion:db2://<server>: 50000. database. and DB2 package.

The fields that appear on the next screen in the wizard depend on the option selected here. After you enter the requested information. JDBC Driver and URL—When you select this option. Defining the Location of the Reporting and Analysis Repository Database Define the location of the Reporting and Analysis Repository database on the target system. enter the information discussed in Table 60. 130 Migrating from Hyperion Analyzer .Field Description ● ● Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. click Test Connection to test the connection to the database. the wizard prompts you to provide full driver information. you use data direct drivers. Location of Reporting and Analysis Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Reporting and AnalysisDatabase Information” on page 129). The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL).

Enter the Reporting and Analysis Repository database port number. Defining the Location of the Reporting and Analysis Repository Database 131 . Enter the password for the Reporting and Analysis Repository database. Enter the name of the Reporting and Analysis Repository database. Enter the database username used to set up a Reporting and Analysis Repository database connection. enter the information discussed in Table 61. Field Host Port Database Name User ID Password Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Reporting and AnalysisDatabase Information” on page 129).Figure 57 Location of Reporting and Analysis Repository Database Defined by Host and Name Table 60 Host and Name Information Description Enter the name of the Reporting and Analysis Repository database host.

if you selected SQL Server.jar.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection.DB2Driver and click Next to load it. Figure 58 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL Table 61 JDBC Driver and URL Information Description Enter the path to the native JDBC driver.db2. you must restart the Migration Utility. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.SQLServerDriver.sqlserver. if you enter hyperion. Note: Once you have loaded an external JDBC driver. 132 Migrating from Hyperion Analyzer . For example. the migration utility would enter hyperion. If you wish to load a different external JDBC driver. For example. you cannot click Back and select another driver. Either type in the path.jdbc. or click Browse to define the path. you cannot load another external JDBC driver with the same name. use sqljdbc.jdbc. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen.

Figure 59 Location of Shared Services Server Defining the Location of the Shared Services Server 133 . jdbc:hyperion:SQLSERVER://<host>: 1433. Modify this JDBC URL by personalizing the bracketed information. Password Defining the Location of the Shared Services Server Define the location of the Shared Services Server on the target system. User ID Enter the database username used to set up a Reporting and Analysis Repository database connection.SelectMethod=cursor remove <host> and <dbname> and replace them with the actual name of your host and database.Field JDBC URL Description The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. in the SQL Server JDBC URL below.DatabaseName=<dbname>. Enter the password for the Reporting and Analysis Repository database. For example. After you enter the requested information. click Test Connection to test the connection to the server.

group names. Figure 60 User/Group Descriptions and Passwords 134 Migrating from Hyperion Analyzer . Field Host Port User ID Password Defining User/Group Names. Enter the password for the User ID. group descriptions.Table 62 Shared Services Server Information Description Enter the name of the Shared Services Server host. Descriptions and Passwords Define how to treat user descriptions. The user must have an administrative role in Shared Services. Enter the login ID for the user in Shared Services. and passwords when creating new users in Shared Services. Enter the Shared Services Server port number.

if a user name consists of more than two names. If you select this option: ❍ ● Specify how the names in the source description fields are separated by clicking the checkbox next to Space. Semi-colon. ● Passwords Define how to handle passwords when creating new native Shared Services users by selecting one of the following options: ● ● ● Auto-generated Same as user name Other Note: If the password is auto-generated. autogenerated password. For example. Specify how to add middle names in Shared Services by selecting an option for Add Middle Name to. or Comma. if the name appears starting with the last name. and email address. Alternate Group Name—Migrates the native Analyzer group name to a native Shared Services group name with a prefix or suffix added to the name.Table 63 Information on User/Group Descriptions and Passwords Description Define how to copy the User Descriptions from Analyzer when creating new native Shared Services users. The default is to copy the Analyzer Group Description to the Shared Services Group Description. Note that you can select more than one option. Select one of the following options: ● Field User Descriptions Shared Services User Description—Copies the Analyzer User Description fields to the Shared Services User Description fields. User/Group Descriptions Define where to copy the Analyzer group descriptions when creating new native Shared Services groups. If the names in the source description fields have a different delimiter. Reviewing User Names 135 . you can specify whether to add the middle name as part of the first name or as part of the last name. Specify how the user names appear in Analyzer by selecting an option for Name Starts With. For example. the migration utility creates a file that lists the new native users along with their login ID. click the checkbox next to Other and specify the delimiter. you would click the checkbox next to Last Name. Enter the desired prefix or suffix in the Prefix or Suffix field. The administrator can use this information to email users their new passwords. ❍ ❍ Group Names Define how to treat group names when migrating native groups by selecting one of the following options: ● Same Group Name—Migrates the native Analyzer group name to a native Shared Services name and keeps the group name the same. Shared Services User First and Last Name Fields—Copies the Analyzer User First and Last Name fields to the Shared Services User First and Last Name fields. Reviewing User Names Review the user mappings and properties and set the migration action for each user.

2 Define how to conduct the search in the Search dialog box and click Search again. Editing User Name Properties ➤ To edit user name properties: 1 Select the desired user name and click Properties or double-click the user name. you can display all the user names again by clicking Show All. For a complete list of properties for a user. After you search for a user name. Figure 61 User Names Searching for User Names ➤ To search for a user name: 1 Click Search. The user names that meet the search criteria display. select a user name and click Properties (see “Editing User Name Properties” on page 136). 136 Migrating from Hyperion Analyzer .Most of the properties for each user name display next to the user name.

the migration utility creates a new native user. You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. you can change the user name. Some properties are read-only and some can be edited. you can set the migration action property to Migrate or Do Not Migrate. For example.The Properties dialog box displays. The user name properties from both systems (source and target) are displayed. you cannot edit any of the Shared Services User properties. however. use one of the following options: Reviewing User Names 137 . 2 Edit the desired properties and click OK. the user is mapped to another Shared Services user or a new user is created with the new name. you would select the user name. it queries the source system for users and attempts to automatically map them to existing Shared Services users based on the following criteria: ● ● ● login ID email address first name/last name If a mapping cannot be made. Note: For existing users. and change the Shared Services user name in the Properties dialog box. then during migration. Verifying User Name Mapping When you run the migration utility. Setting the Migration Action For each user. If you change the user name. to map an Analyzer user name to a different Shared Services user name. To do this. click Properties. then during migration.

● ●

Select the user, click Properties, and select the desired option in the Action field. Select the user and click the checkbox next to Migrate User Name from Analyzer to Shared Services. To set the action for more than one user, press [Shift] and select the desired user names, or click Select All to select all the user names.

When specifying whether to migrate users from Analyzer to Shared Services, keep in mind the following:

When you perform a migration, all new native users whose action is set to Migrate are migrated to the target Shared Services. If you later change a user’s action to Do Not Migrate and perform another migration, the migration utility does not remove the previously-migrated user from target Shared Services system; instead, you must delete the user directly from the target Shared Services. Users who are not migrated lose all access control information associated with them as well as any assigned user properties.

Updating User Name Information
If you wish to refresh the automatic mapping on the User Names screen, click Update Names and select one of the following options:

Keep Changes (use new values)—Validates the user names from each system and keeps any changes made to the mapping and property information. Discard Changes (restore original values)—Retrieves the user names from each system, discards any changes made to the mapping or properties, and restores mapping and property information to the original values.

Reviewing Group Names
Review the group mappings and properties and set the migration action for each group. Most of the properties for each group name display next to the group name. For a complete list of properties for a group, select a group name and click Properties (see “Editing Group Name Properties” on page 139).

138 Migrating from Hyperion Analyzer

Figure 62

Group Names

Searching for Group Names
➤ To search for a group name:
1 Click Search. 2 Define how to conduct the search in the Search dialog box and click Search again.
The group names that meet the search criteria display. After you search for a group name, you can display all the group names again by clicking Show All.

Editing Group Name Properties
➤ To edit group name properties:
1 Select the desired group name and click Properties.
The Properties dialog box displays.

Reviewing Group Names 139

The group name properties from both systems (source and target) are displayed. Some properties are read-only and some can be edited.

2 Edit the desired properties and click OK.
If the group is set to Do Not Migrate, you cannot edit any of the properties in the User Management Group section of the dialog box.

Verifying Group Name Mapping
When you run the migration utility, it queries the source system for groups and attempts to automatically map them to existing Shared Services groups based on the group name. If a mapping cannot be made, then during migration, the migration utility creates a new native group. You can view these mappings on the Group Names screen and manually adjust or change the mappings as necessary. For example, to map an Analyzer group name to a different Shared Services group name, you would select the group name, click Properties, and change the Shared Services group name in the Properties dialog box.

Setting the Migration Action
For each group, you can set the Action property to Migrate or Do Not Migrate. To do this, use one of the following options:
● ●

Select the group, click Properties, and select the desired option in the Action field. Select the group and click the checkbox next to Migrate Group Name from Analyzer to Shared Services. To set the action for more than one group, press [Shift] and select the desired group names, or click Select All to select all the group names.

When specifying whether to migrate groups from Analyzer to Shared Services, keep in mind the following:

140 Migrating from Hyperion Analyzer

When you migrate groups, set the Action property to Migrate for the all users belonging to the group that have already been migrated. This ensures that user/group relationships migrate correctly. When you migrate content, set the Action property to Migrate for all users and groups that have already been migrated. This ensures that user properties and access control information referring to the users and groups migrates correctly. If you migrate a group that is a member of a native parent group (that is going to be migrated or was already migrated), set the Action property of the native parent group to Migrate. This ensures that group-to-group associations migrate correctly.

Adding Users/Groups Assigned in Analyzer to the Native Shared Services Group
➤ To add users and groups assigned in Analyzer to the native Shared Services group:
1 Press [Shift] and select the desired group names, or click Select All to select all the group names. 2 Click the checkbox next to Add Users/Groups Assigned in Analyzer to the Native Shared Services
Group.
Note:

When you select this option, if a group in Analyzer is going to be mapped to a new native group in Shared Services; then upon migration, this new native group is created and any users and groups assigned to the group in the source system are assigned to the group in the target system.

Updating Group Name Information
If you wish to refresh the automatic mapping on the Group Names screen, click Update Names and select one of the following options:

Keep Changes (use new values)—Validates the group names from each system and keeps any changes made to the mapping and property information. Discard Changes (restore original values)—Retrieves the group names from each system, discards any changes made to the mapping or properties, and restores mapping and property information to the original values.

Running the Migration
The final screen of the Migration Utility wizard allows you to review the objects selected to migrate and to run the actual migration. Hyperion strongly recommends that you run a pre-migration process before completing an actual migration. During a pre-migration test, the Migration Utility goes through the migration process without actually moving objects from the source system to the target system. If the

Running the Migration 141

Migration Utility finds any problems, it reports them in the log files. You should fix any potential errors encountered in the pre-migration process before performing an actual migration. Unless addressed, errors may cause the actual migration to stop or remain incomplete.
Note:

For Hyperion Analyzer, you can only run a pre-migration test on users and groups. To do this, select Test Only as the Run Mode. Test Only is disabled for repository content. For example: If you select “Users and Groups,” the Test Only option is enabled. If you select both “Users and Groups” and “Repository Content,” the Text Only option is disabled. If you select “Repository Content,” the Text Only option is disabled.

● ●

After you complete the pre-migration test and fix all the outstanding errors, Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. Note, however, that you must migrate the objects in the order shown in the wizard.

➤ To migrate each object type separately:
1 Select the desired object type.
For example, you could begin by selecting Users and Groups. After all the users and groups migrated successfully, you would select Repository Content.

2 Select Perform Migration as the Run Mode and click Start. 3 Check to make sure the object migrated correctly and fix any errors. 4 Backup your target database (and your OpenLDAP database if you are migrating users and groups.)
This step is optional As an extra precaution, you may want to backup the target database after you successfully migrate each object type. When you migrate users and groups, you should also backup the OpenLDAP database. (The Migration Utility updates both the target database and the OpenLDAP database.)

5 Return to the wizard and select the next object to migrate.
Note:

After you migrate repository content, re-start Oracle's Hyperion® Web Analysis in the servlet container.

142 Migrating from Hyperion Analyzer

the number of objects remaining to be migrated. Perform Migration—Runs the actual migration. Displays informational messages about the migration. Field Select the Objects to Migrate Run Mode Select one of the following options: ● ● Test Only—Runs a pre-migration process to help identify any migration issues. Note: After you migrate repository content. warnings. Note: Oracle recommends that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object. Progress Displays information about the progress of the migration such as successes. and the number of objects migrated.Figure 63 Run Migration Table 64 Run Migration Options Description Review the objects selected to migrate. re-start Oracle's Hyperion® Web Analysis in the servlet container. Status Messages Running the Migration 143 . Note: Test Only is only available for User and Groups in Hyperion Analyzer migrations. The objects that are enabled are the objects selected on the Select Objects to Migrate screen earlier in the wizard (see “Selecting the Objects to Migrate” on page 124). errors.

144 Migrating from Hyperion Analyzer .

...... 147 Defining the Database Used by the Hyperion Performance Suite Repository .................................................................................................................................................................................................. 165 Reviewing User Names ........................x installation to Shared Services and the Reporting and Analysis Repository.................................................x option in the Migration Utility Wizard to migrate users.............. and repository content from a Hyperion Performance Suite 8................................................................................ 149 Identifying Hyperion Performance Suite Groups and Roles with Circular References.............. 146 Entering Logging Details................................... groups........................ 175 About Migrating from Hyperion Performance Suite 8 Use the Hyperion Performance Suite 8........................................................................... 174 Defining Additional Migration Options ................. 160 Defining the Location of the Shared Services Server ...................... 152 Selecting the Objects to Migrate ................................................................................................................... 164 Defining User/Group Names.......... roles.......................................................................................... Before performing the migration.................................................................................................................................................................................................................................................................................................. 174 Running the Migration . 170 Mapping Hosts ....... “Overview and Prerequisites.... 155 Defining Hyperion Registry Database Information ........................ 156 Defining Reporting and Analysis Repository Database Information .....6 In This Chapter Migrating from Hyperion Performance Suite 8 About Migrating from Hyperion Performance Suite 8.................. 148 Defining the Location of the Hyperion Performance Suite Repository Database........” About Migrating from Hyperion Performance Suite 8 145 ..................................................................................................................................................... Descriptions and Passwords. 145 Starting the Migration Utility Wizard. 155 Defining the Location of the Hyperion Registry Database......................................................... 159 Defining the Location of the Reporting and Analysis Repository Database ............................................................................................................... 153 Defining the Hyperion Shared Services Registry Type ..... 146 Selecting a Migration Path ... review the information in Chapter 1......................................................................................................................... 167 Reviewing Group Names ............

Starting the Migration Utility Wizard ➤ To start the Migration Utility Wizard. Figure 64 Welcome Screen 146 Migrating from Hyperion Performance Suite 8 .bat file is located in: C:\Hyperion\products\Foundation\workspace\MigrationUtility\bin If you are using Windows. If you installed to the default location. you can also start the Migration Utility Wizard by choosing Start. then Oracle EPM System. then Programs. Selecting a Migration Path Select Hyperion Performance Suite 8. click migrator.x on the Welcome screen and click Next.bat (Windows) or migrator.sh (UNIX) in the bin folder where you installed the migration utility. and then Run Migration Utility. the migrator. then Workspace.

differences encountered between the old and new systems. which may or may not be important for your particular migration scenario. Figure 65 Logging Details Table 65 Logging Details Description Specify the log level by selecting one of the following options: ● ● Field Log Level Fatal—Fatal messages cause the migration process to stop. you can ignore this message if deleting that user is part of your migration plan. Warn—Warning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. Logging information is important since this is the only place where you can see errors relating to the migration. Oracle recommends this level for most migrations. ● ● Entering Logging Details 147 .Entering Logging Details Select the log level for messages and specify the directory in which to write the log files. Info—Informational messages notify you of structural changes made between the old and new systems. an error message may tell you that a particular user does not exist in the source system. For example. Error—Error messages notify you of potential problems. and potential problems.

click Browse. ● Field Database Type SQL Server 148 Migrating from Hyperion Performance Suite 8 . Figure 66 Database Used by the Hyperion Performance Suite 8.x source repository and select how to specify the database location.x Repository Table 66 Database Type Information Description Select one of the following databases. Log Directory Specify the directory where you want to write the log file.Field Description ● Debug—Debug level messages include all types of messages and produces a very large log file. To search for a specific directory. Oracle recommends this level for testing. Defining the Database Used by the Hyperion Performance Suite Repository Define which database contains the Hyperion Performance Suite 8. Debug level messages are numerous because they give a row-by-row account of all migration steps.

JDBC Driver and URL—When you select this option. enter the information discussed in Table 67. After you enter the requested information.x repository database on your existing system. Defining the Location of the Hyperion Performance Suite Repository Database 149 . The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). you use data direct drivers. The fields that appear on the next screen in the wizard depend on the option selected here. the wizard prompts you to provide full driver information. you can use data direct drivers. If your source system is installed on DB2 version 8. Location of Hyperion Performance Suite Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 148). use IBM native drivers to connect.Field Description ● ● Oracle DB2 Note: If your source system is installed on DB2 version 7. click Test Connection to test the connection to the database.x. Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. Defining the Location of the Hyperion Performance Suite Repository Database Define the connection to the Hyperion Performance Suite 8.x .

enter the information discussed in Table 68. Enter the database port number.Figure 67 Location of Hyperion Performance Suite Repository Database Defined by Host and Name Table 67 Host and Name Information Description Enter the name of the database host. Enter the name of the database. Field Host Port Database Name User ID Password Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 148). 150 Migrating from Hyperion Performance Suite 8 . Enter the database username used to set up a database connection. Enter the password for the database.

Figure 68 Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver and URL Table 68 JDBC Driver and URL Information Description Enter the path to the native JDBC driver. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. Either type in the path.SybaseDriver. you cannot click Back and select another driver. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server.db2.DB2Driver and click Next to load it. If you wish to load a different external JDBC driver. if you enter hyperion.jar.sybase. Defining the Location of the Hyperion Performance Suite Repository Database 151 . Note: Once you have loaded an external JDBC driver. use sqljdbc. or click Browse to define the path. the Migration Utility would enter hyperion.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection. For example.jdbc. For example. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. if you selected Sybase.jdbc. you cannot load another external JDBC driver with the same name. you must restart the Migration Utility.

➤ To remove a circular reference: 1 Select the circular reference under Circular References Found. jdbc:hyperion:sybase://<host>:5000. User ID Password Enter the database username used to set up a database connection. It is important to remove circular references in Hyperion Performance Suite groups and roles since Hyperion Performance Suite allows for circular references in groups and roles and Shared Services does not. Modify this JDBC URL by personalizing the bracketed information. which contains Group C. To search for circular references in Hyperion Performance Suite groups and roles. 2 Select the relationship that contains the circular references under Select a Relationship to Remove From. 152 Migrating from Hyperion Performance Suite 8 . Circular references are groups or roles that contain other groups or roles in a cyclical relationship. For example. If the Migration Utility finds any circular references. Enter the password for the database. For example.Field JDBC URL Description The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. in the Sybase JDBC URL below. Group A contains Group B. they appear under “Circular References Found.DatabaseName=<dbname> remove <host> and <dbname> and replace them with the actual name of your host and database. 3 Click Remove Relationship and Recheck. remove the references in the source Hyperion Performance Suite system before continuing with the migration.” After all circular references are identified. Identifying Hyperion Performance Suite Groups and Roles with Circular References Search for and remove any existing circular references in Hyperion Performance Suite groups and roles. click Start. which contains Group A.

The objects selected here determine what migration screens appear next. To select an object.Figure 69 Circular References Selecting the Objects to Migrate Select the Hyperion Performance Suite objects to migrate. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. that you must migrate the objects in the order shown in the wizard. however. You can select individual objects to migrate here or on the final Run Migration screen. click the checkbox next to the object. Note. Selecting the Objects to Migrate 153 .

and files. Note: If a folder in the repository contains more than 80 to 90 items. Named collections of users. and exceptions. Field User Defined Roles Users Groups User Preferences Repository Metadata Repository Files Events User subscriptions and notifications of events involving subscriptions. the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. To make the folder accessible.x system. Repository content is the largest object to migrate. parameter lists for jobs. Account owners identified by a user ID and user name. the metadata could display the name of the content. Descriptions of the repository data.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices. The content of the system. 154 Migrating from Hyperion Performance Suite 8 . folders. For example.Figure 70 Hyperion Performance Suite Objects to Migrate Table 69 User Provisioning Objects to Migrate Description The roles defined for the users in the Hyperion Performance Suite 8. add -DPerformance.bat script and restart Common Services. User-specific settings (such as an email address). jobs. permissions etc.

0.Field Authorization Description Access control information for folders. ● Once a registry connection is established. Defining the Hyperion Shared Services Registry Type Define the Shared Services Registry to use by selecting an option: ● Default—The Migration Utility takes the connection from the local registry properties file in hyperion_home\common\config\9. and resources.5. define which database is used by the Hyperion Registry and select how to specify the database location. Defining Hyperion Registry Database Information If you selected to define a new Shared Services Registry (see “Defining the Hyperion Shared Services Registry Type” on page 125). New—Two additional wizard screens are displayed where you can enter data source connection details. documents.0. Defining the Hyperion Shared Services Registry Type 155 . the Migration Utility takes the required Shared Services and Foundation connection parameters (host names and ports) from the registry.

click Test Connection to test the connection to the database. JDBC Driver and URL—When you select this option. After you enter the requested information. Defining the Location of the Hyperion Registry Database Define the location of the Hyperion Registry database. you use data direct drivers. the wizard prompts you to provide full driver information. 156 Migrating from Hyperion Performance Suite 8 . The fields that appear on the next screen in the wizard depend on the option selected here.Table 70 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL).

enter the information in Table 58. Field Host Port Database Name User ID Password Location of the Hyperion Registry Database by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard. Enter the password for the Hyperion Registry database. Defining the Location of the Hyperion Registry Database 157 . (see “Defining Hyperion Registry Database Information” on page 126). enter the information in Table 57. Enter the database username used to set up a Hyperion Registry database connection.Location of the Hyperion Registry Database by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion Registry Database Information” on page 126). Enter the Hyperion Registry database port number. Enter the name of the Hyperion Registry database. Table 71 Hyperion Registry Database Host and Name Information Description Enter the name of the Hyperion Registry database host.

you cannot load another external JDBC driver with the same name.jdbc. User ID Enter the database username used to set up a Hyperion Registry database connection. the Migration Utility would enter hyperion. in the DB2 JDBC URL below. Either type in the path. <dbname>.db2. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. 158 Migrating from Hyperion Performance Suite 8 .DB2Driver. you cannot click Back and select another driver. you must restart the Migration Utility. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example. and DB2 package. Note: Once you have loaded an external JDBC driver. or click Browse to define the path. JDBC URL The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. jdbc:hyperion:db2://<server>: 50000. If you wish to load a different external JDBC driver.DatabaseName=<dbname>.PackageName=<package> remove <server>.db2. For example. Modify this JDBC URL by personalizing the bracketed information. database. if you enter hyperion. For example. if you selected DB2. and <package> and replace them with the actual names of your server.Table 72 Hyperion Registry Database JDBC Driver and URL Information Description Enter the path to the native JDBC driver.jdbc.DB2Driver and click Next to load it.

Defining Reporting and Analysis Repository Database Information Define which database contains the target Reporting and Analysis Repository and select how to specify the database location. Figure 71 Database Used by the Reporting and Analysis Repository Table 73 Database Type Information Description Select one of the following databases. ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: Defining Reporting and Analysis Repository Database Information 159 .Field Password Description Enter the password for the Hyperion Registry database.

the wizard prompts you to provide full driver information. JDBC Driver and URL—When you select this option. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL).Field Description ● ● Host and Name—When you select this option. Defining the Location of the Reporting and Analysis Repository Database Define the connection to the Reporting and Analysis Repository database on the target system. enter the information discussed in Table 74. After you enter the requested information. you use data direct drivers. The fields that appear on the next screen in the wizard depend on the option selected here. 160 Migrating from Hyperion Performance Suite 8 . Location of Reporting and Analysis Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 148). click Test Connection to test the connection to the database.

manually copying your source tables to the target database is much quicker than allowing the Migration Utility to copy them over a network. Enter the database username used to set up a Reporting and Analysis Repository database connection. and Provisioning Manager roles. Field Host Port Database Name User ID Password Source tables have been copied to the target database Enter the password for the database. This is because the Migration Utility normally issues multiple commands to Defining the Location of the Reporting and Analysis Repository Database 161 . Enter the Reporting and Analysis Repository database port number. Enter the name of the Reporting and Analysis Repository database. Note: The user must be assigned Global Administrator. Select this option if you manually copied your source tables to the target database. Directory Manager. In most cases.Figure 72 Location of Reporting and Analysis Repository Database Defined by Host and Name Table 74 Host and Name Information Description Enter the name of the Reporting and Analysis Repository database host.

The prefix should consist of alphabetic. Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 148). or alphanumeric characters. add a prefix to differentiate the Hyperion Performance Suite V8 tables from the Hyperion System 9 V8 tables. if the source tables are copied to the target database without adding a prefix. To avoid this. thus resulting in a much faster migration. however. If you manually copy your source tables to the target database. the current V8 tables will be overwritten. make sure to have both the source tables and the target tables accessible in one database user account. numeric. The following tables are affected: V7_CONTAINER V7_CONT_VERSION V7_DATA_CONTAINER V7_SPF_OUT_OPTS V7_COLLECTION_MBRS V7_COLLECTION V7_CONTNR_KEYWORDS V7_FOLDER V7_FOLDER_TREE V7_TASK VY_JOBINPUTVALUES V7_INPUT_PARAMETER Tables Prefix Since both Hyperion Performance Suite and Reporting and Analysis have V8 tables. the Migration Utility issues one command to move all of the rows in the table.Field Description separately move each database row from the source database to the target database. If all of the tables are located in the same database before migration. enter the information discussed in Table 75. 162 Migrating from Hyperion Performance Suite 8 . Having your source and target tables in the same database user account can speed up large migrations by allowing you to use another utility to import large V7 tables into your target database.

For example. use sqljdbc. you cannot load another external JDBC driver with the same name. if you selected SQL Server. you cannot click Back and select another driver. if you enter hyperion.jdbc.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection.jdbc.SQLServerDriver. Note: Once you have loaded an external JDBC driver.db2. the migration utility would enter hyperion. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen. Either type in the path.jar. If you wish to load Defining the Location of the Reporting and Analysis Repository Database 163 .DB2Driver and click Next to load it.sqlserver. Figure 73 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL Table 75 JDBC Driver and URL Information Description Enter the path to the native JDBC driver. For example. or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server.

or alphanumeric characters. Password Source tables have been copied to the target database Tables Prefix Since both Hyperion Performance Suite and Reporting and Analysis have V8 tables. Enter the password for the database. in the SQL Server JDBC URL below. add a prefix to differentiate the Hyperion Performance Suite V8 tables from the Hyperion System 9 V8 tables. jdbc:hyperion:SQLSERVER://<host>: 1433. JDBC URL The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. the current V8 tables will be overwritten. if the source tables are copied to the target database without adding a prefix. click Test Connection to test the connection to the server. After you enter the requested information.SelectMethod=cursor remove <host> and <dbname> and replace them with the actual name of your host and database. User ID Enter the database username used to set up a database connection. For example. Modify this JDBC URL by personalizing the bracketed information. The prefix should consist of alphabetic.Field Description a different external JDBC driver.DatabaseName=<dbname>. See description in Table 74. To avoid this. you must restart the Migration Utility. numeric. 164 Migrating from Hyperion Performance Suite 8 . Defining the Location of the Shared Services Server Define the location of the Shared Services Server on the target system.

Enter the password for the User ID.Figure 74 Location of Target Shared Services Server Table 76 Target Shared Services Server Information Description Enter the name of the Shared Services Server host. user and group descriptions. Descriptions and Passwords Define how to treat user and group names. and passwords when creating new users in Shared Services. The user must have an administrative role in Shared Services. Field Host Port User ID Password Defining User/Group Names. Enter the Shared Services Server port number. Descriptions and Passwords 165 . Enter the login ID for the user in Shared Services. Defining User/Group Names.

click the checkbox next to Other and specify the delimiter. If the names in the source description fields have a different delimiter. you can specify whether to add the middle name as part of the first name or as part of the last name.Figure 75 User/Group Descriptions and Passwords Table 77 Information on User/Group Descriptions and Passwords Description Select User First and Last Name Fields in Shared Services to copy the Hyperion Performance Suite User First and Last Name fields to the Shared Services User First and Last Name fields. If you select this option: ● Field User Names Specify how the names in the source description fields are separated by clicking the checkbox next to Space. you would click the checkbox next to Last Name. ● ● Group Names Define how to treat Group names when migrating native groups by selecting one of the following options: ● Same Group Name—Migrates the native Hyperion Performance Suite group name to a native Shared Services group name and keeps the group name the same. For example. 166 Migrating from Hyperion Performance Suite 8 . or Comma. Note that you can select more than one option. For example. if the name appears starting with the last name. Specify how to add middle names in Shared Services by selecting an option for Add Middle Name to. if a user name consists of more than two names. Semi-colon. Specify how the user names appear in Hyperion Performance Suite by selecting an option for Name Starts With.

Passwords Define how to handle passwords when creating new Shared Services users by selecting one of the following options: ● ● ● Auto-generated Same as user ID Other Note: If the password is auto-generated. The administrator can use this information to email users their new passwords. Reviewing User Names Review the user mappings and properties and set the migration action for each user. For a complete list of properties for a user. Most of the properties for each user name display next to the user name. the migration utility creates a file that lists the new native users along with their login ID. select a user name and click Properties (see “Editing User Name Properties” on page 168). Reviewing User Names 167 .Field Description ● Alternate Group Name—Migrates the native Hyperion Performance Suite group name to a native Shared Services group name with a prefix or suffix added to the name. autogenerated password. Enter the desired prefix or suffix in the Prefix or Suffix field. The default is to copy the Hyperion Performance Suite User/Group Description to the Shared Services User/Group Description. User/Group Descriptions Define where to copy the Hyperion Performance Suite user/group descriptions when creating new native Shared Services groups. and email address.

Editing User Name Properties ➤ To edit user name properties: 1 Select the desired user name and click Properties or double-click the user name. The Properties dialog box displays. you can display all the user names again by clicking Show All. The user names that meet the search criteria display. 168 Migrating from Hyperion Performance Suite 8 .Figure 76 User Names Searching for User Names ➤ To search for a user name: 1 Click Search. After you search for a user name. 2 Define how to conduct the search in the Search dialog box and click Search again.

click Properties. you can set the migration action property to Migrate or Do Not Migrate. You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. the user is mapped to another Shared Services user or a new user is created with the new name. however. then during migration. 2 Edit the desired properties and click OK. Reviewing User Names 169 . to map a Hyperion Performance Suite user name to a different Shared Services user name. Some properties are read-only and some can be edited. and select the desired option in the Action field. If you change the user name.The user name properties from both systems (source and target) are displayed. Setting the Migration Action For each user. you would select the user name. you cannot edit any of the Shared Services User properties. To do this. Note: For existing users. use one of the following options: ● Select the user. click Properties. then during migration. and change the Shared Services user name in the Properties dialog box. it queries the source system for users and attempts to automatically map them to existing Shared Services users based on the following criteria: ● ● ● login ID email address first name/last name If a mapping cannot be made. you can change the user name. For example. Verifying User Name Mapping When you run the migration utility. the migration utility creates a new native user.

you must manually activate the user in the source system before performing the migration. For a complete list properties for a group. or click Select All to select all the user names. If you later change a user’s action to Do Not Migrate and perform another migration. Most of the properties for each group name display next to the group name. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the user names from each system and keeps any changes made to the mapping and property information. discards any changes made to the mapping or properties. instead. Discard Changes (restore original values)—Retrieves the user names from each system. select a group name and click Properties (see “Editing Group Name Properties” on page 171). ● ● Updating User Name Information If you wish to refresh the automatic mapping on the User Names screen. all new native users whose action is set to Migrate are migrated to the target Shared Services. the migration utility does not remove the previously-migrated user from target Shared Services system. keep in mind the following: ● When you perform a migration.● Select the user and click the checkbox next to Migrate User Name from Hyperion Performance Suite to Shared Services. and restores mapping and property information to the original values. When specifying whether to migrate users from Hyperion Performance Suite to Shared Services. press [Shift] and select the desired user names. To migrate a deactivated user. you must delete the user directly from the target Shared Services. This setting cannot be changed. To set the action for more than one user. ● Reviewing Group Names Review the group mappings and properties and set the migration action for each group. The default setting for inactive users is Do Not Migrate. 170 Migrating from Hyperion Performance Suite 8 . Users who are not migrated lose all access control information associated with them as well as any assigned user properties.

After you search for a group name you can display all the group names again by clicking Show All.Figure 77 Group Names Searching for Group Names ➤ To search for a group name: 1 Click Search. The Properties dialog box displays. Reviewing Group Names 171 . Editing Group Name Properties ➤ To edit group name properties: 1 Select the desired group name and click Properties. 2 Define how to conduct the search in the Search dialog box and click Search again. The group names that meet the search criteria display.

and change the Shared Services group name in the Properties dialog box. or click Select All to select all the group names. you can set the Action property to Migrate or Do Not Migrate. Select the group and click the checkbox next to Migrate Group Name from Hyperion Performance Suite to Shared Services. If a mapping cannot be made. the migration utility creates a new native group.The group name properties from both systems (source and target) are displayed. it queries the source system for groups and attempts to automatically map them to existing Shared Services groups based on the group name. Some properties are read-only and some can be edited. When specifying whether to migrate groups from Hyperion Performance Suite to Shared Services. Setting the Migration Action For each group. 2 Edit the desired properties and click OK. you cannot edit any of the properties in the User Management Group section of the dialog box. to map a Hyperion Performance Suite group name to a different Shared Services group name. click Properties. you would select the group name. For example. Verifying Group Name Mapping When you run the migration utility. click Properties. use one of the following options: ● ● Select the group. You can view these mappings on the Group Names screen and manually adjust or change the mappings as necessary. keep in mind the following: 172 Migrating from Hyperion Performance Suite 8 . If the group is set to Do Not Migrate. and select the desired option in the Action field. then during migration. To set the action for more than one group. To do this. press [Shift] and select the desired group names.

If you want to migrate a deactivated group. ● ● ● Adding Users/Groups Assigned in Hyperion Performance Suite to the Native Shared Services Group ➤ To add users and groups assigned in Hyperion Performance Suite to the native Shared Services group: 1 Press [Shift] and select the desired group names.● The default setting for inactive groups is Do Not Migrate. set the Action property of the native parent group to Migrate. This ensures that user/group relationships migrate correctly. 2 Click the checkbox next to Add Users/Groups Assigned in Hyperion Performance Suite to the Native Shared Services Group. This ensures that user properties and access control information referring to the users and groups migrates correctly. Note: When you select this option. set the Action property to Migrate for all users and groups that have already been migrated. set the Action property to Migrate for the all users belonging to the group that have already been migrated. this new native group is created and any users and groups assigned to the group in the source system are assigned to the group in the target system. When you migrate content. and restores mapping and property information to the original values. Updating Group Name Information If you wish to refresh the automatic mapping on the Group Names screen. discards any changes made to the mapping or properties. ● Reviewing Group Names 173 . This setting cannot be changed. This ensures that group-to-group associations migrate correctly. then upon migration. or click Select All to select all the group names. Discard Changes (restore original values)—Retrieves the group names from each system. If you migrate a group that is a member of a native parent group (that is going to be migrated or was already migrated). When you migrate groups. you must manually activate the group in the source system before performing the migration. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the group names from each system and keeps any changes made to the mapping and property information. if a group in Hyperion Performance Suite is going to be mapped to a new native group in Shared Services.

Defining Additional Migration Options Select additional options to provide advanced control of the migration process. 174 Migrating from Hyperion Performance Suite 8 . select a Hyperion Performance Suite Host and a Reporting and Analysis Repository Host and click Map Hosts. Figure 78 Host Mapping ➤ To map a host. select the hosts in the Mapped Hosts text box and click Remove Mapped Host.Mapping Hosts Define the mapping for Hyperion Performance Suite hosts and Reporting and Analysis Repository hosts. ➤ To remove a mapped pair of hosts. For example. you must map each source job factory to a new Reporting and Analysis Repository host. The hosts display in the Mapped Hosts text box.

0 as 90. Hyperion strongly recommends that you run a pre-migration process before completing an actual migration.Figure 79 Additional Migration Options Table 78 Additional Migration Options Description Enter the paths for the following: ● ● Field Repository Content Source server. you must re-compile all your Production Reporting jobs.3 as 83. Version 9. For example. the migration utility goes through the migration Running the Migration 175 . Repository Job Factory If you plan to migrate Production Reporting files. to run a test migration that will help determine any migration issues. During a pre-migration test. Running the Migration The final screen of the Migration Utility wizard allows you to review the objects selected to migrate. and so on.xml and target server. and to run the actual migration.xml Source repository content and target repository content Either type in the path or click Browse to select a path. define the version of the files in the Reporting and Analysis Repository . Note: After you complete the migration. enter Version 8.

After all the user defined roles migrated successfully. For example. Note. errors may cause the actual migration to stop or remain incomplete. you may want to backup the target database after you successfully migrate each object type.process without actually moving objects from the source system to the target system. you could begin by selecting User Defined Roles. however. Unless addressed. 3 Check to make sure the object migrated correctly and fix any errors. 4 Backup your target database (and your OpenLDAP database if you are migrating users and groups. it reports them in the log files. ➤ To migrate each object type separately: 1 Select the desired object type. that you must migrate the objects in the order shown in the wizard. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. After you complete the pre-migration test and fix all the outstanding errors. select Test Only as the Run Mode. When you migrate users and groups.) 5 Return to the wizard and select the next object to migrate. ➤ To run a pre-migration process.) This step is optional As an extra precaution. If the migration utility finds any problems. 176 Migrating from Hyperion Performance Suite 8 . You should fix any potential errors encountered in the pre-migration process before performing an actual migration. (The Migration Utility updates both the target database and the OpenLDAP database. 2 Select Perform Migration as the Run Mode and click Start. you should also backup the OpenLDAP database. you would select Users.

Figure 80 Run Migration Table 79 Run Migration Options Description Review the objects selected to migrate. and the number of objects migrated. The objects that are enabled are the objects selected on the Select Objects to Migrate screen earlier in the wizard (see “Selecting the Objects to Migrate” on page 153). Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. Progress Displays information about the progress of the migration such as successes. Unless addressed. Field Select the Objects to Migrate Run Mode Select one of the following options: ● ● Test Only—Runs a pre-migration process to help identify any migration issues. errors. Note: Oracle recommends that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object. Perform Migration—Runs the actual migration. errors may cause the actual migration to stop or remain incomplete. warnings. the number of objects remaining to be migrated. Status Messages Running the Migration 177 . Displays informational messages about the migration.

178 Migrating from Hyperion Performance Suite 8 .

............................. 192 Defining the Location of the Reporting and Analysis Repository Database ............................................................................................................... groups............................................... 182 Defining the Location of the Reports Repository Database .2............................. 193 Defining the Location of the Reporting and Analysis Repository Server .................................................” Starting the Migration Utility Wizard ➤ To start the Migration Utility Wizard................................... 198 Reviewing User Names ..................................... If you installed to the default location........................................................................................................................................... and repository contents from a Hyperion Reports 7........................................................................... 179 Selecting a Migration Path ........................................................... the migrator................... 188 Defining the Location of the Hyperion Registry Database.......................... roles.................... 186 Defining the Hyperion Shared Services Registry Type ......... 179 Starting the Migration Utility Wizard..bat (Windows) or migrator...... 196 Defining the Location of the Shared Services Server ....................................................... 180 Entering Logging Details.................................... 200 Running the Migration ......... click migrator.................... Descriptions and Passwords............... review the information in Chapter 1........ Before performing the migration.................................................................................................................... 183 Defining the Hyperion Reports Administrator................................................................................0...............................sh (UNIX) in the bin folder where you installed the migration utility............. “Overview and Prerequisites...................... 185 Selecting the Objects to Migrate ...............................................bat file is located in: About Migrating from Hyperion Reports 179 .x or 7...............................x installation to Shared Services and the Reporting and Analysis Repository.............. 197 Defining User/Group Names.......................................7 In This Chapter Migrating from Hyperion Reports About Migrating from Hyperion Reports.................................................................... 206 About Migrating from Hyperion Reports Use the Hyperion Reports option in the Migration Utility Wizard to migrate users............................ 188 Defining Hyperion Registry Database Information ............................... 189 Defining Reporting and Analysis Repository Database Information ........... 180 Defining the Database Used by the Reports Repository ...........................................................................

then Programs. and then Run Migration Utility. Logging information is important since this is the only place where you can see errors relating to the migration. Figure 81 Welcome Screen Entering Logging Details Select the log level for messages and specify the directory in which to write the log files. then Oracle EPM System. Selecting a Migration Path Select Hyperion Reports on the Welcome screen and click Next.C:\Hyperion\products\Foundation\workspace\MigrationUtility\bin If you are using Windows. you can also start the Migration Utility Wizard by choosing Start. 180 Migrating from Hyperion Reports . then Workspace.

Error—Error messages notify you of potential problems. Warn—Warning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. To search for a specific directory. you can ignore this message if deleting that user is part of your migration plan. ● ● ● Log Directory Specify the directory where you want to write the log file. Oracle recommends this level for testing. For example. an error message may tell you that a particular user does not exist in the source system. Info—Informational messages notify you of structural changes made between the old and new systems. Debug level messages are numerous because they give a row-by-row account of all migration steps. and potential problems.Figure 82 Logging Details Table 80 Logging Details Description Specify the log level by selecting one of the following options: ● ● Field Log Level Fatal—Fatal messages cause the migration process to stop. Entering Logging Details 181 . differences encountered between the old and new systems. Oracle recommends this level for most migrations. Debug—Debug level messages include all types of messages and produces a very large log file. click Browse. which may or may not be important for your particular migration scenario.

you can use data direct drivers. use IBM native drivers to connect. ● ● ● Field Database Type SQL Server Oracle DB2 Note: If your source system is installed on DB2 version 7.Defining the Database Used by the Reports Repository Define which database contains the Reports source repository and select how to specify the database location. Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option.x. Figure 83 Database Used by the Reports Repository Table 81 Database Type Information Description Select one of the following databases. The fields that appear on the next screen in the wizard depend on the option selected here. If your source system is installed on DB2 version 8. you use data direct drivers. JDBC Driver and URL—When you select this option. the wizard prompts you to provide full driver information.x. 182 Migrating from Hyperion Reports .

enter the information discussed in Table 82. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). Location of Reports Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Reports Repository” on page 182). After you enter the requested information.Defining the Location of the Reports Repository Database Define the connection to the Reports repository database on your existing system. Enter the database port number. click Test Connection to test the connection to the database. Field Host Port Defining the Location of the Reports Repository Database 183 . Figure 84 Location of Reports Repository Database Defined by Host and Name Table 82 Host and Name Information Description Enter the name of the database host.

Field Database Name User ID Password Description Enter the name of the database. Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection. Enter the database username used to set up a database connection. Figure 85 Location of Reports Repository Database Defined by JDBC Driver and URL 184 Migrating from Hyperion Reports . Enter the password for the database. use sqljdbc. Location of Reports Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Reports Repository” on page 182). If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server.jar. enter the information discussed in Table 83.

jdbc.SelectMethod=cursor remove <host> and <dbname> and replace them with the actual name of your host and database. you must restart the Migration Utility. For example. Enter the password for the database. if you selected SQL Server. For example. Defining the Hyperion Reports Administrator 185 .DatabaseName=<dbname>. Modify this JDBC URL by personalizing the bracketed information. For example.DB2Driver and click Next to load it. the migration utility would enter hyperion. Either type in the path. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen. User ID Password Enter the database username used to set up a database connection.Table 83 JDBC Driver and URL Information Description Enter the path to the native JDBC driver. jdbc:hyperion:SQLSERVER://<host>: 1433. If you wish to load a different external JDBC driver. if you enter hyperion. JDBC URL The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen.SQLServerDriver.db2. you cannot load another external JDBC driver with the same name. Note: Once you have loaded an external JDBC driver. or click Browse to define the path.jdbc. you cannot click Back and select another driver. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. in the SQL Server JDBC URL below.sqlserver. Defining the Hyperion Reports Administrator Enter a Hyperion Reports Administrator username and click Test Connection.

You can select individual objects to migrate here or on the final Run Migration screen. click the checkbox next to the object. however. The objects selected here determine what Reports migration screens appear next. Note. 186 Migrating from Hyperion Reports . that you must migrate the objects in the order shown in the wizard.Figure 86 Hyperion Reports Administrator Selecting the Objects to Migrate Select the Reports objects to migrate. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. To select an object.

Named collections of users. namely: folders. To make the folder accessible. Selecting the Objects to Migrate 187 . which consists of files in the native file system and metadata for each object in a database in a Relational Database Management System (RDBMS).MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices. select one of the following options: ● ● Field Users Groups Repository Content Overwrite the item in the Reporting and Analysis Repository Do not copy the item into the Reporting and Analysis Repository Note: If a folder in the repository contains more than 80 to 90 items. add -DPerformance. The content of the system. Repository content is the largest object to migrate. jobs. and their metadata (properties). URLs. files.Figure 87 Hyperion Reports Objects to Migrate Table 84 Hyperion Reports Objects to Migrate Description Account owners identified by a user ID and user name. The content resides in the Repository. and shortcuts. the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. When an item in the Reporting and Analysis Repository repository has the same name and type as an object in the Hyperion Reports repository.bat script and restart Common Services.

define which database is used by the Hyperion Registry and select how to specify the database location. 188 Migrating from Hyperion Reports .5.0.Defining the Hyperion Shared Services Registry Type Define the Shared Services Registry to use by selecting an option: ● Default—The Migration Utility takes the connection from the local registry properties file in hyperion_home\common\config\9. ● Once a registry connection is established. Defining Hyperion Registry Database Information If you selected to define a new Oracle's Hyperion Shared Services Registry (see “Defining the Hyperion Shared Services Registry Type” on page 125). New—Two additional wizard screens are displayed where you can enter data source connection details.0. the Migration Utility takes the required Shared Services and Foundation connection parameters (host names and ports) from the registry.

Table 85 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: ● ● Host and Name—When you select this option. click Test Connection to test the connection to the database. the wizard prompts you to provide full driver information. JDBC Driver and URL—When you select this option. After you enter the requested information. Defining the Location of the Hyperion Registry Database Define the location of the Hyperion Registry database. you use data direct drivers. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). The fields that appear on the next screen in the wizard depend on the option selected here. Defining the Location of the Hyperion Registry Database 189 .

Table 86 Hyperion Registry Database Host and Name Information Description Enter the name of the Hyperion Registry database host.Location of the Hyperion Registry Database by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion Registry Database Information” on page 126). (see “Defining Hyperion Registry Database Information” on page 126). Enter the name of the Hyperion Registry database. 190 Migrating from Hyperion Reports . Enter the Hyperion Registry database port number. Field Host Port Database Name User ID Password Location of the Hyperion Registry Database by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard. Enter the password for the Hyperion Registry database. Enter the database username used to set up a Hyperion Registry database connection. enter the information in Table 57. enter the information in Table 58.

Note: You do not need to enter a native JDBC driver path for DataDirect drivers. Defining the Location of the Hyperion Registry Database 191 . Note: Once you have loaded an external JDBC driver. if you selected DB2.db2.PackageName=<package> remove <server>. and <package> and replace them with the actual names of your server. jdbc:hyperion:db2://<server>: 50000. you must restart the Migration Utility.DatabaseName=<dbname>.DB2Driver.jdbc. and DB2 package. JDBC URL The Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen.DB2Driver and click Next to load it. you cannot click Back and select another driver. Field Native JDBC Driver Path JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. Either type in the path. If you wish to load a different external JDBC driver.db2. or click Browse to define the path.jdbc. For example.Table 87 Hyperion Registry Database JDBC Driver and URL Information Description Enter the path to the native JDBC driver. <dbname>. the Migration Utility would enter hyperion. in the DB2 JDBC URL below. if you enter hyperion. you cannot load another external JDBC driver with the same name. For example. database. User ID Enter the database username used to set up a Hyperion Registry database connection. Modify this JDBC URL by personalizing the bracketed information. For example.

Defining Reporting and Analysis Repository Database Information Define which database contains the target Reporting and Analysis Repository and select how to specify the database location. Figure 88 Database Used by the Reporting and Analysis Repository Repository Table 88 Database Type Information Description Select one of the following database drivers: ● ● ● Field Database Type SQL Server Oracle DB2 Database Location Select one of the following options to specify the database location: 192 Migrating from Hyperion Reports .Field Password Description Enter the password for the Hyperion Registry database.

JDBC Driver and URL—When you select this option. enter the information discussed in Table 89. you use data direct drivers. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). Defining the Location of the Reporting and Analysis Repository Database 193 . The fields that appear on the next screen in the wizard depend on the option selected here. Defining the Location of the Reporting and Analysis Repository Database Define the location of the Reporting and Analysis Repository database on the target system. Location of Reporting and Analysis Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 192).Field Description ● ● Host and Name—When you select this option. the wizard prompts you to provide full driver information. click Test Connection to test the connection to the database. After you enter the requested information.

Enter the Reporting and Analysis Repository database port number. Enter the password for the Reporting and Analysis Repository database. enter the information discussed in Table 90.Figure 89 Location of Reporting and Analysis Repository Database Defined by Host and Name Table 89 Host and Name Information Description Enter the name of the Reporting and Analysis Repository database host. Enter the name of the Reporting and Analysis Repository database. Field Host Port Database Name User ID Password Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Reporting and Analysis Repository Database Information” on page 192). 194 Migrating from Hyperion Reports . Enter the database username used to set up a Reporting and Analysis Repository database connection.

For example.jdbc.Note: It is recommended to use the same native JDBC drivers when you use the “JDBC Driver and URL” option for source and target system connection.sqlserver. Defining the Location of the Reporting and Analysis Repository Database 195 .jdbc. or click Browse to define the path. if you enter hyperion. use sqljdbc. For example. you cannot load another external JDBC driver with the same name. If you wish to load a different external JDBC driver. if you selected SQL Server. Either type in the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers. Figure 90 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL Table 90 JDBC Driver and URL Information Description Enter the path to the native JDBC driver. the migration utility would enter hyperion.SQLServerDriver.jar. you must restart the Migration Utility.db2. you cannot click Back and select another driver. If you are migrating from an MsSQL 2000 server to an MsSQL 2005 server. Field Native JDBC Driver Path JDBC Driver The migration utility automatically enters a JDBC driver based on the database you selected on the previous screen. Note: Once you have loaded an external JDBC driver.DB2Driver and click Next to load it.

DatabaseName=<dbname>. After you enter the requested information.SelectMethod=cursor remove <host> and <dbname> and replace them with the actual name of your host and database. click Test Connection to test the connection to the server. in the SQL Server JDBC URL below. jdbc:hyperion:SQLSERVER://<host>: 1433. Enter the password for the Reporting and Analysis Repository database. 196 Migrating from Hyperion Reports . Password Defining the Location of the Reporting and Analysis Repository Server Define the connection to the Reporting and Analysis Repository Server on the target system. Modify this JDBC URL by personalizing the bracketed information.Field JDBC URL Description The migration utility automatically enters a JDBC URL based on the database you selected on the previous screen. For example. User ID Enter the database username used to set up a Reporting and Analysis Repository database connection.

click Test Connection to test the connection to the server. After you enter the requested information. and Provisioning Manager roles. Defining the Location of the Shared Services Server 197 . Directory Manager.Figure 91 Location of the Target Reporting and Analysis Repository Server Table 91 Target Reporting and Analysis Repository Server Information Description Enter the name of the Reporting and Analysis Repository Server host. Enter the login ID for the user with Global Administrator. Field Host Port User ID Password Defining the Location of the Shared Services Server Define the location of the Shared Services Server on the target system. Enter the password for the user ID. Enter the Oracle's Hyperion Reporting and Analysis Repository Server port number.

198 Migrating from Hyperion Reports . group descriptions. Field Host Port User ID Password Defining User/Group Names. Enter the password for the User ID. Enter the Shared Services Server port number. The user must have an administrative role in Shared Services.Figure 92 Location of Shared Services Server Table 92 Shared Services Server Information Description Enter the name of the Shared Services Server host. group names. and passwords when creating new users in the Shared Services Server. Enter the login ID for the user in Shared Services. Descriptions and Passwords Define how to treat user descriptions.

For example. For example. Shared Services User First and Last Name Fields—Copies the Reports User First and Last Name fields to the Shared Services User First and Last Name fields. Semi-colon. Select one of the following options: ● Field User Descriptions Shared Services User Description—Copies the Reports User Description fields to the Shared Services User Description fields. Specify how the user names appear in Analyzer by selecting an option for Name Starts With. Note that you can select more than one option. click the checkbox next to Other and specify the delimiter. If the names in the source description fields have a different delimiter. if a user name consists of more than two names. you would click the checkbox next to Last Name. you can specify whether to add the middle name as part of the first name or as part of the last name. ❍ ❍ Defining User/Group Names. or Comma. If you select this option: ❍ ● Specify how the names in the source description fields are separated by clicking the checkbox next to Space.Figure 93 User/Group Descriptions and Passwords Table 93 Information on User/Group Descriptions and Passwords Description Define how to copy the User Descriptions from Reports when creating new native Shared Services users. Specify how to add middle names in Shared Services by selecting an option for Add Middle Name to. Descriptions and Passwords 199 . if the name appears starting with the last name. Tab.

select a user name and click Properties (see “Editing User Name Properties” on page 201). 200 Migrating from Hyperion Reports . the migration utility creates a file that lists the new native users along with their login ID.Field Group Names Description Define how to treat group names when migrating native groups by selecting one of the following options: ● Same Group Name—Migrates the native Reports group name to a native Shared Services group name and keeps the group name the same. Enter the desired prefix or suffix in the Prefix or Suffix field. For a complete list of properties for a user. Most of the properties for each user name display next to the user name. The default is to copy the Reports Group Description to the Shared Services Group Description. User/Group Descriptions Define where to copy the Reports group descriptions when creating new native Shared Services groups. The administrator can use this information to email users their new passwords. and email address. Alternate Group Name—Migrates the native Reports group name to a native Shared Services group name with a prefix or suffix added to the name. Reviewing User Names Review the user mappings and properties and set the migration action for each user. ● Passwords Define how to handle passwords when creating new Shared Services users by selecting one of the following options: ● ● ● Auto-generated Same as user ID Other Note: If the password is auto-generated. autogenerated password.

Editing User Name Properties ➤ To edit user name properties: 1 Select the desired user name and click Properties or double-click the user name. 2 Define how to conduct the search in the Search dialog box and click Search again.Figure 94 User Names Searching for User Names ➤ To search for a user name: 1 Click Search. Reviewing User Names 201 . The user names that meet the search criteria display. The Properties dialog box displays. After you search for a user name. you can display all the user names again by clicking Show All.

Some properties are read-only and some can be edited. you can change the user name. click Properties. you cannot edit any of the Shared Services User properties. click Properties. If you change the user name. Setting the Migration Action For each user. To do this. then during migration. For example. the user is mapped to another Shared Services user or a new user is created with the new name. Note: For existing users. it queries the source system for users and attempts to automatically map them to existing Shared Services users based on the following criteria: ● ● ● login ID email address first name/last name If a mapping cannot be made. then during migration. 202 Migrating from Hyperion Reports . 2 Edit the desired properties and click OK. however. Verifying User Name Mapping When you run the migration utility. use one of the following options: ● Select the user. You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. and select the desired option in the Action field. to map a Reports user name to a different Shared Services user name. you would select the user name. the migration utility creates a new native user. and change the Shared Services user name in the Properties dialog box.The user name properties from both systems (source and target) are displayed. you can set the migration action property to Migrate or Do Not Migrate.

all new native users whose action is set to Migrate are migrated to the target Shared Services. the migration utility does not remove the previously-migrated user from target Shared Services system. Discard Changes (restore original values)—Retrieves the user names from each system. or click Select All to select all the user names. you must delete the user directly from the target Shared Services. For a complete list of group name properties.● Select the user and click the checkbox next to Migrate User Name from Hyperion Reports to Shared Services. instead. you can either save the changes or discard the changes and set the information back to the default values (see “Updating Group Name Information” on page 206). ● Updating User Name Information If you wish to refresh the automatic mapping on the User Names screen. Reviewing User Names 203 . When specifying whether to migrate users from Reports to Shared Services. If you later change a user’s action to Do Not Migrate and perform another migration. and restores mapping and property information to the original values. click Properties (see “Editing Group Name Properties” on page 204). Users who are not migrated lose all access control information associated with them as well as any assigned user properties. Most of the properties for each group name display next to the group name. ● Reviewing Group Names Review the group mappings and properties and set the migration action for each group. When you make changes on this screen. To set the action for more than one user. press [Shift] and select the desired user names. keep in mind the following: ● When you perform a migration. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the user names from each system and keeps any changes made to the mapping and property information. discards any changes made to the mapping or properties.

Editing Group Name Properties ➤ To edit group name properties: 1 Select the desired group name and click Properties.Figure 95 Group Names Searching for Group Names ➤ To search for a group name: 1 Click Search. 204 Migrating from Hyperion Reports . The group names that meet the search criteria display. The Properties dialog box displays. After you search for a group name you can display all the group names again by clicking Show All. 2 Define how to conduct the search in the Search dialog box and click Search again.

You can view these mappings on the Group Names screen and manually adjust or change the mappings as necessary. Verifying Group Name Mapping When you run the migration utility. press [Shift] and select the desired group names. If a mapping cannot be made. or click Select All to select all the group names. click Properties. click Properties.The group name properties from both systems (source and target) are displayed. you would select the group name. When specifying whether to migrate groups from Reports to Shared Services. For example. you can set the Action property to Migrate or Do Not Migrate. to map a Reports group name to a different Shared Services group name. To do this. 2 Edit the desired properties and click OK. use one of the following options: ● ● Select the group. Select the group and click the checkbox next to Migrate Group Name from Reports to Shared Services. then during migration. If the group is set to Do Not Migrate. you cannot edit any of the properties in the User Management Group section of the dialog box. and select the desired option in the Action field. Setting the Migration Action For each group. the migration utility creates a new native group. keep in mind the following: Reviewing User Names 205 . and change the Shared Services group name in the Properties dialog box. Some properties are read-only and some can be edited. it queries the source system for groups and attempts to automatically map them to existing Shared Services groups based on the group name. To set the action for more than one group.

then upon migration. or click Select All to select all the group names. the Migration Utility goes through the migration 206 Migrating from Hyperion Reports . set the Action property to Migrate for all users and groups that have already been migrated. click Update Names and select one of the following options: ● Keep Changes (use new values)—Validates the group names from each system and keeps any changes made to the mapping and property information. discards any changes made to the mapping or properties. this new native group is created and any users and groups assigned to the group in the source system are assigned to the group in the target system. set the Action property to Migrate for the all users belonging to the group that have already been migrated. Discard Changes (restore original values)—Retrieves the group names from each system. If you migrate a group that is a member of a native parent group (that is going to be migrated or was already migrated). Updating Group Name Information If you wish to refresh the automatic mapping on the Group Names screen. Hyperion strongly recommends that you run a pre-migration process before completing an actual migration. This ensures that user properties and access control information referring to the users and groups migrates correctly. This ensures that user/group relationships migrate correctly. ● ● Adding Users/Groups Assigned in Reports to the Native Shared Services Group ➤ To add users and groups assigned in Reports to the native Shared Services group: 1 Press [Shift] and select the desired group names. and restores mapping and property information to the original values. ● Running the Migration The final screen of the Migration Utility wizard allows you to review the objects selected to migrate and to run the actual migration. This ensures that group-to-group associations migrate correctly.● When you migrate groups. 2 Click the checkbox next to Add Users/Groups Assigned in Reports to the Native Shared Services Group. set the Action property of the native parent group to Migrate. When you migrate content. if a group in Reports is going to be mapped to a new native group in Oracle's Hyperion® Shared Services . During a pre-migration test. Note: When you select this option.

Test Only is disabled for repository content. Oracle recommends that you migrate each object type separately and check to ensure that the object migrated correctly before migrating the next object. 4 Backup your target database (and your OpenLDAP database if you are migrating users and groups. Note: For Hyperion Reports you can only run a pre-migration test on users and groups. Unless addressed. After all the users migrated successfully. you should also backup the OpenLDAP database.) 5 Return to the wizard and select the next object to migrate.” the Text Only option is disabled. For example: ● ● ● If you select “Users” and/or “Groups” the Test Only option is enabled. ➤ To migrate each object type separately: 1 Select the desired object type. To do this.“ Groups. 2 Select Perform Migration as the Run Mode and click Start. You should fix any potential errors encountered in the pre-migration process before performing an actual migration.” the Text Only option is disabled. however. If you select “Users. When you migrate users and groups. If you select “Repository Content. (The Migration Utility updates both the target database and the OpenLDAP database. that you must migrate the objects in the order shown in the wizard. errors may cause the actual migration to stop or remain incomplete. select Test Only as the Run Mode. you may want to backup the target database after you successfully migrate each object type. For example.process without actually moving objects from the source system to the target system. Running the Migration 207 . If the Migration Utility finds any problems. After you complete the pre-migration test and fix all the outstanding errors. Note.) This step is optional As an extra precaution. you could begin by selecting Users. 3 Check to make sure the object migrated correctly and fix any errors. you would select Groups. it reports them in the log files.” and “Repository Content.

Progress Displays information about the progress of the migration such as successes. Displays information messages about the migration. and the number of objects migrated. Note: Oracle recommends that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object. errors. Field Select the Objects to Migrate Run Mode Select one of the following options: ● ● Test Only—Runs a pre-migration process to help identify any migration issues. the number of objects remaining to be migrated. Perform Migration—Runs the actual migration. The objects that are enabled are the objects selected on the Select Objects to Migrate screen earlier in the wizard (see “Defining the Hyperion Reports Administrator” on page 185). warnings. Note: Test Only is disabled for repository content in Hyperion Reports migrations. Status Messages 208 Migrating from Hyperion Reports .Figure 96 Run Migration Table 94 Run Migration Options Description Review the objects selected to migrate.

32. 59. 151. 99. 37. 115 prerequisites. 15 Hyperion Performance Suite migration. 163. 67. 14 filtering content filtering. 66. 33 defining the location of. 185. 141 prerequisites. 75. 206 prerequisites. 15 what happens during migration. 106 D database. 15 G group ids editing properties. 159. 37. 104. 123. 152 content filtering. 66. 156. 32. 117 pre-migration test. 10 H hosts. 34 Hyperion Reports migration. 15 circular references. access. 113. 189 Hyperion Registry Database:type. 22. 171. 145 pre-migration test. 81. 112. 15 general. defining for the source repository. 92. 15 Hyperion Reports. 98. 155. 179 pre-migration test. 68. 14 BrioONE pre-migration test. mapping. 128.B C D F G H J L M O P R S U Index B before migrating Brio Intelligence. 50 prerequisites. 45. 175 prerequisites. 92. 15 Brio Intelligence pre-migration test. 174 Hyperion Analyzer migration. 158. 139. 14 BrioONE. 26. 204 searching for. 99. 126. 74. 58. 14 Brio Portal. 188 Hyperion Reporting and Analysis Repository Database defining information for. 70. 148. 196 Index 209 . 19 pre-migration test. 84 prerequisites. 106 folders. 204 groups provisioning. 70. 139. 10 special symbols in. 191. 14 Brio Portal migration. 132. 127. 191. 195 JDBC URL. 29. 158. 82. 15 C categories. 14 Hyperion Analyzer. 55. 120. 15 J JDBC driver. 97. 30. 45. 182 F file system. 128. 133. 47. 103. 15 Hyperion Performance Suite 8. 26. 123. 171. 25. 185. 164. 152. 15 Hyperion Registry Database:location.

50. 192 defining the location of. 101. 17 source repository defining the database location. 71. selecting for migration. 180 defining the database used. defining the location of. 14 migration. 198 users provisioning. 39. 110. 180 pre-migration Brio Intelligence. 149. 148. 183 210 Index . 108. selecting. 75. 146. 105. 188 SmartCuts.B C D F G H J L M O P R S U L log files. 134. 197 Shared Services:registry type. 15 what happens during migration. 14 provisioning of users and groups. 42. 206 prerequisites. 182 special symbols. 84. 175 Hyperion Reports. 84 Hyperion Analyzer. 206 U user ids editing properties. 60. in users and groups. 60 OnDemand Server. 130. 141. prerequisites. 201 user provisioning. 164. 168. 206 S Shared Services Server. 62. 84. location of installation files. 118. 38. 146. 10 special symbols in. 96. 10 O OCE path. 79. 133. 110. 94 ODS. 21. 115 Brio Portal. 20. 155. what happens during migration. 180 migration utility. 147. 72. 50. 10. 175. 20. 22. 118. 120. general. 76. 193 Reporting and Analysis Repository Server. 136. 141. 121. 174 migration path. 66. running. 115. 104 repository content.pwd. 60 ODS. 145 user/group descriptions and passwords. 29.ini. 13 running the migration. 55. 59 P path. 168. 125. 77. 47. 79. 165. 159. defining the location of. 100. 115. 201 searching for. 136. 23. 15 M mapping hosts. 10 R Reporting and Analysis Repository Database defining information for. 175. 129. 50 BrioONE. 118. 141 Hyperion Performance Suite.

Sign up to vote on this title
UsefulNot useful