You are on page 1of 182

HYPERION REPORTING AND ANALYSIS MIGRATION UTILITY

RELEASE 9.3.1

MIGRATION UTILITY GUIDE

Reporting and Analysis Migration Utility Guide, 9.3.1 Copyright 2002, 2007, Oracle and/or its affiliates. All rights reserved. Authors: Angela Vermeer The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

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 Reporting and Analysis 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Defining Reporting and Analysis Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . 29 Location of Reporting and Analysis Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . 33 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Contents

iii

Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Adding Users/Groups Assigned in Portal to the Native Shared Services Group . . . . . . 41 Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Chapter 3. Migrating from BrioONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 About Migrating from BrioOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Running the Brio Portal Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Defining the Database Used by the OnDemand Server Repository . . . . . . . . . . . . . . . 49 Defining the Location of the OnDemand Server Repository Database . . . . . . . . . . . . . 50 Defining the Location of the OnDemand Server Installation Files . . . . . . . . . . . . . . . . 53 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Defining Target Row Level Security Repository Database Information . . . . . . . . . . . . 56 Defining the Location of the Target Row Level Security Repository Database . . . . . . . 57 Defining Reporting and Analysis Database Information . . . . . . . . . . . . . . . . . . . . . . . 60 Defining the Location of the Reporting and Analysis Database . . . . . . . . . . . . . . . . . . 61 Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . 64 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Defining User/Group Names, Descriptions, and Passwords . . . . . . . . . . . . . . . . . . . . 66 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Chapter 4. Migrating from the Brio Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 About Migrating from the Brio Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Running the Broadcast Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Defining the Database Used by the Broadcast Server Repository . . . . . . . . . . . . . . . . . 79 Defining the Location of the Broadcast Server Repository Database . . . . . . . . . . . . . . 80

iv

Contents

Defining the Broadcast Server Name and the Location of the Broadcast Server Initialization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . 86 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . 87 Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . 90 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Defining Content Filtering for Broadcast Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . . 91 Defining User/Group Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Chapter 5. Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 About Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Defining the Database Used by the Analyzer Repository . . . . . . . . . . . . . . . . . . . . . . . . 106 Defining the Location of the Analyzer Repository Database . . . . . . . . . . . . . . . . . . . . . . 107 Location of Analyzer Repository Database Defined by Host and Name . . . . . . . . . . . 107 Location of Analyzer Repository Database Defined by JDBC Driver and URL . . . . . . 108 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . 110 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . 111 Location of Reporting and Analysis Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . 115 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Contents

Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Adding Users/Groups Assigned in Analyzer to the Native Shared Services Group . . . 123 Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Chapter 6. Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 About Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Defining the Database Used by the Hyperion Performance Suite Repository . . . . . . . . . . 130 Defining the Location of the Hyperion Performance Suite Repository Database . . . . . . . 131 Location of Hyperion Performance Suite Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Identifying Hyperion Performance Suite Groups with Circular References . . . . . . . . . . . 133 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . 136 Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . 137 Location of Reporting and Analysis Repository Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . 141 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Adding Users/Groups Assigned in Hyperion Performance Suite to the Native Shared Services Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

vi

Contents

Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Chapter 7. Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 About Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Defining the Database Used by the Reports Repository . . . . . . . . . . . . . . . . . . . . . . . . . 158 Defining the Location of the Reports Repository Database . . . . . . . . . . . . . . . . . . . . . . . 159 Location of Reports Repository Database Defined by Host and Name . . . . . . . . . . . . 159 Location of Reports Repository Database Defined by JDBC Driver and URL . . . . . . . 160 Defining the Hyperion Reports Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . 164 Defining the Location of the Reporting and Analysis Respository Database . . . . . . . . . . . 165 Location of Reporting and Analysis Repository' Database Defined by Host and Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . . . 167 Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . 169 Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Adding Users/Groups Assigned in Reports to the Native Shared Services Group . . . . 177 Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Contents

vii

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

viii

Contents

1
In This Chapter

Overview and Prerequisites

Overview of the Migration Process................................................................................................. 9 Prerequisites for Using the Reporting and Analysis Migration Utility ..........................................................13 Other Migration Considerations...................................................................................................15

Overview of the Migration Process


Migration involves migrating information from the source system to Oracle's Hyperion Shared Services and Oracle's Hyperion Reporting and Analysis System 9 Repository. 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 systemUsers, groups, roles, repository content, and the database used by one of the following source products:

Brio Portal 7.0.5 or later BrioONE (Brio Portal 7.0.5 or later and OnDemand Server 6.6.4 or later) Brio Intelligence Server (OnDemand Server and Broadcast Server 6.6.4 or later) Hyperion Analyzer 6.5, 7.0.1, 7.2, or 7.2.1 Hyperion Performance Suite 8.x Hyperion Reports 7.0.x or 7.2.x

Shared ServicesDefines both external users and groups in external directory systems, and native users maintained in an Open LDAP database. Reporting and Analysis RepositoryStores information about the mapping between the users and groups in the source system and the users and groups in Shared Services.

Overview of the Migration Process

What Happens During Migration


Migration involves users, groups, roles, and repository content. Review the following topics for information on migrating each of these objects.

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, and the information on this mapping is stored in the Reporting and Analysis Repository. For users and groups in the source system that do not map to existing users and groups in Shared Services, new native users and groups are created in Shared Services. All users and groups that are migrated are provisioned for the application that is registered during product installation and configuration.

Provisioning of Users and Groups During Migration


Provisioning is the process of granting roles and access control to users of Hyperion applications. Based on roles assigned, users can perform specific tasks and access content in various applications. During user provisioning, keep in mind the following:

If a user/group is explicitly assigned roles by the source product (other than default roles), the user/group is explicitly provisioned with these roles subject to the mapping of the roles in the Oracle's Hyperion Reporting and Analysis Migration Utility. For example, if a user is assigned role x in the source product, and this role is mapped to role y in the Reporting and Analysis Repository, the user will be provisioned with role y.

If a user/group is not explicitly assigned any roles (or is only assigned default roles), the user/ group is not explicitly provisioned. All users/groups that are migrated (with the exception of the World group) are assigned as members of the new native group (for example, AnalyzerGroup) regardless of whether they were explicitly assigned roles. The new native group is provisioned for the application and is assigned the default roles. This means that every user/group is granted these roles, and every user/group is at least implicitly provisioned. The World group is not explicitly provisioned. You can provision the World group after migration if desired. When you provision the World group, all users displayed in Shared Services can login. If you want only a subset of the users to be able to login, do not provision the World group.

10

Overview and Prerequisites

To keep the same behavior for users/groups created after migration, add any new user/s groups to the native group (for example, AnalyzerGroup). By doing this, the new users/ groups inherit the same roles and are implicitly provisioned. You only need to explicitly provision new user/groups if you want to assign them additional roles.

Migrating Roles
During migration, pre-configured roles in the source system are mapped to new roles in Shared Services. The mapping determines how users and groups are provisioned. For example, if a user is granted a pre-configured role in the source system, the user will be provisioned with new Reporting and Analysis roles based on this mapping. When you migrate user-defined roles, new roles are created in Shared Services. The following tables correlate legacy roles for Hyperion Analyzer, Hyperion Metrics Builder, Oracle's Hyperion Performance Suite, and Hyperion Reports to Reporting and Analysis and Hyperion roles.
Hyperion Analyzer Role Administrator Reporting and Analysis or Hyperion Role Reporting and Analysis Global Administrator, Directory Manager, 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 Role Administrator

Reporting and Analysis or Hyperion Role Reporting and Analysis Administrator, Directory Manager, Provisioning Manager Explorer Content Manager Content Publisher Schedule Manager Reporting and Analysis Global Administrator, Directory Manager, 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 Job Manager Deprecated Provisioning Manager Explorer Schedule Manager

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 Physical Resource Administrator Related Content Viewer Role Administrator Role Locator Schedule Administrator

12

Overview and Prerequisites

Oracle's Hyperion Performance Suite Role 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 Hyperion Role Reporting and Analysis Administrator Trusted Application Explorer Trusted Application Explorer, Personal Page Editor Directory Manager Explorer Viewer Viewer Favorites Distributor

Hyperion Reports Role Designer Security Administrator System Administrator Viewer

Reporting and Analysis or Hyperion Role Scheduler, Report Designer Reporting and Analysis Global Administrator, Directory Manager, Provisioning Manager Reporting and Analysis Global Administrator, Directory Manager, Provisioning Manager Explorer

Migrating Repository Content


All repository content/metadata is migrated from the source system to the Reporting and Analysis Repository.

Prerequisites for Using the Reporting and Analysis Migration Utility


Prerequisites include tasks that you must complete for the Reporting and Analysis Migration Utility to run properly, regardless of system configuration or content migrated. Before using the Reporting and Analysis Migration Utility on a test or production system, fulfill the prerequisites in Table 1.
Note:

When using the Reporting and Analysis Migration Utility, screen resolutions set to 800x600 or lower are not supported.

Prerequisites for Using the Reporting and Analysis Migration Utility

13

Table 1

Prerequisites for Using the Reporting and Analysis Migration Utility Details

Prerequisite Type General

Have a working Reporting and Analysis installation on the target system. Have access to the old and new Repository databases. Have an administrator user ID and password for the source and target systems. Have user ID, password, and connectivity information for the repository databases. Configure Shared Services for external authentication. For example, if your source system uses external authentication, then you must configure Shared Services with the same external directory services. 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.

Disable the Harvester service. Log onto Oracle's Hyperion Workspace, select Administrator > General, and ensure that Enable Harvesting is not selected.

If your target system is DB2, set the LOCKTIMEOUT parameter to a finite value. To do this, select the Reporting and Analysis Repository database in the DB2 Administration tool; choose database parameters and change the LOCKTIMEOUT parameter value to a finite value (instead of the default NULL, or -1); and restart the database.

For systems using X-Windows on UNIX, start vncserver so that it uses (at a minimum) HiColor. For example, vncserver -depth 15 or vncserver -depth 16.

If your target system is Oracle, set the NLS_LENGTH_SEMANTICS parameter to char.


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. 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.

Brio Intelligence

In addition to the General prerequisites:

Turn off the services on the source system. (The services on the target system should stay running.) For UNIX systems, add the BQ_FONT_PATH to the services.sh file located in the <brio>/BrioPlatform/bin directory and restart the services. 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. For additional information on BQ_FONT_PATH, see Fonts for Unix in the Hyperion Workspace Administrators Guide.

Note: Scheduled jobs are migrated as part of the Broadcast Server migration. If a job is scheduled to run during the time of the migration, it triggers the Event Service and creates faulty job output. If jobs run during migration, there may be some changes to the BRIOJOBS table, such as updating last run date and decreasing the number of remaining times for the job to run, and a migrated 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.

14

Overview and Prerequisites

Prerequisite Type

Details

