HYPERION® SYSTEM™ 9 BI+™ - Oracle · PDF filehyperion® system™ 9...

H Y P E R I O N ® S Y S T E M ™ 9 B I + ™

FINANCIAL REPORTING™ , INTERACTIVE REPORTING,

PRODUCTION REPORTING, WEB ANALYSIS

R E L E A S E 9 . 2

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

Copyright 2002–2006 Hyperion Solutions Corporation. All rights reserved.

“Hyperion,” the Hyperion logo, and Hyperion’s product names are trademarks of Hyperion. References to other companies and their products use trademarks owned by the respective companies and are for reference purpose only.

No portion hereof may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the recipient’s personal use, without the express written permission of Hyperion.

The information contained herein is subject to change without notice. Hyperion shall not be liable for errors contained herein or consequential damages in connection with the furnishing, performance, or use hereof.

Any Hyperion software described herein is licensed exclusively subject to the conditions set forth in the Hyperion license agreement.

Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Hyperion license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable.

Hyperion Solutions Corporation 5450 Great America Parkway Santa Clara, California 95054

Printed in the U.S.A.

Contents iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Where to Find Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Help Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Additional Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Education Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Consulting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

CHAPTER 1 Overview and Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Overview of the Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Migration Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

What Happens During Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Prerequisites for Using the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Other Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Special Symbols in Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

SmartCuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

CHAPTER 2 Migrating from Brio Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

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

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

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

Identifying Portal Groups with Circular References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

iv Contents

Defining Hyperion System 9 BI+ Repository Database Information . . . . . . . . . . . . . . . . . . . . 33

Defining the Location of the Hyperion System 9 BI+ Repository Database . . . . . . . . . . . . . . 34

Location of Hyperion System 9 BI+ Repository Database Defined by Host and Name . . 34

Location of Hyperion System 9 BI+ Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

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

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

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

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

Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

CHAPTER 3 Migrating from BrioONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Running the Brio Portal Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

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

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

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

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

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

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

Defining Hyperion System 9 BI+ Repository Database Information . . . . . . . . . . . . . . . . 63

Defining the Location of the Hyperion System 9 BI+ Repository Database . . . . . . . . . . . 64

Defining the Location of the Hyperion System 9 BI+ Repository Server . . . . . . . . . . . . . 66

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

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

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Contents v

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

Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Running the Broadcast Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

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

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

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

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

Defining Hyperion System 9 BI+ Repository Database Information . . . . . . . . . . . . . . . . . 86

Defining the Location of the Hyperion System 9 BI+ Repository Database . . . . . . . . . . . 87

Defining the Location of the Hyperion System 9 BI+ Repository Server . . . . . . . . . . . . . . 89

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

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

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

CHAPTER 5 Migrating from Hyperion Analyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

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

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

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

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

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Defining Hyperion System 9 BI+ Repository Database Information . . . . . . . . . . . . . . . . . . . 108


Location of Hyperion System 9 BI+ Repository Database Defined by Host and Name . 109



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



Editing User Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115


Setting the Migration Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116


Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117


Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

vi Contents


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

Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

CHAPTER 6 Migrating from Hyperion Performance Suite 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123


Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

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

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

Location of Hyperion Performance Suite Repository Database by Host and Name . . . 127

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

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

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130


Defining the Location of the Hyperion System 9 BI+ Repository Database . . . . . . . . . . . . . 132

Location of Hyperion System 9 BI+ Repository Database Defined by Host and Name 132

Location of Hyperion System 9 BI+ Repository Database Defined by JDBC Driver and URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

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

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

Reviewing User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Searching for User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138


Verifying User Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139


Updating User Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Editing Group Name Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142


Adding Users/Groups Assigned in Hyperion Performance Suite to the Native Shared Services Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Defining Additional Migration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145


Contents vii

CHAPTER 7 Migrating from Hyperion Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149


Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Entering Logging Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

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

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

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

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

Defining the Hyperion Reports Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Selecting the Objects to Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156



Location of Hyperion System 9 BI+ Repository Database Defined by Host and Name . 158


Defining the Location of the Hyperion System 9 BI+ Repository Server . . . . . . . . . . . . . . . . 160


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







Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Searching for Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167


Verifying Group Name Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168


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

Updating Group Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169


Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

viii Contents

Preface ix

Preface

Welcome to the Hyperion System 9 BI+ Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis Migration Guide. This preface discusses the following topics:

● “Purpose” on page ix

● “Audience” on page x

● “Document Structure” on page x

● “Where to Find Documentation” on page xi

● “Help Menu Commands” on page xi

● “Conventions” on page xii

● “Additional Support” on page xiii

● “Documentation Feedback” on page xiii

PurposeThis guide provides information that you need to migrate users, groups, roles, and repository content from the following products to Hyperion System 9 Shared Services™ and Hyperion System 9 BI+™ Repository. Hyperion supports migration from the following product versions:

● Brio Portal™ 7.0.5 or later

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

