Hs Migration

8/4/2019 Hs Migration

1/182

H Y P E R I O N R E P O R T I N G A N D A N A L Y S I S

M I G R A T I O N U T I L I T YR E L E A S E 9 . 3 . 1

M I G R A T I O N U T I L I T Y G U I D E


2/182

Reporting and Analysis Migration Utility Guide, 9.3.1

Copyright 2002, 2007, Oracle and/or its affiliates. All rights reserved.

Authors: Angela Vermeer

The Programs (which include both the software and documentation) contain proprietary information; they are provided

under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and

other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except

to the extent required to obtain interoperability with other independently created software or as specified by law, is

prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the

documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be

expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or

transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the

United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered toU.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the

applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,

disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject

to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional

rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500

Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous

applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures

to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any

damages caused by such use of the Programs.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their

respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is

not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with

the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly

between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b)

fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty

obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you

may incur from dealing with any third party.


3/182

Contents

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

Overview of the Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Migration Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

What Happens During Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Prerequisites for Using the Reporting and Analysis Migration Utility . . . . . . . . . . . . . . . . 13

Other Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Special Symbols in Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Invalid Characters in Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SmartCuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Migrating SAP Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

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

About Migrating from Brio Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Defining the Database Used by the Portal Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Defining the Location of the Portal Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . 23

Location of Portal Repository Database Defined by Host and Name . . . . . . . . . . . . . . 23

Location of Portal Repository Database Defined by JDBC Driver and URL . . . . . . . . . 24

Identifying Portal Groups with Circular References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Defining Reporting and Analysis Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . . 29

Location of Reporting and Analysis Repository Database Defined by Host andName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Location of Reporting and Analysis Repository Database Defined by JDBC Driver andURL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . 33

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Contents iii


4/182

Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Adding Users/Groups Assigned in Portal to the Native Shared Services Group . . . . . . 41

Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 3. Migrating from BrioONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

About Migrating from BrioOne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Running the Brio Portal Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Defining the Database Used by the OnDemand Server Repository . . . . . . . . . . . . . . . 49

Defining the Location of the OnDemand Server Repository Database . . . . . . . . . . . . . 50

Defining the Location of the OnDemand Server Installation Files . . . . . . . . . . . . . . . . 53

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Defining Target Row Level Security Repository Database Information . . . . . . . . . . . . 56

Defining the Location of the Target Row Level Security Repository Database . . . . . . . 57

Defining Reporting and Analysis Database Information . . . . . . . . . . . . . . . . . . . . . . . 60

Defining the Location of the Reporting and Analysis Database . . . . . . . . . . . . . . . . . . 61

Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . 64

Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Defining User/Group Names, Descriptions, and Passwords . . . . . . . . . . . . . . . . . . . . 66

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

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

About Migrating from the Brio Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Running the Broadcast Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Defining the Database Used by the Broadcast Server Repository . . . . . . . . . . . . . . . . . 79

Defining the Location of the Broadcast Server Repository Database . . . . . . . . . . . . . . 80

iv Contents


5/182

Defining the Broadcast Server Name and the Location of the Broadcast ServerInitialization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . 86

Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . 87

Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . 90

Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Defining Content Filtering for Broadcast Server Jobs . . . . . . . . . . . . . . . . . . . . . . . . . 91

Defining User/Group Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 5. Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

About Migrating from Hyperion Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Defining the Database Used by the Analyzer Repository . . . . . . . . . . . . . . . . . . . . . . . . 106

Defining the Location of the Analyzer Repository Database . . . . . . . . . . . . . . . . . . . . . . 107

Location of Analyzer Repository Database Defined by Host and Name . . . . . . . . . . . 107

Location of Analyzer Repository Database Defined by JDBC Driver and URL . . . . . . 108

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Defining Reporting and Analysis Repository Database Information . . . . . . . . . . . . . . . . 110

Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . 111Location of Reporting and Analysis Repository Database Defined by Host andName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Location of Reporting and Analysis Repository Database Defined by JDBC Driver andURL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Defining the Location of the Shared Services Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . 115

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Contents v


6/182

Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122


Adding Users/Groups Assigned in Analyzer to the Native Shared Services Group . . . 123

Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

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

About Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128


Defining the Database Used by the Hyperion Performance Suite Repository . . . . . . . . . . 130

Defining the Location of the Hyperion Performance Suite Repository Database . . . . . . . 131

Location of Hyperion Performance Suite Repository Database Defined by Host andName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Location of Hyperion Performance Suite Repository Database Defined by JDBC Driverand URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Identifying Hyperion Performance Suite Groups with Circular References . . . . . . . . . . . 133



Defining the Location of the Reporting and Analysis Repository Database . . . . . . . . . . . 137

Location of Reporting and Analysis Repository Database Defined by Host andName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137



Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . 141

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143






Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146


Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148