Complete the Portal migration, including all pre-migration steps, before running the OnDemand Server migration. Ensure that Portal cCategories (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.

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 users first name, a users last name, a users login ID, and a group name that are not allowed in Reporting and Analysis. If the Reporting and Analysis 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.
Table 2

Special Symbols Symbol in Reporting and Analysis _ * [ ]

Symbol in Source System , = + < >

Other Migration Considerations

15

Symbol in Source System ( ) ; \ " #

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

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 Reporting and Analysis Workspace after migration. To ensure that your SmartCuts appear in Oracle's Hyperion Workspace, update all 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 Reporting and Analysis 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

2
In This Chapter

Migrating from Brio Portal

About Migrating from Brio Portal .................................................................................................19 Starting the Migration Utility Wizard..............................................................................................19 Selecting a Migration Path ........................................................................................................20 Entering Logging Details...........................................................................................................20 Defining the Database Used by the Portal Repository..........................................................................22 Defining the Location of the Portal Repository Database ......................................................................23 Identifying Portal Groups with Circular References .............................................................................25 Selecting the Objects to Migrate .................................................................................................26 Defining Reporting and Analysis Database Information........................................................................28 Defining the Location of the Reporting and Analysis Repository Database ..................................................29 Defining the Location of the Shared Services Server ...........................................................................32 Defining User/Group Names, Descriptions and Passwords....................................................................33 Reviewing User Names ............................................................................................................35 Reviewing Group Names ..........................................................................................................38 Mapping Hosts .....................................................................................................................41 Defining Additional Migration Options ...........................................................................................42 Running the Migration .............................................................................................................44

About Migrating from Brio Portal


Use the Brio Portal option in the Reporting and Analysis Migration Utility Wizard to migrate users, groups, roles, and repository content from a Brio Portal 7.0.5 or later installation to Shared Services and the Reporting and Analysis Repository. Before performing the migration, review the information in Chapter 1, Overview and Prerequisites.

Starting the Migration Utility Wizard


To start the Reporting and Analysis Migration Utility Wizard, click migrator.bat (Windows) or
migrator.sh (UNIX) in the bin folder where you installed the Reporting and Analysis Migration Utility. If you installed to the default location, the migrator.bat file is located in:

About Migrating from Brio Portal

19

C:\Hyperion\Migration Utility\bin

If you are using Windows, you can also start the Reporting and Analysis Migration Utility Wizard by choosing Start > Programs > Hyperion > Reporting and Analysis > Utilities and Administration > Migration Utility.

Selecting a Migration Path


Select Brio Portal on the Welcome screen and click Next.
Figure 1 Welcome Screen

Entering Logging Details


Select the log level for messages and specify the directory in which to write the log files. Logging information is important since this is the only place where you can see errors relating to the migration.

20

Migrating from Brio Portal

Figure 2

Logging Details

Table 3

Logging Details Specify the log level by selecting one of the following options:

Log Level

FatalFatal messages cause the migration process to stop. ErrorError messages notify you of potential problems, which may or may not be important for your particular migration scenario. For example, 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. WarnWarning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. InfoInformational messages notify you of structural changes made between the old and new systems, differences encountered between the old and new systems, and potential problems. This level is recommended for most migrations. DebugDebug level messages include all types of messages and produces a very large log file. Debug level messages are numerous because they give a row-by-row account of all migration steps.This level is recommended for testing.

Log Directory

Specify the directory where you want to write the log file. To search for a specific directory, click Browse.

Entering Logging Details

21

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.

Figure 3

Database Used by the Portal Repository

Table 4

Database Type Information Select one of the following databases.


Database Type

SQL Server Oracle DB2 Informix Sybase

Note: If your source system is installed on DB2 version 7.x, use IBM native drivers to connect. If your source system is installed on DB2 version 8.x, you can use data direct drivers. Database Location Select one of the following options to specify the database location:

Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

22

Migrating from Brio Portal

Defining the Location of the Portal Repository Database


Define the connection to the Portal 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). After you enter the requested information, click Test Connection to test the connection to the database.

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), enter the information discussed in Table 5.

Figure 4

Location of Portal Repository Database Defined by Host and Name

Table 5

Host and Name Information Enter the name of the database host. Enter the database port number. Enter the name of the database.

Host Port Database Name

Defining the Location of the Portal Repository Database

23

User ID Password Owner

Enter the database username used to set up a database connection. Enter the password for the database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username.

Location of Portal Repository Database Defined by JDBC Driver and URL


If you specified a JDBC Driver and URL on the previous screen in the wizard (see Defining the Database Used by the Portal Repository on page 22), enter the information discussed in Table 6.
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, use sqljdbc.jar.

Figure 5

Location of Portal Repository Database Defined by JDBC Driver and URL

24

Migrating from Brio Portal

Table 6

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected Sybase, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.sybase.SybaseDriver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility.

JDBC URL

The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the Sybase JDBC URL below,
jdbc:hyperion:sybase://<host>:5000;DatabaseName=<dbname>

remove <host> and <dbname> and replace them with the actual name of your host and database. User ID Password Owner Enter the database username used to set up a database connection. Enter the password for the database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username.

Identifying Portal Groups with Circular References


Search for and remove any existing circular references in Portal groups. Circular references are groups that contain other groups in a cyclical relationship. For example, Group A contains Group B, which contains Group C, which contains Group A.

To search for circular references in Portal groups, click Start.


If the Reporting and Analysis Migration Utility finds any circular references, they appear under Circular References Found. After all circular references are identified, remove the references in the source Portal system before continuing with the migration. It is important to remove circular references in Portal groups since Portal allows for circular references in groups and Shared Services does not.

To remove a circular reference:


1 Select the circular reference under Circular References Found. 2 Select the relationship that contains the circular references under Select a Relationship to Remove
From.

Identifying Portal Groups with Circular References

25

3 Click Remove Relationship and Recheck.


Figure 6 Circular References

Selecting the Objects to Migrate


Select the Portal objects to migrate. To select an object, click the checkbox next to the object. It is recommended 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. You can select individual objects to migrate here or on the final Run Migration screen. The objects selected here determine what Portal migration screens appear next.

26

Migrating from Brio Portal

Figure 7

Portal Objects to Migrate

Table 7

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

Users Groups User Preferences Repository Metadata

Events

Authorization Repository Content

Selecting the Objects to Migrate

27

Defining Reporting and Analysis Database Information


Define which database contains the target Reporting and Analysis Repository and select how to specify the database location.

Figure 8

Database Used by the Reporting and Analysis Repository

Table 8

Database Type Information Select one of the following databases:


Database Type

SQL Server Oracle DB2

Database Location

Select one of the following options to specify the database location:


Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

28

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 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, 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 Database Information on page 28), enter the information discussed in Table 9.

Figure 9

Location of Reporting and Analysis Repository Database Defined by Host and Name

Table 9

Host and Name Information Enter the name of the Reporting and Analysis Repository database host.

Host

Defining the Location of the Reporting and Analysis Repository Database

29

Port

Enter the Reporting and Analysis Repository database port number. 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 password for the Reporting and Analysis Repository database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username. Select this option if you manually copied your source tables to the target database. In most cases, manually copying your source tables to the target database is much quicker than allowing the Reporting and Analysis Migration Utility to copy them over a network. This is because the Reporting and Analysis Migration Utility normally issues multiple commands to 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, however, the Reporting and Analysis Migration Utility issues one command to move all of the rows in the table, 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. 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. 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

Database Name

User ID

Password

Owner

Source tables have been copied to the target database

30

Migrating from Brio Portal

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL
If you specified a JDBC Driver and URL on the previous screen in the wizard (see Defining Reporting and Analysis Database Information on page 28), enter the information discussed in Table 10.
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, use sqljdbc.jar.

Figure 10

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL

Table 10

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous

Defining the Location of the Reporting and Analysis Repository Database

31

screen. For example, if you selected DB2, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.db2.DB2Driver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility. JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the DB2 JDBC URL below,
jdbc:hyperion:db2://<server>: 50000;DatabaseName=<dbname>;PackageName=<packa ge>

remove <server>, <dbname>, and <package> and replace them with the actual names of your server, database, and DB2 package. User ID Enter the database username used to set up a Reporting and Analysis Repository database connection. Enter the password for the Reporting and Analysis Repository database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username. See description in Table 9.

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. After you enter the requested information, click Test Connection to test the connection to the server.

32

Migrating from Brio Portal

Figure 11

Location of Shared Services Server

Table 11

Shared Services Server Information Enter the name of the Shared Services Server host. Enter the Shared Services Server port number. Enter the login ID for the user in Shared Services. The user must have an administrative role in Shared Services. Enter the password for the User ID.

Host Port User ID

Password

Defining User/Group Names, Descriptions and Passwords


Define how to treat user descriptions, group names, passwords, and authentication when creating new users in Shared Services.

Defining User/Group Names, Descriptions and Passwords

33

Figure 12

User/Group Descriptions and Passwords

Table 12

Information on User/Group Descriptions and Passwords Define how to copy the User Descriptions from Portal when creating new native Shared Services users. Select one of the following options:

User Descriptions

Shared Services User DescriptionCopies the Portal User Description fields to the Shared Services User Description fields. Shared Services User First and Last Name FieldsCopies the Portal User First and Last Name fields to the Shared Services User First and Last Name fields. If you select this option:

Specify how the names in the source description fields are separated by selecting Space, Semi-colon, Tab, or Comma. Note that you can select more than one option. If the names in the source description fields have a different delimiter, select Other and specify the delimiter. Specify how the user names appear in Portal by selecting an option for Name Starts With. For example, if the name appears starting with the last name, you would select Last Name. Specify how to add middle names in Shared Services by selecting an option for Add Middle Name to. For example, if a user name consists of more than two names, you can specify whether to add the middle name as part of the first name or as part of the last name.

Group Names

Define how to treat group names when migrating native groups by selecting one of the following options:

34

Migrating from Brio Portal

Same Group Name Migrates the native Portal group name to a native Shared Services group name and keeps the group name the same. Alternate Group NameMigrates the native Portal 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.

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, the Reporting and Analysis 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. Authentication If Portal currently uses external NT authentication to authenticate users, click the checkbox next to Portal Uses External NT Authentication and enter the default NT authentication domain.

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 properties for a user, select a user name and click Properties (see Editing User Name Properties on page 36).

Reviewing User Names

35

Figure 13

User Names

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.

36

Migrating from Brio Portal

The user name properties from both systems (source and target) are displayed. Some properties are read-only and some can be edited. In the above screen, the first and last name fields are automatically entered in the User Management User information.

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 Reporting and Analysis 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 email address first name/last name

If a mapping cannot be made, then during migration, the Reporting and Analysis 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 a Portal 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.

Reviewing User Names

37

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 Portal 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 Portal 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 Shared Services. If you later change a users action to Do Not Migrate and perform another migration, the Reporting and Analysis Migration Utility does not remove the previously-migrated user from Shared Services; instead, you must delete the user directly from 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


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 39).

38

Migrating from Brio Portal

Figure 14

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 or double-click the group name.
The Properties dialog box displays.

Reviewing Group Names

39

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 Shared Services Group section of the dialog box.

Verifying Group Name Mapping


When you run the Reporting and Analysis 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 Reporting and Analysis 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 a Portal 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 Portal 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 Portal to Shared Services, keep in mind the following:

40

Migrating from Brio Portal

The default setting for inactive groups is Do Not Migrate. This setting cannot be changed. If you want to migrate a deactivated group, you must manually activate the group in the source system before performing the migration. 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 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, or click Select All to select all the group names. 2 Click the checkbox next to Add Users/Groups Assigned in Portal to the Native Shared Services Group.
Note:

When you select this option, if a group in Portal 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.

Mapping Hosts
Define the mapping for the Portal hosts and the Reporting and Analysis Repository hosts. For example, you must map each source job factory to a new Reporting and Analysis Repository host.

Mapping Hosts

41

Figure 15

Host Mapping

To map a host, select a Portal Host and a Reporting and Analysis Repository Host and click Map
Hosts. The hosts display in the Mapped Hosts text box.

To remove a mapped pair of hosts, select the hosts in the Mapped Hosts text box and click
Remove Mapped Host.

Defining Additional Migration Options


Select additional Portal options to provide advanced control of the migration process.

42

Migrating from Brio Portal

Figure 16

Additional Migration Options

Table 13

Additional Migration Options Define how to translate the Write access control in Portal by selecting one of the following options:

Authorization

Modify in the Reporting and Analysis RepositorySelect this option to map "Write" or "Write and Execute" to the "Modify" access control. Full Control in the Reporting and Analysis RepositorySelect this option to map "Write" or "Write and Execute" to the Full Control access control. In Portal 7.x, you could delete an object if you had permission to write to the object. The Write permission in 7.x maps to the Modify role in the Reporting and Analysis Repository, which does not allow deletion. As a result, if you want permission to delete an object in the Reporting and Analysis Repository, you must map the version 7.x Write or Write and Execute permissions to the Reporting and Analysis RepositoryFull Control role.

Select Setup job publishing mask group permissions to use job group publishing masks when migrating jobs to the Reporting and Analysis Repository. Publishing masks are permissions that the output gets when it runs in the Reporting and Analysis Repository. Job Group Publishing Masks only apply if you are doing authorization. Repository Content Enter the Source Path and the Target Path for the repository content. Either type in the path or click Browse to select a path. If you plan to migrate Oracle's Hyperion SQR Production Reporting System 9 files, define the version of the files in the Reporting and Analysis Repository. For example, enter Version 8.3 as 83, Version 9.0 as 90, and so on.

