Hs Migration

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

Overview of the Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Migration Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
What Happens During Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Prerequisites for Using the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Other Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Special Symbols in Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Invalid Characters in Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
SmartCuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Migrating SAP Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2. Migrating from Brio Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

About Migrating from Brio Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Defining the Database Used by the Portal Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Defining the Location of the Portal Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . 23
Location of Portal Repository Database Defined by Host and Name . . . . . . . . . . . . . . 23
Location of Portal Repository Database Defined by JDBC Driver and URL . . . . . . . . . 24
Identifying Portal Groups with Circular References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . . . . . . . . . . . 30
Location of the Hyperion Registry Database by Host and Name . . . . . . . . . . . . . . . . . 31
Location of the Hyperion Registry Database by JDBC Driver and URL . . . . . . . . . . . . 31
Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . . 33
Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . 34
Location of Reporting and Analysis Repository Database Defined by Host and
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Contents iii
Location of Reporting and Analysis Repository Database Defined by JDBC Driver and
URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . 39
Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Adding Users/Groups Assigned in Portal to the Native Shared Services Group . . . . . . 47
Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 3. Migrating from BrioONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

About Migrating from BrioOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Running the Brio Portal Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Defining the Database Used by the OnDemand Server Repository . . . . . . . . . . . . . . . 55
Defining the Location of the OnDemand Server Repository Database . . . . . . . . . . . . . 56
Defining the Location of the OnDemand Server Installation Files . . . . . . . . . . . . . . . . 59
Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Defining Target Row Level Security Repository Database Information . . . . . . . . . . . . 62
Defining the Location of the Target Row Level Security Repository Database . . . . . . . 63
Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . 66
Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . . . . . . . . 68
Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . 71
Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . 72
Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . 75
Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Defining User/Group Names, Descriptions, and Passwords . . . . . . . . . . . . . . . . . . . . 77
Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
iv Contents
Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Chapter 4. Migrating from the Brio Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

About Migrating from the Brio Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Running the Broadcast Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Defining the Database Used by the Broadcast Server Repository . . . . . . . . . . . . . . . . . 89
Defining the Location of the Broadcast Server Repository Database . . . . . . . . . . . . . . 90
Defining the Broadcast Server Name and the Location of the Broadcast Server
Initialization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . 96
Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . . . . . . . . 98
Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . 100
Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . 101
Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . 104
Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . 105
Defining Content Filtering for Broadcast Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . 106
Defining User/Group Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . 108
Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Chapter 5. Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

About Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Defining the Database Used by the Analyzer Repository . . . . . . . . . . . . . . . . . . . . . . . . 120
Defining the Location of the Analyzer Repository Database . . . . . . . . . . . . . . . . . . . . . . 121
Location of Analyzer Repository Database Defined by Host and Name . . . . . . . . . . . 121
Location of Analyzer Repository Database Defined by JDBC Driver and URL . . . . . . 122
Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Defining the Hyperion Shared Services Registry Type . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Defining Hyperion Registry Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Defining the Location of the Hyperion Registry Database . . . . . . . . . . . . . . . . . . . . . . . 127
Location of the Hyperion Registry Database by Host and Name . . . . . . . . . . . . . . . . 127
Location of the Hyperion Registry Database by JDBC Driver and URL . . . . . . . . . . . 128
Contents v
Defining Reporting and AnalysisDatabase Information . . . . . . . . . . . . . . . . . . . . . . . . . 129
Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . 130
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . 134
Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Adding Users/Groups Assigned in Analyzer to the Native Shared Services Group . . . 141
Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Chapter 6. Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

About Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Defining the Database Used by the Hyperion Performance Suite Repository . . . . . . . . . . 148
Defining the Location of the Hyperion Performance Suite Repository Database . . . . . . . 149
Location of Hyperion Performance Suite Repository Database Defined by Host and
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver
and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Identifying Hyperion Performance Suite Groups and Roles with Circular References . . . . 152
vi Contents
Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . 159
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Adding Users/Groups Assigned in Hyperion Performance Suite to the Native Shared
Services Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Chapter 7. Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

About Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Defining the Database Used by the Reports Repository . . . . . . . . . . . . . . . . . . . . . . . . . 182
Defining the Location of the Reports Repository Database . . . . . . . . . . . . . . . . . . . . . . . 183
Location of Reports Repository Database Defined by Host and Name . . . . . . . . . . . . 183
Location of Reports Repository Database Defined by JDBC Driver and URL . . . . . . . 184
Defining the Hyperion Reports Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Contents vii
Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . 192
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . . . 196
Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Adding Users/Groups Assigned in Reports to the Native Shared Services Group . . . . 206
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
viii Contents
Overview and Prerequisites
1
In This Chapter
Overview of the Migration Process................................................................................................. 9
Prerequisites for Using the 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 the Oracle's Hyperion Reporting and Analysis 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 system—Users, 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 Services—Defines both external users and groups in external directory systems, and
native users maintained in an Open LDAP database.
● Reporting and Analysis Repository—Stores information about the mapping between the
users and groups in the source system and the users and groups in Shared Services.
Overview of the Migration Process 9

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 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
Oracle Hyperion Enterprise Performance Management System roles.
Hyperion Analyzer Role Reporting and Analysis or EPM System Role
Administrator Reporting and Analysis Global Administrator, Directory Manager , Provisioning

Manager
Information Consumer Analyst
Interactive User Data Source Publisher
Power User Content Manager
permission-administer-users Reporting and Analysis Global Administrator
permission-create-links Content Manager
permission-create-pv Personal Parameter Editor
permission-create-pov Personal Parameter Editor
permission-create-report Content Publisher
permission-cube-navigator Analyst
permission-design-report Report Designer
permission-edit-data Data Editor
permission-manage-database Data Source Publisher
permission-open-report Explorer
permission-user-preferences Deprecated
permission-print-report Deprecated
permission-save-report Content Publisher
Overview of the Migration Process 11

Hyperion Metrics Builder Role Reporting and Analysis or EPM System Role
Administrator Reporting and Analysis Administrator
HTML End User Metrics Viewer
Editor Metrics Editor
Java End User Metrics Analyst
Oracle's Hyperion® Performance Suite™ Role Reporting and Analysis or EPM System Role
Administrator Reporting and Analysis Administrator, Directory Manager,

Provisioning Manager
Browser Explorer
Content Administrator Content Manager
Content Publisher Content Publisher
Event Services Administrator Schedule Manager
Global Administrator Reporting and Analysis Global Administrator, Directory Manager,

and Provisioning Manager
Group Administrator Directory Manager
Group Locator Explorer
iHTML Viewer Analyst
Intelligence Analyzer Analyst
Intelligence Dynamic Viewer Dynamic Viewer
Intelligence Viewer Interactive Reporting Viewer
Job Administrator Job Manager
Job Publisher Job Publisher
Job Runner Job Runner
Job Scheduler Scheduler
MIME Type Administrator Content Manager
Name Service Administrator Reporting and Analysis Administrator
OCE Publisher Data Source Publisher
Organizational Administrator Directory Manager and Provisioning Manager
Personal Page Personal Page Editor
Personal Page Publisher Personal Page Publisher