Adding Users/Groups Assigned in Hyperion Performance Suite to the Native SharedServices Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

vi Contents


7/182


Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150


Chapter 7. Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

About Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156


Defining the Database Used by the Reports Repository . . . . . . . . . . . . . . . . . . . . . . . . . 158

Defining the Location of the Reports Repository Database . . . . . . . . . . . . . . . . . . . . . . . 159

Location of Reports Repository Database Defined by Host and Name . . . . . . . . . . . . 159

Location of Reports Repository Database Defined by JDBC Driver and URL . . . . . . . 160

Defining the Hyperion Reports Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161



Defining the Location of the Reporting and Analysis Respository Database . . . . . . . . . . . 165

Location of Reporting and Analysis Repository' Database Defined by Host andName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165


Defining the Location of the Reporting and Analysis Repository Server . . . . . . . . . . . . . 167


Defining User/Group Names, Descriptions and Passwords . . . . . . . . . . . . . . . . . . . . . . 169Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171






Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174


Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176


Adding Users/Groups Assigned in Reports to the Native Shared Services Group . . . . 177



Contents vii


8/182

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

viii Contents


9/182

1 Overview and PrerequisitesIn This Chapter

Overview of the Migration Process........ ...... ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... . 9

Prerequisites for Using the Reporting and Analysis Migration Utility ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .13

Other Migration Considerations......... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... .15

Overview of the Migration ProcessMigration involves migrating information from the source system to Oracle's Hyperion Shared

Services and Oracle's Hyperion Reporting and Analysis System 9 Repository. Review the

following topics for information on the migration process.

Migration Components

What Happens During Migration

Migration ComponentsEach migration involves the following components:

Source systemUsers, groups, roles, repository content, and the database used by one of

the following source products:

Brio Portal 7.0.5 or later

BrioONE (Brio Portal 7.0.5 or later and OnDemand Server 6.6.4 or later)

Brio Intelligence Server (OnDemand Server and Broadcast Server 6.6.4 or later)

Hyperion Analyzer 6.5, 7.0.1, 7.2, or 7.2.1

Hyperion Performance Suite 8.x

Hyperion Reports 7.0.x or 7.2.x

Shared ServicesDefines both external users and groups in external directory systems, andnative users maintained in an Open LDAP database.

Reporting and Analysis RepositoryStores information about the mapping between the

users and groups in the source system and the users and groups in Shared Services.

Overview of the Migration Process 9


10/182

What Happens During MigrationMigration 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 registeredduring product installation and configuration.

Provisioning of Users and Groups During Migration

Provisioning is the process of granting roles and access control to users of Hyperion applications.

Based on roles assigned, users can perform specific tasks and access content in various

applications. During user provisioning, keep in mind the following:

If a user/group is explicitly assigned roles by the source product (other than default roles),

the user/group is explicitly provisioned with these roles subject to the mapping of the roles

in the Oracle's Hyperion Reporting and Analysis Migration Utility.

For example, if a user is assigned rolexin the source product, and this role is mapped to

roleyin the Reporting and Analysis Repository, the user will be provisioned with roley.

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


11/182

To keep the same behavior for users/groups created after migration, add any new user/s

groups to the native group (for example, AnalyzerGroup). By doing this, the new users/

groups inherit the same roles and are implicitly provisioned. You only need to explicitly

provision new user/groups if you want to assign them additional roles.

Migrating Roles

During migration, pre-configured roles in the source system are mapped to new roles in Shared

Services. The mapping determines how users and groups are provisioned. For example, if a user

is granted a pre-configured role in the source system, the user will be provisioned with new

Reporting and Analysis roles based on this mapping. When you migrate user-defined roles, new

roles are created in Shared Services.

The following tables correlate legacy roles for Hyperion Analyzer, Hyperion Metrics Builder,

Oracle's Hyperion Performance Suite, and Hyperion Reports to Reporting and Analysis and

Hyperion roles.

Hyperion Analyzer Role Reporting and Analysis or Hyperion 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

permiss ion-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


12/182

Oracle's Hyperion Performance Suite Role Reporting and Analysis or Hyperion 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

Physical Resource Administrator Job Manager

Related Content Viewer Deprecated

Role Administrator Provisioning Manager

Role Locator Explorer

Schedule Administrator Schedule Manager



13/182

Oracle's Hyperion Performance Suite Role Reporting and Analysis or Hyperion Role

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

Hyperion Reports Role Reporting and Analysis or Hyperion 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 ContentAll repository content/metadata is migrated from the source system to the Reporting and

Analysis Repository.

Prerequisites for Using the Reporting and Analysis MigrationUtility

Prerequisites include tasks that you must complete for the Reporting and Analysis Migration

Utility to run properly, regardless of system configuration or content migrated. Before using the