Repository Job Factory

Defining Additional Migration Options

43

Note: After you complete the migration, you must re-compile all your SQR Production Reporting jobs.

Running the Migration


The final screen of the Reporting and Analysis Migration Utility Wizard allows you to review the objects selected to migrate, to run a test migration that will help determine any migration issues, and to run the actual migration. It is strongly recommended that you run a pre-migration process before completing an actual migration. During a pre-migration test, the Reporting and Analysis Migration Utility goes through the migration process without actually moving objects from the source system to the target system. If the Reporting and Analysis 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.

To run a pre-migration process, select Test Only as the Run Mode.


After you complete the pre-migration test and fix all the outstanding errors, it is recommended 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. After all the users migrate successfully, you would select Groups.

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 Reporting and Analysis 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 complete the migration, you must re-compile all your SQR Production Reporting jobs.

44

Migrating from Brio Portal

Figure 17

Run Migration

Table 14

Run Migration Options Review the objects selected to migrate. 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 26). Note: It is strongly recommended that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object.

Select the Objects to Migrate

Run Mode

Select one of the following options:


Test OnlyRuns a pre-migration process to help identify any migration issues. Perform MigrationRuns the actual migration.

Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. Unless addressed, errors may cause the actual migration to stop or remain incomplete. Progress Displays information about the progress of the migration such as successes, errors, warnings, the number of objects remaining to be migrated, and the number of objects migrated. Displays information messages about the migration.

Status Messages

Running the Migration

45

46

Migrating from Brio Portal

3
In This Chapter

Migrating from BrioONE

About Migrating from BrioOne ....................................................................................................47 Running the Brio Portal Migration ................................................................................................47 Running the OnDemand Server Migration .......................................................................................48

About Migrating from BrioOne


Use the BrioONE option in the Reporting and Analysis Migration Utility Wizard to migrate users, groups, roles, and repository content from a BrioONE installation to Shared Services and the Reporting and Analysis Repository. BrioONE consists of the following components:

Brio Portal 7.0.5 or later OnDemand Server 6.6.4 or later

When you run a BrioONE migration, you can migrate both Brio Portal information and OnDemand Server information. Checking both options on the Welcome screen directs the Reporting and Analysis Migration Utility to run the Portal steps in the wizard followed directly by the OnDemand Server steps in the wizard. If desired, you can run the Portal and OnDemand Server wizard steps separately; however, you must run the Portal wizard before you run the OnDemand Server wizard. Before performing the migration, review the information in Chapter 1, Overview and Prerequisites.

Running the Brio Portal Migration


To run Brio Portal information following directly by OnDemand Server information, select BrioONE on the Welcome screen (this checks both the Portal and the OnDemand Server options). To run the Brio Portal wizard steps separately, select the Portal option under BrioONE. After you have selected a migration path and entered logging details, running the Brio Portal migration involves:

Defining the Database Used by the Portal Repository

About Migrating from BrioOne

47

Defining the Location of the Portal Repository Database Identifying Portal Groups with Circular References Selecting the Objects to Migrate Defining Reporting and Analysis Database Information Defining the Location of the Reporting and Analysis Repository Database Defining the Location of the Shared Services Server Defining User/Group Names, Descriptions and Passwords Reviewing User Names Reviewing Group Names Mapping Hosts Defining Additional Migration Options Running the Migration

See Chapter 2, Migrating from Brio Portal for detailed information on migrating information from Brio Portal.

Running the OnDemand Server Migration


Before you migrate OnDemand Server information, make sure that you have already migrated Brio Portal 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. If you selected both Portal and OnDemand Server under BrioOne on the Welcome screen, the OnDemand Server wizard screens automatically appear after the Portal wizard screens.

After you have selected a migration path and entered logging details, running the OnDemand Server migration involves:

Defining the Database Used by the OnDemand Server Repository on page 49 Defining the Location of the OnDemand Server Repository Database on page 50 Defining the Location of the OnDemand Server Installation Files on page 53 Selecting the Objects to Migrate on page 54 Defining Target Row Level Security Repository Database Information on page 56 Defining the Location of the Target Row Level Security Repository Database on page 57 Defining Reporting and Analysis Database Information on page 60 Defining the Location of the Reporting and Analysis Database on page 61 Defining the Location of the Reporting and Analysis Repository Server on page 64 Defining the Location of the Shared Services Server on page 65

48

Migrating from BrioONE

Defining User/Group Names, Descriptions, and Passwords on page 66 Reviewing User Names on page 67 Reviewing Group Names on page 70 Running the Migration on page 74

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.

Figure 18

Database Used by the OnDemand Server Repository

Table 15

Database Type Information Select one of the following databases.


Database Type

SQL Server Oracle DB2 Informix

Running the OnDemand Server Migration

49

Sybase Redbrick

Note: If your source system is installed on DB2 version 7.x, use IBM native drivers to connect. If your source system is installed on DB2 version 8.x, you can use data direct drivers. Database Location Select one of the following options to specify the database location:

Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

Defining the Location of the OnDemand Server Repository Database


Define the connection to the OnDemand Server 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). After you enter the requested information, click Test Connection to test the connection to the database.

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 49), enter the information discussed in Table 16.

50

Migrating from BrioONE

Figure 19

Location of OnDemand Server Repository Database Defined by Host and Name

Table 16

Host and Name Information Enter the name of the database host. Enter the database port number. Enter the name of the database. Enter the database username used to set up a database connection. Enter the password for the database. Enter the table owner/schema name. In most cases, the owner is the same as the database username.

Host Port Database Name User ID Password Owner

Location of OnDemand Server Repository Database Defined by JDBC Driver and URL
If you specified a JDBC Driver and URL on the previous screen in the wizard (see Defining the Database Used by the OnDemand Server Repository on page 49), enter the information discussed in Table 17.

Running the OnDemand Server Migration

51

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, use sqljdbc.jar.

Figure 20

Location of OnDemand Server Repository Database Defined by JDBC Driver and URL

Table 17

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected DB2, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.db2.DB2Driver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility.

52

Migrating from BrioONE

JDBC URL

The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the DB2 JDBC URL below,
jdbc:hyperion:db2://<server>: 50000;DatabaseName=<dbname>;PackageName=<package>

remove <server>, <dbname>, and <package> and replace them with the actual names of your server, database, and DB2 package. User ID Password Owner Enter the database username used to set up an OnDemand Server database connection. Enter the password for the database. Enter the table owner/schema name. In most cases, the owner is the same as the database username.

Defining the Location of the OnDemand Server Installation Files


Enter the location of the ODS.ini file and the ODS.pwd file.

Figure 21

OnDemand Server Installation Files

Running the OnDemand Server Migration

53

Table 18

OnDemand Server Installation Files Enter the path for the location of your ODS.ini file. This file is usually found under:
<drive>:/Program Files/Brio/Brio Intelligence Server/Server

ODS.ini File

ODS.pwd File

Enter the path for the location of your ODS.pwd file. 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 Reporting and Analysis Migration Utility from a machine other than the source system. If running on a machine other than the source, enter the following information:

Mapped OCE PathMap the OCE directory on the installation machine to the OCE directory on the source system. For example, map Z:\ on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \Program\Open Catalog Extensions on the source system.

Mapped BQY PathMap the BQY directory on the installation machine to the BQY directory on the source system. For example, map Z:\ on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \Program\Documents on the source system.

Selecting the Objects to Migrate


Select the OnDemand Server objects to migrate. To select an object, click the checkbox next to the object. It is recommended 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. You can select individual objects to migrate here or on the final Run Migration screen. The objects selected here determine what OnDemand Server migration screens appear next.

54

Migrating from BrioONE

Figure 22

OnDemand Server Objects to Migrate

Table 19

OnDemand Server Objects to Migrate Account owners identified by a user ID and user name. To select a User Insight Privilege, click the checkbox and select an option from the list that appears. User Insight Privileges include:

Users

Insight Quickview Freeview

Groups

Named collections of users. When you migrate groups, you must enter a Parent Group. The default parent group is / BrioODSGroup.

Folders

Items are organized into folders. Folders are similar to the directories or folders of your operating system, and are arranged in a hierarchical structure. A folder can contain subfolders, items, or both. Note: If a folder in the repository contains more than 80 to 90 items, the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. To make the folder accessible, add -DPerformance.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices.bat script and restart Common Services.

OCE Files

Files that encapsulate and store connection information used to connect Hyperion applications to a database. OCE files specify the database API (ODBC, SQL*Net, etc.),

Running the OnDemand Server Migration

55

database software, the network address of the database server, and your database user name. Once created, a user can specify the OCE file and database password and logon. An OCE file is required for a Hyperion Intelligence document to use a database. The file extension is .oce. When you migrate OCE files, you must enter the OCE folder on Target. The default is / Open Catalog Extensions. BQY Documents Files created by Hyperion Intelligence and published into the Repository as files or as jobs. To view BQY documents in the Shared Services thin-client, click the checkbox next to Enable Thin Client Version. 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. For example, managers need payroll information on their direct reports. Managers do not need to know payroll information for other departments within the organization. When you select this object, the next page in the Reporting and Analysis Migration Utility Wizard prompts you to configure the target row level security repository.

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.
Note:

This screen appears only if you selected Row Level Security Data on the Objects to Migrate wizard screen.

56

Migrating from BrioONE

Figure 23

Database Used by the Target Row Level Security Repository

Table 20

Database Type Information Select one of the following database drivers:


Database Type

SQL Server Oracle DB2

Database Location

Select one of the following options to specify the database location:


Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

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. 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, click Test Connection to test the connection to the database.

Running the OnDemand Server Migration

57

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 Database Information on page 60), enter the information discussed in Table 21.

Figure 24

Location of Row Level Security Repository Database Defined by Host and Name

Table 21

Host and Name Information Enter the name of the Row Level Security Repository database host. Enter theRow Level Security Repository database port number. Enter the name of the Row Level Security Repository database. Enter the username used to set up a Row Level Security Repository database connection. Enter the password for the Row Level Security Repository database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username.

Host Port Database Name User ID Password Owner

58

Migrating from BrioONE

Location of Target Row Level Security Database Defined by JDBC Driver and URL
If you specified a JDBC Driver and URL on the previous screen in the wizard (see Defining Reporting and Analysis Database Information on page 60), enter the information discussed in Table 22.
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, use sqljdbc.jar.

Figure 25

Location of Row Level Security Repository Defined by JDBC Driver and URL

Table 22

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected SQL Server, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.sqlserver.SQLServerDriver.

Running the OnDemand Server Migration

59

Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility. JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the SQL Server JDBC URL below,
jdbc:hyperion:SQLSERVER://<host>: 1433;DatabaseName=<dbname>;SelectMethod=cursor

remove <host> and <dbname> replace them with the actual host and database names. User ID Enter the database username used to set up a Row Level Security Repository database connection. Enter the password for the Row Level Security Repository database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username.

Password Owner

Defining Reporting and Analysis Database Information


Define which database contains the target Reporting and Analysis Repository and select how to specify the database location.

60

Migrating from BrioONE

Figure 26

Database Used by the Reporting and Analysis Repository

Table 23

Database Type Information Select one of the following databases:


Database Type

SQL Server Oracle DB2

Database Location

Select one of the following options to specify the database location:


Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

Defining the Location of the Reporting and Analysis Database


Define the location of theReporting and Analysis Repository database on the target system. 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, click Test Connection to test the connection to the database.

Running the OnDemand Server Migration

61

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 Database Information on page 60), enter the information discussed in Table 24.

Figure 27

Location of Reporting and Analysis Repository Database Defined by Host and Name

Table 24

Host and Name Information Enter the name of the Reporting and Analysis Repository database host. Enter the Reporting and Analysis Repository database port number. Enter the name of the Reporting and Analysis Repository database. Enter the username used to set up a Reporting and Analysis Repository database connection. Enter the password for the Reporting and Analysis Repository database.

Host Port Database Name User ID Password

62