● Brio Intelligence Server™ (Brio OnDemand Server™ and Brio 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™ 2.6, 2.6.1, 7.0, 7.0.1, 7.2, or 7.2.1

x Preface

AudienceThis guide is for administrators responsible for understanding the migration process. The guide assumes familiarity with products, distributed computing environments and terminology, server management, Web servers and servlet engines, and the Microsoft Windows or UNIX operating system or both.

Document StructureThis document contains the following information:

Chapter 1, “Overview and Prerequisites,” describes tasks that must be completed for the Migration Utility to run properly, regardless of system configuration or content migrated.

Chapter 2, “Migrating from Brio Portal,” describes how to migrate users, groups, roles, and repository content from a Brio Portal 7.0.5 or later installation to Shared Services and the Hyperion System 9 BI+ Repository.

Chapter 3, “Migrating from BrioONE,” describes how to migrate users, groups, roles, and repository content from a BrioONE installation to Shared Services and the Hyperion System 9 BI+ Repository.

Chapter 4, “Migrating from the Brio Intelligence Server,” describes how to migrate users, groups, roles, and repository content from a Brio Intelligence Server installation to Shared Services and the Hyperion System 9 BI+ Repository.

Chapter 5, “Migrating from Hyperion Analyzer,” describes how to migrate users, groups, roles, and repository content from a Hyperion Analyzer 6.5, 7.0.1, 7.2, or 7.2.1installation to Shared Services and the Hyperion System 9 BI+ Repository.

Chapter 6, “Migrating from Hyperion Performance Suite 8,” describes how to migrate users groups, roles, and repository content from a Hyperion Performance Suite 8.x installation to Shared Services and the Hyperion System 9 BI+ Repository.

Chapter 7, “Migrating from Hyperion Reports,” describes how to migrate users, groups, roles, and repository contents from a Hyperion Reports 2.6, 2.6.1, 7.0, 7.0.1, 7.2, or 7.2.1 installation to Shared Services and the Hyperion System 9 BI+ Repository.

Index contains a list of terms and their page references.

Help Menu Commands xi

Where to Find DocumentationAll Migration Utility documentation is accessible from the following locations:

● The HTML Information Map is available from the Migration Utility Help menu for all operating systems; for products installed on Microsoft Windows systems, it is also available from the Start menu.

● Online help is available from within the Migration Utility. After you log on to the product, you can access online help by clicking the Help button or selecting Help from the menu bar.

● The Hyperion Download Center can be accessed from the Hyperion Solutions Web site.

➤ To access documentation from the Hyperion Download Center:

1 Go to the Hyperion Solutions Web site and navigate to Services > WorldWide Support > Download Center.

Note: Your Login ID for the Hyperion Download Center is your e-mail address. The Login ID and Password required for the Hyperion Download Center are different from the Login ID and Password required for Hyperion Support Online through Hyperion.com. If you are not sure whether you have a Hyperion Download Center account, follow the on-screen instructions.

2 In the Login ID and Password text boxes, enter your e-mail address and password.

3 In the Language list box, select the appropriate language and click Login.

4 If you are a member on multiple Hyperion Solutions Download Center accounts, select the account that you want to use for the current session.

5 To access documentation online, from the Product List, select the appropriate product and follow the on-screen instructions.

Help Menu CommandsTable i describes the commands that are available from the Help menu in the Migration Utility.

Table i Help Menu Commands

Command Description

Help on This Topic Launches a help topic specific to the window or Web page.

Contents Launches the Migration Utility help.

Information Map Launches the Migration Utility Information Map, which provides the following assistance:

● Online help in PDF and HTML format

● Links to related resources to assist you in using the Migration Utility

Technical Support Launches the Hyperion Technical Support site, where you submit defects and contact Technical Support.

xii Preface

ConventionsThe following table shows the conventions that are used in this document:

Hyperion Developer’s Network

Launches the Hyperion Developer Network site, where you access information about known defects and best practices. This site also provides tools and information to assist you in getting starting using Hyperion products:

● Sample models

● A resource library containing FAQs, tips, and technical white papers

● Demos and Webcasts demonstrating how Hyperion products are used

Hyperion.com Launches Hyperion’s corporate Web site, where you access a variety of information about Hyperion:

● Office locations

● The Hyperion Business Intelligence and Business Performance Management product suite

● Consulting and partner programs

● Customer and education services and technical support

About the Migration Utility Launches the About the Migration Utility dialog box, which contains copyright and release information, along with version details.

Table ii Conventions Used in This Document

Item Meaning

Arrows indicate the beginning of procedures consisting of sequential steps or one-step procedures.

Brackets [ ] In examples, brackets indicate that the enclosed elements are optional.

Bold Bold in procedural steps highlights user interface elements on which the user must perform actions.

CAPITAL LETTERS Capital letters denote commands and various IDs. (Example: CLEARBLOCK command)

Ctrl+0 Keystroke combinations shown with the plus sign (+) indicate that you should press the first key and hold it while you press the next key. Do not type the plus sign.

Ctrl+Q, Shift+Q For consecutive keystroke combinations, a comma indicates that you press the combinations consecutively.

Example text Courier font indicates that the example text is code or syntax.

Courier italics Courier italic text indicates a variable field in command syntax. Substitute a value in place of the variable shown in Courier italics.

ARBORPATH When you see the environment variable ARBORPATH in italics, substitute the value of ARBORPATH from your site.

n, x Italic n stands for a variable number; italic x can stand for a variable number or a letter. These variables are sometimes found in formulas.

Table i Help Menu Commands (Continued)

➤

Documentation Feedback xiii

Additional SupportIn addition to providing documentation and online help, Hyperion offers the following product information and support. For details on education, consulting, or support options, click the Services link at the Hyperion Solutions Web site.

Education ServicesHyperion offers instructor-led training, custom training, and e-Learning covering all Hyperion applications and technologies. Training is geared to administrators, end users, and information systems professionals.

Consulting ServicesExperienced Hyperion consultants and partners implement software solutions tailored to clients’ particular reporting, analysis, modeling, and planning requirements. Hyperion also offers specialized consulting packages, technical assessments, and integration solutions.

Technical SupportHyperion provides enhanced telephone and electronic-based support to clients to resolve product issues quickly and accurately. This support is available for all Hyperion products at no additional cost to clients with current maintenance agreements.

Documentation FeedbackHyperion strives to provide complete and accurate documentation. Your opinion on the documentation is of value, so please send your comments by going to http://www.hyperion.com/services/support_programs/doc_survey/index.cfm.

Ellipses (...) Ellipsis points indicate that text has been omitted from an example.

Mouse orientation This document provides examples and procedures using a right-handed mouse. If you use a left-handed mouse, adjust the procedures accordingly.

Menu options Options in menus are shown in the following format. Substitute the appropriate option names in the placeholders, as indicated.

Menu name > Menu command > Extended menu command

For example: 1. Select File > Desktop > Accounts.

Table ii Conventions Used in This Document (Continued)

Item Meaning

http://www.hyperion.com/services/support_programs/doc_survey/index.cfm

xiv Preface

Overview and Prerequisites 15

C h a p t e r

1Overview and Prerequisites

This chapter providesReview the following topics for an overview of the migration process and discusses the prerequisites for using the Migration Utility.

Note: When using the Migration Utility, screen resolutions set to 800x600 or lower are not supported.

In This Chapter Overview of the Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Prerequisites for Using the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Other Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

16 Overview and Prerequisites

Overview of the Migration ProcessMigration involves migrating information from the source system to Shared Services and the Hyperion System 9 BI+ Repository. Review the following sectionstopics for information on the migration process.

● Migration Components

● What Happens During Migration

Migration ComponentsEach 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 2.6, 2.6.1, 7.0, 7.0.1, 7.2, or 7.2.1

● Shared Services—Defines both external users and groups in external directory systems, and native users maintained in an Open LDAP database.

● Hyperion System 9 BI+ Repository—Stores information about the mapping between the users and groups in the source system and the users and groups in Shared Services.

What Happens During MigrationMigration involves users, groups, roles, and repository content. Review the following sectionstopics for information on migrating each of these objects.

● “Migrating Users and Groups” on page 16

● “Migrating Roles” on page 17

● “Migrating Repository Content” on page 20

Migrating Users and GroupsDuring 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 Hyperion System 9 BI+ 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.

Overview of the Migration Process 17

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 Hyperion System 9 BI+ 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 the Shared Services can login. If you want only a subset of the users to be able to login, do not provision the World group.

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

Note: For detailed information about roles and user provisioning, see the Hyperion System 9 BI+ Shared Services User Management Guide.

Migrating RolesDuring 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 Hyperion System 9 BI+ roles based on this mapping. When you migrate user-defined roles, new roles are created in Shared Services.

Table 3 correlates the legacy roles to the new Hyperion System 9 BI+ roles. For additional information on the roles in Hyperion System 9 BI+, see Appendix B, “Hyperion System 9 BI+ Roles” in the Hyperion System 9 BI+ Shared Services User Management Guide.


Table 3 Mapping from legacy Roles to New Roles in Hyperion System 9 BI+

Old Role Name New Role Name Notes

Administrator BI+ Administrator Also maps to Shared Services Directory Manager and Provisioning Manager.

Browser Explorer

Content Administrator Content Manager

Content Publisher Content Publisher

Event Services Administrator Deprecated. Map to Schedule Manager.

Global Administrator BI+ Global Administrator Also maps to Shared Services Directory Manager and Provisioning Manager.

Group Administrator Deprecated. Map to Shared Services Directory Manager.

Group Locator Deprecated. Map to Explorer.

iHTML Viewer Deprecated. Map to Interactive Reporting Viewer.

Intelligence Analyzer Analyst

Intelligence Dynamic Viewer, Quickview

Deprecated. Map to Dynamic Viewer.

Intelligence Viewer,

Freeview

Deprecated. Map to Interactive Reporting Viewer.

Job Administrator Job Manager

Job Publisher Job Publisher

Job Runner Job Runner

Job Scheduler Scheduler

MIME Type Administrator Deprecated. Map to BI+ Administrator.

Name Service Administrator Deprecated. Map to BI+ Administrator

OCE Publisher Data Source Publisher

Organizational Administrator Deprecated. Map to Shared Services Directory Manager and Provisioning Manager.

Personal Page Personal Page Editor

Personal Page Publisher Personal Page Publisher

Physical Resource Administrator

Deprecated. Map to Job Manager.

Related Content Viewer Deprecated.

Overview of the Migration Process 19

Role Administrator Deprecated. Map to Shared Services Provisioning Manager.

Role Locator Deprecated. Map to Explorer.

Schedule Administrator Schedule Manager

Session Administrator Deprecated. Map to BI+ Administrator.

System Crawler Deprecated. Map to Trusted Application.

System Viewer Deprecated. Map to Explorer.

Trusted Application Trusted Application

User Deprecated. Map to Explorer and Personal Page Editor.

User Administrator Deprecated. Map to Directory Manager.

User Locator Deprecated. Map to Explorer.

View Manager Viewer

View Manager Administrator Deprecated. Map to Viewer.

View Manager Content Pusher

Favorites Distributor

Analyzer Administrator Deprecated. Map to BI+ Global Administrator.

Analyzer Custom Custom Aggregated Role. Repurposed.

Analyzer Power User Advanced Document Editor

Analyzer Information Consumer

Deprecated. Map to Information Consumer

Analyzer Interactive User Document Editor

Analyzer Create Reports Deprecated. Map to Document Editor.

Analyzer Create POV Deprecated. Map to Personal Parameters Editor.

Analyzer Create Links Deprecated

Analyzer Design Custom Reports

Deprecated. Map to Advanced Document Editor.

Analyzer Save Reports Deprecated. Map to Content Publisher.

Analyzer Edit Data Data Editor

Analyzer Administer Users and Groups

Deprecated. Map to BI+ Global Administrator.

Table 3 Mapping from legacy Roles to New Roles in Hyperion System 9 BI+ (Continued)



Migrating Repository ContentAll repository content/metadata is migrated from the source system to the Hyperion System 9 BI+ Repository.

Analyzer Print Reports Deprecated

Analyzer Open User Preferences

Deprecated. Map to Personal Parameter Editor and Data Source Publisher.

Analyzer Manage Databases Deprecated. Map to Data Source Publisher.

Analyzer Cube Navigator Data Layout The term Cube Navigator has been removed from the UI. Changing name to Data Layout.

Analyzer Open Reports Deprecated. Map to Viewer.

Analyzer Create Personal Variables

Personal Parameter Editor

Reports Viewer Deprecated. Map to Explorer.

Reports Designer Deprecated. Facets mapped to Explorer, Content Publisher, and Scheduler.

Reports System Administrator


Reports Security Administrator


Metrics Builder Administrator Deprecated. Map to BI+ Administrator

Metrics Builder HTML End User

Metrics Viewer

Smart Form Publisher

Metrics Builder Editor Metrics Editor

Metrics Builder Java End User Metrics Analyst

Table 3 Mapping from legacy Roles to New Roles in Hyperion System 9 BI+ (Continued)


Prerequisites for Using the Migration Utility 21

Prerequisites for Using the Migration UtilityPrerequisites 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 4below.

Table 4 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 the Hyperion System 9 BI+ Workspace, choose Administrator > General, and ensure that Enable Harvesting is not selected.

● If your target system is DB2, set the LOCKTIMEOUT parameter to a finite value.

To do this, select the Hyperion System 9 BI+ 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 System 9 BI+ 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 job might run an extra time in the migrated system than it needs to run. These changes do not affect migration.


Other Migration ConsiderationsIn addition to understanding the general migration process and reviewing the migration prerequisites, review the following sectionstopics to understand how certain symbols and characters are handled during migration.

● Special Symbols in Users and Groups

● SmartCuts

Special Symbols in Users and GroupsThere 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 Hyperion System 9 BI+. If the Migration Utility encounters any of these symbols, it replaces them with an acceptable symbol. Table 5 shows the symbol in the source system and the symbol it is replaced with in Hyperion System 9 BI+.

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

❏ Hyperion Reports Complete the general prerequisites.

Table 5 Special Symbols

Symbol in Source System Symbol in Hyperion System 9 BI+

, _

= -

+ *

< [

> ]

Table 4 Prerequisites for Using the Migration Utility (Continued)

Prerequisite Type Details

Other Migration Considerations 23

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.

SmartCutsSmartCuts for object names with unsupported characters will not be displayed in the Hyperion System 9 BI+ Workspace after migration. To ensure that your SmartCuts appear in the Workspace, you should update any SmartCuts in your source system to use supported characters.

For information on supported characters for SmartCuts, see “Managing SmartCuts” in the Hyperion System 9 BI+ Workspace Administrator’s Guide.

( [

) ]

; :

\ /

" `

# ~

Note: The '#' symbol is replaced with the ‘~’ symbol only if the '#' symbol is in the first position.

Table 5 Special Symbols (Continued)

Symbol in Source System Symbol in Hyperion System 9 BI+

Migrating from Brio Portal 25

C h a p t e r

2Migrating 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 Hyperion System 9 BI+ Repository. Before performing the migration, review the information in Chapter 1, “Overview and Prerequisites.”

In This Chapter Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Entering Logging Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

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

Identifying Portal Groups with Circular References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Selecting the Objects to Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Defining Hyperion System 9 BI+ Repository Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Defining the Location of the Hyperion System 9 BI+ Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

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

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

Reviewing User Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Defining Additional Migration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

26 Migrating from Brio Portal

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\Migration Utility\bin

If you are using Windows, you can also start the Migration Utility Wizard by choosing Start > Programs > Hyperion System 9 BI+ > Utilities and Administration > Migration Utility.

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

Figure 1 Welcome Screen

Entering Logging Details 27

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.

Figure 2 Logging Details

Table 6 Logging Details

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. Hyperion recommends this level for most migrations.

● 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. Hyperion 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 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 7 Database Type Information

Database Type Select one of the following databases.

● SQL Server

● Oracle

● DB2

● Informix

● Sybase

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

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

● Host and 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 29

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

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

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

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 URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Portal Repository” on page 28), enter the information discussed in Table 9.

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

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

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.