Reporting and Analysis Migration Utility on a test or production system, fulfill the prerequisitesin Table 1.

Note:

When using the Reporting and Analysis Migration Utility, screen resolutions set to 800x600 or

lower are not supported.

Prerequisites for Using the Reporting and Analysis Migration Utility 13


14/182

Table 1 Prerequisites for Using the Reporting and Analysis Migration Utility

Prerequisite Type Details

General Have a working Reporting and Analysis installation on the target system.

Have access to the old and new Repository databases.

Have an administrator user ID and password for the source and target systems.

Have user ID, password, and connectivity information for the repository databases. Configure Shared Services for external authentication.

For example, if your source system uses external authentication, then you must configure

Shared Services with the same external directory services. Review the list of users and groups

in Shared Services to confirm that they are the external users and groups to which you want

to map the source system users and groups.

Disable the Harvester service.

Log onto Oracle's Hyperion Workspace, select Administrator > General, and ensure that

Enable Harvesting is notselected.

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 finitevalue (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 orvncserver -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

/BrioPlatform/bin directory and restart the services.

The BQ_FONT_PATH environment variable is needed by the Interactive Reporting Service on

the target system to ensure that BQY jobs and documents are rendered properly in the new

environment. For additional information on BQ_FONT_PATH, see Fonts for Unix in the

Hyperion Workspace Administrators Guide.

Note: Scheduled jobs are migrated as part of the Broadcast Server migration. If a job is scheduledto run during the time of the migration, it triggers the Event Service and creates faulty job output.

If jobs run during migration, there may be some changes to the BRIOJOBS table, such as updating

last run date and decreasing the number of remaining times for the job to run, and a migrated

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

affect migration.

BrioONE In addition to the General prerequisites:

Complete all prerequisites for the Brio Portal and Brio Intelligence migrations.



15/182

Prerequisite Type Details

Complete the Portal migration, including all pre-migration steps, before running the

OnDemand Server migration.

Ensure that Portal cCategories (folders) have been correctly migrated before starting the

OnDemand Server migration.

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

Hyperion Reports Complete the general prerequisites.

Other Migration ConsiderationsIn addition to understanding the general migration process and reviewing the migrationprerequisites, 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 GroupsThere are certain symbols in a users first name, a users last name, a users login ID, and a group

name that are not allowed in Reporting and Analysis. If the Reporting and Analysis Migration

Utility encounters any of these symbols, it replaces them with an acceptable symbol. Table 2

shows the symbol in the source system and the symbol it is replaced with in Reporting and

Analysis.

Table 2 Special Symbols

Symbol in Source System Symbol in Reporting and Analysis

, _

= -

+ *

< [

> ]

Other Migration Considerations 15


16/182

Symbol in Source System Symbol in Reporting and Analysis

( [

) ]

; :

\ /

" `

# ~

Note: The '#' symbol is replaced with the ~ symbol only if the '#' symbol is in the firstposition.

Example

During migration, a user name ofSmith,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 WorkspaceThe following characters are not supported for objects in Workspace. Rename objects or folders

containing these characters before migrating from the source system to the Reporting and

Analysis Repository.

Invalid Name Characters \

/

%

?

+

|

'

*

:

"



17/182

Invalid Path Characters

\

%

?

+

|

'

*

:

"

SmartCutsSmartCuts for object names with unsupported characters will not be displayed in Reporting and

Analysis Workspace after migration. To ensure that your SmartCuts appear in Oracle's

Hyperion Workspace, update all SmartCuts in your source system to use supported characters.

For information on supported characters for SmartCuts, see Managing SmartCuts in the

Hyperion Workspace Administrator's Guide.

Migrating SAP Database ConnectionsTo migrate SAP database connections, do the following before running the Reporting and

Analysis Migration Utility:

UNIX: CopySAPLOGON.INI to the $HOME directory, or ensure that the file location is

specified in the $SAPLOGON_INI_FILE environment variable.

Windows: CopySAPLOGON.INI to the %WINDIR% directory, or ensure that file location is

specified in the %SAPLOGON_INI_FILE% environment variable on the server where SAP is

installed.

Note:

The SAPLOGON_INI_FILE environment variable should be a directory.

Other Migration Considerations 17


18/182



19/182

2 Migrating from Brio PortalIn This Chapter

About Migrating from Brio Portal ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ..... ..... ...... ..... ....19

Starting the Migration Utility Wizard... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ..19

Selecting a Migration Path........................................................................................................20

Entering Logging Details...........................................................................................................20

Defining the Database Used by the Portal Repository..........................................................................22

Defining the Location of the Portal Repository Database ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .23

Identifying Portal Groups with Circular References ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..25

Selecting the Objects to Migrate ...... ..... ...... ...... ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ...... ..... ...26

Defining Reporting and Analysis Database Information........................................................................28

Defining the Location of the Reporting and Analysis Repository Database .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..29

Defining the Location of the Shared Services Server. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..32

Defining User/Group Names, Descriptions and Passwords... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..33

Reviewing User Names ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ..... ..... ....35

Reviewing Group Names ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... .....38

Mapping Hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Defining Additional Migration Options ..... ...... ..... ..... ...... ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... ....42

Running the Migration.............................................................................................................44

About Migrating from Brio PortalUse the Brio Portal option in the Reporting and Analysis Migration Utility Wizard to migrate

users, groups, roles, and repository content from a Brio Portal 7.0.5 or later installation to Shared

Services and the Reporting and Analysis Repository. Before performing the migration, review

the information in Chapter 1, Overview and Prerequisites.

Starting the Migration Utility Wizard

To start the Reporting and Analysis Migration Utility Wizard, click migrator.bat (Windows) or

migrator.sh(UNIX) in thebin folder where you installed the Reporting and Analysis Migration

Utility.

If you installed to the default location, the migrator.bat file is located in:

About Migrating from Brio Portal 19


20/182

C:\Hyperion\Migration Utility\bin

If you are using Windows, you can also start the Reporting and Analysis Migration Utility Wizard

by choosing Start > Programs > Hyperion > Reporting and Analysis > Utilities and

Administration > Migration Utility.

Selecting a Migration PathSelect Brio Portal on the Welcome screen and click Next.

Figure 1 Welcome Screen

Entering Logging DetailsSelect the log level for messages and specify the directory in which to write the log files. Logging

information is important since this is the only place where you can see errors relating to the

migration.

20 Migrating from Brio Portal


21/182

Figure 2 Logging Details

Table 3 Logging Details

Log Level Specify the log level by selecting one of the following options:

FatalFatal messages cause the migration process to stop.

ErrorError messages notify you of potential problems, which may or may not be important for

your particular migration scenario. For example, an error message may tell you that a particular

user does not exist in the source system; you can ignore this message if deleting that user is part

of your migration plan.

WarnWarning messages notify you of issues that may or may not be important for your particular

migration scenario but deserve investigation.

InfoInformational messages notify you of structural changes made between the old and new

systems, differences encountered between the old and new systems, and potential problems.

This level is recommended for most migrations.

DebugDebug level messages include all types of messages and produces a very large log file.

Debug level messages are numerous because they give a row-by-row account of all migration

steps.This level is recommended for testing.

Log Directory Specify the directory where you want to write the log file. To search for a specific directory, clickBrowse.

Entering Logging Details 21


22/182

Defining the Database Used by the Portal RepositoryDefine 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

Database Type Select one of the following databases.

SQL Server

Oracle

DB2

Informix

Sybase

Note: If your source system is instal led on DB2 version 7.x, use IBM native drivers to connect.If your source system is installed on DB2 version 8.x, you can use data direct drivers.

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

Host and NameWhen you select this option, you use data direct drivers.

JDBC Driver and URLWhen you select this option, the wizard prompts you to provide full

driver information.

The fields that appear on the next screen in the wizard depend on the option selected here.



23/182

Defining the Location of the Portal Repository DatabaseDefine 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 andNameIf you specified Host and Name on the previous screen in the wizard (see Defining the Database

Used by the Portal Repository on page 22), enter the information discussed in Table 5.

Figure 4 Location of Portal Repository Database Defined by Host and Name

Table 5 Host and Name Information

Host Enter the name of the database host.

Port Enter the database port number.

Database Name Enter the name of the database.

Defining the Location of the Portal Repository Database 23


24/182

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

Location of Portal Repository Database Defined by JDBCDriver and URLIf you specified a JDBC Driver and URL on the previous screen in the wizard (see Defining the

Database Used by the Portal Repository on page 22), enter the information discussed in

Table 6.

Note:

It is recommended to use the same native JDBC drivers when you use the JDBC Driver and

URL option for source and target system connection. If you are migrating from an MsSQL 2000server to an MsSQL 2005 server, use sqljdbc.jar.

Figure 5 Location of Portal Repository Database Defined by JDBC Driver and URL



25/182

Table 6 JDBC Driver and URL Information

Native JDBC Driver Path Enter the path to the native JDBC driver. Either type in the path, or click Browse to definethe path.

Note: You do not need to enter a native JDBC driver path for DataDirect drivers.

JDBC Driver The Reporting and Analysis Migration Utility automatically enters a JDBC driver based on

the database you selected on the previous screen. For example, if you selected Sybase,

the Reporting and Analysis Migration Utility would enterhyperion.jdbc.sybase.SybaseDriver .

Note: Once you have loaded an external JDBC driver, you cannot load another externalJDBC driver with the same name. For example, if you enter hyperion.jdbc.db2.DB2Driver

and click Next to load it, you cannot click Back and select another driver. If you wish to

load a different external JDBC driver, you must restart the Reporting and Analysis Migration

Utility.

JDBC URL The Reporting and Analysis Migration Utility automatically enters a JDBC URL based onthe 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://:5000;DatabaseName=

remove and and replace them with the actual name of your hostand database.



Owner Optional: Enter the table owner/schema name. In most cases, the owner is the same asthe database username.

Identifying Portal Groups with Circular ReferencesSearch for and remove any existing circular references in Portal groups. Circular references are

groups that contain other groups in a cyclical relationship. For example, Group A contains

Group B, which contains Group C, which contains Group A.

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

If the Reporting and Analysis Migration Utility finds any circular references, they appear under

Circular References Found.

After all circular references are identified, remove the references in the source Portal system

before continuing with the migration. It is important to remove circular references in Portal

groups since Portal allows for circular references in groups and Shared Services does not.

To remove a circular reference:

1 Select the circular reference underCircular References Found.2 Select the relationship that contains the circular references underSelect a Relationship to Remove

From.

Identifying Portal Groups with Circular References 25


26/182

3 ClickRemove Relationship and Recheck.

Figure 6 Circular References

Selecting the Objects to MigrateSelect the Portal objects to migrate. To select an object, click the checkbox next to the object.

It is recommended that you migrate each object type separately and check to ensure that the

object migrated correctly before migrating the next object. Note, however, that you must migrate

the objects in the order shown in the wizard. You can select individual objects to migrate here

or on the final Run Migration screen.

The objects selected here determine what Portal migration screens appear next.



27/182

Figure 7 Portal Objects to Migrate

Table 7 Portal Objects to Migrate

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

Note: If a folder in the repository contains more than 80 to 90 items, the folder is inaccessiblein Shared Services and the Reporting and Analysis Repository. To make the folder accessible,

add -DPerformance.MAX_UUIDS_BATCH_SIZE=75 to the end of the set

BP_FLAGS= line in the startCommonServices.bat script and restart Common

Services.

Selecting the Objects to Migrate 27


28/182

Defining Reporting and Analysis Database InformationDefine 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


Database Type Select one of the following databases:

SQL Server

Oracle

DB2




driver information.




29/182

Defining the Location of the Reporting and Analysis RepositoryDatabase

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 DatabaseDefined by Host and NameIf you specified Host and Name on the previous screen in the wizard (see Defining Reporting

and Analysis Database Information on page 28), enter the information discussed in Table 9.

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


Host Enter the name of the Reporting and Analysis Repository

database host.

Defining the Location of the Reporting and Analysis Repository Database 29


30/182

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 mostcases, the owner is the same as the database username.

Source tables have been copied to the targetdatabase

Select this option if you manually copied your source

tables to the target database.

In most cases, manually copying your source tables to the

target database is much quicker than allowing the

Reporting and Analysis Migration Utility to copy them over

a network. This is because the Reporting and Analysis

Migration Utility normally issues multiple commands toseparately move each database row from the source

database to the target database. If all of the tables are

located in the same database before migration, however,

the Reporting and Analysis Migration Utility issues one

command to move all of the rows in the table, thus

resulting in a much faster migration.

If you manually copy your source tables to the target

database, make sure to have both the source tables and

the target tables accessible in one database user account.

Having your source and target tables in the same database

user account can speed up large migrations by allowing

you to use another utility to import large V7 tables into your

target database.

The following tables are affected:

V7_CONTAINER

V7_CONT_VERSION

V7_DATA_CONTAINER

V7_SPF_OUT_OPTS

V7_COLLECTION_MBRS

V7_COLLECTION

V7_CONTNR_KEYWORDS

V7_FOLDER

V7_FOLDER_TREE

V7_TASK

VY_JOBINPUTVALUES

V7_INPUT_PARAMETER



31/182

Location of Reporting and Analysis Repository DatabaseDefined by JDBC Driver and URLIf you specified a JDBC Driver and URL on the previous screen in the wizard (see Defining

Reporting and Analysis Database Information on page 28), enter the information discussed in

Table 10.

Note:

It is recommended to use the same native JDBC drivers when you use the JDBC Driver and

URL option for source and target system connection. If you are migrating from an MsSQL 2000

server to an MsSQL 2005 server, use sqljdbc.jar.

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

Table 10 JDBC Driver and URL Information

Native JDBC Driver Path Enter the path to the native JDBC driver. Either type in the path, orclick Browse to define the path.

Note: You do not need to enter a native JDBC driver path forDataDirect drivers.

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

Defining the Location of the Reporting and Analysis Repository Database 31


32/182

screen. For example, if you selected DB2, the Reporting and

Analysis Migration Utility would enter

hyperion.jdbc.db2.DB2Driver .

Note: Once you have loaded an external JDBC driver, you cannot

load another external JDBC driver with the same name. For example,

if you enter hyperion.jdbc.db2.DB2Driver and click Next to load it,

you cannot click Back and select another driver. If you wish to load

a different external JDBC driver, you must restart the Reporting and

Analysis Migration Utility.

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

screen. Modify this JDBC URL by personalizing the bracketed

information. For example, in the DB2 JDBC URL below,

jdbc:hyperion:db2://:

50000;DatabaseName=;PackageName=

remove , , and 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 andAnalysis Repository database connection.

Password Enter the password for the Reporting and Analysis Repositorydatabase.

Owner Optional: Enter the table owner/schema name. In most cases, theowner is the same as the database username.

Source tables have been copied to the targetdatabase

See description inTable 9.

Defining the Location of the Shared Services ServerDefine 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.



33/182

Figure 11 Location of Shared Services Server

Table 11 Shared Services Server Information

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 PasswordsDefine how to treat user descriptions, group names, passwords, and authentication when

creating new users in Shared Services.

Defining User/Group Names, Descriptions and Passwords 33


34/182

Figure 12 User/Group Descriptions and Passwords

Table 12 Information on User/Group Descriptions and Passwords

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 DescriptionCopies the Portal User Description fields to the Shared

Services User Description fields.

Shared Services User First and Last Name FieldsCopies the Portal User First and Last

Name fields to the Shared Services User First and Last Name fields.

If you select this option:

Specify how the names in the source description fields are separated by selecting Space,

Semi-colon, Tab, or Comma. Note that you can select more than one option. If the names

in the source description fields have a different delimiter, select Other and specify the

delimiter.

Specify how the user names appear in Portal by selecting an option forName Starts

With. For example, if the name appears starting with the last name, you would selectLast Name.

Specify how to add middle names in Shared Services by selecting an option forAdd

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



35/182

Same Group Name Migrates the native Portal group name to a native Shared Services

group name and keeps the group name the same.

Alternate Group NameMigrates the native Portal group name to a native Shared Services

group name with a prefix or suffix added to the name. Enter the desired prefix or suffix in the

Prefix or Suffix field.

Passwords Define how to handle passwords when creating new Shared Services users by selecting one ofthe following options:

Auto-generated

Same as user ID

Get from Source

Note: If the password is auto-generated, the Reporting and Analysis Migration Utility creates a

file that lists the new native users along with their login ID, autogenerated password, and email

address. The administrator can use this information to email users their new passwords.

Authentication If Portal currently uses external NT authentication to authenticate users, click the checkbox nextto Portal Uses External NT Authentication and enter the default NT authentication domain.

Reviewing User NamesReview the user mappings and properties and set the migration action for each user.

Most of the properties for each user name display next to the user name. For a complete list of

properties for a user, select a user name and click Properties (see Editing User Name Properties

on page 36).

Reviewing User Names 35


36/182

Figure 13 User Names

Searching for User Names

To search for a user name:

1 ClickSearch.2 Define how to conduct the search in the Search dialog box and clickSearch 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 clickProperties or double-click the user name.The Properties dialog box displays.



37/182

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

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 MappingWhen you run the Reporting and Analysis Migration Utility, it queries the source system for

users and attempts to automatically map them to existing Shared Services users based on the

following criteria:

login ID

email address

first name/last name

If a mapping cannot be made, then during migration, the Reporting and Analysis Migration

Utility creates a new native user.

You can view these mappings on the User Names screen and manually adjust or change themappings as necessary. For example, to map a Portal user name to a different Shared Services

user name, you would select the user name, click Properties, and change the Shared Services user

name in the Properties dialog box.

Reviewing User Names 37


38/182

Setting the Migration ActionFor each user, you can set the migration action property toMigrate 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 toMigrate are

migrated to Shared Services. If you later change a users action to Do Not Migrate and perform

another migration, the Reporting and Analysis Migration Utility does not remove the

previously-migrated user from Shared Services; instead, you must delete the user directly

from Shared Services.

The default setting for inactive users is Do Not Migrate. This setting cannot be changed. To

migrate a deactivated user, you must manually activate the user in the source system before

performing the migration.

Users who are not migrated lose all access control information associated with them as well

as any assigned user properties.

Updating User Name InformationTo refresh the automatic mapping on the User Names screen, click Update Names and select

one of the following options:

Keep Changes (use new values)Validates the user names from each system and keeps any

changes made to the mapping and property information.

Discard Changes (restore original values)Retrieves the user names from each system,

discards any changes made to the mapping or properties, and restores mapping and property

information to the original values.

Reviewing Group Names

Review the group mappings and properties and set the migration action for each group.Most of the properties for each group name display next to the group name. For a complete list

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

Properties on page 39).