Oracle's Hyperion® Performance Suite™ Role Reporting and Analysis or EPM System Role
Physical Resource Administrator Job Manager
Related Content Viewer Deprecated
Role Administrator Provisioning Manager
Role Locator Explorer
Schedule Administrator Schedule Manager
Session Administrator Reporting and Analysis Administrator
System Crawler Trusted Application
System Viewer Explorer
Trusted Application Trusted Application
User Explorer, Personal Page Editor
User Administrator Directory Manager
User Locator Explorer
View Manager Viewer
View Manager Administrator Viewer
View Manager Content Publisher Favorites Distributor
Reporting and Analysis or Oracle Hyperion Enterprise Performance Management

Hyperion Reports Role System Role
Designer Scheduler, Report Designer
Security Administrator Reporting and Analysis Global Administrator, Directory Manager, Provisioning Manager
System Administrator Reporting and Analysis Global Administrator, Directory Manager, Provisioning Manager
Viewer Explorer
Migrating Repository Content

All repository content/metadata is migrated from the source system to the Reporting and
Analysis Repository.
Prerequisites for Using the Migration Utility

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

Note:
When using the Migration Utility, screen resolutions set to 800x600 or lower are not supported.
Table 1 Prerequisites for Using the Migration Utility
Prerequisite Type Details
General ● Have a working Avalanche 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 Enterprise Performance Management Workspace, Fusion Edition, choose
Administrator, then 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 Administrator’s 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

Prerequisite Type Details
job might run an extra time in the migrated system than it needs to run. These changes do not
affect migration.
BrioONE In addition to the General prerequisites:

● Complete all prerequisites for the Brio Portal and Brio Intelligence migrations.
● Complete the Portal migration, including all pre-migration steps, before running the
OnDemand Server migration.
● Ensure that Portal categories (folders) have been correctly migrated before starting the
OnDemand Server migration.
Hyperion Analyzer Complete the general prerequisites.
Hyperion Performance Suite 8 In addition to the general prerequisites:

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

In addition to understanding the general migration process and reviewing the migration
prerequisites, review the following topics for some additional issues to consider before
migration.
● Special Symbols in Users and Groups
● Invalid Characters in Workspace
● SmartCuts
● Migrating SAP Database Connections
Special Symbols in Users and Groups

There are certain symbols in a user’s first name, a user’s last name, a user’s login ID, and a group
name that are not allowed in Reporting and Analysis. If the Migration Utility encounters any of
these symbols, it replaces them with an acceptable symbol. Table 2 shows the symbol in the
source system and the symbol it is replaced with in Reporting and Analysis.
Note:
These symbols also apply to roles migrated from the Hyperion Performance Suite 8 source
system.
Other Migration Considerations 15

Table 2 Special Symbols
Symbol in 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
Invalid Name Characters

● \
● /
● %
● ?
● +
● <>

● |
● '
● *
● :
● "
Invalid Path Characters

● \
● %
● ?
● +
● <>
● |
● '
● *
● :
● "
SmartCuts
SmartCuts for object names with unsupported characters will not be displayed in EPM
Workspace after migration. To ensure that your SmartCuts appear in Oracle Enterprise
Performance Management Workspace, Fusion Edition, update any SmartCuts in your source
system to use supported characters.
For information on supported characters for SmartCuts, see “Managing SmartCuts” in the
Hyperion Workspace Administrator's Guide.
Migrating SAP Database Connections

To migrate SAP database connections, do the following before running the Migration Utility:
● UNIX: Copy SAPLOGON.INI to the $HOME directory, or ensure that the file location is
specified in the $SAPLOGON_INI_FILE environment variable.
● Windows: Copy SAPLOGON.INI to the %WINDIR% directory, or ensure that file location is
specified in the %SAPLOGON_INI_FILE% environment variable on the server where SAP is
installed.
Note:
The SAPLOGON_INI_FILE environment variable should be a directory.
Other Migration Considerations 17

Migrating from Brio Portal
2
In This Chapter
About Migrating from Brio Portal .................................................................................................19
Starting the Migration Utility Wizard..............................................................................................20
Selecting a Migration Path ........................................................................................................20
Entering Logging Details...........................................................................................................21
Defining the Database Used by the Portal Repository..........................................................................22
Defining the Location of the Portal Repository Database ......................................................................23
Identifying Portal Groups with Circular References .............................................................................26
Selecting the Objects to Migrate .................................................................................................27
Defining the Hyperion Shared Services Registry Type ..........................................................................29
Defining Hyperion Registry Database Information ..............................................................................29
Defining the Location of the Hyperion Registry Database......................................................................30
Defining Reporting and Analysis Repository Database Information ...........................................................33
Defining the Location of the Reporting and Analysis Repository Database ..................................................34
Defining the Location of the Shared Services Server ...........................................................................38
Defining User/Group Names, Descriptions and Passwords....................................................................39
Reviewing User Names ............................................................................................................41
Reviewing Group Names ..........................................................................................................44
Mapping Hosts .....................................................................................................................47
Defining Additional Migration Options ...........................................................................................48
Running the Migration .............................................................................................................50
About Migrating from Brio Portal

Use the Brio Portal option in the 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.”
About Migrating from Brio Portal 19

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

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

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.
Figure 2 Logging Details
Table 3 Logging Details
Field Description
Log Level Specify the log level by selecting one of the following options:
● Fatal—Fatal messages cause the migration process to stop.
● Error—Error 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.
● Warn—Warning messages notify you of issues that may or may not be important for your particular
migration scenario but deserve investigation.
● Info—Informational messages notify you of structural changes made between the old and new
systems, differences encountered between the old and new systems, and potential problems.
Oracle recommends this level for most migrations.
Entering Logging Details 21

Field Description
● Debug—Debug 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. Oracle recommends this level for testing.
Log Directory Specify the directory where you want to write the log file. To search for a specific directory, click
Browse.
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
Field Description
Database Type Select one of the following databases.

● SQL Server
● Oracle

Field Description
● 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 Name—When you select this option, you use data direct drivers.
● JDBC Driver and URL—When 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 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.
Defining the Location of the Portal Repository Database 23

Figure 4 Location of Portal Repository Database Defined by Host and Name
Table 5 Host and Name Information
Field Description
Host Enter the name of the database host.
Port Enter the database port number.
Database Name Enter the name of the database.
User ID Enter the database username used to set up a database connection.
Password Enter the password for the database.
Owner 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 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
Table 6 JDBC Driver and URL Information
Field Description
Native JDBC Driver Path 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.
JDBC Driver The Migration Utility automatically enters a JDBC driver based on the database you
selected on the previous screen. For example, if you selected Sybase, the 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 Migration Utility.
Defining the Location of the Portal Repository Database 25