Identifying Portal Groups with Circular References 31

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 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 MigrateSelect the Portal objects to migrate. To select an object, click the checkbox next to the object.

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

Figure 7 Portal Objects to Migrate

Table 10 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 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 Hyperion System 9 BI+ 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 Hyperion System 9 BI+ Repository Database Information 33

Defining Hyperion System 9 BI+ Repository Database Information

Define which database contains the target Hyperion System 9 BI+ Repository and select how to specify the database location.

Figure 8 Database Used by the Hyperion System 9 BI+ Repository


Database Type Select one of the following databases:

● SQL Server

● Oracle

● DB2






Defining the Location of the Hyperion System 9 BI+ Repository Database

Define the location of the Hyperion System 9 BI+ 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 Hyperion System 9 BI+ Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion System 9 BI+ Repository Database Information” on page 33), enter the information discussed in Table 12.

Figure 9 Location of Hyperion System 9 BI+ Repository Database Defined by Host and Name


Host Enter the name of the Hyperion System 9 BI+ Repository database host.

Port Enter the Hyperion System 9 BI+ Repository database port number.

Database Name Enter the name of the Hyperion System 9 BI+ Repository database.

User ID Enter the database username used to set up a Hyperion System 9 BI+ Repository database connection.

Defining the Location of the Hyperion System 9 BI+ Repository Database 35