39/182

Figure 14 Group Names

Searching for Group Names

To search for a group name:

1 ClickSearch.2 Define how to conduct the search in the Search dialog box and clickSearch again.

The group names that meet the search criteria display. After you search for a group name, you

can display all the group names again by clicking Show All.

Editing Group Name Properties

To edit group name properties:

1 Select the desired group name and clickProperties or double-click the group name.The Properties dialog box displays.

Reviewing Group Names 39


40/182

The group name properties from both systems (source and target) are displayed. Some properties

are read-only and some can be edited.

2 Edit the desired properties and clickOK.If the group is set to Do Not Migrate, you cannot edit any of the properties in the Shared ServicesGroup section of the dialog box.

Verifying Group Name MappingWhen you run the Reporting and Analysis Migration Utility, it queries the source system for

groups and attempts to automatically map them to existing Shared Services groups based on the

group name.

If a mapping cannot be made, then during migration, the Reporting and Analysis Migration

Utility creates a new native group. You can view these mappings on the Group Names screen

and manually adjust or change the mappings as necessary.

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

select the group name, click Properties, and change the Shared Services group name in the

Properties dialog box.

Setting the Migration ActionFor each group, you can set the Action property toMigrate 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:



41/182

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 toMigrate 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 toMigrate forall users and groups thathave 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 toMigrate. This