Migrating from BrioONE

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL
If you specified a JDBC Driver and URL on the previous screen in the wizard (see Defining Reporting and Analysis Database Information on page 60), enter the information discussed in Table 25.
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, use sqljdbc.jar.

Figure 28

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL

Table 25

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected DB2, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.db2.DB2Driver.

Running the OnDemand Server Migration

63

Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility. JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the DB2 JDBC URL below,
jdbc:hyperion:db2://<server>: 50000;DatabaseName=<dbname>;PackageName=<package>

remove <server>, <dbname>, and <package> and replace them with the actual names of your server, database, and DB2 package. User ID Enter the database username used to set up a Reporting and Analysis Repository database connection. Enter the password for the Reporting and Analysis Repository database.

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. After you enter the requested information, click Test Connection to test the connection to the server.

64

Migrating from BrioONE

Figure 29

Location of Target Reporting and Analysis Repository Server

Table 26

Reporting and Analysis Repository Server Information Enter the name of the Reporting and Analysis Repository Server host. Enter the Reporting and Analysis Repository Server port number. Enter the user ID of a user with Global Administrator, Directory Manager, and Provisioning Manager roles. Enter the password for the user ID.

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. After you enter the requested information, click Test Connection to test the connection to the server.

Running the OnDemand Server Migration

65

Figure 30

Location of Target Shared Services Server

Table 27

Shared Services Server Information Enter the name of the Shared Services Server host. Enter the Shared Services Server port number. Enter the login ID for the user in Shared Services. The user must have an administrative role in Shared Services. Enter the password for the User ID.

Host Port User ID

Password

Defining User/Group Names, Descriptions, and Passwords


Define how to treat group names and passwords when creating new users in the Shared Services Server.

66

Migrating from BrioONE

Figure 31

User/Group Descriptions and Passwords

Table 28

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

Group Names

Same Group NameMigrates the native Intelligence group name to a native Shared Services group name and keeps the group name the same. Alternate Group NameMigrates 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.

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 Reporting and Analysis 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.
Running the OnDemand Server Migration

67

Most of the properties for each user name display next to the user name. For a complete list of properties for a user, select a user name and click Properties (see Editing User Name Properties on page 68).

Figure 32

User Names

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.

68

Migrating from BrioONE

The user ID 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 Reporting and Analysis 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 email address first name/last name

If a mapping cannot be made, then during migration, the Reporting and Analysis 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:

Running the OnDemand Server Migration

69

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 users action to Do Not Migrate and perform another migration, the Reporting and Analysis 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.

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 properties for a group, select a group name and click Properties (see Editing Group Name Properties on page 71).

70

Migrating from BrioONE

Figure 33

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.

Running the OnDemand Server Migration

71

The group names 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.
Note:

When you select this option, if a group in the source system 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.

Verifying Group Name Mapping


When you run the Reporting and Analysis 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 Reporting and Analysis 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 Intelligence 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.

72

Migrating from BrioONE

Select the group and click the checkbox next to Migrate Group Name from Intelligence 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 Intelligence to Shared Services, keep in mind the following:

The default setting for inactive groups is Do Not Migrate. This setting cannot be changed. To migrate a deactivated group, you must manually activate the group in the source system before performing the migration. 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 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, or click Select All to select all the group names. 2 Click the checkbox next to Add Users/Groups Assigned in Intelligence to the Native Shared Services
Group.
Note:

When you select this option, if a group in Intelligence 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.

Running the OnDemand Server Migration

73

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 Reporting and Analysis Migration Utility Wizard allows you to review the objects selected to migrate, to run a test migration that will help determine any migration issues, 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 Reporting and Analysis Migration Utility goes through the migration process without actually moving objects from the source system to the target system. If the Reporting and Analysis Migration Utility finds any problems, it reports them in the log files. You should you 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.

To run a pre-migration process, select Test Only as the Run Mode.


After you complete the pre-migration test and fix all the outstanding errors, it is recommended 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. After all the users migrated successfully, you would select Groups.

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 Reporting and Analysis Migration Utility updates both the target database and the OpenLDAP database.)

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

74

Migrating from BrioONE

Figure 34

Run Migration

Table 29

Run Migration Options Review the objects selected to migrate. 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 54). Note: It is recommended that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object.

Select the Objects to Migrate

Run Mode

Select one of the following options:


Test OnlyRuns a pre-migration process to help identify any migration issues. Perform MigrationRuns the actual migration.

Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. Unless addressed, errors may cause the actual migration to stop or remain incomplete. Progress Displays information about the progress of the migration such as successes, errors, warnings, the number of objects remaining to be migrated, and the number of objects migrated. Displays information messages about the migration.

Status Messages

Running the OnDemand Server Migration

75

76

Migrating from BrioONE

4
In This Chapter

Migrating from the Brio Intelligence Server

About Migrating from the Brio Intelligence Server ..............................................................................77 Running the OnDemand Server Migration .......................................................................................77 Running the Broadcast Server Migration.........................................................................................78

About Migrating from the Brio Intelligence Server


Use the Brio Intelligence Server option in the Reporting and Analysis Migration Utility Wizard to migrate users, groups, roles, and repository content from a Brio Intelligence Server installation to Shared Services and the Reporting and Analysis Repository. The Intelligence Server consists of the following components:

OnDemand Server 6.6.4 or later Broadcast Server 6.6.4 or later

When you run a Brio Intelligence Server migration, you can migrate both OnDemand Server information and Broadcast Server information. Checking both options directs the Reporting and Analysis Migration Utility to run the OnDemand Server steps in the wizard followed directly by the Broadcast Server steps in the wizard. If desired, you can run the OnDemand Server and Broadcast Server wizard steps separately; however, you must run the OnDemand Server wizard steps before you run the Broadcast Server wizard steps. Before performing the migration, review the information in Chapter 1, Overview and Prerequisites.

Running the OnDemand Server Migration


To run OnDemand Server information following directly by Broadcast Server information, select Brio Intelligence Server on the Welcome screen (this checks both the OnDemand Server and the Broadcast Server options). 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, running the OnDemand Server migration involves:

Defining the Database Used by the OnDemand Server Repository

About Migrating from the Brio Intelligence Server

77

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 Reporting and Analysis Database Information Defining the Location of the Reporting and Analysis Database Defining the Location of the Reporting and Analysis Repository Server Defining the Location of the Shared Services Server Defining User/Group Names, Descriptions, and Passwords Reviewing User Names Reviewing Group Names Running the Migration

See Running the OnDemand Server Migration on page 48 for detailed information on migrating information from the OnDemand Server.

Running the Broadcast Server Migration


Before you migrate Broadcast Server information, make sure that you have already migrated OnDemand Server information.

If you already ran the OnDemand Server migration and exited from the wizard, you can start the Broadcast Server migration by checking the Broadcast Server option under Brio Intelligence Server. If you selected both OnDemand Server and Broadcast Server under Brio Intelligence Server on the Welcome screen, the Broadcast Server wizard screens automatically appear after the OnDemand Server wizard screens.

After you have selected a migration path and entered logging details, running the Broadcast Server migration involves:

Defining the Database Used by the Broadcast Server Repository on page 79 Defining the Location of the Broadcast Server Repository Database on page 80 Defining the Broadcast Server Name and the Location of the Broadcast Server Initialization File on page 83 Selecting the Objects to Migrate on page 84 Defining Reporting and Analysis Repository Database Information on page 86 Defining the Location of the Reporting and Analysis Repository Database on page 87 Defining the Location of the Shared Services Server on page 91 Defining User/Group Descriptions and Passwords on page 93

78

Migrating from the Brio Intelligence Server

Reviewing User Names on page 94 Reviewing Group Names on page 97 Running the Migration on page 100

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

Table 30

Database Type Information Select one of the following databases.


Database Type

SQL Server Oracle DB2 Informix Sybase Redbrick

Running the Broadcast Server Migration

79

Note: If your source system is installed on DB2 version 7.x, use IBM native drivers to connect. If your source system is installed on DB2 version 8.x, you can use data direct drivers. Database Location Select one of the following options to specify the database location:

Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

Defining the Location of the Broadcast Server Repository Database


Define the connection to the Broadcast Server 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). After you enter the requested information, click Test Connection to test the connection to the database.

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 79), enter the information discussed in Table 31.

80

Migrating from the Brio Intelligence Server

Figure 36

Location of Broadcast Server Repository Database Defined by Host and Name

Table 31

Host and Name Information Enter the name of the database host. Enter the database port number. Enter the name of the database. Enter the database username used to set up a database connection. Enter the password for the database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username.

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 79), enter the information discussed in Table 33.

Running the Broadcast Server Migration

81

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, use sqljdbc.jar.

Figure 37

Location of Broadcast Server Repository Database Defined by JDBC Driver and URL

Table 32

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected DB2, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.db2.DB2Driver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility.

JDBC URL

The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the DB2 JDBC URL below,

82

Migrating from the Brio Intelligence Server

jdbc:hyperion:db2://<server>: 50000;DatabaseName=<dbname>;PackageName=<package>

remove <server>, <dbname>, and <package> and replace them with the actual names of your server, database, and DB2 package. User ID Password Owner Enter the database username for a Broadcast Server Repository database connection. Enter the password for the Broadcast Server Repository database. Optional: Enter the table owner/schema name. In most cases, the owner is the same as the database username.

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.ini).

Figure 38

Broadcast Server Configuration

Table 33

Broadcast Server Configuration Information Enter the path for the location of the BQServ1.ini file (the ini file for the Broadcast Server). Either type in the path to

BQServ1.ini

Running the Broadcast Server Migration

83

the file, or click Browse to search for the file. This file is usually found under:
<drive>:/winnt/BQServ1.ini

BCS Server Name

Enter the name of the Broadcast Server. If you do not know the name, you can find it in the Broadcast Server Administrator utility. Select this option if you are running the Reporting and Analysis Migration Utility from a machine other than the source system. If you select this option, enter the mapped job storage path and enter the following information:

Migration Utility is Not Running on the Broadcast Server

Mapped OCE PathMap the OCE directory on the installation machine to the OCE directory on the source system. For example, map Z:\ on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \Program\Open Catalog Extensions on the source system.

Mapped Job Storage PathMap the job storage directory on the installation machine to the job storage directory on the source system. For example, map Z:\on the installation machine to C: \Program Files\Brio\Brio Intelligence Server \BCS_Jobs on the source system.

Selecting the Objects to Migrate


Select the Broadcast Server objects to migrate. To select an object, click the checkbox next to the object. It is recommended 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. You can select individual objects to migrate here or on the final Run Migration screen. The objects selected here determine what Broadcast Server migration screens appear next.

84

Migrating from the Brio Intelligence Server

Figure 39

Broadcast Server Objects to Migrate

Table 34

Broadcast Server Objects to Migrate Account owners identified by a user ID, user name, and password. A named collection of users. Calendars used to schedule jobs in the Broadcast Server. Events in the Broadcast Server. Printer path definitions in the Broadcast Server. Path definitions in the Broadcast Server. Note: If you have Broadcast Server output directories names (paths) that differ only in case (for example SAMPLE, Sample, and sample), only the first path is migrated.

Users Groups Calendar Events Printer Paths Paths

OCE Files

Files that encapsulate and store connection information used to connect Hyperion applications to a database. OCE files specify the database API (ODBC, SQL*Net, etc.), database software, the network address of the database server, and your database user name. Once created, a user can specify the OCE file and database password and logon. An OCE file is required for a Hyperion Intelligence document to use a database. The file extension is .oce. When you migrate OCE files, you must enter the OCE folder on Target. The default is /Open Catalog Extensions.

Running the Broadcast Server Migration

85

BQY Jobs

Files created by Hyperion Intelligence and published into the Repository as files or as jobs. Enter the job category on target and click the checkbox to run the job in the background. If you leave the Job Category on Target field empty, jobs are migrated to the root. Note: Select Filter Content to filter BQY job content upon migration. You enter the criteria for filtering on the Content Filter screen that appears later on in the wizard.

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 40

Database Used by the Reporting and Analysis Repository

Table 35

Database Type Information Select one of the following databases:


Database Type