Field Description
JDBC URL The 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.
Owner 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 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.
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.
Oracle recommends that you migrate each object type separately and check to ensure that the
object migrated correctly before migrating the next object. Note, however, that you must migrate
the objects in the order shown in the wizard. 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.
Selecting the Objects to Migrate 27

Figure 7 Portal Objects to Migrate
Table 7 Portal Objects to Migrate
Field Description
Users Account owners identified by a user ID and user name.
Groups Named collections of users.
User Preferences User-specific settings (such as an email address).
Repository Metadata Descriptions of the repository data. For example, the metadata could display the name of
the content, permissions etc.
Events User subscriptions and notifications of events involving subscriptions, jobs, parameter lists
for jobs, and exceptions.
Authorization Access control information for folders, documents, and resources.
Repository Content 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.

Defining the Hyperion Shared Services Registry Type
Define the Oracle's Hyperion Shared Services Registry to use by selecting an option:
● Default—The Migration Utility takes the connection from the local registry properties file
in hyperion_home\common\config\9.5.0.0.
● New—Two additional wizard screens are displayed where you can enter data source
connection details.
Once a registry connection is established, the Migration Utility takes the required Shared Services
and Foundation connection parameters (host names and ports) from the registry.
Defining Hyperion Registry Database Information

If you selected to define a new Shared Services Registry (see “Defining the Hyperion Shared
Services Registry Type” on page 125), define which database is used by the Hyperion Registry
and select how to specify the database location.
Defining the Hyperion Shared Services Registry Type 29

Field Description
Database Type Select one of the following database drivers:

● SQL Server
● Oracle
● DB2
driver information.
Defining the Location of the Hyperion Registry Database

Define the location of the Hyperion Registry database. The fields displayed vary depending on
the database location specified on previous screen (Host and Name or JDBC Driver and URL).
After you enter the requested information, click Test Connection to test the connection to the
database.

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

and URL
If you specified JDBC Driver and URL on the previous screen in the wizard, (see “Defining
Hyperion Registry Database Information” on page 126), enter the information in Table 58.
Defining the Location of the Hyperion Registry Database 31

Table 10 Hyperion Registry Database JDBC Driver and URL Information
Field Description
the path.
selected on the previous screen. For example, if you selected DB2, the Migration Utility
would enter hyperion.jdbc.db2.DB2Driver.
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.

Field Description
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 8 Database Used by the Reporting and Analysis Repository
Field Description
Database Type Select one of the following databases:

● SQL Server
● Oracle
● DB2
Defining Reporting and Analysis Repository Database Information 33

Field Description
driver information.
Defining the Location of the Reporting and Analysis Repository

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

Figure 9 Location of Reporting and Analysis Repository Database Defined by Host and Name
Field Description
Host Enter the name of the Reporting and Analysis Repository

database host.
Port Enter the Reporting and Analysis Repository database port

number.
Database Name Enter the name of the Reporting and Analysis Repository
database.
User ID Enter the database username used to set up a Reporting

and Analysis Repository database connection.
Password Enter the password for the Reporting and Analysis

Repository database.
Owner Optional: Enter the table owner/schema name. In most

cases, the owner is the same as the database username.
Source tables have been copied to the target Select this option if you manually copied your source tables
database to the target database.
In most cases, manually copying your source tables to the
target database is much quicker than allowing the
Migration Utility to copy them over a network. This is
Defining the Location of the Reporting and Analysis Repository Database 35

Field Description
because the 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 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

Defined by JDBC Driver and URL
If you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining
Reporting and Analysis Repository Database Information” on page 33), enter the information
discussed in Table 13.
Note:

Figure 10 Location of Reporting and Analysis Repository Database Defined by JDBC Driver and URL
Field Description
Native JDBC Driver Path 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.
JDBC Driver The Migration Utility automatically enters a JDBC driver based on
the database you selected on the previous screen. For example, if
you selected DB2, the 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 Migration
Utility.
JDBC URL The 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,

Field Description
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.
Password Enter the password for the Reporting and Analysis Repository
database.
Owner Optional: Enter the table owner/schema name. In most cases, the
owner is the same as the database username.
Source tables have been copied to the target See description in Table 12.
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.

Figure 11 Location of Shared Services Server
Table 14 Shared Services Server Information
Field Description
Host Enter the name of the Shared Services Server host.
Port Enter the Shared Services Server port number.
User ID Enter the login ID for the user in Shared Services. The user must have an administrative role in Shared
Services.
Password Enter the password for the User ID.
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 39

Figure 12 User/Group Descriptions and Passwords
Table 15 Information on User/Group Descriptions and Passwords
Field Description
User Descriptions Define how to copy the User Descriptions from Portal when creating new native Shared Services
users. Select one of the following options:
● Shared Services User Description—Copies the Portal User Description fields to the Shared
Services User Description fields.
● Shared Services User First and Last Name Fields—Copies the Portal User First and Last
Name fields to the Shared Services User First and Last Name fields.
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 inShared 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.

Field Description
Group Names Define how to treat group names when migrating native groups by selecting one of the following
options:
● Same Group Name —Migrates the native Portal group name to a native Shared Services
group name and keeps the group name the same.
● Alternate Group Name—Migrates the native Portal group name to a native Shared Services
group name with a prefix or suffix added to the name. 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 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 42).
Reviewing User Names 41

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.

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

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 user’s action to Do Not Migrate and perform
another migration, the 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

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

Figure 14 Group Names
Searching for Group Names

➤ To search for a group name:
1 Click Search.
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.
Reviewing Group Names 45

The group name properties from both systems (source and target) are displayed. Some properties
are read-only and some can be edited.
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 Migration Utility, it queries the source system for groups and attempts to
automatically map them to existing Shared Services groups based on the group name.
If a mapping cannot be made, then during migration, the Migration Utility creates a new native
group. You can view these mappings on the Group Names screen and manually adjust or change
the mappings as necessary.
For example, to map 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.

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:

● 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,
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 47
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.

Figure 16 Additional Migration Options
Table 16 Additional Migration Options
Field Description
Authorization Define how to translate the Write access control in Portal by selecting one of the following
options:
● Modify in the Reporting and Analysis Repository—Select this option to map "Write"
or "Write and Execute" to the "Modify" access control.
● Full Control in the Reporting and Analysis Repository—Select 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 Repository “Full
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.
Defining Additional Migration Options 49

Field Description
Repository Job Factory If you plan to migrate 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 Production Reporting
jobs.
Running the Migration

The final screen of the 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 Migration Utility goes through the migration
process without actually moving objects from the source system to the target system. If the
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, Oracle recommends
that you migrate each object type separately and check to ensure that the object migrated
correctly before migrating the next object. Note, however, that you must migrate the objects in
the order shown in the wizard.
➤ To migrate each object type separately:

1 Select the desired object type.
For example, you could begin by selecting Users. 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 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 Production Reporting jobs.