ensures that group-to-group associations migrate correctly.

Adding Users/Groups Assigned in Portal to the Native SharedServices 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 clickSelect 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 InformationIf you wish to refresh the automatic mapping on the Group Names screen, click Update

Names and select one of the following options:

Keep Changes (use new values)Validates the group names from each system and keeps

any changes made to the mapping and property information.

Discard Changes (restore original values)Retrieves the group names from each system,

discards any changes made to the mapping or properties, and restores mapping and property

information to the original values.

Mapping HostsDefine the mapping for the Portal hosts and the Reporting and Analysis Repository hosts. For

example, you must map each source job factory to a new Reporting and Analysis Repository

host.

Mapping Hosts 41


42/182

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 OptionsSelect additional Portal options to provide advanced control of the migration process.



43/182

Figure 16 Additional Migration Options

Table 13 Additional Migration Options

Authorization Define how to translate the Write access control in Portal by selecting one of the following

options:

Modify in the Reporting and Analysis RepositorySelect this option to map "Write"

or "Write and Execute" to the "Modify" access control.

Full Control in the Reporting and Analysis RepositorySelect this option to map

"Write" or "Write and Execute" to the Full Control access control.

In Portal 7.x, you could delete an object if you had permission to write to the object.

The Write permission in 7.x maps to the Modify role in the Reporting and Analysis