Password Enter the password for the Hyperion System 9 BI+ Repository database.


Source tables have been copied to the target database

Select this option if you manually copied your source tables to the target database.

In most cases, manually copying your source tables to the target database is much quicker than allowing the Migration Utility to copy them over a network. This is 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

Table 12 Host and Name Information (Continued)


Location of Hyperion System 9 BI+ Repository Database Defined by JDBC Driver and URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Hyperion System 9 BI+ Repository Database Information” on page 33), enter the information discussed in Table 13.

Figure 10 Location of Hyperion System 9 BI+ Repository Database Defined by JDBC Driver and URL




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.


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,

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.


Defining the Location of the Shared Services Server 37

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.

Figure 11 Location of Shared Services Server




See description in Table 12.

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

Table 13 JDBC Driver and URL Information (Continued)


Defining User/Group Names, Descriptions and PasswordsDefine how to treat user descriptions, group names, passwords, and authentication when creating new users in Shared Services.

Figure 12 User/Group Descriptions and Passwords

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

Defining User/Group Names, Descriptions and Passwords 39

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.

Table 15 Information on User/Group Descriptions and Passwords (Continued)


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

Reviewing User Names 41

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 MappingWhen 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 ActionFor 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 InformationIf 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 43

Reviewing Group NamesReview 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 44).

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.


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

Setting the Migration ActionFor 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 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 Hyperion System 9 BI+ Repository hosts. For example, you must map each source job factory to a new Hyperion System 9 BI+ Repository host.

Figure 15 Host Mapping

➤ To map a host, select a Portal Host and a Hyperion System 9 BI+ 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 47

Defining Additional Migration OptionsSelect additional Portal options to provide advanced control of the migration process.

Figure 16 Additional Migration Options

Table 16 Additional Migration Options

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

● Modify in the Hyperion System 9 BI+ Repository—Select this option to map "Write" or "Write and Execute" to the "Modify" access control.