Figure 17 Run Migration
Table 17 Run Migration Options
Field Description
Select the Objects to Migrate 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 27).
Note: Oracle recommends that you migrate each object type separately and check
to ensure that the object type migrated correctly before migrating the next object.
Run Mode Select one of the following options:

● Test Only—Runs a pre-migration process to help identify any migration issues.
● Perform Migration—Runs 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.
Status Messages Displays information messages about the migration.
Running the Migration 51

Migrating from BrioONE
3
In This Chapter
About Migrating from BrioOne ....................................................................................................53
Running the Brio Portal Migration ................................................................................................53
Running the OnDemand Server Migration .......................................................................................54
About Migrating from BrioOne

Use the BrioONE option in the Migration Utility Wizard to migrate users, groups, roles, and
repository content from a BrioONE installation to Shared Services and the Reporting and
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
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 53

● Defining the Location of the Portal Repository Database
● Identifying Portal Groups with Circular References
● Selecting the Objects to Migrate
● Defining Reporting and Analysis Repository Database Information
● Defining the Location of the Reporting and Analysis Repository Database
● Defining the Location of the Shared Services Server
● Defining User/Group Names, 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 55
● “Defining the Location of the OnDemand Server Repository Database” on page 56
● “Defining the Location of the OnDemand Server Installation Files” on page 59
● “Selecting the Objects to Migrate” on page 60
● “Defining Target Row Level Security Repository Database Information” on page 62
● “Defining the Location of the Target Row Level Security Repository Database” on page
63
● “Defining the Hyperion Shared Services Registry Type” on page 66
● “Defining Hyperion Registry Database Information” on page 67
● “Defining the Location of the Hyperion Registry Database” on page 68
● “Defining Reporting and Analysis Repository Database Information” on page 71
54 Migrating from BrioONE

● “Defining the Location of the Reporting and Analysis Repository Database” on page 72
● “Defining the Location of the Reporting and Analysis Repository Server” on page 75
● “Defining the Location of the Shared Services Server” on page 76
● “Defining User/Group Names, Descriptions, and Passwords” on page 77
● “Reviewing User Names” on page 78
● “Reviewing Group Names” on page 81
● “Running the Migration” on page 84
Defining the Database Used by the OnDemand Server

Repository
Define which database contains the OnDemand Server source repository and select how to
Figure 18 Database Used by the OnDemand Server Repository
Running the OnDemand Server Migration 55

Field Description

● SQL Server
● Oracle
● DB2
● Informix
● Sybase
● Redbrick
driver information.
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
Location of OnDemand Server Repository Database Defined by Host and

Name
Used by the OnDemand Server Repository” on page 55), enter the information discussed in
Table 19.

Figure 19 Location of OnDemand Server Repository Database Defined by Host and Name
Field Description
Owner Enter the table owner/schema name. In most cases, the owner is the same as the database
username.
Location of OnDemand Server Repository Database Defined by JDBC Driver

and URL
Database Used by the OnDemand Server Repository” on page 55), enter the information

Note:
Figure 20 Location of OnDemand Server Repository Database Defined by JDBC Driver and URL
Field Description
the path.
JDBC Driver The migration utility automatically enters a JDBC driver based on the database you
selected on the previous screen. For example, if you selected DB2, the migration utility

Field Description
JDBC URL The migration utility automatically enters a JDBC URL based on the database you selected
User ID Enter the database username used to set up an OnDemand Server database connection.
Owner 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

Table 21 OnDemand Server Installation Files
Field Description
ODS.ini File 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.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 Select this option if you are running the migration utility from
Server a machine other than the source system. If running on a
machine other than the source, enter the following
information:
● Mapped OCE Path—Map 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 Path—Map the BQY directory on the
installation machine to the BQY directory on the source
system.
\Program\Documents on the source system.

Select the OnDemand Server objects to migrate. To select an object, click the checkbox next to
the object.
The objects selected here determine what OnDemand Server migration screens appear next.

Figure 22 OnDemand Server Objects to Migrate
Table 22 OnDemand Server Objects to Migrate
Field Description

To select a User Insight Privilege, click the checkbox and select an option from the list
that appears. User Insight Privileges include:
● Insight
● Quickview
● Freeview

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.

Field Description
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.
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 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
Note:
This screen appears only if you selected Row Level Security Data on the Objects to Migrate wizard
screen.

Figure 23 Database Used by the Target Row Level Security Repository
Field Description

● SQL Server
● Oracle
● DB2
driver information.
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

Location of Target Row Level Security Repository Database Defined by Host

and Name
in Table 24.
Figure 24 Location of Row Level Security Repository Database Defined by Host and Name
Field Description
Host Enter the name of the Row Level Security Repository database host.
Port Enter theRow Level Security Repository database port number.
Database Name Enter the name of the Row Level Security Repository database.
User ID Enter the username used to set up a Row Level Security Repository database connection.
Password Enter the password for the Row Level Security Repository database.

Field Description
database username.
Location of Target Row Level Security Repository Database Defined by JDBC

Driver and URL
Note:
Figure 25 Location of Row Level Security Repository Defined by JDBC Driver and URL

Field Description
the path.
selected on the previous screen. For example, if you selected SQL Server, the migration
utility would enter hyperion.jdbc.sqlserver.SQLServerDriver.
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.
Password Enter the password for the Row Level Security Repository database.

Define the Shared Services Registry to use by selecting an option:
connection details.


Field Description

● SQL Server
● Oracle
● DB2
driver information.

database.

Field Description
Location of the Hyperion Registry Database by JDBC Driver and URL


Field Description
the path.

Field Description

Information
Field Description

● SQL Server
● Oracle
● DB2

Field Description
driver information.
Defining the Location of the Reporting and Analysis

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

and Name
in Table 30.

Field Description
Host Enter the name of the Reporting and Analysis Repository database host.
Port Enter the Reporting and Analysis Repository database port number.
Database Name Enter the name of the Reporting and Analysis Repository database.
User ID Enter the username used to set up a Reporting and Analysis Repository database connection.
Password Enter the password for the Reporting and Analysis Repository database.
Location of Reporting and Analysis Repository Database Defined by JDBC

Driver and URL

Note:
Field Description
the path.

Field Description
User ID Enter the database username used to set up a Reporting and Analysis Repository
database connection.

Repository Server
Define the connection to the Reporting and Analysis Repository Server on the target system.
server.
Figure 29 Location of Target Reporting and Analysis Repository Server

Table 32 Reporting and Analysis Repository Server Information
Field Description
Host Enter the name of the Reporting and Analysis Repository Server host.
Port Enter the Reporting and Analysis Repository Server port number.
User ID Enter the user ID of a user with Global Administrator, Directory Manager, and Provisioning Manager roles.
Password Enter the password for the user ID.

Figure 30 Location of Target Shared Services Server
Field Description

Field Description
Services.
Defining User/Group Names, Descriptions, and Passwords