Repository, which does not allow deletion. As a result, if you want permission to delete

an object in the Reporting and Analysis Repository, you must map the version 7.x Write

or Write and Execute permissions to the Reporting and Analysis RepositoryFull

Control role.

SelectSetup 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 pathor click Browse to select a path.

Repository Job Factory If you plan to migrate Oracle's Hyperion SQR Production Reporting System 9 files,define the version of the files in the Reporting and Analysis Repository. For example, enter

Version 8.3 as 83, Version 9.0 as 90, and so on.

Defining Additional Migration Options 43


44/182

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

Running the MigrationThe final screen of the Reporting and Analysis Migration Utility Wizard allows you to review

the objects selected to migrate, to run a test migration that will help determine any migration

issues, and to run the actual migration.

It is strongly recommended that you run a pre-migration process before completing an actual

migration. During a pre-migration test, the Reporting and Analysis Migration Utility goes

through the migration process without actually moving objects from the source system to the

target system. If the Reporting and Analysis Migration Utility finds any problems, it reports

them in the log files. You should fix any potential errors encountered in the pre-migration

process before performing an actual migration. Unless addressed, errors may cause the actual

migration to stop or remain incomplete.

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

After you complete the pre-migration test and fix all the outstanding errors, it is recommended

that you migrate each object type separately and check to ensure that the object migrated