SQL Server Oracle DB2

Database Location

Select one of the following options to specify the database location:

86

Migrating from the Brio Intelligence Server

Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

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 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, 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 86), enter the information discussed in Table 36.

Figure 41

Location of Reporting and Analysis Repository Database Defined by Host and Name

Running the Broadcast Server Migration

87

Table 36

Host and Name Information Enter the name of the Reporting and Analysis Repository database host. Enter the Reporting and Analysis Repository database port number. 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 password for the Reporting and Analysis Repository database.

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 86), enter the information discussed in Table 37.
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, use sqljdbc.jar.

88

Migrating from the Brio Intelligence Server

Figure 42

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL

Table 37

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected DB2, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.db2.DB2Driver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility.

JDBC URL

The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the DB2 JDBC URL below,
jdbc:hyperion:db2://<server>: 50000;DatabaseName=<dbname>;PackageName=<package>

remove <server>, <dbname>, and <package> and replace them with the actual names of your server, database, and DB2 package.

Running the Broadcast Server Migration

89

User ID

Enter the database username used to set up a Reporting and Analysis Repository database connection. Enter the password for the Reporting and Analysis Repositorydatabase.

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. After you enter the requested information, click Test Connection to test the connection to the server.

Figure 43

Location of Target Reporting and Analysis Repository Server

Table 38

Reporting and Analysis Repository Server Information Enter the name of the Reporting and Analysis Repository Server host. Enter the Reporting and Analysis Repository Server port number. Enter the username of a user with Global Administrator, Directory Manager, and Provisioning Manager roles. Enter the password for the User ID.

Host Port User ID

Password

90

Migrating from the Brio Intelligence Server

Defining the Location of the Shared Services Server


Define the location of the Shared Services Server on the target system. After you enter the requested information, click Test Connection to test the connection to the server.

Figure 44

Location of Target Shared Services Server

Table 39

Shared Services Server Information Enter the name of the Shared Services Server host. Enter the Shared Services Server port number. Enter the login ID for the user in Shared Services. Enter the password for the User ID.

Host Port User ID Password

Defining Content Filtering for Broadcast Server Jobs


Content filtering involves selectively moving content to different folders in the Reporting and Analysis target system. When you use content filtering, you can map Broadcast Server jobs to multiple folders in the target system during a single migration run. You can map Broadcast Server jobs to existing or non-existing folders. When you map jobs to folders that do not currently exist in the target system, the folders are created during migration.
Running the Broadcast Server Migration

91

The Content Filtering screen displays each content item with its location, owner, type, and migration action. Use this screen to verify the location of content items, view or change the mapping, and set the migration action for each item.

Figure 45

Content Filtering

Searching for Content Items


To search for a content item:
1 Click Search. 2 Define how to conduct the search in the Search dialog box and click Search again.
The content items that meet the search criteria display. After you search for a content item, you can display all the content items again by clicking Show All.

Mapping Content Items


To change mapping information:
1 Select the desired BCS jobs(s). 2 Click Map to and select a folder in the Browse Target File System dialog box.

92

Migrating from the Brio Intelligence Server

Setting the Migration Action


By default, the migration action for each content item is set to Migrate.

To change the migration action, select the content item and select or clear the checkbox next to
Do not migrate.

To set the migration action for more than one content item, press [Shift] and select the desired
content items, or click Select All to select all the content items.

Saving Content Filtering Changes to an External File


To save content filtering changes to an external file, click Save.
Clicking Save is optional. You can successfully run a migration without saving content filtering settings to an external file. If you do decide to save settings to an external file, however, you can load the file if you close and then re-open the Reporting and Analysis Migration Utility. You can also make changes in the external file and load it into the Reporting and Analysis Migration Utility.

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.

Running the Broadcast Server Migration

93

Figure 46

User/Group Descriptions and Passwords

Table 40

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

Group Names

Same Group NameMigrates the native Intelligence group name to a native Shared Services group name and keeps the group names the same. Alternate Group NameMigrates 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.

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 Reporting and Analysis 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.
94
Migrating from the Brio Intelligence Server

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 95).

Figure 47

User Names

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.

Running the Broadcast Server Migration

95

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 Reporting and Analysis 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 email address first name/last name

If a mapping cannot be made, then during migration, the Reporting and Analysis 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:

96

Migrating from the Brio Intelligence Server

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 users action to Do Not Migrate and perform another migration, the Reporting and Analysis 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.

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 properties for a group, select a group name and click Properties (see Editing Group Name Properties on page 98).

Running the Broadcast Server Migration

97

Figure 48

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.

98

Migrating from the Brio Intelligence Server

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 Reporting and Analysis Migration Utility, it queries the source system for groups and attempts to automatically map them to existing Shared Services roups based on the group name. If a mapping cannot be made, then during migration, the Reporting and Analysis 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 Intelligence group name to a different Shared Services roup name, you would select the group name, click Properties, and change the Shared Services roup 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 Intelligence 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 Intelligence to Shared Services, keep in mind the following:

Running the Broadcast Server Migration

99

The default setting for inactive groups is Do Not Migrate. This setting cannot be changed. To migrate a deactivated group, you must manually activate the group in the source system before performing the migration. 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 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, or click Select All to select all the group names. 2 Click the checkbox next to Add Users/Groups Assigned in Intelligence to the Native Shared Services
Group.
Note:

When you select this option, if a group in Intelligence 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 Reporting and Analysis Migration Utility Wizard allows you to review the objects selected to migrate, to run a test migration that will help determine any migration issues, and to run the actual migration.

100 Migrating from the Brio Intelligence Server

Hyperion strongly recommends that you run a pre-migration process before completing an actual migration. During a pre-migration test, the Reporting and Analysis Migration Utility goes through the migration process without actually moving objects from the source system to the target system. If the Reporting and Analysis 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.

To run a pre-migration process, select Test Only as the Run Mode.


After you complete the pre-migration test and fix all the outstanding errors, it is recommended 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. After all the users migrated successfully, you would select Groups.

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 Reporting and Analysis Migration Utility updates both the target database and the OpenLDAP database.)

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

Running the Broadcast Server Migration 101

Figure 49

Run Migration

Table 41

Run Migration Options Review the objects selected to migrate. 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 84). Note: It is recommended that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object.

Select the Objects to Migrate

Run Mode

Select one of the following options:


Test OnlyRuns a pre-migration process to help identify any migration issues. Perform MigrationRuns the actual migration.

Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. Unless addressed, errors may cause the actual migration to stop or remain incomplete. Progress Displays information about the progress of the migration such as successes, errors, warnings, the number of objects remaining to be migrated, and the number of objects migrated. Displays information messages about the migration.

Status Messages

102 Migrating from the Brio Intelligence Server

5
In This Chapter

Migrating from Hyperion Analyzer

About Migrating from Hyperion Analyzer ....................................................................................... 103 Starting the Migration Utility Wizard............................................................................................ 103 Selecting a Migration Path ...................................................................................................... 104 Entering Logging Details......................................................................................................... 104 Defining the Database Used by the Analyzer Repository..................................................................... 106 Defining the Location of the Analyzer Repository Database ................................................................. 107 Selecting the Objects to Migrate ............................................................................................... 109 Defining Reporting and Analysis Repository Database Information ......................................................... 110 Defining the Location of the Reporting and Analysis Repository Database ................................................ 111 Defining the Location of the Shared Services Server ......................................................................... 114 Defining User/Group Names, Descriptions and Passwords.................................................................. 115 Reviewing User Names .......................................................................................................... 117 Reviewing Group Names ........................................................................................................ 120 Running the Migration ........................................................................................................... 123

About Migrating from Hyperion Analyzer


Use the Hyperion Analyzer option in the Reporting and Analysis Migration Utility Wizard to migrate users, groups, roles, and repository content from a Hyperion Analyzer 6.5, 7.0.1, 7.2, or 7.2.1 installation to Shared Services and the Reporting and Analysis Repository. Before performing the migration, review the information in Chapter 1, Overview and Prerequisites.

Starting the Migration Utility Wizard


To start the Reporting and Analysis Migration Utility Wizard, click migrator.bat (Windows) or
migrator.sh (UNIX) in the bin folder where you installed the Reporting and Analysis Migration Utility. If you installed to the default location, the migrator.bat file is located in:
C:\Hyperion\Migration Utility\bin

About Migrating from Hyperion Analyzer 103

If you are using Windows, you can also start the Reporting and Analysis Migration Utility Wizard by choosing Start > Programs > Hyperion > Reporting and Analysis > Utilities and Administration > Migration Utility.

Selecting a Migration Path


Select Hyperion Analyzer on the Welcome screen and click Next.
Figure 50 Welcome Screen

Entering Logging Details


Select the log level for messages and specify the directory in which to write the log files. Logging information is important since this is the only place where you can see errors relating to the migration.

104 Migrating from Hyperion Analyzer

Figure 51

Logging Details

Table 42

Logging Details Specify the log level by selecting one of the following options:

Log Level

FatalFatal messages cause the migration process to stop. ErrorError messages notify you of potential problems, which may or may not be important for your particular migration scenario. For example, 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. WarnWarning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. InfoInformational messages notify you of structural changes made between the old and new systems, differences encountered between the old and new systems, and potential problems. This level is recommended level for most migrations. DebugDebug level messages include all types of messages and produces a very large log file. Debug level messages are numerous because they give a row-by-row account of all migration steps. This level is recommended level for testing.

Log Directory

Specify the directory where you want to write the log file. To search for a specific directory, click Browse.

Entering Logging Details 105

Defining the Database Used by the Analyzer Repository


Define which database contains the Analyzer source repository and select how to specify the database location.

Figure 52

Database Used by the Analyzer Repository

Table 43

Database Type Information Select one of the following databases.


Database Type

SQL Server Oracle DB2 MySQL

Note: If your source system is installed on DB2 version 7.x, use IBM native drivers to connect. If your source system is installed on DB2 version 8.x, you can use data direct drivers. Database Location Select one of the following options to specify the database location:

Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

106 Migrating from Hyperion Analyzer

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). After you enter the requested information, click Test Connection to test the connection to the database.

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 106), enter the information discussed in Table 44.

Figure 53

Location of Analyzer Repository Database Defined by Host and Name

Table 44

Host and Name Information Enter the name of the database host. Enter the database port number. Enter the name of the database.

Host Port Database Name

Defining the Location of the Analyzer Repository Database 107

User ID Password

Enter the database username used to set up a database connection. Enter the password for the database.

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 106), enter the information discussed in Table 45.
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, use sqljdbc.jar.

Figure 54

Location of Analyzer Repository Database Defined by JDBC Driver and URL

Table 45

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path.

Native JDBC Driver Path

108 Migrating from Hyperion Analyzer

Note: You do not need to enter a native JDBC driver path for DataDirect drivers. JDBC Driver The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected SQL Server, the Reporting and Analysis Migration Utility would enter
hyperion.jdbc.sqlserver.SQLServerDriver.

Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility. JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the SQL Server JDBC URL below,
jdbc:hyperion:SQLSERVER://<host>: 1433;DatabaseName=<dbname>;SelectMethod=cursor

remove <host> and <dbname> and replace them with the actual name of your host and database. User ID Password Enter the database username used to set up a database connection. Enter the password for the database.

Selecting the Objects to Migrate


Select the Analyzer objects to migrate. To select an object, click the checkbox next to the object. It is recommended 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. You can select individual objects to migrate here or on the final Run Migration screen. The objects selected here determine what Analyzer migration screens appear next.

Selecting the Objects to Migrate 109

Figure 55

Hyperion Analyzer Objects to Migrate

Table 46

Hyperion Analyzer Objects to Migrate UsersAccount owners identified by a user ID and user name. GroupsNamed collections of users.

Users and Groups

Repository Content

The content of the system, namely: folders, files, jobs, URLs, and shortcuts, and their metadata (properties). The content resides in the repository, which consists of files in the native file system and metadata for each object in a database in a Relational Database Management System (RDBMS). Repository content is the largest object to migrate. Note: If a folder in the repository contains more than 80 to 90 items, the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. To make the folder accessible, add -DPerformance.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices.bat script and restart Common Services.

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.