Define how to treat group names and passwords when creating new users in the Shared Services
Server.
Table 34 Information on Group Descriptions and Passwords
Field Description
options:
● Same Group Name—Migrates the native Intelligence group name to a native Shared Services
group name and keeps the group name the same.

Field Description
● Alternate Group Name—Migrates the native Intelligence group name to a native Shared Services
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 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.

on page 79).


1 Click Search.

The user ID properties from both systems (source and target) are displayed. Some properties
Note:

When you run the migration utility, it queries the source system for users and attempts to
● login ID

● email address
If a mapping cannot be made, then during migration, the migration utility creates a new native
user.
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.

● Select the user and click the checkbox next to Migrate User Name from Intelligence to
Shared Services.
When specifying whether to migrate users from Intelligence to Shared Services, keep in mind
the following:
migrated to the target Shared Services. If you later change a user’s action to Do Not
Migrate and perform another migration, the migration utility does not remove the
previously-migrated user from target Shared Services system; instead, you must delete the
user directly from the target Shared Services.


properties for a group, select a group name and click Properties (see “Editing Group Name

1 Click Search.


1 Select the desired group name and click Properties.
The group names properties from both systems (source and target) are displayed. Some
properties are read-only and some can be edited.
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.

When you run the migration utility, it queries the source system for groups and attempts to
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.

● Select the group and click the checkbox next to Migrate Group Name from Intelligence to
Shared Services.
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.
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:
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.


The final screen of the Migration Utility wizard allows you to review the objects selected to
actual migration.
actual migration. During a pre-migration test, the migration utility goes through the migration
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.


For example, you could begin by selecting Users. After all the users migrated successfully, you

Field Description

objects migrated.

Migrating from the Brio
4 Intelligence Server
In This Chapter
About Migrating from the Brio Intelligence Server ..............................................................................87
Running the OnDemand Server Migration .......................................................................................87
Running the Broadcast Server Migration.........................................................................................88
About Migrating from the Brio Intelligence Server

Use the Brio Intelligence Server option in the Migration Utility Wizard to migrate users, groups,
roles, and repository content from a Brio Intelligence Server installation toShared 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 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
● Defining the Database Used by the OnDemand Server Repository
About Migrating from the Brio Intelligence Server 87

● Defining the Location of the OnDemand Server Repository Database
● Defining the Location of the OnDemand Server Installation Files
● Selecting the Objects to Migrate
● Defining Target Row Level Security Repository Database Information
● Defining the Location of the Target Row Level Security Repository Database
● Defining the Hyperion Shared Services Registry Type
● Defining Hyperion Registry Database Information
● Defining the Location of the Hyperion Registry Database
● Defining Reporting and Analysis Repository Database Information
● Defining the Location of the Reporting and Analysis Repository Database
● Defining the Location of the Reporting and Analysis Repository Server
● Defining the Location of the Shared Services Server
● Defining User/Group Names, Descriptions, and Passwords
● Reviewing User Names
● Reviewing Group Names
● Running the Migration
See “Running the OnDemand Server Migration” on page 54 for detailed information on
migrating information from the OnDemand Server.
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
● “Defining the Database Used by the Broadcast Server Repository” on page 89
● “Defining the Location of the Broadcast Server Repository Database” on page 90
● “Defining the Broadcast Server Name and the Location of the Broadcast Server Initialization
File” on page 93
● “Selecting the Objects to Migrate” on page 94
● “Defining the Hyperion Shared Services Registry Type” on page 66
88 Migrating from the Brio Intelligence Server

● “Defining Hyperion Registry Database Information” on page 67
● “Defining the Location of the Hyperion Registry Database” on page 68
● “Defining Reporting and Analysis Repository Database Information” on page 100
● “Defining the Location of the Reporting and Analysis Repository Database” on page 101
● “Defining the Location of the Shared Services Server” on page 105
● “Defining User/Group Descriptions and Passwords” on page 108
● “Reviewing User Names” on page 109
● “Reviewing Group Names” on page 112
● “Running the Migration” on page 115
Defining the Database Used by the Broadcast Server

Repository
Define which database contains the Broadcast Server source repository and select how to specify
the database location.
Figure 35 Database Used by the Broadcast Server Repository
Running the Broadcast Server Migration 89

Field Description

● SQL Server
● Oracle
● DB2
● Informix
● Sybase
● Redbrick
Note: If your source system is installed on DB2 version 7.x, use IBM native drivers to connect.
driver information.
Defining the Location of the Broadcast Server Repository

Database
Define the connection to the Broadcast Server repository database on your existing system. The
Location of Broadcast Server Repository Database Defined by Host and

Name
Used by the Broadcast Server Repository” on page 89), enter the information discussed in
Table 37.

Figure 36 Location of Broadcast Server Repository Database Defined by Host and Name
Field Description
database username.
Location of Broadcast Server Repository Database Defined by JDBC Driver

and URL
Database Used by the Broadcast Server Repository” on page 89), enter the information discussed
in Table 39.

Note:
Figure 37 Location of Broadcast Server Repository Database Defined by JDBC Driver and URL
Field Description
Native JDBC Driver Path Enter the path to the native JDBC driver. Either type in the path, or click Browse.

Field Description
User ID Enter the database username for a Broadcast Server Repository database connection.
Password Enter the password for the Broadcast Server Repository database.
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 39 Broadcast Server Configuration Information
Field Description
BQServ1.ini Enter the path for the location of the BQServ1.ini file (the
ini file for the Broadcast Server). Either type in the path to
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.
Migration Utility is Not Running on the Broadcast Select this option if you are running the migration utility from
Server a machine other than the source system. If you select this
option, enter the mapped job storage path and enter the
following information:
● Mapped OCE Path—Map the OCE directory on the
installation machine to the OCE directory on the source
system.
\Program\Open Catalog Extensions on the source
system.
● Mapped Job Storage Path—Map 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:
\BCS_Jobs on the source system.

Select the Broadcast Server objects to migrate. To select an object, click the checkbox next to the
object.
The objects selected here determine what Broadcast Server migration screens appear next.

Figure 39 Broadcast Server Objects to Migrate
Table 40 Broadcast Server Objects to Migrate
Field Description
Users Account owners identified by a user ID, user name, and password.
Groups A named collection of users.
Calendar Calendars used to schedule jobs in the Broadcast Server.
Events Events in the Broadcast Server.
Printer Paths Printer path definitions in the Broadcast Server.
Paths 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.
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.

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

connection details.

Field Description

● SQL Server
● Oracle
● DB2
driver information.

database.

Field Description

Location of the Hyperion Registry Database by JDBC Driver and URL
Field Description
the path.

Field Description

Information
Field Description

● SQL Server

Field Description
● Oracle
● DB2
driver information.

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

and Name
in Table 45.

Field Description
User ID Enter the database username used to set up a Reporting and Analysis Repository database
connection.
Location of Reporting and Analysis Repository Database Defined by JDBC