correctly before migrating the next object. Note, however, that you must migrate the objects in

the order shown in the wizard.

To migrate each object type separately:

1 Select the desired object type.

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

would select Groups.2 Select Perform Migration as the Run Mode and clickStart.3 Check to make sure the object migrated correctly and fix any errors.

4 Backup your target database (and your OpenLDAP database if you are migrating users and groups.)

This step is optional. As an extra precaution, you may want to backup the target database after

you successfully migrate each object type. When you migrate users and groups, you should also

backup the OpenLDAP database. (The Reporting and Analysis Migration Utility updates both

the target database and the OpenLDAP database.)

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

Note:

After you complete the migration, you must re-compile all your SQR Production Reporting

jobs.



45/182

Figure 17 Run Migration

Table 14 Run Migration Options

Select the Objects to Migrate Review the objects selected to migrate. The objects that are enabled are the objectsselected on the Select Objects to Migrate screen earlier in the wizard (see Selecting

the Objects to Migrate on page 26).

Note: It is strongly recommended that you migrate each object type separately andcheck to ensure that the object type migrated correctly before migrating the next

object.

Run Mode Select one of the following options:

Test OnlyRuns a pre-migration process to help identify any migration issues.

Perform MigrationRuns the actual migration.

Note: You should fix any potential errors encountered in the pre-migration processbefore 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 45