110 Migrating from Hyperion Analyzer

Figure 56

Database Used by the Reporting and Analysis Repository

Table 47

Database Type Information Select one of the following database drivers:


Database Type

SQL Server Oracle DB2

Database Location

Select one of the following options to specify the database location:


Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

Defining the Location of the Reporting and Analysis Repository Database


Define the location of theReporting and Analysis Repository database on the target system. 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, click Test Connection to test the connection to the database.
Defining the Location of the Reporting and Analysis Repository Database 111

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 110), enter the information discussed in Table 48.

Figure 57

Location of Reporting and Analysis Repository Database Defined by Host and Name

Table 48

Host and Name Information Enter the name of the Reporting and Analysis Repository database host. Enter the Reporting and Analysis Repository database port number. 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 password for the Reporting and Analysis Repository database.

Host Port Database Name User ID

Password

112 Migrating from Hyperion Analyzer

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 110), enter the information discussed in Table 49.
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, use sqljdbc.jar.

Figure 58

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL

Table 49

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected SQL Server,

Defining the Location of the Reporting and Analysis Repository Database 113

the Reporting and Analysis Migration Utility would enter


hyperion.jdbc.sqlserver.SQLServerDriver.

Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility. JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the SQL Server JDBC URL below,
jdbc:hyperion:SQLSERVER://<host>: 1433;DatabaseName=<dbname>;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 Reporting and Analysis Repository database connection. Enter the password for the Reporting and Analysis Repository. database.

Password

Defining the Location of the Shared Services Server


Define the location of the Shared Services Server on the target system. After you enter the requested information, click Test Connection to test the connection to the server.

114 Migrating from Hyperion Analyzer

Figure 59

Location of Shared Services Server

Table 50

Shared Services Server Information Enter the name of the Shared Services Server host. Enter the Shared Services Server port number. Enter the login ID for the user in Shared Services. The user must have an administrative role in Shared Services. Enter the password for the User ID.

Host Port User ID

Password

Defining User/Group Names, Descriptions and Passwords


Define how to treat user descriptions, group names, group descriptions, and passwords when creating new users in Shared Services.

Defining User/Group Names, Descriptions and Passwords 115

Figure 60

User/Group Descriptions and Passwords

Table 51

Information on User/Group Descriptions and Passwords Define how to copy the User Descriptions from Analyzer when creating new native Shared Services users. Select one of the following options:

User Descriptions

Shared Services User DescriptionCopies the Analyzer User Description fields to the Shared Services User Description fields. Shared Services User First and Last Name FieldsCopies the Analyzer User First and Last Name fields to the Shared Services User First and Last Name fields. 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, or Comma. Note that you can select more than one option. If the names in the source description fields have a different delimiter, click the checkbox next to Other and specify the delimiter. Specify how the user names appear in Analyzer by selecting an option for Name Starts With. For example, if the name appears starting with the last name, you would click the checkbox next to Last Name. Specify how to add middle names in Shared Services by selecting an option for Add Middle Name to. For example, if a user name consists of more than two names, you can specify whether to add the middle name as part of the first name or as part of the last name.

Group Names

Define how to treat group names when migrating native groups by selecting one of the following options:

116 Migrating from Hyperion Analyzer

Same Group NameMigrates the native Analyzer group name to a native Shared Services name and keeps the group name the same. Alternate Group NameMigrates the native Analyzer 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.

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, the Reporting and Analysis 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. User/Group Descriptions Define where to copy the Analyzer group descriptions when creating new native Shared Services groups. The default is to copy the Analyzer Group Description to the Shared Services Group Description.

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 properties for a user, select a user name and click Properties (see Editing User Name Properties on page 118).

Reviewing User Names 117

Figure 61

User Names

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.

118 Migrating from Hyperion Analyzer

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 Reporting and Analysis 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 email address first name/last name

If a mapping cannot be made, then during migration, the Reporting and Analysis 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 Analyzer 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:

Reviewing User Names 119

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 users action to Do Not Migrate and perform another migration, the Reporting and Analysis 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 121).

120 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 121

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 Reporting and Analysis 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 Reporting and Analysis 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:

122 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 NativeShared 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 Reporting and Analysis 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 Reporting and Analysis Migration Utility goes through the migration process without actually moving objects from the source system to the

Running the Migration 123

target system. If the Reporting and Analysis 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, it is recommended 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 Reporting and Analysis 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 System 9 in the servlet container.

124 Migrating from Hyperion Analyzer

Figure 63

Run Migration

Table 52

Run Migration Options Review the objects selected to migrate. 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 109). Note: It is recommended that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object. Note: After you migrate repository content, re-startOracle's Hyperion Web Analysis System 9 in the servlet container.

Select the Objects to Migrate

Run Mode

Select one of the following options:


Test OnlyRuns a pre-migration process to help identify any migration issues. Perform MigrationRuns the actual migration.

Note: Test Only is only available for User and Groups in Hyperion Analyzer migrations. Progress Displays information about the progress of the migration such as successes, errors, warnings, the number of objects remaining to be migrated, and the number of objects migrated. Displays informational messages about the migration.

Status Messages

Running the Migration 125

126 Migrating from Hyperion Analyzer

6
In This Chapter

Migrating from Hyperion Performance Suite 8

About Migrating from Hyperion Performance Suite 8......................................................................... 127 Starting the Migration Utility Wizard............................................................................................ 127 Selecting a Migration Path ...................................................................................................... 128 Entering Logging Details......................................................................................................... 128 Defining the Database Used by the Hyperion Performance Suite Repository .............................................. 130 Defining the Location of the Hyperion Performance Suite Repository Database........................................... 131 Identifying Hyperion Performance Suite Groups with Circular References .................................................. 133 Selecting the Objects to Migrate ............................................................................................... 134 Defining Reporting and Analysis Repository Database Information ........................................................ 136 Defining the Location of the Reporting and Analysis Repository Database ................................................ 137 Defining the Location of the Shared Services Server ......................................................................... 140 Defining User/Group Names, Descriptions and Passwords.................................................................. 141 Reviewing User Names .......................................................................................................... 143 Reviewing Group Names ........................................................................................................ 146 Mapping Hosts ................................................................................................................... 150 Defining Additional Migration Options ......................................................................................... 150 Running the Migration ........................................................................................................... 151

About Migrating from Hyperion Performance Suite 8


Use the Hyperion Performance Suite 8.x option in the Reporting and Analysis Migration Utility Wizard to migrate users, groups, roles, and repository content from a Hyperion Performance Suite 8.x installation to Shared Services and the Reporting and Analysis Repository. Before performing the migration, review the information in Chapter 1, Overview and Prerequisites.

Starting the Migration Utility Wizard


To start the Reporting and Analysis Migration Utility Wizard, click migrator.bat (Windows) or
migrator.sh (UNIX) in the bin folder where you installed the Reporting and Analysis Migration Utility. If you installed to the default location, the migrator.bat file is located in:

About Migrating from Hyperion Performance Suite 8 127

C:\Hyperion\Migration Utility\bin

If you are using Windows, you can also start the Reporting and Analysis Migration Utility Wizard by choosing Start > Programs > Hyperion > Reporting and Analysis > Utilities and Administration > Migration Utility.

Selecting a Migration Path


Select Hyperion Performance Suite 8.x on the Welcome screen and click Next.
Figure 64 Welcome Screen

Entering Logging Details


Select the log level for messages and specify the directory in which to write the log files. Logging information is important since this is the only place where you can see errors relating to the migration.

128 Migrating from Hyperion Performance Suite 8

Figure 65

Logging Details

Table 53

Logging Details Specify the log level by selecting one of the following options:

Log Level

FatalFatal messages cause the migration process to stop. ErrorError messages notify you of potential problems, which may or may not be important for your particular migration scenario. For example, 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. WarnWarning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. InfoInformational messages notify you of structural changes made between the old and new systems, differences encountered between the old and new systems, and potential problems. This level is recommended for most migrations. DebugDebug level messages include all types of messages and produces a very large log file. Debug level messages are numerous because they give a row-by-row account of all migration steps. This level is recommended for testing.

Log Directory

Specify the directory where you want to write the log file. To search for a specific directory, click Browse.

Entering Logging Details 129

Defining the Database Used by the Hyperion Performance Suite Repository


Define which database contains the Hyperion Performance Suite 8.x source repository and select how to specify the database location.

Figure 66

Database Used by the Hyperion Performance Suite 8.x Repository

Table 54

Database Type Information Select one of the following databases.


Database Type

SQL Server Oracle DB2

Note: If your source system is installed on DB2 version 7.x, use IBM native drivers to connect. If your source system is installed on DB2 version 8.x, you can use data direct drivers. Database Location Select one of the following options to specify the database location:

Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

130 Migrating from Hyperion Performance Suite 8

Defining the Location of the Hyperion Performance Suite Repository Database


Define the connection to the Hyperion Performance Suite 8.x 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). After you enter the requested information, click Test Connection to test the connection to the database.

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 130), enter the information discussed in Table 55.

Figure 67

Location of Hyperion Performance Suite Repository Database Defined by Host and Name

Table 55

Host and Name Information Enter the name of the database host. Enter the database port number.

Host Port

Defining the Location of the Hyperion Performance Suite Repository Database 131

Database Name User ID Password

Enter the name of the database. Enter the database username used to set up a database connection. Enter the password for the database.

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 130), enter the information discussed in Table 56.
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, use sqljdbc.jar.

Figure 68

Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver and URL

132 Migrating from Hyperion Performance Suite 8

Table 56

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected Sybase, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.sybase.SybaseDriver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility

JDBC URL

The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the Sybase JDBC URL below,
jdbc:hyperion:sybase://<host>:5000;DatabaseName=<dbname>

remove <host> and <dbname> and replace them with the actual name of your host and database. User ID Password Enter the database username used to set up a database connection. Enter the password for the database.

Identifying Hyperion Performance Suite Groups with Circular References


Search for and remove any existing circular references in Hyperion Performance Suite groups. Circular references are groups that contain other groups in a cyclical relationship. For example, Group A contains Group B, which contains Group C, which contains Group A. To search for circular references in Hyperion Performance Suite groups, click Start. If the Reporting and Analysis Migration Utility finds any circular references, they appear under Circular References Found. After all circular references are identified, remove the references in the source Hyperion Performance Suite system before continuing with the migration. It is important to remove circular references in Hyperion Performance Suite groups since Hyperion Performance Suite allows for circular references in groups and Shared Services does not.

To remove a circular reference:


1 Select the circular reference under Circular References Found. 2 Select the relationship that contains the circular references under Select a Relationship to Remove
From.

3 Click Remove Relationship and Recheck.

Identifying Hyperion Performance Suite Groups with Circular References 133

Figure 69

Circular References

Selecting the Objects to Migrate


Select the Hyperion Performance Suite objects to migrate. To select an object, click the checkbox next to the object. It is recommended 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. You can select individual objects to migrate here or on the final Run Migration screen. The objects selected here determine what migration screens appear next.

134 Migrating from Hyperion Performance Suite 8

Figure 70

Hyperion Performance Suite Objects to Migrate

Table 57

User Provisioning Objects to Migrate The roles defined for the users in the Hyperion Performance Suite 8.x system. Account owners identified by a user ID and user name. Named collections of users. User-specific settings (such as an email address). Descriptions of the repository data. For example, the metadata could display the name of the content, permissions etc. The content of the system, folders, and files. Repository content is the largest object to migrate. Note: If a folder in the repository contains more than 80 to 90 items, the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. To make the folder accessible, add -DPerformance.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices.bat script and restart Common Services.

User Defined Roles Users Groups User Preferences Repository Metadata

Repository Files

Events

User subscriptions and notifications of events involving subscriptions, jobs, parameter lists for jobs, and exceptions. Access control information for folders, documents, and resources.

Authorization

Selecting the Objects to Migrate 135

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 58

Database Type Information Select one of the following databases.


Database Type

SQL Server Oracle DB2

Database Location

Select one of the following options to specify the database location:


Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

136 Migrating from Hyperion Performance Suite 8