● Full Control in the Hyperion System 9 BI+ 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 Hyperion System 9 BI+ Repository, which does not allow deletion. As a result, if you want permission to delete an object in the Hyperion System 9 BI+ Repository, you must map the version 7.x “Write” or “Write and Execute” permissions to the Hyperion System 9 BI+ Repository “Full Control” role.

Select Setup job publishing mask group permissions to use job group publishing masks when migrating jobs to the Hyperion System 9 BI+ Repository. Publishing masks are permissions that the output gets when it runs in the Hyperion System 9 BI+ 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.

Repository Job Factory If you plan to migrate Production Reporting files, define the version of the files in the Hyperion System 9 BI+ 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 MigrationThe 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, Hyperion 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.


Running the Migration 49

Figure 17 Run Migration

Table 17 Run Migration Options

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

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

Migrating from BrioONE 51

C h a p t e r

3Migrating 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 Hyperion System 9 BI+ 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 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.”

In This Chapter Running the Brio Portal Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

52 Migrating from BrioONE

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

● Defining the Location of the Portal Repository Database

● Identifying Portal Groups with Circular References

● Selecting the Objects to Migrate

● Defining Hyperion System 9 BI+ Repository Database Information

● Defining the Location of the Hyperion System 9 BI+ 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 53

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 54

● “Defining the Location of the OnDemand Server Repository Database” on page 55

● “Defining the Location of the OnDemand Server Installation Files” on page 57

● “Selecting the Objects to Migrate” on page 58

● “Defining Target Row Level Security Repository Database Information” on page 60

● “Defining the Location of the Target Row Level Security Repository Database” on page 61

● “Defining Hyperion System 9 BI+ Repository Database Information” on page 63

● “Defining the Location of the Hyperion System 9 BI+ Repository Database” on page 64

● “Defining the Location of the Hyperion System 9 BI+ Repository Server” on page 66

● “Defining the Location of the Shared Services Server” on page 67

● “Defining User/Group Names, Descriptions, and Passwords” on page 68

● “Reviewing User Names” on page 69

● “Reviewing Group Names” on page 72

● “Running the Migration” on page 75


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



● SQL Server

● Oracle

● DB2

● Informix

● Sybase

● Redbrick







Defining the Location of the OnDemand Server Repository DatabaseDefine the connection to the OnDemand Server repository database on your existing system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information, click Test Connection to test the connection to the database.

Location of OnDemand Server Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the OnDemand Server Repository” on page 54), enter the information discussed in Table 19.

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







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 URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the OnDemand Server Repository” on page 54), enter the information discussed in Table 20.

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




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.


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,



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 FilesEnter the location of the ODS.ini file and the ODS.pwd file.

Figure 21 OnDemand Server Installation Files

Table 21 OnDemand Server Installation Files

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 Server

Select this option if you are running the migration utility from a machine other than the source system. If running on a machine other than the source, enter the following information:

● Mapped OCE 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.

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


Selecting the Objects to MigrateSelect 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


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.


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.

Table 22 OnDemand Server Objects to Migrate (Continued)


Defining Target Row Level Security Repository Database InformationDefine which database contains the target Row Level Security Repository and select how to specify the database location.

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

Figure 23 Database Used by the Target Row Level Security Repository


Database Type Select one of the following database drivers:

● SQL Server

● Oracle

● DB2






Defining the Location of the Target Row Level Security Repository DatabaseDefine the location of the Row Level Security Repository database on the target system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information, click Test Connection to test the connection to the database.

Location of Target Row Level Security Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining Hyperion System 9 BI+ Repository Database Information” on page 63), enter the information discussed in Table 24.

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


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.



Location of Target Row Level Security Repository Database Defined by JDBC Driver and URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining Hyperion System 9 BI+ Repository Database Information” on page 63), enter the information discussed in Table 25.

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




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.


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,

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.



Defining Hyperion System 9 BI+ Repository Database InformationDefine which database contains the target Hyperion System 9 BI+ Repository and select how to specify the database location.




● SQL Server

● Oracle

● DB2






Defining the Location of the Hyperion System 9 BI+ Repository DatabaseDefine the location of the Hyperion System 9 BI+ 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.







User ID Enter the username used to set up a Hyperion System 9 BI+ Repository database connection.



Defining the Location of the Hyperion System 9 BI+ Repository ServerDefine the connection to the Hyperion System 9 BI+ Repository Server on the target system. After you enter the requested information, click Test Connection to test the connection to the server.

Figure 29 Location of Target Hyperion System 9 BI+ Repository Server

Table 29 Hyperion System 9 BI+ Repository Server Information

Host Enter the name of the Hyperion System 9 BI+ Repository Server host.

Port Enter the Hyperion System 9 BI+ 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







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




● Same Group Name—Migrates the native Intelligence group name to a native Shared Services group name and keeps the group name the same.

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


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







1 Click Search.








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



Verifying User Name MappingWhen 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


If a mapping cannot be made, then during migration, the migration utility creates a new native user.

You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. For example, to map an Intelligence user name to a different Shared Services user name, you would select the user name, click Properties, and change the Shared Services user name in the Properties dialog box.




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

● When you perform a migration, all new native users whose action is set to Migrate are migrated to the target Shared Services. If you later change a user’s action to Do Not Migrate and perform another migration, the migration utility does not remove the previously-migrated user from target Shared Services system; instead, you must delete the user directly from the target Shared Services.








Most of the properties for each group name display next to the group name. For a complete list properties for a group, select a group name and click Properties (see “Editing Group Name Properties” on page 73).




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.

Verifying Group Name MappingWhen you run the migration utility, it queries the source system for groups and attempts to automatically map them to existing Shared Services groups based on the group name.

If a mapping cannot be made, then during migration, the migration utility creates a new native group. You can view these mappings on the Group Names screen and manually adjust or change the mappings as necessary.

For example, to map an 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.




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.





Running the MigrationThe 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 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 would select Groups.






Migrating from the Brio Intelligence Server 77

C h a p t e r

4Migrating 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 to Shared Services and the Hyperion System 9 BI+ 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.”

In This Chapter Running the OnDemand Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Running the Broadcast Server Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

78 Migrating from the Brio Intelligence Server