Driver and URL

Note:
Field Description
the path.

Field Description

Repository Server
server.
Figure 43 Location of Target Reporting and Analysis Repository Server

Table 47 Reporting and Analysis Repository Server Information
Field Description
Port Enter the Reporting and Analysis Repository Server port number.
User ID Enter the username of a user with Global Administrator, Directory Manager, and Provisioning Manager
roles.

Field Description

Field Description
User ID Enter the login ID for the user in Shared Services.
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.
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.
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.

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 Migration Utility. You can also make changes in
the external file and load it into the 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.
Field Description
options:
● Same Group Name—Migrates the native Intelligence group name to a native Shared Services
group name and keeps the group names the same.
● Alternate Group Name—Migrates the native Intelligence group name to a native Shared Services

Field Description
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 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 name properties, click Properties (see “Editing User Name Properties” on page 110).


1 Click Search.

Note:

● login ID

● email address
user.
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.

● Select the user and click the checkbox next to Migrate User Name from Intelligence to
Shared Services.
When specifying whether to migrate users from Intelligence to Shared Services , keep in mind
the following:



1 Click Search.



For example, to map an Intelligence group name to a different Shared Services group name, you

● Select the group and click the checkbox next to Migrate Group Name from Intelligence to
Shared Services.

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


actual migration.
migration utility finds any problems, it reports them in the log files. You should fix any potential



Field Description

objects migrated.

Migrating from Hyperion
5 Analyzer
In This Chapter
About Migrating from Hyperion Analyzer ....................................................................................... 117
Starting the Migration Utility Wizard............................................................................................ 117
Selecting a Migration Path ...................................................................................................... 118
Entering Logging Details......................................................................................................... 118
Defining the Database Used by the Analyzer Repository..................................................................... 120
Defining the Location of the Analyzer Repository Database ................................................................. 121
Selecting the Objects to Migrate ............................................................................................... 124
Defining the Hyperion Shared Services Registry Type ........................................................................ 125
Defining Hyperion Registry Database Information ............................................................................ 126
Defining the Location of the Hyperion Registry Database.................................................................... 127
Defining Reporting and AnalysisDatabase Information....................................................................... 129
Defining the Location of the Reporting and Analysis Repository Database ................................................ 130
Defining the Location of the Shared Services Server ......................................................................... 133
Defining User/Group Names, Descriptions and Passwords.................................................................. 134
Reviewing User Names .......................................................................................................... 135
Reviewing Group Names ........................................................................................................ 138
Running the Migration ........................................................................................................... 141
About Migrating from Hyperion Analyzer

Use the Hyperion Analyzer option in the 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.”

the bin folder where you installed the migration utility.
About Migrating from Hyperion Analyzer 117


Select Hyperion Analyzer on the Welcome screen and click Next.

migration.
118 Migrating from Hyperion Analyzer

Field Description
Browse.

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
Field Description

● SQL Server
● Oracle
● DB2
● MySQL
driver information.

Field Description
Defining the Location of the Analyzer Repository Database

Define the connection to the Analyzer repository database on your existing system. The fields
Location of Analyzer Repository Database Defined by Host

and Name
Used by the Analyzer Repository” on page 120), enter the information discussed in Table 53.
Figure 53 Location of Analyzer Repository Database Defined by Host and Name
Defining the Location of the Analyzer Repository Database 121

Field Description
Location of Analyzer Repository Database Defined by JDBC

Driver and URL
Database Used by the Analyzer Repository” on page 120), enter the information discussed in
Table 54.
Note:

Figure 54 Location of Analyzer Repository Database Defined by JDBC Driver and URL
Field Description
the path.
and database.
Defining the Location of the Analyzer Repository Database 123

Field Description

Select the Analyzer objects to migrate. To select an object, click the checkbox next to the object.
The objects selected here determine what Analyzer migration screens appear next.
Figure 55 Hyperion Analyzer Objects to Migrate
Table 55 Hyperion Analyzer Objects to Migrate
Field Description
Users and Groups Users—Account owners identified by a user ID and user name.
Groups—Named collections of users.

Field Description
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.
BP_FLAGS= line in the startCommonServices.bat script and restart Common Services.

connection details.

Field Description

● SQL Server
● Oracle
● DB2
driver information.

database.

Field Description

and URL
Field Description
the path.

Field Description
Defining Reporting and AnalysisDatabase Information

Field Description

● SQL Server
Defining Reporting and AnalysisDatabase Information 129

Field Description
● Oracle
● DB2
driver information.

Database

and AnalysisDatabase Information” on page 129), enter the information discussed in
Table 60.

Field Description
connection.

Reporting and AnalysisDatabase Information” on page 129), enter the information discussed in
Table 61.
Note:
Field Description
the path.

Field Description
and database.

Defining the Location of the Shared Services Server 133

Field Description
Services.

Define how to treat user descriptions, group names, group descriptions, and passwords when

Field Description
User Descriptions Define how to copy the User Descriptions from Analyzer when creating new native Shared
Services users. Select one of the following options:
● Shared Services User Description—Copies the Analyzer User Description fields to
the Shared Services User Description fields.
● Shared Services User First and Last Name Fields—Copies the Analyzer User First
and Last Name fields to the Shared Services User First and Last Name fields.
❍ 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:
● Same Group Name—Migrates the native Analyzer group name to a native Shared
Services name and keeps the group name the same.
● Alternate Group Name—Migrates the native Analyzer group name to a native Shared
Services group name with a prefix or suffix added to the name. 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 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.


on page 136).

1 Click Search.


Note:

● login ID
● email address
user.
mappings as necessary. For example, to map an Analyzer user name to a different Shared Services


● Select the user and click the checkbox next to Migrate User Name from Analyzer to Shared
Services.
When specifying whether to migrate users from Analyzer to Shared Services, keep in mind the
following:


of properties for a group, select a group name and click Properties (see “Editing Group Name


1 Click Search.



For example, to map an Analyzer group name to a different Shared Services group name, you

● Select the group and click the checkbox next to Migrate Group Name from Analyzer to
Shared Services.
When specifying whether to migrate groups from Analyzer to Shared Services, keep in mind the
following:

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:
2 Click the checkbox next to Add Users/Groups Assigned in Analyzer to the Native Shared Services
Group.
Note:
When you select this option, if a group in Analyzer is going to be mapped to a new native group
in Shared Services; then upon migration, this new native group is created and any users and
groups assigned to the group in the source system are assigned to the group in the target system.


migrate and to run the actual migration.

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.

For example, you could begin by selecting Users and Groups. After all the users and groups
migrated successfully, you would select Repository Content.
This step is optional As an extra precaution, you may want to backup the target database after
Note:
After you migrate repository content, re-start Oracle's Hyperion® Web Analysis in the servlet
container.

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

Note: Test Only is only available for User and Groups in Hyperion Analyzer
migrations.
objects migrated.
Status Messages Displays informational messages about the migration.

6 Performance Suite 8
In This Chapter
About Migrating from Hyperion Performance Suite 8......................................................................... 145
Defining the Database Used by the Hyperion Performance Suite Repository .............................................. 148
Defining the Location of the Hyperion Performance Suite Repository Database........................................... 149
Identifying Hyperion Performance Suite Groups and Roles with Circular References...................................... 152
Defining Reporting and Analysis Repository Database Information ......................................................... 159
Reviewing Group Names ........................................................................................................ 170
Mapping Hosts ................................................................................................................... 174
Defining Additional Migration Options ......................................................................................... 174
About Migrating from Hyperion Performance Suite 8

Use the Hyperion Performance Suite 8.x option in the 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.”
About Migrating from Hyperion Performance Suite 8 145


Select Hyperion Performance Suite 8.x on the Welcome screen and click Next.
146 Migrating from Hyperion Performance Suite 8

migration.
Field Description

Field Description
Browse.
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
Field Description

● SQL Server

Field Description
● Oracle
● DB2
driver information.
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

Used by the Hyperion Performance Suite Repository” on page 148), enter the information
Defining the Location of the Hyperion Performance Suite Repository Database 149
Figure 67 Location of Hyperion Performance Suite Repository Database Defined by Host and Name
Field Description
Location of Hyperion Performance Suite Repository Database

Database Used by the Hyperion Performance Suite Repository” on page 148), enter the
information discussed in Table 68.

Note:
Figure 68 Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver and URL
Field Description
the path.
selected on the previous screen. For example, if you selected Sybase, the Migration Utility
would enter hyperion.jdbc.sybase.SybaseDriver.
Defining the Location of the Hyperion Performance Suite Repository Database 151
Field Description
For example, in the Sybase JDBC URL below,
jdbc:hyperion:sybase://<host>:5000;DatabaseName=<dbname>
and database.
Identifying Hyperion Performance Suite Groups and Roles with

Circular References
Search for and remove any existing circular references in Hyperion Performance Suite groups
and roles. Circular references are groups or roles that contain other groups or roles 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 and roles, click Start.
If the 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 and roles since Hyperion Performance
Suite allows for circular references in groups and roles 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.

Figure 69 Circular References

Select the Hyperion Performance Suite objects to migrate. To select an object, click the checkbox
next to the object.
The objects selected here determine what migration screens appear next.

Figure 70 Hyperion Performance Suite Objects to Migrate
Table 69 User Provisioning Objects to Migrate
Field Description
User Defined Roles The roles defined for the users in the Hyperion Performance Suite 8.x system.
User Preferences User-specific settings (such as an email address).
Repository Metadata Descriptions of the repository data. For example, the metadata could display the name of
the content, permissions etc.
Repository Files The content of the system, folders, and files. Repository content is the largest object to
migrate.
BP_FLAGS= line in the startCommonServices.bat script and restart Common
Services.
Events User subscriptions and notifications of events involving subscriptions, jobs, parameter lists
for jobs, and exceptions.

Field Description
Authorization Access control information for folders, documents, and resources.

connection details.


Field Description

● SQL Server
● Oracle
● DB2
driver information.

database.

Field Description

and URL

Field Description
the path.

Field Description

Information
Field Description

● SQL Server
● Oracle
● DB2
Defining Reporting and Analysis Repository Database Information 159

Field Description
driver information.

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

Used by the Hyperion Performance Suite Repository” on page 148), enter the information

Field Description
Host Enter the name of the Reporting and Analysis Repository

database host.
Port Enter the Reporting and Analysis Repository database port

number.
Database Name Enter the name of the Reporting and Analysis Repository
database.
User ID 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.
Source tables have been copied to the target Select this option if you manually copied your source tables
database to the target database.
In most cases, manually copying your source tables to the
target database is much quicker than allowing the Migration
Utility to copy them over a network. This is because the
Migration Utility normally issues multiple commands to
Field Description
separately move each database row from the source
database to the target database. If all of the tables are
located in the same database before migration, however,
the 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
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 Hyperion System 9 V8 tables.
The prefix should consist of alphabetic, numeric, or
alphanumeric characters.

Database Used by the Hyperion Performance Suite Repository” on page 148), enter the
information discussed in Table 75.

Note:
Field Description
Native JDBC Driver Path 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.
JDBC Driver The 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 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
Field Description
a different external JDBC driver, you must restart the Migration
Utility.
JDBC URL The 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,
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.
Source tables have been copied to the target See description in Table 74.
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 Hyperion System 9 V8 tables.
The prefix should consist of alphabetic, numeric, or alphanumeric
characters.


Table 76 Target Shared Services Server Information
Field Description
Services.

Define how to treat user and group names, user and group descriptions, and passwords when

Field Description
User Names 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:
● 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 Name—Migrates the native Hyperion Performance Suite group name
to a native Shared Services group name and keeps the group name the same.

Field Description
● Alternate Group Name—Migrates the native Hyperion Performance Suite group
name to a native Shared Services group name with a prefix or suffix added to the
name. 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
● Auto-generated
● Same as user ID
● Other
User/Group Descriptions Define where to copy the Hyperion Performance Suite user/group descriptions when
creating new native Shared Services groups. The default is to copy the Hyperion
Performance Suite User/Group Description to the Shared Services User/Group
Description.

on page 168).


1 Click Search.


Note:

● login ID
● email address
user.
mappings as necessary. For example, to map a Hyperion Performance Suite 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.


● Select the user and click the checkbox next to Migrate User Name from Hyperion
Performance Suite to Shared Services.
When specifying whether to migrate users from Hyperion Performance Suite to Shared Services,
keep in mind the following:




1 Click Search.
The group names that meet the search criteria display. After you search for a group name you



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.

● Select the group and click the checkbox next to Migrate Group Name from Hyperion
Performance Suite to Shared Services.
When specifying whether to migrate groups from Hyperion Performance Suite to Shared
Services, keep in mind the following:

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


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.

Figure 79 Additional Migration Options
Table 78 Additional Migration Options
Field Description
Repository Content Enter the paths for the following:

● 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 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 Production Reporting
jobs.

actual migration.

migration utility finds any problems, it reports them in the log files. You should fix any potential


For example, you could begin by selecting User Defined Roles. After all the user defined roles
migrated successfully, you would select Users.

Field Description

objects migrated.
Status Messages Displays informational messages about the migration.

7 Reports
In This Chapter
About Migrating from Hyperion Reports........................................................................................ 179
Defining the Database Used by the Reports Repository ..................................................................... 182
Defining the Location of the Reports Repository Database .................................................................. 183
Defining the Hyperion Reports Administrator.................................................................................. 185
Defining Reporting and Analysis Repository Database Information ......................................................... 192
Defining the Location of the Reporting and Analysis Repository Server .................................................... 196
About Migrating from Hyperion Reports