Defining the Location of the Reporting and Analysis Repository Database


Define the connection to the Reporting and Analysis Repository database on the target system. 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, 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 the Database Used by the Hyperion Performance Suite Repository on page 130), enter the information discussed in Table 59.

Figure 72

Location of Reporting and Analysis Repository Database Defined by Host and Name

Table 59

Host and Name Information Enter the name of the Reporting and Analysis Repository database host.

Host

Defining the Location of the Reporting and Analysis Repository Database 137

Port

Enter the Reporting and Analysis Repository database port number. 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. Note: The user must be assigned Global Administrator, Directory Manager, and Provisioning Manager roles.

Database Name

User ID

Password Source tables have been copied to the target database

Enter the password for the database. Select this option if you manually copied your source tables to the target database. In most cases, manually copying your source tables to the target database is much quicker than allowing the Reporting and Analysis Migration Utility to copy them over a network. This is because the Reporting and Analysis Migration Utility normally issues multiple commands to 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, however, the Reporting and Analysis Migration Utility ssues one command to move all of the rows in the table, 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. 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. 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, if the source tables are copied to the target database without adding a prefix, the current V8

138 Migrating from Hyperion Performance Suite 8

tables will be overwritten. To avoid this, add a prefix to differentiate the Hyperion Performance Suite V8 tables from the Reporting and Analysis V8 tables. The prefix should consist of alphabetic, numeric, or alphanumeric characters.

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 130), enter the information discussed in Table 60.
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, use sqljdbc.jar.

Figure 73

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL

Defining the Location of the Reporting and Analysis Repository Database 139

Table 60

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected SQL Server, the Reporting and Analysis Migration Utility would enter
hyperion.jdbc.sqlserver.SQLServerDriver.

Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility. JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the SQL Server JDBC URL below,
jdbc:hyperion:SQLSERVER://<host>: 1433;DatabaseName=<dbname>;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. Enter the password for the database. See description in Table 59.

Password Source tables have been copied to the target database Tables Prefix

Since both Hyperion Performance Suite and Reporting and Analysis have V8 tables, if the source tables are copied to the target database without adding a prefix, the current V8 tables will be overwritten. To avoid this, add a prefix to differentiate the Hyperion Performance Suite V8 tables from the Reporting and Analysis V8 tables. The prefix should consist of alphabetic, numeric, or alphanumeric characters.

Defining the Location of the Shared Services Server


Define the location of the Shared Services Server on the target system. After you enter the requested information, click Test Connection to test the connection to the server.

140 Migrating from Hyperion Performance Suite 8

Figure 74

Location of Target Shared Services Server

Table 61

Target Shared Services Server Information Enter the name of the Shared Services Server host. Enter the Shared Services Server port number. Enter the login ID for the user in Shared Services. The user must have an administrative role in Shared Services. Enter the password for the User ID.

Host Port User ID

Password

Defining User/Group Names, Descriptions and Passwords


Define how to treat user and group names, user and group descriptions, and passwords when creating new users in Shared Services.

Defining User/Group Names, Descriptions and Passwords 141

Figure 75

User/Group Descriptions and Passwords

Table 62

Information on User/Group Descriptions and Passwords 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:

User Names

Specify how the names in the source description fields are separated by clicking the checkbox next to Space, Semi-colon, or Comma. Note that you can select more than one option. If the names in the source description fields have a different delimiter, click the checkbox next to Other and specify the delimiter. Specify how the user names appear in Hyperion Performance Suite by selecting an option for Name Starts With. For example, if the name appears starting with the last name, you would click the checkbox next to Last Name. Specify how to add middle names in Shared Services by selecting an option for Add Middle Name to. For example, if a user name consists of more than two names, you can specify whether to add the middle name as part of the first name or as part of the last name.

Group Names

Define how to treat Group names when migrating native groups by selecting one of the following options:

Same Group NameMigrates the native Hyperion Performance Suite group name to a native Shared Services group name and keeps the group name the same. Alternate Group NameMigrates the native Hyperion Performance Suite group name to a native Shared Services roup name with a prefix or suffix added to the name. Enter the desired prefix or suffix in the Prefix or Suffix field.

142 Migrating from Hyperion Performance Suite 8

Passwords

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

Auto-generated Same as user ID Other

Note: If the password is auto-generated, the Reporting and Analysis 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. User/Group Descriptions Define where to copy the Hyperion Performance Suite user/group descriptions when creating new native Shared Services roups. The default is to copy the Hyperion Performance Suite User/Group Description to the Shared Services ser/Group Description.

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 properties for a user, select a user name and click Properties (see Editing User Name Properties on page 144).

Reviewing User Names 143

Figure 76

User Names

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.

144 Migrating from Hyperion Performance Suite 8

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 server 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 server or a new user is created with the new name.

Verifying User Name Mapping


When you run the Reporting and Analysis Migration Utility, it queries the source system for users and attempts to automatically map them to existing Shared Services servers based on the following criteria:

login ID email address first name/last name

If a mapping cannot be made, then during migration, the Reporting and Analysis 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 a Hyperion Performance Suite user name to a different Shared Services server name, you would select the user name, click Properties, and change the Shared Services server 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:

Reviewing User Names 145

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 Hyperion Performance Suite 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 Hyperion Performance Suite 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 users action to Do Not Migrate and perform another migration, the Reporting and Analysis Migration Utility does not remove the previously-migrated user from target Shared Services ystem; 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.

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 properties for a group, select a group name and click Properties (see Editing Group Name Properties on page 147).

146 Migrating from Hyperion Performance Suite 8

Figure 77

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 147

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 Reporting and Analysis 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 Reporting and Analysis 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 a Hyperion Performance Suite 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 Hyperion Performance Suite 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 Hyperion Performance Suite to Shared Services, keep in mind the following:

148 Migrating from Hyperion Performance Suite 8

The default setting for inactive groups is Do Not Migrate. This setting cannot be changed. If you want to migrate a deactivated group, you must manually activate the group in the source system before performing the migration. 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 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, or click Select All to select all the group names. 2 Click the checkbox next to Add Users/Groups Assigned in Hyperion Performance Suite to the Native
Shared Services Group.
Note:

When you select this option, if a group in Hyperion Performance Suite 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.

Reviewing Group Names 149

Mapping Hosts
Define the mapping for Hyperion Performance Suite hosts and Reporting and Analysis Repository hosts. For example, you must map each source job factory to a new Reporting and Analysis Repository host.

Figure 78

Host Mapping

To map a host, select a Hyperion Performance Suite Host and a Reporting and Analysis
Repository Host and click Map Hosts. The hosts display in the Mapped Hosts text box.

To remove a mapped pair of hosts, select the hosts in the Mapped Hosts text box and click
Remove Mapped Host.

Defining Additional Migration Options


Select additional options to provide advanced control of the migration process.

150 Migrating from Hyperion Performance Suite 8

Figure 79

Additional Migration Options

Table 63

Additional Migration Options Enter the paths for the following:


Repository Content

Source server.xml and target server.xml Source repository content and target repository content

Either type in the path or click Browse to select a path. Repository Job Factory If you plan to migrate SQR Production Reporting files, define the version of the files in the Reporting and Analysis Repository. For example, enter Version 8.3 as 83, Version 9.0 as 90, and so on. Note: After you complete the migration, you must re-compile all your Oracle's Hyperion SQR Production Reporting System 9 jobs.

Running the Migration


The final screen of the Reporting and Analysis Migration Utility Wizard allows you to review the objects selected to migrate, to run a test migration that will help determine any migration issues, 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 Reporting and Analysis Migration Utility goes through the migration process without actually moving objects from the source system to the
Running the Migration 151

target system. If the Reporting and Analysis 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.

To run a pre-migration process, select Test Only as the Run Mode.


After you complete the pre-migration test and fix all the outstanding errors, it is recommended 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 User Defined Roles. After all the user defined roles migrated successfully, you would select Users.

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 Reporting and Analysis Migration Utility updates both the target database and the OpenLDAP database.)

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

152 Migrating from Hyperion Performance Suite 8

Figure 80

Run Migration

Table 64

Run Migration Options Review the objects selected to migrate. 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 134). Note: It is recommended that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object.

Select the Objects to Migrate

Run Mode

Select one of the following options:


Test OnlyRuns a pre-migration process to help identify any migration issues. Perform MigrationRuns the actual migration.

Note: You should fix any potential errors encountered in the pre-migration process before performing the actual migration. Unless addressed, errors may cause the actual migration to stop or remain incomplete. Progress Displays information about the progress of the migration such as successes, errors, warnings, the number of objects remaining to be migrated, and the number of objects migrated. Displays informational messages about the migration.

Status Messages

Running the Migration 153

154 Migrating from Hyperion Performance Suite 8

7
In This Chapter

Migrating from Hyperion Reports

About Migrating from Hyperion Reports........................................................................................ 155 Starting the Migration Utility Wizard............................................................................................ 155 Selecting a Migration Path ...................................................................................................... 156 Entering Logging Details......................................................................................................... 156 Defining the Database Used by the Reports Repository ..................................................................... 158 Defining the Location of the Reports Repository Database .................................................................. 159 Defining the Hyperion Reports Administrator.................................................................................. 161 Selecting the Objects to Migrate ............................................................................................... 162 Defining Reporting and Analysis Repository Database Information ......................................................... 164 Defining the Location of the Reporting and Analysis Respository Database ............................................... 165 Defining the Location of the Reporting and Analysis Repository Server .................................................... 167 Defining the Location of the Shared Services Server ......................................................................... 168 Defining User/Group Names, Descriptions and Passwords.................................................................. 169 Reviewing User Names .......................................................................................................... 171 Running the Migration ........................................................................................................... 177

About Migrating from Hyperion Reports


Use the Hyperion Reports option in the Reporting and Analysis Migration Utility Wizard to migrate users, groups, roles, and repository contents from a Hyperion Reports 7.0.x or 7.2.x installation to Shared Services and the Reporting and Analysis Repository. Before performing the migration, review the information in Chapter 1, Overview and Prerequisites.

Starting the Migration Utility Wizard


To start the Reporting and Analysis Migration Utility Wizard, click migrator.bat (Windows) or
migrator.sh (UNIX) in the bin folder where you installed the Reporting and Analysis Migration Utility. If you installed to the default location, the migrator.bat file is located in:
C:\Hyperion\Migration Utility\bin

About Migrating from Hyperion Reports 155

If you are using Windows, you can also start the Reporting and Analysis Migration Utility Wizard by choosing Start > Programs > Hyperion > Reporting and Analysis > Utilities and Administration > Migration Utility.

Selecting a Migration Path


Select Hyperion Reports on the Welcome screen and click Next.
Figure 81 Welcome Screen

Entering Logging Details


Select the log level for messages and specify the directory in which to write the log files. Logging information is important since this is the only place where you can see errors relating to the migration.

156 Migrating from Hyperion Reports

Figure 82

Logging Details

Table 65

Logging Details Specify the log level by selecting one of the following options:

Log Level

FatalFatal messages cause the migration process to stop. ErrorError messages notify you of potential problems, which may or may not be important for your particular migration scenario. For example, 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. WarnWarning messages notify you of issues that may or may not be important for your particular migration scenario but deserve investigation. InfoInformational messages notify you of structural changes made between the old and new systems, differences encountered between the old and new systems, and potential problems. This level is recommended for most migrations. DebugDebug level messages include all types of messages and produces a very large log file. Debug level messages are numerous because they give a row-by-row account of all migration steps. This level is recommended for testing.

Log Directory

Specify the directory where you want to write the log file. To search for a specific directory, click Browse.

Entering Logging Details 157

Defining the Database Used by the Reports Repository


Define which database contains the Reports source repository and select how to specify the database location.

Figure 83

Database Used by the Reports Repository

Table 66

Database Type Information Select one of the following databases.


Database Type

SQL Server Oracle DB2

Note: If your source system is installed on DB2 version 7.x, use IBM native drivers to connect. If your source system is installed on DB2 version 8.x, you can use data direct drivers. Database Location Select one of the following options to specify the database location:

Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

158 Migrating from Hyperion Reports

Defining the Location of the Reports Repository Database