Running the OnDemand Server MigrationTo run OnDemand Server information following directly by Broadcast Server information, select Brio Intelligence Server on the Welcome screen (this checks both the OnDemand Server and the Broadcast Server options).

To run the OnDemand Server wizard steps separately, select the OnDemand Server option under Brio Intelligence Server.

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

● Defining the Database Used by the OnDemand Server Repository

● 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 Hyperion System 9 BI+ Repository Database Information

● Defining the Location of the Hyperion System 9 BI+ Repository Database

● Defining the Location of the Hyperion System 9 BI+ 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 53 for detailed information on migrating information from the OnDemand Server.

Running the Broadcast Server Migration 79

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

● If you already ran the OnDemand Server migration and exited from the wizard, you can start the Broadcast Server migration by checking the Broadcast Server option under Brio Intelligence Server.

● If you selected both OnDemand Server and Broadcast Server under Brio Intelligence Server on the Welcome screen, the Broadcast Server wizard screens automatically appear after the OnDemand Server wizard screens.

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

● “Defining the Database Used by the Broadcast Server Repository” on page 80

● “Defining the Location of the Broadcast Server Repository Database” on page 81

● “Defining the Broadcast Server Name and the Location of the Broadcast Server Initialization File” on page 83

● “Selecting the Objects to Migrate” on page 84

● “Defining Hyperion System 9 BI+ Repository Database Information” on page 86

● “Defining the Location of the Hyperion System 9 BI+ Repository Database” on page 87

● “Defining the Location of the Shared Services Server” on page 90

● “Defining User/Group Descriptions and Passwords” on page 91

● “Reviewing User Names” on page 92

● “Reviewing Group Names” on page 95

● “Running the Migration” on page 98


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



● 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. If your source system is installed on DB2 version 8.x, you can use data direct drivers.






Defining the Location of the Broadcast Server Repository DatabaseDefine the connection to the Broadcast Server repository database on your existing system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information, click Test Connection to test the connection to the database.

Location of Broadcast Server Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Broadcast Server Repository” on page 80), enter the information discussed in Table 34.

Figure 36 Location of Broadcast Server Repository Database Defined by Host and Name









Location of Broadcast Server Repository Database Defined by JDBC Driver and URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Broadcast Server Repository” on page 80), enter the information discussed in Table 36.

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


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







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 FileEnter the name of the Broadcast Server and the location of the Broadcast Server initialization file (BQServ1.ini).

Figure 38 Broadcast Server Configuration

Table 36 Broadcast Server Configuration Information

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 Server

Select this option if you are running the migration utility from a machine other than the source system. If you select this option, enter the mapped job storage path and enter the following information:

● 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 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:\Program Files\Brio\Brio Intelligence Server\BCS_Jobs on the source system.


Selecting the Objects to MigrateSelect 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 37 Broadcast Server Objects to Migrate

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.

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 if you want the job to run in the background. If you leave the Job Category on Target field empty, jobs are migrated to the root.

Table 37 Broadcast Server Objects to Migrate (Continued)


Defining Hyperion System 9 BI+ Repository Database InformationDefine which database contains the target Hyperion System 9 BI+ Repository and select how to specify the database location.




● SQL Server

● Oracle

● DB2






Defining the Location of the Hyperion System 9 BI+ Repository DatabaseDefine the location of the Hyperion System 9 BI+ Repository database on the target system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information, click Test Connection to test the connection to the database.










Defining the Location of the Hyperion System 9 BI+ Repository ServerDefine the connection to the Hyperion System 9 BI+ Repository Server on the target system. After you enter the requested information, click Test Connection to test the connection to the server.

Figure 43 Location of Target Hyperion System 9 BI+ Repository Server

Table 41 Hyperion System 9 BI+ Repository Server Information



User ID Enter the username of a user with Global Administrator, Directory Manager, and Provisioning Manager roles.








User ID Enter the login ID for the user in Shared Services.



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




● Same Group Name—Migrates the native Intelligence group name to a native Shared Services group name and keeps the group names the same.

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


● Auto-generated

● Same as user ID

● Other




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




1 Click Search.








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




● login ID

● email address



You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. For example, to map an Intelligence user name to a different Shared Services user name, you would select the user name, click Properties, and change the Shared Services user name in the Properties dialog box.




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




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.






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.











Migrating from Hyperion Analyzer 101

C h a p t e r

5Migrating 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.1installation to Shared Services and the Hyperion System 9 BI+ Repository. Before performing the migration, review the information in Chapter 1, “Overview and Prerequisites.”

In This Chapter Starting the Migration Utility Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Selecting a Migration Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Entering Logging Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

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

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

Selecting the Objects to Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Defining Hyperion System 9 BI+ Repository Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Defining the Location of the Hyperion System 9 BI+ Repository Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

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

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

Reviewing User Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Reviewing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Running the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

102 Migrating from Hyperion Analyzer


➤ To start the Migration Utility Wizard, click migrator.bat (Windows) or migrator.sh (UNIX) in the bin folder where you installed the migration utility.




Selecting a Migration PathSelect Hyperion Analyzer on the Welcome screen and click Next.



Defining the Database Used by the Analyzer RepositoryDefine which database contains the Analyzer source repository and select how to specify the database location.

Figure 51 Database Used by the Analyzer Repository



● SQL Server

● Oracle

● DB2

● MySQL






Defining the Location of the Analyzer Repository Database 105

Defining the Location of the Analyzer Repository DatabaseDefine the connection to the Analyzer repository database on your existing system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information, click Test Connection to test the connection to the database.

Location of Analyzer Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Analyzer Repository” on page 104), enter the information discussed in Table 47.

Figure 52 Location of Analyzer Repository Database Defined by Host and Name








Location of Analyzer Repository Database Defined by JDBC Driver and URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Analyzer Repository” on page 104), enter the information discussed in Table 48.

Figure 53 Location of Analyzer Repository Database Defined by JDBC Driver and URL











Selecting the Objects to Migrate 107

Selecting the Objects to MigrateSelect 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 54 Hyperion Analyzer Objects to Migrate

Table 49 Hyperion Analyzer Objects to Migrate

Users and Groups Users—Account owners identified by a user ID and user name.