46/182



47/182

3 Migrating from BrioONEIn This Chapter

About Migrating from BrioOne ..... ..... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ..47

Running the Brio Portal Migration ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ......47

Running the OnDemand Server Migration ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...... ...... ..... ...... ..... ...48

About Migrating from BrioOneUse the BrioONE option in the Reporting and Analysis Migration Utility Wizard to migrate

users, groups, roles, and repository content from a BrioONE installation to Shared Services and

the Reporting and Analysis Repository.

BrioONE consists of the following components:

Brio Portal 7.0.5 or later

OnDemand Server 6.6.4 or later

When you run a BrioONE migration, you can migrate both Brio Portal information and

OnDemand Server information. Checking both options on the Welcome screen directs the

Reporting and Analysis Migration Utility to run the Portal steps in the wizard followed directly

by the OnDemand Server steps in the wizard. If desired, you can run the Portal and OnDemand

Server wizard steps separately; however, you mustrun 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 MigrationTo run Brio Portal information following directly by OnDemand Server information, select

BrioONE on the Welcome screen (this checks both the Portal and the OnDemand Serveroptions).

To run the Brio Portal wizard steps separately, select the Portal option under BrioONE.

After you have selected a migration path and entered logging details, running the Brio Portal

migration involves:

Defining the Database Used by the Portal Repository

About Migrating from BrioOne 47


48/182

Defining the Location of the Portal Repository Database

Identifying Portal Groups with Circular References

Selecting the Objects to Migrate

Defining Reporting and Analysis Database Information

Defining the Location of the Reporting and Analysis Repository Database

Defining the Location of the Shared Services Server

Defining User/Group Names, Descriptions and Passwords

Reviewing User Names

Reviewing Group Names

Mapping Hosts

Defining Additional Migration Options

Running the Migration

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

from Brio Portal.

Running the OnDemand Server MigrationBefore you migrate OnDemand Server information, make sure that you have already migrated

Brio Portal information.

If you already ran the Portal migration and exited from the wizard, you can start the

OnDemand Server migration by checking the OnDemand Server option under BrioOne.

If you selected both Portal and OnDemand Server under BrioOne on the Welcome screen,

the OnDemand Server wizard screens automatically appear after the Portal wizard screens.After you have selected a migration path and entered logging details, running the OnDemand

Server migration involves:

Defining the Database Used by the OnDemand Server Repository on page 49

Defining the Location of the OnDemand Server Repository Database on page 50

Defining the Location of the OnDemand Server Installation Files on page 53

Selecting the Objects to Migrate on page 54

Defining Target Row Level Security Repository Database Information on page 56

Defining the Location of the Target Row Level Security Repository Database on page

57

Defining Reporting and Analysis Database Information on page 60

Defining the Location of the Reporting and Analysis Database on page 61

Defining the Location of the Reporting and Analysis Repository Server on page 64

Defining the Location of the Shared Services Server on page 65

48 Migrating from BrioONE


49/182

Defining User/Group Names, Descriptions, and Passwords on page 66

Reviewing User Names on page 67

Reviewing Group Names on page 70

Running the Migration on page 74

Defining the Database Used by the OnDemand ServerRepositoryDefine which database contains the OnDemand Server source repository and select how to

specify the database location.

Figure 18 Database Used by the OnDemand Server Repository


Database Type Select one of the following databases.

SQL Server

Oracle

DB2

Informix

Running the OnDemand Server Migration 49


50/182

Sybase

Redbrick

Note: If your source system is instal led 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.




driver information.


Defining the Location of the OnDemand Server RepositoryDatabaseDefine 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 TestConnection to test the connection to the database.

Location of OnDemand Server Repository Database Defined by Host andName

If you specified Host and Name on the previous screen in the wizard (see Defining the Database

Used by the OnDemand Server Repository on page 49), enter the information discussed in

Table 16.

50 Migrating from BrioONE


51/182

Figure 19 Location of OnDemand Server Repository Database Defined by Host and Name


Host Enter the name of the database host.

Port Enter the database port number.

Database Name Enter the name of the database.



Owner Enter the table owner/schema name. In most cases, the owner is the same as the databaseusername.

Location of OnDemand Server Repository Database Defined by JDBC Driverand URL

If you specified a JDBC Driver and URL on the previous s

Documents

Hs Migration