Define the connection to the Reports 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). After you enter the requested information, click Test Connection to test the connection to the database.

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 158), enter the information discussed in Table 67.

Figure 84

Location of Reports Repository Database Defined by Host and Name

Table 67

Host and Name Information Enter the name of the database host. Enter the database port number. Enter the name of the database.

Host Port Database Name

Defining the Location of the Reports Repository Database 159

User ID Password

Enter the database username used to set up a database connection. Enter the password for the database.

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 158), enter the information discussed in Table 68.
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, use sqljdbc.jar.

Figure 85

Location of Reports Repository Database Defined by JDBC Driver and URL

Table 68

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path.

Native JDBC Driver Path

160 Migrating from Hyperion Reports

Note: You do not need to enter a native JDBC driver path for DataDirect drivers. JDBC Driver The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected SQL Server, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.sqlserver.SQLServerDriver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility. JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the SQL Server JDBC URL below,
jdbc:hyperion:SQLSERVER://<host>: 1433;DatabaseName=<dbname>;SelectMethod=cursor

remove <host> and <dbname> and replace them with the actual name of your host and database. User ID Password Enter the database username used to set up a database connection. Enter the password for the database.

Defining the Hyperion Reports Administrator


Enter a Hyperion Reports Administrator username and click Test Connection.

Defining the Hyperion Reports Administrator 161

Figure 86

Hyperion Reports Administrator

Selecting the Objects to Migrate


Select the Reports objects to migrate. To select an object, click the checkbox next to the object. It is recommended 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. You can select individual objects to migrate here or on the final Run Migration screen. The objects selected here determine what Reports migration screens appear next.

162 Migrating from Hyperion Reports

Figure 87

Hyperion Reports Objects to Migrate

Table 69

Hyperion Reports Objects to Migrate Account owners identified by a user ID and user name. Named collections of users. The content of the system, namely: folders, files, jobs, URLs, and shortcuts, and their metadata (properties). The content resides in the Repository, which consists of files in the native file system and metadata for each object in a database in a Relational Database Management System (RDBMS). Repository content is the largest object to migrate. When an item in the Reporting and Analysis Repository repository has the same name and type as an object in the Hyperion Reports repository, select one of the following options:

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, the folder is inaccessible in Shared Services and the Reporting and Analysis Repository. To make the folder accessible, add -DPerformance.MAX_UUIDS_BATCH_SIZE=75 to the end of the set BP_FLAGS= line in the startCommonServices.bat script and restart Common Services.

Selecting the Objects to Migrate 163

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 70

Database Type Information Select one of the following database drivers:


Database Type

SQL Server Oracle DB2

Database Location

Select one of the following options to specify the database location:


Host and NameWhen you select this option, you use data direct drivers. JDBC Driver and URLWhen you select this option, 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.

164 Migrating from Hyperion Reports

Defining the Location of the Reporting and Analysis Respository Database


Define the location of the Reporting and Analysis Repository database on the target system. 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, 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 164), enter the information discussed in Table 71.

Figure 89

Location of Reporting and Analysis Repository Database Defined by Host and Name

Table 71

Host and Name Information Enter the name of the Reporting and Analysis Repository database host. Enter the Reporting and Analysis Repository database port number.

Host Port

Defining the Location of the Reporting and Analysis Respository Database 165

Database Name User ID

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 password for the Reporting and Analysis Repository database.

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 164), enter the information discussed in Table 72.
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, use sqljdbc.jar.

Figure 90

Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL

166 Migrating from Hyperion Reports

Table 72

JDBC Driver and URL Information Enter the path to the native JDBC driver. Either type in the path, or click Browse to define the path. Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

Native JDBC Driver Path

JDBC Driver

The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on the database you selected on the previous screen. For example, if you selected SQL Server, the Reporting and Analysis Migration Utility would enter hyperion.jdbc.sqlserver.SQLServerDriver. Note: Once you have loaded an external JDBC driver, you cannot load another external JDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it, you cannot click Back and select another driver. If you wish to load a different external JDBC driver, you must restart the Reporting and Analysis Migration Utility.

JDBC URL

The Reporting and Analysis Migration Utility automatically enters a JDBC URL based on the database you selected on the previous screen. Modify this JDBC URL by personalizing the bracketed information. For example, in the SQL Server JDBC URL below,
jdbc:hyperion:SQLSERVER://<host>: 1433;DatabaseName=<dbname>;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 Reporting and Analysis Repository database connection. Enter the password for the Reporting and Analysis Repository database.

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. After you enter the requested information, click Test Connection to test the connection to the server.

Defining the Location of the Reporting and Analysis Repository Server 167

Figure 91

Location of the Target Reporting and Analysis Repository Server

Table 73

Target Reporting and Analysis Repository Server Information Enter the name of the Reporting and Analysis Repository Server host. Enter the Oracle's Hyperion Reporting and Analysis System 9 Repository Server port number. Enter the login ID for the user with Global Administrator, Directory Manager, and Provisioning Manager roles. Enter the password for the user ID.

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. After you enter the requested information, click Test Connection to test the connection to the server.

168 Migrating from Hyperion Reports

Figure 92

Location of Shared Services Server

Table 74

Shared Services Server Information Enter the name of the Shared Services Server host. Enter the Shared Services Server port number. Enter the login ID for the user in Shared Services. The user must have an administrative role in Shared Services. Enter the password for the User ID.

Host Port User ID

Password

Defining User/Group Names, Descriptions and Passwords


Define how to treat user descriptions, group names, group descriptions, and passwords when creating new users in the Shared Services Server.

Defining User/Group Names, Descriptions and Passwords 169

Figure 93

User/Group Descriptions and Passwords

Table 75

Information on User/Group Descriptions and Passwords Define how to copy the User Descriptions from Reports when creating new native Shared Services users. Select one of the following options:

User Descriptions

Shared Services User DescriptionCopies the Reports User Description fields to the Shared Services User Description fields. Shared Services User First and Last Name FieldsCopies the Reports User First and Last Name fields to the Shared Services User First and Last Name fields. 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, Tab, or Comma. Note that you can select more than one option. If the names in the source description fields have a different delimiter, click the checkbox next to Other and specify the delimiter. Specify how the user names appear in Analyzer by selecting an option for Name Starts With. For example, if the name appears starting with the last name, you would click the checkbox next to Last Name. Specify how to add middle names in Shared Services by selecting an option for Add Middle Name to. For example, if a user name consists of more than two names, you can specify whether to add the middle name as part of the first name or as part of the last name.

Group Names

Define how to treat group names when migrating native groups by selecting one of the following options:

170 Migrating from Hyperion Reports

Same Group NameMigrates the native Reports group name to a native Shared Services group name and keeps the group name the same. Alternate Group NameMigrates the native Reports 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.

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 Reporting and Analysis 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. User/Group Descriptions Define where to copy the Reports group descriptions when creating new native Shared Services groups. The default is to copy the Reports Group Description to the Shared Services Group Description.

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 properties for a user, select a user name and click Properties (see Editing User Name Properties on page 172).

Reviewing User Names 171

Figure 94

User Names

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.

172 Migrating from Hyperion Reports

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 Reporting and Analysis 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 email address first name/last name

If a mapping cannot be made, then during migration, the Reporting and Analysis 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 a Reports 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:

Reviewing User Names 173

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 Hyperion Reports 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 Reports 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 users action to Do Not Migrate and perform another migration, the Reporting and Analysis 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 group name properties, click Properties (see Editing Group Name Properties on page 175). When you make changes on this screen, 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 177).

174 Migrating from Hyperion Reports

Figure 95

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 User Names 175

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 Reporting and Analysis 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 Reporting and Analysis 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 a Reports 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 Reports 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 Reports to Shared Services, keep in mind the following:

176 Migrating from Hyperion Reports

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 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, or click Select All to select all the group names. 2 Click the checkbox next to Add Users/Groups Assigned in Reports to the Native Shared Services
Group.
Note:

When you select this option, if a group in Reports is going to be mapped to a new native group in Oracle's Hyperion 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 Reporting and Analysis 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 Reporting and Analysis Migration Utility goes

Running the Migration 177

through the migration process without actually moving objects from the source system to the target system. If the Reporting and Analysis 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 Reports 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/or Groups the Test Only option is enabled. If you select Users, 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, it is recommended 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. After all the users migrated successfully, you would select Groups.

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 Oracle's Hyperion Reporting and Analysis Migration Utility updates both the target database and the OpenLDAP database.)

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

178 Migrating from Hyperion Reports

Figure 96

Run Migration

Table 76

Run Migration Options Review the objects selected to migrate. 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 161). Note: It is recommended that you migrate each object type separately and check to ensure that the object type migrated correctly before migrating the next object.

Select the Objects to Migrate

Run Mode

Select one of the following options:


Test OnlyRuns a pre-migration process to help identify any migration issues. Perform MigrationRuns the actual migration.

Note: Test Only is disabled for repository content in Hyperion Reports migrations. Progress Displays information about the progress of the migration such as successes, errors, warnings, the number of objects remaining to be migrated, and the number of objects migrated. Displays information messages about the migration.

Status Messages

Running the Migration 179

180 Migrating from Hyperion Reports

Index

B
before migrating Brio Intelligence, 14 Brio Portal, 14 BrioONE, 14 general, 14 Hyperion Analyzer, 15 Hyperion Performance Suite 8, 15 Hyperion Reports, 15 Brio Intelligence pre-migration test, 101 prerequisites, 14 Brio Portal migration, 19 pre-migration test, 44 prerequisites, 14 BrioONE pre-migration test, 74 prerequisites, 14

G
group ids editing properties, 39, 71, 98, 121, 147, 175 searching for, 39, 71, 98, 121, 147, 175 groups provisioning, 10 special symbols in, 15 what happens during migration, 10

H
hosts, mapping, 41, 150 Hyperion Analyzer migration, 103 pre-migration test, 123 prerequisites, 15 Hyperion Performance Suite migration, 127 pre-migration test, 151 prerequisites, 15 Hyperion Reports migration, 155 pre-migration test, 177 prerequisites, 15

C
categories, 15 circular references, 25, 133 content filtering, 91

J D
database, defining for the source repository, 22, 49, 106, 130, 136, 158 JDBC driver, 25, 31, 52, 59, 63, 82, 89, 109, 113, 133, 140, 161, 167 JDBC URL, 25, 32, 53, 60, 64, 82, 89, 109, 114, 133, 140, 161, 167

F
file system, access, 14 filtering content filtering, 91 folders, 15

L
log files, 20, 104, 128, 156

M
mapping hosts, 41, 150 migration path, selecting, 20, 104, 128, 156

Index 181

migration utility, prerequisites, 14 migration, running, 44, 74, 100, 123, 151, 177

U
user ids editing properties, 36, 68, 95, 118, 144, 172 searching for, 68, 95, 118, 144, 172 user provisioning, 10, 127 user/group descriptions and passwords, 33, 66, 93, 115, 141, 169 users provisioning, 10 special symbols in, 15 what happens during migration, 10

O
OCE path, 54, 84 ODS.ini, 54 ODS.pwd, 54 OnDemand Server, location of installation files, 53

P
path, selecting for migration, 20, 104, 128, 156 pre-migration Brio Intelligence, 101 Brio Portal, 44 BrioONE, 74 Hyperion Analyzer, 123 Hyperion Performance Suite, 151 Hyperion Reports, 177 prerequisites, general, 14 provisioning of users and groups, 10

R
Reporting and Analysis Database defining information for, 28, 60, 86 defining the location of, 61 Reporting and Analysis Repository Database defining information for, 56, 110, 164 defining the location of, 29, 87, 111, 165 Reporting and Analysis Repository Server, defining the location of, 90 Reporting and Analysis Server, defining the location of, 64 repository content, what happens during migration, 13 running the migration, 44, 74, 100, 123, 151, 177

S
Shared Services Server, defining the location of, 32, 65, 91, 114, 140, 168 SmartCuts, 17 source repository defining the database location, 23, 107, 131, 159 defining the database used, 22, 49, 106, 130, 136, 158 special symbols, in users and groups, 15

182 Index