Groups—Named collections of users.

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.








● SQL Server

● Oracle

● DB2










Port Enter the Shared ServicesServer port number.




Defining User/Group Names, Descriptions and PasswordsDefine how to treat user descriptions, group names, group descriptions, and passwords when creating new users in Shared Services.



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.




● 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


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.








1 Click Search.












● login ID

● email address



You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. For example, to map an Analyzer user name to a different Shared Services user name, you would select the user name, click Properties, and change the Shared Services user name in the Properties dialog box.




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








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




1 Click Search.













For example, to map an Analyzer group name to a different Shared Services group name, you would select the group name, click Properties, and change the Shared Services group name in the Properties dialog box.




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




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.





Running the MigrationThe final screen of the Migration Utility wizard allows you to review the objects selected to 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 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.)


Note: After you migrate repository content, re-start Hyperion System 9 BI+ Web Analysis in the servlet container.







Note: After you migrate repository content, re-start Hyperion System 9 BI+ Web Analysis in the servlet container.




Note: Test Only is only available for User and Groups in Hyperion Analyzer migrations.


Status Messages Displays informational messages about the migration.

Migrating from Hyperion Performance Suite 8 123

C h a p t e r


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 Hyperion System 9 BI+ Repository. Before performing the migration, review the information in Chapter 1, “Overview and Prerequisites.”




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

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

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








Mapping Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Defining Additional Migration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145


124 Migrating from Hyperion Performance Suite 8






Selecting a Migration PathSelect Hyperion Performance Suite 8.x on the Welcome screen and click Next.



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 65 Database Used by the Hyperion Performance Suite 8.x Repository



● SQL Server

● Oracle

● DB2






Defining the Location of the Hyperion Performance Suite Repository Database 127

Defining the Location of the Hyperion Performance Suite Repository Database

Define the connection to the Hyperion Performance Suite 8.x repository database on your existing system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information, click Test Connection to test the connection to the database.

Location of Hyperion Performance Suite Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 126), enter the information discussed in Table 58.

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








Location of Hyperion Performance Suite Repository Database Defined by JDBC Driver and URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 126), enter the information discussed in Table 59.

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




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.


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>




Identifying Hyperion Performance Suite Groups with Circular References 129

Identifying Hyperion Performance Suite Groups with Circular References

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

To search for circular references in Hyperion Performance Suite groups, click Start. If the Migration Utility finds any circular references, they appear under “Circular References Found.”

After all circular references are identified, remove the references in the source Hyperion Performance Suite system before continuing with the migration. It is important to remove circular references in Hyperion Performance Suite groups since Hyperion Performance Suite allows for circular references in groups and Shared Services does not.

➤ To remove a circular reference:

1 Select the circular reference under Circular References Found.

2 Select the relationship that contains the circular references under Select a Relationship to Remove From.

3 Click Remove Relationship and Recheck.

Figure 68 Circular References


Selecting the Objects to MigrateSelect 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 69 Hyperion Performance Suite Objects to Migrate

Table 60 User Provisioning Objects to Migrate

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.






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.



● SQL Server

● Oracle

● DB2





Table 60 User Provisioning Objects to Migrate (Continued)



Define the connection to the Hyperion System 9 BI+ 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 Hyperion System 9 BI+ Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 126), enter the information discussed in Table 62.







Note: The user must be assigned Global Administrator, Directory Manager, and Provisioning Manager roles.




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 Migration Utility to copy them over a network. This is 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

Tables Prefix Since both Hyperion Performance Suite and Hyperion System 9 BI+ 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 62 Host and Name Information (Continued)


Location of Hyperion System 9 BI+ Repository Database Defined by JDBC Driver and URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Hyperion Performance Suite Repository” on page 126), enter the information discussed in Table 63.
















See description in Table 62.

Tables Prefix Since both Hyperion Performance Suite and Hyperion System 9 BI+ 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 64 Target Shared Services Server Information





Table 63 JDBC Driver and URL Information (Continued)


Defining User/Group Names, Descriptions and PasswordsDefine how to treat user and group names, user and group descriptions, and passwords when creating new users in Shared Services.



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.



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.

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


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








1 Click Search.












● login ID

● email address



You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. For example, to map a Hyperion Performance Suite user name to a different Shared Services 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 can display all the group names again by clicking Show All.











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.




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 HostsDefine the mapping for Hyperion Performance Suite hosts and Hyperion System 9 BI+ Repository hosts. For example, you must map each source job factory to a new Hyperion System 9 BI+ Repository host.

Figure 77 Host Mapping

➤ To map a host, select a a Hyperion Performance Suite Host and a Hyperion System 9 BI+ 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 145

Defining Additional Migration OptionsSelect additional options to provide advanced control of the migration process.

Figure 78 Additional Migration Options

Table 66 Additional Migration Options

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 Hyperion System 9 BI+ Repository. For example, enter Version 8.3 as 83, Version 9.0 as 90, and so on.




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.





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

















Status Messages Displays informational messages about the migration.

Migrating from Hyperion Reports 149

C h a p t e r


Reports

Use the Hyperion Reports option in the Migration Utility Wizard to migrate users, groups, roles, and repository contents from a Hyperion Reports 2.6, 2.6.1, 7.0, 7.0.1, 7.2, or 7.2.1 installation to Shared Services and the Hyperion System 9 BI+ Repository. Before performing the migration, review the information in Chapter 1, “Overview and Prerequisites.”




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

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

Defining the Hyperion Reports Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155




Defining the Location of the Hyperion System 9 BI+ Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160






150 Migrating from Hyperion Reports






Selecting a Migration PathSelect Hyperion Reports on the Welcome screen and click Next.



Defining the Database Used by the Reports RepositoryDefine which database contains the Reports source repository and select how to specify the database location.

Figure 82 Database Used by the Reports Repository



● SQL Server

● Oracle

● DB2






Defining the Location of the Reports Repository Database 153

Defining the Location of the Reports Repository DatabaseDefine the connection to the Reports repository database on your existing system. The fields displayed vary depending on the database location specified on previous screen (Host and Name or JDBC Driver and URL). After you enter the requested information, click Test Connection to test the connection to the database.