Use the Hyperion Reports option in the 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.”

About Migrating from Hyperion Reports 179


Select Hyperion Reports on the Welcome screen and click Next.

migration.
180 Migrating from Hyperion Reports

Field Description
Browse.

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
Field Description

● SQL Server
● Oracle
● DB2
driver information.

Defining the Location of the Reports Repository Database
Define the connection to the Reports repository database on your existing system. The fields
Location of Reports Repository Database Defined by Host and

Name
Used by the Reports Repository” on page 182), enter the information discussed in Table 82.
Figure 84 Location of Reports Repository Database Defined by Host and Name
Field Description
Defining the Location of the Reports Repository Database 183

Field Description
Location of Reports Repository Database Defined by JDBC

Driver and URL
Database Used by the Reports Repository” on page 182), enter the information discussed in
Table 83.
Note:
Figure 85 Location of Reports Repository Database Defined by JDBC Driver and URL

Field Description
the path.
and database.
Defining the Hyperion Reports Administrator

Enter a Hyperion Reports Administrator username and click Test Connection.
Defining the Hyperion Reports Administrator 185

Figure 86 Hyperion Reports Administrator

Select the Reports objects to migrate. To select an object, click the checkbox next to the object.
The objects selected here determine what Reports migration screens appear next.

Figure 87 Hyperion Reports Objects to Migrate
Table 84 Hyperion Reports Objects to Migrate
Field Description
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.
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:
● Overwrite the item in the Reporting and Analysis Repository
● Do not copy the item into the Reporting and Analysis Repository
BP_FLAGS= line in the startCommonServices.bat script and restart Common Services.

connection details.

If you selected to define a new Oracle's Hyperion Shared Services Registry (see “Defining the
Hyperion Shared Services Registry Type” on page 125), define which database is used by the
Hyperion Registry and select how to specify the database location.

Field Description

● SQL Server
● Oracle
● DB2
driver information.

database.

Field Description

and URL

Field Description
the path.

Field Description

Information
Figure 88 Database Used by the Reporting and Analysis Repository Repository
Field Description

● SQL Server
● Oracle
● DB2

Field Description
driver information.

Database

in Table 89.
Field Description
connection.


Note:
Field Description
the path.
Field Description
and database.

Server
server.

Figure 91 Location of the Target Reporting and Analysis Repository Server
Table 91 Target Reporting and Analysis Repository Server Information
Field Description
Port Enter the Oracle's Hyperion Reporting and Analysis Repository Server port number.
User ID Enter the login ID for the user with Global Administrator, Directory Manager, and Provisioning Manager
roles.
Password Enter the password for the user ID.

Defining the Location of the Shared Services Server 197

Field Description
Services.

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

Field Description
User Descriptions Define how to copy the User Descriptions from Reports when creating new native Shared
Services users. Select one of the following options:
● Shared Services User Description—Copies the Reports User Description fields to
the Shared Services User Description fields.
● Shared Services User First and Last Name Fields—Copies the Reports User First
and Last Name fields to the Shared Services User First and Last Name fields.
❍ 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.

Field Description
Group Names Define how to treat group names when migrating native groups by selecting one of the
following options:
● Same Group Name—Migrates the native Reports group name to a native Shared
Services group name and keeps the group name the same.
● Alternate Group Name—Migrates the native Reports group name to a native Shared
Services group name with a prefix or suffix added to the name. 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
● Auto-generated
● Same as user ID
● Other
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.

on page 201).


1 Click Search.


Note:

● login ID
● email address
user.
mappings as necessary. For example, to map a Reports user name to a different Shared Services


● Select the user and click the checkbox next to Migrate User Name from Hyperion Reports
to Shared Services.
When specifying whether to migrate users from Reports to Shared Services, keep in mind the
following:


of group name properties, click Properties (see “Editing Group Name Properties” on page
204).
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 206).


1 Click Search.
The group names that meet the search criteria display. After you search for a group name you



For example, to map a Reports group name to a different Shared Services group name, you

● Select the group and click the checkbox next to Migrate Group Name from Reports to
Shared Services.
When specifying whether to migrate groups from Reports to Shared Services, keep in mind the
following:

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


migrate and to run the actual migration.

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.


Field Description
selected on the Select Objects to Migrate screen earlier in the wizard (see “Defining
the Hyperion Reports Administrator” on page 185).

Note: Test Only is disabled for repository content in Hyperion Reports migrations.
objects migrated.

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

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

Hs Migration

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Hs Migration

Hochgeladen von

Copyright:

Verfügbare Formate

HYPERION® REPORTING AND ANALYSIS

Chapter 1. Overview and Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2. Migrating from Brio Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3. Migrating from BrioONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 4. Migrating from the Brio Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 5. Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 6. Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Chapter 7. Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Overview of the Migration Process

Overview of the Migration Process 9

Migrating Users and Groups

Provisioning of Users and Groups During Migration

10 Overview and Prerequisites

Hyperion Analyzer Role Reporting and Analysis or EPM System Role

Administrator Reporting and Analysis Global Administrator, Directory Manager , Provisioning

Information Consumer Analyst

Interactive User Data Source Publisher

Power User Content Manager

permission-administer-users Reporting and Analysis Global Administrator

permission-create-links Content Manager

permission-create-pv Personal Parameter Editor

permission-create-pov Personal Parameter Editor

permission-create-report Content Publisher

permission-design-report Report Designer

permission-edit-data Data Editor

permission-manage-database Data Source Publisher

permission-save-report Content Publisher

Overview of the Migration Process 11

Administrator Reporting and Analysis Administrator

HTML End User Metrics Viewer

Editor Metrics Editor

Java End User Metrics Analyst

Administrator Reporting and Analysis Administrator, Directory Manager,

Content Administrator Content Manager

Content Publisher Content Publisher

Event Services Administrator Schedule Manager

Global Administrator Reporting and Analysis Global Administrator, Directory Manager,

Group Administrator Directory Manager

Group Locator Explorer

iHTML Viewer Analyst

Intelligence Analyzer Analyst

Intelligence Dynamic Viewer Dynamic Viewer

Intelligence Viewer Interactive Reporting Viewer

Job Administrator Job Manager

Job Publisher Job Publisher

Job Runner Job Runner

Job Scheduler Scheduler

MIME Type Administrator Content Manager

Name Service Administrator Reporting and Analysis Administrator

OCE Publisher Data Source Publisher

Organizational Administrator Directory Manager and Provisioning Manager

Personal Page Personal Page Editor

Personal Page Publisher Personal Page Publisher

12 Overview and Prerequisites

Physical Resource Administrator Job Manager

Related Content Viewer Deprecated

Role Administrator Provisioning Manager

Role Locator Explorer

Schedule Administrator Schedule Manager

Session Administrator Reporting and Analysis Administrator

System Crawler Trusted Application

System Viewer Explorer

Trusted Application Trusted Application