Location of Reports Repository Database Defined by Host and Name If you specified Host and Name on the previous screen in the wizard (see “Defining the Database Used by the Reports Repository” on page 152), enter the information discussed in Table 70.

Figure 83 Location of Reports Repository Database Defined by Host and Name








Location of Reports Repository Database Defined by JDBC Driver and URLIf you specified JDBC Driver and URL on the previous screen in the wizard (see “Defining the Database Used by the Reports Repository” on page 152), enter the information discussed in Table 71.

Figure 84 Location of Reports Repository Database Defined by JDBC Driver and URL











Defining the Hyperion Reports Administrator 155

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

Figure 85 Hyperion Reports Administrator


Selecting the Objects to MigrateSelect 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 86 Hyperion Reports Objects to Migrate

Table 72 Hyperion Reports Objects to Migrate



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 Hyperion System 9 BI+ 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 Hyperion System 9 BI+ Repository

● Do not copy the item into the Hyperion System 9 BI+ Repository





Figure 87 Database Used by the Hyperion System 9 BI+ Repository Repository



● SQL Server

● Oracle

● DB2






Defining the Location of the Hyperion System 9 BI+ Repository Server

Define the connection to the Hyperion System 9 BI+ Repository Server on the target system. After you enter the requested information, click Test Connection to test the connection to the server.

Figure 90 Location of the Target Hyperion System 9 BI+ Repository Server

Table 76 Target Hyperion System 9 BI+ Repository Server Information



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 User/Group Names, Descriptions and PasswordsDefine how to treat user descriptions, group names, group descriptions, and passwords when creating new users in the Shared Services Server.



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.




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


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








1 Click Search.












● login ID

● email address



You can view these mappings on the User Names screen and manually adjust or change the mappings as necessary. For example, to map a Reports user name to a different Shared Services user name, you would select the user name, click Properties, and change the Shared Services user name in the Properties dialog box.




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








Most of the properties for each group name display next to the group name. For a complete list of group name properties, click Properties (see “Editing Group Name Properties” on page 168).

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




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.











For example, to map a Reports group name to a different Shared Services group name, you would select the group name, click Properties, and change the Shared Services group name in the Properties dialog box.




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




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





Running the MigrationThe final screen of the Migration Utility wizard allows you to review the objects selected to 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.














Review the objects selected to migrate. The objects that are enabled are the objects selected on the Select Objects to Migrate screen earlier in the wizard (see “Defining the Hyperion Reports Administrator” on page 155).





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



Index B 173

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index

Bbefore migrating

Brio Intelligence, 21

Brio Portal, 21

BrioONE, 22

general, 21

Hyperion Analyzer, 22

Hyperion Performance Suite 8, 22

Hyperion Reports, 22

Brio Intelligence

migration, 77

pre-migration test, 98

prerequisites, 21

Brio Portal

migration, 25


prerequisites, 21

BrioONE

migration, 51


prerequisites, 22

Ccategories, 22

circular references, 31, 129

commands, Help menu, xi

consulting services, xiii

Ddatabase, defining for the source repository, 28, 54, 104,

126, 131, 152

documents

conventions used, xii

feedback, xiii

documents, accessing

Hyperion Download Center, xi

Hyperion Solutions Web site, xi

Information Map, xi

online help, xi

Eeducation services, xiii

Ffile system, access, 21

folders, 22

Ggroup ids

editing properties, 44, 73, 96, 118, 142, 168

searching for, 43, 72, 95, 117, 141, 167

groups

provisioning, 16

special symbols in, 22

what happens during migration, 16

HHelp menu commands, xi

hosts, mapping, 46, 144

Hyperion Analyzer

migration, 101


prerequisites, 22

Hyperion Consulting Services, xiii

Hyperion Download Center, accessing documents, xi

Hyperion Education Services, xiii

174 Index J

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Hyperion Performance Suite

migration, 123


prerequisites, 22

Hyperion product information, xiii

Hyperion Reports

migration, 149


prerequisites, 22

Hyperion support, xiii

Hyperion System 9 BI+ Repository Database

defining information for, 33, 60, 63, 86, 108, 157

defining the location of, 34, 64, 87, 109, 158

Hyperion System 9 BI+ Repository Server, defining the location of, 66, 89

Hyperion Technical Support, xiii

JJDBC driver, 30, 36, 56, 62, 65, 82, 88, 106, 110, 128, 134,

154, 159

JDBC URL, 30, 36, 56, 62, 65, 82, 88, 106, 110, 128, 134, 154, 159

Llog files, 27, 103, 125, 151

Mmapping hosts, 46, 144

migration path, selecting, 26, 102, 124, 150

migration utility, prerequisites, 21

migration, running, 48, 75, 98, 120, 146, 170

OOCE path, 57, 83

ODS.ini, 57

ODS.pwd, 57

OnDemand Server, location of installation files, 57

Ppath, selecting for migration, 26, 102, 124, 150

pre-migration

Brio Intelligence, 98

Brio Portal, 48

pre-migration (continued)

BrioONE, 75

Hyperion Analyzer, 120

Hyperion Performance Suite, 146

Hyperion Reports, 170

prerequisites, general, 21

provisioning of users and groups, 16

Rrepository content, what happens during migration, 20

roles

mapping from legacy roles to new roles, 18


running the migration, 48, 75, 98, 120, 146, 170

SShared Services Server, defining the location of, 37, 67, 90,

111, 135, 161

SmartCuts, 23

source repository

defining the database location, 29, 105, 127, 153

defining the database used, 28, 54, 104, 126, 131, 152

special symbols, in users and groups, 22

Ttechnical support, xiii

Uuser ids

editing properties, 41, 70, 93, 115, 139, 165

searching for, 69, 92, 114, 138, 164

user provisioning, 16, 123

user/group descriptions and passwords, 38, 68, 91, 112, 136, 162

users

provisioning, 16

special symbols in, 22


HYPERION® SYSTEM™ 9 BI+™ - Oracle · PDF filehyperion® system™ 9...

Documents

Transcript of HYPERION® SYSTEM™ 9 BI+™ - Oracle · PDF filehyperion® system™ 9...