Hyperion System 9 Performance Scorecard 9.2 Administrator ...“Managing User Accounts and Authorization” on page 21 describes the default security used by Performance Scorecard

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

P E R F O R M A N C E S C O R E C A R D ™

R E L E A S E 9 . 2

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

P / N : D 5 0 1 9 4 0 0 0 0

Copyright 1999-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.U.S. Patent Numbers: 5,359,724 and 6,317,750.

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

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Additional Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Education Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Consulting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

CHAPTER 1 About Hyperion System 9 Performance Scorecard Administration . . . . . . . . . . . . . . . . . . . . . . . . . 15

Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Logging On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Menus and Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

CHAPTER 2 Managing User Accounts and Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

User Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Setting User Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Authorization Priority Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Users and Employees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Managing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Defining Domain Hierarchies and Permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Creating Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Modifying Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Deleting Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Managing Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Default Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Creating Customized Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

iv Contents

Modifying Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Deleting Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Creating User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Specifying Password Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Modifying User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Deleting User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Generating User Accounts Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Creating and Provisioning Users and Groups Using Shared Services . . . . . . . . . . . . . . . . . . . . 51

Access Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Creating Users Using Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Provisioning a New User Using Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Provisioning a New Group Using Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Modifying a Group Using Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Deleting Groups Using Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Bulk Provisioning in Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Migrating Multiple Users to Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

CHAPTER 3 Generating Results Using Analytic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

About Star Schema Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

HPS_STAR_FACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

HPS_STAR_STATUS_SYMBOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

HPS_STAR_DIM_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

HPS_STAR_MEASURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

HPS_STAR_SCORECARDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

HPS_STAR_DIM_<dimension_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Generating the Star Schema Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

About Hyperion System 9 BI+ Analytic Services Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Generating an Analytic Services Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Retrieving Results in Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Customizing Analytic Services Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Scheduling Automatic Database Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

CHAPTER 4 Using External Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

About External Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Analytic Services Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Working with External Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Defining an External Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Synchronizing Analytic Services with Imported Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Contents v

Modifying an External Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Deleting an External Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

CHAPTER 5 Promoting and Migrating Application Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

About Promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

External Application Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Non-Promotable Business Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Before Promoting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Promoting Application Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

CHAPTER 6 Backing up and Restoring Attachment Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Backing up Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Restoring Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

CHAPTER 7 Managing Shared Services Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

About Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Registering Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

About Managing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

About Sharing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

About Sharing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Working with Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Working with Private Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Working with Shared Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Managing Applications for Metadata Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Working with Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Synchronizing Models and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Sync Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Model Naming Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Comparing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Compare Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Viewing and Editing Model Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Editing Member Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

About Application System Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Renaming Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Deleting Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Sharing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Filtering the Content of Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Tracking Model History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Managing Permissions to Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

About Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

vi Contents

Assigning Permissions to Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Editing Permissions to Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Deleting Permissions to Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Viewing and Setting Model Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Sharing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Prerequisites for Moving Data Between Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Assigning Access to Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Accessing Data Integration Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Filtering Integration Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Creating or Editing a Data Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Deleting Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Scheduling Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Managing Scheduled Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Grouping Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

CHAPTER 8 Managing Alerts using the Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Using Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Alerter Process Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

CHAPTER 9 Extended Customized Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

About Interactive Reporting Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Smart Cuts URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Default Generated Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Scorecard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Scorecard with Measure Trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Strategy Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Extended Reporting through Interactive Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Creating the .oce File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Importing the .oce File through Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Importing the BQY File through Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Generating an Interactive Reporting Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Viewing Generated Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Extended Reporting through Hyperion Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Creating an .oce File in Hyperion Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Publishing an .oce File to the Hyperion Intelligence Server . . . . . . . . . . . . . . . . . . . . . . . 202

Publishing a BQY File through Hyperion Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Generating a Hyperion Intelligence Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Viewing Generated Intelligence Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

CHAPTER 10 Managing and Monitoring Application Business Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Using the Locked Business Objects Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Contents vii

Using the Audit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Using the User Session Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

APPENDIX A Customizing Hyperion System 9 Performance Scorecard and the Alerter . . . . . . . . . . . . . . . . . . 215

Customizing Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Customizing Hyperion System 9 Performance Scorecard . . . . . . . . . . . . . . . . . . . . . . . . . 216

Customizing the Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Customizing the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Working With Cascading Style Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

APPENDIX B Common Member Attributes for Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Configuration Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Account Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Account Type Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Entity Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Scenario Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Version Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Year Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Consolidation Method Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Container Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Element Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Measure Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Variable Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Employee Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Accountability Element or Strategy Element Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . 230

Unit Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

CHAPTER C Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Increasing Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Increasing Startup Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Increase Data Caching Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Allocating Physical Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Tuning Garbage Collection for Sun JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

viii Contents

Preface ix

Preface

Welcome to the Hyperion® System ™ 9 Performance Scorecard ™ Administrator’s Guide. This preface discusses these 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 xii

● “Conventions” on page xiii

● “Additional Support” on page xiv

● “Documentation Feedback” on page xiv

PurposeThis guide provides the information and procedures that administrative users need to

configure, maintain, manage, and secure Hyperion® System™9 Performance Scorecard™ (Performance Scorecard) applications, and examples that you need to use the software. The Administrator’s Guide describes these tasks:

● Create and manage domains

● Create and manage user accounts, security roles and permissions.

● Define and run data integrations that enable users to publish metadata and data to

Hyperion ® System™9 Shared Services (Shared Services).

● Enable single sign-on with supported Hyperion products and configure for external authentication, in standalone mode or through Shared Services.

● Generate Star Schema tables or multidimensional Hyperion ® System™9 BI+™ Analytic Services™ (Analytic Services) databases of application data.

● Use external data sources to populate a Performance Scorecard model

● Migrate application data to different environments

x Preface

AudienceThis guide is written for Hyperion System 9 Performance Scorecard Administrators, Database Administrators, or IT representatives who are responsible for performing administrative tasks. Hyperion recommends that end users or application designers do not perform the administrative tasks described in this guide.

Document StructureThis document contains the following information:

● “About Hyperion System 9 Performance Scorecard Administration” on page 15 outlines the administrative tasks you can perform, explains how to access the Administrator, and describes the administrative environment.

● “Managing User Accounts and Authorization” on page 21 describes the default security used by Performance Scorecard and explains how to create and manage domains, user accounts, security roles, permissions, and restrictions.

● “Generating Results Using Analytic Services” on page 81 describes how to generate a Hyperion System 9 BI+ Analytic Services database of a application data.

● “Using External Data Sources” on page 101 explains how to use external data sources, such as Hyperion System 9 BI+ Analytic Servicesor Hyperion System 9 BI+ Enterprise Metrics, to populate a Performance Scorecard model.

● “Promoting and Migrating Application Data” on page 117 explains how to migrate application data from one environment such as a test environment to another, such as production.

● “Backing up and Restoring Attachment Files” on page 123 describes how to back up and restore files used in attachments if the Web application server is upgraded or Hyperion System 9 Performance Scorecard is uninstalled.

● “Managing Shared Services Models” on page 125 describes how to publish data to Shared Services for use in other Hyperion product applications.

● “Managing Alerts using the Alerter” on page 179 describes how to monitor alert activity using the Alerter Process report.

● “Managing and Monitoring Application Business Objects” on page 207 describes how to break locks applied to business objects that are in use or have been frozen. This chapter also explains how to use the Audit Report to track changes made to business objects such as scorecards and measures.

● “Customizing Hyperion System 9 Performance Scorecard and the Alerter” on page 215 explains how to customize functional and graphical aspects of Hyperion System 9 Performance Scorecard and the Alerter.

● “Common Member Attributes for Shared Services” on page 225 lists the common member attributes used in Shared Services and their equivalents in other Hyperion products.

● “Frequently Asked Questions” on page 231 answers some questions about performing administrative tasks.

Where to Find Documentation xi

Where to Find DocumentationAll Performance Scorecard documentation is accessible from these locations:

● The HTML Information Map launched by selecting Help > Information Map in Performance Scorecard.

● Online help is available from within Performance Scorecard. After logging on to the product, access online help by clicking the Help button or selecting Help from the menu bar.

● The Hyperion Download Center can be accessed from http://hyperion.subscribenet.com or from http://www.hyperion.com.

➤ To access documentation through the Hyperion Solutions Web site:

1 Log on to http://www.hyperion.com.

2 Select the Support link and type your username and password to log on.

Note: New users must register to receive a username and password.

3 Click the Hyperion Download Center link and follow the on-screen instructions.

➤ To access documentation from the Hyperion Download Center:

1 Go to http://hyperion.subscribenet.com.

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

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.

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 to use for the current session.

5 Perform one of these actions:

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

● To order printed documentation, from the Information section in the left frame, select Order Printed Documentation and follow the on-screen instructions.

● To order a CD that contains the complete set of Hyperion Business Performance Management documentation, from the Information section in the left frame, select Order Printed Documentation, then select Business Performance Management Product Documentation CD and follow the on-screen instructions.

● To order printed documentation or the documentation CD if you cannot access the Hyperion Download Center:

❍ In the United States, call Hyperion Solutions Customer Support at 877-901-4975.

http://hyperion.subscribenet.com

http://hyperion.subscribenet.com

http://www.hyperion.com



xii Preface

❍ From outside the United States, including Canada, call Hyperion Solutions Customer Support at 203-703-3600. Clients who are not serviced by support from the Americas should call their local support centers.

Help Menu Commands Table i describes the commands that are available from the Help menu in Performance Scorecard.

Table i Help Menu Commands

Command Description

Information Map Launches the Performance Scorecard Information Mapto dislay:

● Online help in PDF and HTML format

● Links to related resources to assist you in using Performance Scorecard.

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

Hyperion Developer’s Network Launches the Hyperion Developer Network site, where you access information about known defects and best practices. This site provides tools and information to assist 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 Hyperion System 9 Performance Scorecard

Select this option to display the release number of the version of Performance Scorecard that is currently installed.

Conventions xiii

ConventionsThis table describes the typographical conventions used in this guide.

Table ii Document Conventions

Item Meaning

Arrows indicate the beginning of a procedure consisting of sequential steps.

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

Bold Bold text indicates words or characters that you type exactly as they appear on the page. Bold in procedural steps highlights major interface elements.

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

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

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

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

Italics Italics in a product-related term in the body of a book indicates that the term is also included in the glossary of the book.

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: Menu name→Menu command→Extended menu command

For example: File→Desktop→Accounts

n, x The variable n indicates that you must supply a generic number; the variable x indicates that you must supply a generic letter.

xiv Preface

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 on the Hyperion Web site at http://www.hyperion.com.

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’ reporting, analysis, modeling, and planning requirements. Hyperion also offers specialized consulting packages, technical assessments, and integration solutions.

Technical SupportHyperion provides enhanced electronic-based and telephone 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.

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

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


About Hyperion System 9 Performance Scorecard Administration 15

C h a p t e r

1About Hyperion System 9

Performance Scorecard Administration

This chapter outlines the tasks used to administer Performance Scorecard applications. It also explains how to access the Performance Scorecard Administrator and familiarizes you with the administrative environment.

Note: If you access the Administrator using the admin user account, Hyperion recommends that you change the default password (password) as soon as possible.

In This Chapter Logging On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Menus and Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

16 About Hyperion System 9 Performance Scorecard Administration

Administrative TasksThe Administrator role enables you to perform these tasks:

● Create and manage user accounts, including defining and applying domains and security roles that establish a user’s access to business objects, such as measures, scorecards, Web pages and reports.

● Configure Performance Scorecard and the Alerter to use a another database. See the Hyperion System 9 Performance Scorecard Installation Guide.

● Authenticate users using a supported authentication provider, such as NTLM, LDAP or

MSAD, or using Hyperion® System™ 9 Shared Services™ (Shared Services)

● Provision users for Shared Services authentication

● Monitor changes made to business objects.

● Unlock locked business objects.

● Generate multidimensional Hyperion System 9 BI+ Analytic Services databases.

● Import and export data through Shared Services to other Hyperion applications, and manage models.

● Backup or restore notes containing file attachments.

● Promote application data from one environment, such as development or testing, to another environment, such as production.

● View details about active and historical user sessions for a selected user ID and date range.

Logging OnThis section describes how to log on as the Performance Scorecard Administrator.

Note: Before logging on to Performance Scorecard, install and configure the application and databases, as outlined in the Hyperion System 9 Performance Scorecard Installation Guide.

➤ To log on to the Performance Scorecard Administrator:

1 With your browser, navigate to http://<computer name>:<port number>/HPSWebReports.

This URL is case-sensitive. The Performance Scorecard Logon page is displayed.

If you have not configured Performance Scorecard, the Configure Application page is displayed.

2 Enter your username and password.

Tip: If you have not created with the admin security role, log on using admin and password. To create your own user account, see “Managing User Accounts and Authorization” on page 21.

3 Optional: If you are using LDAP or NTML security, enter the domain.

Menus and Toolbars 17

4 Click Logon.

The Performance Scorecard Administrator’s Start page is displayed.

Menus and ToolbarsMost tasks can be initiated from the main menu or toolbar. Review these sections:

● “File Menu” on page 18

● “View Menu” on page 18

● “Administration Menu” on page 19

● “Favorites Menu” on page 20

● “Toolbar Options” on page 20

Number Description

1 Masthead

2 Main Menu

3 Toolbar

4 Viewer Pane

5 Contents Pane

3

2

1


If you have another security role assigned to your user account, additional menu options are available. Refer to the Hyperion System 9 Performance Scorecard Application Designer’s Guide or

Hyperion System 9 Performance Scorecard User’s Guide.

File MenuFrom the File menu, you can perform these tasks:

View MenuFrom the View menu, you can perform these tasks:

Command Description

Print Display the Print dialog box

Export to Microsoft Excel Export selected information to Excel.

Log Off Logs off and returns you to the Performance Scorecard Logon page.

Exit Logs off and exits the application.

Command Description

Refresh Update the page with any recent information saved to the application database

Home Returns you to the default Home page from any location within the application

Masthead Toggle to show or hide the masthead

View Pane Toggle to show or hide the view pane

Menus and Toolbars 19

Administration MenuFrom the Administration menu, you can perform these tasks:

Command Description

Locked Business Objects Report

Identify and break the locks on locked business objects currently in use or otherwise unavailable. For more information about this report, see “Using the Locked Business Objects Report” on page 208.

Audit Report Track changes made to business objects. For information about this report, see “Using the Audit Report” on page 209.

User Session Report Identifies users currently logged into Performance Scorecard

Attachment Backup Enter the backup directory for attachments

Promotion Copy application data from one environment, such as development or testing, to another environment, such as production. See “Promoting and Migrating Application Data” on page 117.

Star Schema Generation Create Star Schema tables or a multidimensional Analytic Services database of application data. See “Generating Results Using Analytic Services” on page 81.

Configure External Authentication

Add, remove or resequence the order of external authentication service providers

Data Source List Add, edit or remove an external data source for importing data

Manage Models Publish application business objects, such as measures and targets, to Shared Services for use in other Hyperion product applications.

Manage Projects Manage projects and applications in Shared Services.

Manage Data Publish business object data and attributes, such as results and scorecard scores, to Shared Services for use in other Hyperion product applications.

User Management Create and provision Performance Scorecard users in Shared Services.

Scheduled Integrations Schedule data integrations to share data between Shared Services and other Hyperion applications

User Provisioning Migration Perform a one-time migration of users from Performance Scorecard to Shared Services

Alerter Use the Alerter Process Report to monitor alert activity


Favorites MenuFrom the Favorites menu, you can perform these tasks:

Toolbar OptionsFrom the Toolbar, you can perform these tasks:

Command Description

Add Current Page Add a link to your Favorites for a Performance Scorecard or Web page

Edit Favorites Modify your list of Favorites

Button Description

Print a report or page

Export a report or active data to Microsoft Excel.

Update the page with any recent information

Display the Preferences tab to change your settings

Return to the Home page

Log out of the application and return to the Logon page

Display the Performance Scorecard Information Map from which you can access help in PDF and HTML format

Managing User Accounts and Authorization 21

C h a p t e r

2Managing User Accounts and

Authorization

This chapter describes how to use security roles to assign or restrict access to business objects, such as measures, scorecards and Web pages. It also explains how to create and provision users.

You can authenticate Performance Scorecard users in two ways:

● Standalone mode uses basic JDBC, user account-based authentication, or an external authentication provider such as LDAP, MSAD, NTLM or Netegrity Siteminder. Perform the configuration from the Performance Scorecard Administration menu. For information on setting up external authentication, refer to the Hyperion System 9 Performance Scorecard Installation Guide.

● Shared Services mode uses Shared Services to authenticate Performance Scorecard users. During configuration, select Shared Services as the authentication mode, then use the Shared Services User Management Console to authenticate users. Refer to the Hyperion System 9 Shared Services User Management Guide.

In This Chapter User Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Managing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Managing Security Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Creating and Provisioning Users and Groups Using Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Bulk Provisioning in Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Migrating Multiple Users to Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

22 Managing User Accounts and Authorization

User AuthorizationAuthorization controls access to the application, based on the security roles and domain associations assigned to user accounts.

These sections explain how user accounts, security roles and domains control access to Performance Scorecard data, reports and Web pages:

● “Setting User Authorization” on page 22

● “Security Roles” on page 23

● “Users and Employees” on page 24

● “Defining Domain Hierarchies and Permission” on page 25

Setting User AuthorizationUsers can only access business objects which they have been authorized to view or modify. Authorization involves these steps:

1. Optional: Define domains to manage business objects, such as branch offices, geographic locations or specific departments, such as Human Resources or Accounting. This step enables organizations with large applications and business objects to streamline and manage data in logical groups.

You can associate the user’s account with a domain and grant them access to business objects in that domain. For information about creating and managing domains, see “Managing Domains” on page 25.

2. Optional: Create a custom security role to establish measure, scorecard, and Web page access permissions. These settings determine the tasks that users can perform and the data they can access. See “Managing Security Roles” on page 30.

3. Create accounts for users, as outlined in “Creating User Accounts” on page 43. This includes these tasks:

❍ Associating an employee with the account

❍ Associating the account with a domain (optional)

❍ Applying a default or custom security role to determine access permissions

User Authorization 23

Figure 1 Creating User Accounts

Security RolesBy default, access is restricted to all measures and scorecards in an application. Assign access to measures and scorecards by specifying permissions for the security role that is applied to a user’s account.

The following default security roles are provided; however, you can create customized security roles:

● user (for end users)

● designer (for application designers)

● admin (for administrators)

For information about the permissions for each security role, see “Default Security Roles” on page 31.

If you use Shared Services for external authentication, each Performance Scorecard security role is associated with an equivalent security role in Shared Services:

Shared Services Role Performance Scorecard Security Role

Power Manager Administrator


Authorization Priority RulesBecause you can apply multiple, sometimes conflicting, permissions and restrictions to a security role, these authorization priority rules are used:

Restrictions and permissions are cumulative, meaning the total of all restrictions and permissions are

used.

For example, if a security role has Grant All and Deny All access, the user can see all scorecards

because Grant All has a higher priority level than Deny All.

Users and EmployeesUsers are individuals who use Performance Scorecard. Employees are individuals in an application who are responsible for, or associated with business objects, such as Strategy elements, measures, and targers. Employees are created by application designers.

For authorization purposes, the user account for each Performance Scorecard user must be associated with an employee. The employee associated with the account determines which measures, scorecards, initiatives, and reports that the user can access.

DomainsIf your organization contains distinct functional or regional business areas such as national and regional offices or departments, define domains to represent these areas.

Interactive Designer

Basic User

Access Level Priority

Grant One 1 - Highest

Deny One 2 - High-Middle

Grant Group 3

Deny Group 4

Grant All 5 - Middle-Low

Deny All 6 - Lowest

Shared Services Role Performance Scorecard Security Role

Managing Domains 25

For example, domains may represent on geographical divisions, functional areas, or a special project or task force. Application designers can associate any combination of business objects, such as maps, measures, employees, initiatives and scorecards, with a domain.

Because domains can represent a hierarchy within the organization, specify the level of information that users can access in each domain. Access may be implicit (access to all child domains) or explicit (access to specific portions in the domain hierarchy). See “Defining Domain Hierarchies and Permission” on page 25

For information about creating, editing, and deleting domains, see “Managing Domains” on page 25

Managing DomainsThis section explains how to define, create, modify and delete the domains to which business objects are assigned. These topics are covered:

● “Defining Domain Hierarchies and Permission” on page 25

● “Creating Domains” on page 26

● “Modifying Domains” on page 28

● “Deleting Domains” on page 29

Defining Domain Hierarchies and PermissionDomains are optional, but if they are used, access permissions to each domain must be assigned to the associated users. When access is assigned, the user has access to all business objects associated with the domain, and each business object created by that user is automatically added to the domain.

There are two ways to assign access permissions:

● Explicit access is assigned on an individual basis. The domain designer specifically assigns Modify access to one or more assigned domains. This option is useful when you want to restrict permission to the domain to a limited number of users.

● Implicit access is offered by default, and assigns Modify access to the selected domain and its direct and indirect children.The implicit rule can be enabled or disabled when setting access permissions.

The domains are created in a hierarchy, and access levels roll up from children to the top level. A Domain can have either No Parent (at the top of the hierarchy) or one parent. The parent domain must exist before the child domain can be created. To take advantage of a bulk domain assignment, the user must have write access to the objects and the domain that are being created.


The example in this table illustrates the assignment of permission through a simplified hierarchy.

Creating DomainsThis section describes how to define a new domain.

Before creating a domain, identify those business objects that should be associated with the domain, such as measures, scorecards, and employees.

➤ To define a new domain:

1 Log on to Performance Scorecard as an Administrator.

The Performance Scorecard Administrator is displayed.

2 From Object View, select Security > Domain List.

The Domain List is displayed.

Table 3 Sample Domain Hierarchy and Associated Permissions

Domain Parent Access

Global No Parent All Domains

North America Global All North America (Canada, Mexico and United States)

Canada North America All Canada (Sales and Human Resources)

● Human Resources

● Sales

Canada Canada Sales Only

Canada Human Resources Only

Mexico North America All Mexico (Sales and Human Resources)

● Human Resources

● Sales

Mexico Mexico Sales Only

Mexico Human Resources Only

United States North America All United States (Sales and Human Resources)

● Human Resources

● Sales

United States United States Sales Only

United States Human Resources Only

Europe Global All Europe (France, United Kingdom and Germany)

France Europe France Only

United Kingdom Europe United Kingdom Only

Germany Europe Germany Only

Managing Domains 27

3 Click Add.

The Domain Setup is displayed.

4 Under Name, enter a unique name to identify the scope of the new domain, such as a country, region, office, business unit, project or department.

For example, if your organization has multiple development offices in North America, you may create a domain for each office, such as Development:Boston or Development:Chicago. You can also create a domain for a specific project or task force.

5 Under Description, enter a description of the domains.

6 From Parent Domain, select the name of the parent for the new domain.

In the case of a top-level domain, select [No Parent]; otherwise, select the domain level which contains the new domain. For example, if the top-level domain is Global (with no parent), the domains North America and South America would have Global as the parent domain. The domains Canada and Mexico would have North America as the parent domain.


7 Click Save.

The domain is created and added to the Domain List. You can assign access or a business object to the created domain, as outlined in these procedures:

● Grant users access to the business objects in the domain when creating their user account. See “Creating User Accounts” on page 43.

● Assign employees, measures and measure templates to the domain, as outlined in the Hyperion System 9 Performance Scorecard Application Designer’s Guide.

Modifying DomainsThis section explains how to edit the name or description for a domain, or to select a new parent domain.

➤ To modify a domain:





3 From Domain, select the domain to be modifed.

4 Click Edit.

The Domain Setup is displayed.

Managing Domains 29

5 Under Parent Domain, enter a name or description, or select a new Parent Domain from the list.

6 Click Save.

Deleting DomainsThis section describes how to delete domains. Before deleting a domain, contact users to determine whether the domain is still required. If you delete a domain that contains business objects, only a designer can access those business objects.

Caution! Do not delete a domain that is currently in use. The only way to check whether the domain is currently assigned would be to examine the associated scorecards or measures. Contact the designer to determine whether the domain is still required.

➤ To delete a domain:





3 Under Domain, select the domain to be deleted, then click Delete.

A deletion confirmation message is displayed.


4 Click Yes to confirm the deletion.

The deleted Domain is removed from the Domain list.

Managing Security RolesThese sections explain how to create and customize security roles:

● “Default Security Roles” on page 31

● “Creating Customized Security Roles” on page 32

● “Modifying Security Roles” on page 41

● “Deleting Security Roles” on page 42

Managing Security Roles 31

Default Security RolesThis table identifies the tasks that each default security role can perform.

Table 4 Default Security Roles

Performance Scorecard Security Role

Shared Services User Role Description

designer Interactive ● Creatie frameworks and employees

● Define measures and dimensional outlines

● Build Strategy, Accountability, and Cause and Effect maps

● Enter employee and scorecard data

● Create alerts and subscriptions

● Create, access and reply to notes

● Set reporting periods

● Create and modify initiatives

● Assign annotation creators to a business object

● Build application components

● Access all Performance Scorecard reports and perform data entry

● Vew and drill down into the components of the Strategy, Accountability, and Cause and Effect maps to which they have access

● Alerter: To create and subscribe to alerts. This includes creating public alerts and subscribing others to alerts

● Shared Services: To publish data to Shared Services for use in other supported Hyperion product applications by running data integrations

user Basic ● View maps and drill down into map elements

● Access data about business objects to which they have access and use notes

● Create and subscribe to alerts

● Create, edit or delete annotations

Note: This role restricts access to measures and scorecards unless the user meets certain criteria. Do not apply this role to the accounts of employees whodefine frameworks, build maps, create measures, and setup scorecards.


Creating Customized Security RolesYou can create customized security roles for user accounts. For example, you can create a “super user” security role to access all business objects and work areas, or a security role for a distinct corporate department, such as Human Resources.

For customized security roles, assign access for the security role for measures, scorecards, and Web pages. See these sections:

● “Assigning Scorecard Permissions” on page 34

● “Assigning Measure Permissions” on page 38

● “Assigning Access to Web Pages” on page 39

Note: Restrictions and permissions are cumulative, meaning the total of all restrictions and permissions are used.

admin Power Manager ● Create and manage user accounts. This includes applying security roles and establishing permissions and task restrictions

● Track changes made to application business objects and monitor locks applied to business objects in use

● Generate Star Schema and multidimensional Analytic Services databases of application data

● Configure Performance Scorecard for Shared Services

● Manage models through Shared Services

● Promote application data to another environment

● Configure the Alerter, enabling users to send and receive alert notifications

● Create, modify or delete domains

● Edit or delete annotations

● Monitor user activity through the User Session Report

Table 4 Default Security Roles (Continued)

Performance Scorecard Security Role

Shared Services User Role Description


➤ To create security roles:



2 FromObject View, select Security > Security Role List.

The Security Role List is displayed.

3 Click Add.

The Security Role Setup is displayed, listing the default security roles, and any custom roles.

4 Under Security Role Name, enter a unique name for the security role.

5 Under Description, summarize how the security role is used.

6 Under Scorecard Permission, click Add to assign access to individual or group scorecards, as outlined in “Assigning Scorecard Permissions” on page 34.

7 Under Measure Permission, click Add to assign access to individual or group measures, as outlined in “Assigning Measure Permissions” on page 38.

8 Under Web Page Restrictions, click Add to add the restricted Web pages for which access is to be denied for the selected user or group, as outlined in “Assigning Access to Web Pages” on page 39.

9 Click Save.

The security role is available to assign to user accounts. Any user account with this security role inherits the permissions and restrictions you defined, determining the measures, scorecards, and Web pages they can access.


Caution! Although you can assign multiple security roles to an account, the permissions associated with the least restrictive role are applied

Assigning Scorecard PermissionsThis section explains how to assign scorecard permissions for a security role.

➤ To assign scorecard permissions:



2 From Object View, select Security > Security Role List.


3 Click Add.

The Security Role Setup window is displayed.

4 Under Scorecard Permissions, click Add in the Scorecard Permissions list.

The Scorecard Permissions page is displayed.


5 In Permission Name, enter a name for the set of scorecard permissions you are applying to the selected security role.

6 Under Permission, select the appropriate scorecard permissions for the security role from these available permissions.

Table 5 Scorecard Permissions

Permission Access Level

Grant access to all scorecards All scorecards in an application.

Grant access to all Strategy element scorecards only

Only to scorecards gauging strategy element performance.

Grant access to all scorecards in Domain(s) Scorecards assigned to a selected domain.

❍ Click Select to display a list of available Domains.

❍ Select the appropriate domain, then click Apply.

To select Implicit access for all domain members, click Domain Implicit Access.

Grant access to this scorecard The single scorecard selected from the list of available scorecards.

Deny access to this scorecard Blocks access to the selected scorecard only.

Deny access to all scorecards in Domain(s) Blocks access to scorecards assigned to a selected domain.

❍ Click Select to display a list of available Domains.

❍ Select the appropriate domain, then click Apply.


Deny access to all scorecards: Blocks access to all scorecards in an application based on the following conditions:

● Unless the scorecard is the user’s primary scorecard

Scorecards created for a user by their manager.

● Unless the scorecard is an Accountability element scorecard owned by the user

Only to scorecards measuring the performance of accountability elements owned by the user.

● Unless the scorecard is a child of an Accountability element scorecard to which the user has access

Only to the child scorecards of a scorecard that measures the performance of accountability elements owned by the user.

In the illustration, access is provided to the box labelled “Child,” as the child of the Accountability scorecard, “A.”

This option also grant s access to grandchildren, great-grandchildren and so on of the original scorecard.

● Unless the scorecard is a parent of an Accountability element scorecard to which the user has access

Only to the parent scorecards of a scorecard that measures the performance of accountability elements owned by the user.

In the illustration, access is provided to the box labelled “Parent,” as the parent of the Accountability scorecard, “A.” In addition, access is also provided to the “Grandparent” of “A,” which is the parent of the parent of “A”.

Table 5 Scorecard Permissions (Continued)



7 Click Save.

● Unless the scorecard is an Accountability element scorecard and the user is a member of that element

Only to scorecards assessing the performance of accountability elements of which the user is a member.

● Unless the scorecard is a Strategy element scorecard to which the user belongs

Only to scorecards evaluating the performance of strategy elements with which the user is associated.

● Unless the scorecard is a child of an Strategy element scorecard to which the user has access

Only to the child scorecards of a scorecard that measures the performance of strategy elements owned by the user.

In the illustration, access is provided to the box labelled “Child,” as the child of the Strategy scorecard, “A.”

This option also grants access to grandchildren, great-grandchildren and so on of the original scorecard.

● Unless the scorecard is a parent of an Strategy element scorecard to which the user has access

Only to the parent scorecards of a scorecard that measures the performance of strategy elements owned by the user.

In the illustration, access is provided to the box labelled “Parent,” as the parent of the Strategy scorecard, “A.” In addition, access is also provided to the “Grandparent” of “A,” which is the parent of the parent of “A.”

● Unless the scorecard is an employee scorecard for which the user is the manager

Only to scorecards for employees that the user manages.

Table 5 Scorecard Permissions (Continued)



Assigning Measure PermissionsThis section explains how to grant complete or conditional access to measures using the security role.

➤ To assign measure permissions:





3 Select the security role to which you want to assign measure permission, then click Edit.


4 Under Measure Permissions, click Add to select the measures to which the user with the security role will have access.

The Measure Permissions Setup page is displayed.

5 In Permission Name, enter a name for the set of measure permissions.


6 Under Permission, select the appropriate measure permissions for the security role from this table:

7 Click Save.

Assigning Access to Web PagesThis section describes how to block users from accessing Web pages and reports.

Caution! Web pages listed on the Security Role Setup window are restricted and cannot be viewed. To access a Web page, it must be removed from the list.

➤ To restrict Web pages:





3 Select the security role for which you want to restrict access to Web pages, then click Edit.


Table 6 Measure Permissions


Grant access to all measures All measures in an application.

Grant access to all measures in Domain(s) Scorecards assigned to a selected domain.

● Click Select to display a list of available Domains.

● Select the appropriate domain, then click Apply.

To select Implicit access for all domain members, click Domain Implicit Access.

Grant access to this measure Only the individual measure that you specify.

Deny access to this measure Blocks access to a measure that you specify.

Deny access to all measures in Domain(s) Blocks access to scorecards assigned to a selected domain.

● Click Select to display a list of available Domains.

● Select the appropriate domain, then click Apply.

Deny access to all measures Blocks access to all measures unless one of these conditions apply:

● Unless measure owner Only to measures that a user owns.

● Unless measure on accessible scorecard

Only to measures on scorecards to which the user has access.


4 Under Web Restriction, click Add.

The Web Page Restriction page is displayed, showing those Web pages which are currently blocked.

5 Optional: To grant access to a Web page:

a. Under Web Restriction, select the Web page to which you want to grant access.

b. Click Delete to remove the Web page from the restricted list. The selected Web page is available.

6 Optional: To restrict or remove access to a Web page:

a. Under Web Restriction, select the individual page, report or group of Web pages to be restricted.

❍ To select a range of pages, press Shift and select the first and last pages in the range.

❍ To select random multiple selections, press CTRL and select each individual page.

Table 7 Webpage Restrictions

Restriction Access Level

Admin Group Administration menu, enabling users to perform all the tasks described in this guide.

Designer Group Browser and Object views enabling users to create and modify business objects such as employees, maps, and measures.

Result Collection Admin Result Collectors enabling users to enter results for locked measure.

Alerter Group Create and subscribe to alerts.

Shared Services Group Publish data to Shared Services by running data integrations.

Analysis View Annotation and Initiatives tab on a Measure, Accountability or Strategy Initiative.


b. To remove links in reports to the scorecards of other employees, select Hide <Employee> Scorecards.

c. Click Save.

All the Web pages listed in the Webpage Restriction list are unavailable for users to whose accounts the new security role is applied.

Note: To restrict pages in these groups, you must also restrict the Designer group: - Reports group - Alerter group - Admin group - General group - Shared Services group

7 Click Save.

Modifying Security RolesYou can edit a security role to increase or restrict access for a user to scorecards, measures and Web pages.

➤ To modify a security role:



2 FromObject View, select Security > Security Role List.

The Security Role list is displayed.

3 Select the security role you want to modify and click Edit.

The Security Role Setup page is displayed, identifying any permissions and restrictions assigned to the security role.


4 Optional: In Security Role Name, change the name of the security role.

5 Optional: In Description, update the purpose of the security role.

6 Under Scorecard Permission and Measure Permission, modify the assigned permissions using these methods:

● To remove any scorecard or measure permission, select the permission and click Delete.

● To add new permissions to make additional measures and scorecards available, see “Assigning Scorecard Permissions” on page 34 and “Assigning Measure Permissions” on page 38 for detailed instructions.

7 Under Web Page Restrictions, modify access to a Web page using these methods:

❍ To restrict access to a Web page, click Add. The Web page is added to the restricted list, and is NOT available for the user.

❍ To allow access to a Web page, click Delete. The Web page is removed from the list, making it accessible for the user.

8 Click Save.

Deleting Security RolesThis section describes how to remove a security role.

Caution! Ensure no users are using the security role before you delete it.

Managing User Accounts 43

➤ To remove a security role:



2 From Object View, select Security > Security Roles.


3 Select the security role you want to delete from the list and click Delete.

A confirmation message is displayed.


The security role is removed from the Security Role List.

Managing User AccountsThis section explains how to define, modify, and delete user accounts. Refer to these topics for detailed instructions:

● “Creating User Accounts” on page 43

● “Specifying Password Syntax” on page 45

● “Modifying User Accounts” on page 47

● “Deleting User Accounts” on page 48

● “Generating User Accounts Automatically” on page 49

● “Creating and Provisioning Users and Groups Using Shared Services” on page 51

Creating User AccountsYou can create an individual account for a single user. If you have a large number of users to create, you can automatically generate a user account for each employee. See “Generating User Accounts Automatically” on page 49.

To make the user account the application designer for a specific domain, assign a primary domain to the user’s account. See “Managing Domains” on page 25.

If you are using external authentication through Shared Services, you can create and provision users through Shared Services, as outlined in “Creating and Provisioning Users and Groups Using Shared Services” on page 51.

➤ To create user accounts:



2 From Object View, select Security > User Account List.

The User Account List is displayed, showing user accounts and the associated security role (Basic, Interactive or Power Manager).


3 Click Add.

Note: If you are using Shared Services for external authentication, Add, Edit and Delete are not available to create or modify users. You must add, modify or remove any users through Shared Services; therefore, only the Synchronize with Employee and Synchronize with Shared Services buttons are available.

The User Account Setup page is displayed.

4 In User ID, enter the user ID for the account.


Note: The ID you specify must be unique, and case-insensitive. For example, if an account called LHagen already exists, you cannot specify lhagen as the account name.

5 Beside Employees, click Select.

The Select Employee dialog box is displayed.

6 Select the employee who will use this user account to log on to Performance Scorecard.

Note: If you are applying a custom security role to the account that establishes conditional access to measures and scorecards, ensure that the employee you choose satisfies those conditions. For example, the employee may have to be the owner of a specific measure or member of a certain strategy element to access the information.

7 In Initial Password, enter the case-sensitive Performance Scorecard password.

8 In Confirm Initial Password, re-enter the password.

Tip: For information on setting the syntax or a pattern for the passwords, refer to “Specifying Password Syntax” on page 45.

9 From Primary Domain, select the name of primary domain with which the user is to be associated. By default, measures and scorecards created by the user are automatically assigned to the user’s primary domain.

Note: Assigning a primary domain automatically places each business object that the user creates in the domain.

10 From Security Roles, select the appropriate role or roles for this user.

● For information about the access for each security role, see “Default Security Roles” on page 31.

● For information about creating security roles, see “Creating Customized Security Roles” on page 32.

11 Click Save.

The new user account is saved and added to the User Account list.

Specifying Password SyntaxYou can establish the syntax or pattern that passwords must have to be accepted by Performance Scorecard by modifying the HPSConfig.properties file and inserting an expression. This feature enables you to define a specific format for passwords.

Refer to these sections to establish a password syntax:

● “Specifying a Required Password Length” on page 46

● “Specifying a Required Number or Character Range” on page 46


Specifying a Required Password Length

➤ To specify the length for the password:

1 From <Web application server>\webappsconf\config, open HPSConfig.properties in any text editor.

2 Navigate to this entry in the #Password section:

Hyperion.hps.password_constraint=.{3, }

The number in this line of code (by default 3), represents the minimum number of characters required in a password.

3 Between the braces { }, enter the number of characters that represent the length of the password.

For example, if you want the password to be at least seven characters in length, change this line of code to Hyperion.hps.password_constraint=.{7, }

4 Save and close the file.

5 From <HPSWebReports>\Web-INF\classes, open ApplicationResources.properties.

6 Enter a message to be displayed if users enter a password that does not correspond to the required length.

# Translation strings that clients might want to change webreports.password_change.password_not_match_constraint=Passwords must be at least 3 characters in length. Your message.


Specifying a Required Number or Character Range

➤ To specify a number or letter range requirement for the password:


2 Navigate to this entry in the #Password section:

Hyperion.hps.password_constraint=.{3, }

The number in this line of code (by default 3), represents the minimum number of characters required in a password.

3 Use square brackets to enter the required number of letters or a range of required letters.

For example, Hyperion.hps.password_constraint= [a-z] states that only passwords comprised of letters a-z in lower case are accepted.

Tip: Use (\W) to specify characters or ranges that are not be accepted in a password. For example, [A-D]\W[E-Z] would only accept capital letters A-D and would reject any letters following d.

4 Save and close HPSConfig.properties.


Frequently Used Expressions for Password SyntaxThis table identifies some of the most frequently used regular expressions you can use to specify password syntax.

Modifying User AccountsYou can modify user accounts as needed to extend or limit access to specific business objects, reports, and tasks.

➤ To modify user accounts:



2 Select Security > User Account List.

The User Account List is displayed.

Table 8 Regular Expressions

Expression Description

[-] Range Only accepts the items in a range enclosed in square brackets. For example, Hyperion.hps.password_constraint= [a-z]+ states that only passwords comprised of one of more letters between a-z in lower case are accepted.

| Or Accepts one set of items in a range or another specified set of items. For example, Hyperion.hps.password_constraint= [a-z]|[2-50] accepts passwords using letters a-z or numbers 2-50.

. When used outside a bracket, a period matches any character in the supported character set except NUL. For example, r.t would match the strings rat, rut, r t, but not root.

[^] Negates a bracket expression and matches any character except those enclosed. For example, [^X] accepts UML, HTML, SGML, but not XML.

^ Indicates that the pattern must appear at the beginning of a string. For example, ^ball accepts any string that starts with ball, such as ballistics or ballroom dancing.

$ Specifies that the characters following $must appear at the end of the string. For example, $@hyperion accepts anything with @Hyperion at the end.

\s Accepts any white-space character (any key stroke that creates white space such as tab, space bar stroke). For example, a\s+b searches for the letter a followed by white space which is then followed by a letter b.

{n} Bound Specifies the exact number of times the preceding item of match can occur. For example, [0-9]{3} matches any three digits in the range of 1-9.

{n,} Bound Specifies the minimum number of times the preceding item of match can occur. For example, [0-9]{3,} accepts three or more repetitions of a number in the 0-9 range.


3 Select the account you want to modify and click Edit.

The User Account Setup page is displayed.

4 Modify the account by changing any of these properties:

● Password

● Domain with which the user account is associated. The employee has access to all business objects associated with the domain you specify.

● Full or conditional access to measures

● Full or conditional access to scorecards

● Full or partial access to Web pages and reports

5 Click Save.

Deleting User AccountsThis section explains how to remove a user account from an application.

Caution! Before deleting a user account, ensure that the account is no longer required by the employee , and that the account was not used to generate public accounts that may need to be modified.

➤ To delete user accounts:



2 Select Security > User Accounts.

The User Account List is displayed.


3 Select the user account you want to remove from the application and click Delete.



The user accounts is removed from the user account list and can no longer be used to access Performance Scorecard.

Generating User Accounts AutomaticallyThis section describes how to automatically create user accounts for all employees in an application.

By default, the names of the accounts generated are the first portion of the employee’s e-mail address specified on their employee profile. For example, [email protected] would generate a user, John Smith.

If you want to use another format to generate user accounts, you can modify the HPSConfig.properties file to reflect another option. For instructions on modifying the configuration properties file, refer to “Customizing Hyperion System 9 Performance Scorecard and the Alerter” on page 215.

Note: The user security role is automatically assigned to all mass-generated accounts

Before You BeginBefore automatically generating user accounts, keep these conditions in mind:

● If an employee already has a user account and the account name is the same as the employee name (jburns, for example), another account is not generated.

● If an employee already has a user account and the account name is not the same as the employee name, an account is generated and you are prompted to delete the user account.


Automatically Generating User Accounts

➤ To automatically generate multiple user accounts:

1 Log on to Performance Scorecard as a Designer.

Performance Scorecard is displayed on the Browser view tab.

2 FromObject View, select Security > User Account List.

The User Account List is displayed, listing the three default user accounts and any other user accounts that have been defined.

3 Click Synchronize with Employees to generate user accounts for all the employees on the Employee List.

A confirmation message is displayed, advising that user accounts may be created.

4 Click Yes to confirm the synchronization process.

A user account is created for each employee. When the synchronization is complete, the User Account Synchronization Result report is displayed, showing the user accounts that were added. Any user accounts that do not seem to be associated with existing employees are highlighted.

Creating and Provisioning Users and Groups Using Shared Services 51

5 From the list of unrelated user accounts, select those accounts that should be deleted, using these options:

● Deselect the checkboxes for any user accounts that are to be kept.

● Click Select All to delete all the displayed user accounts.

● Click De-select All to keep all the user accounts listed.

6 Click Delete to remove the selected user accounts from the list.

The User Account List is displayed, showing all added user accounts.

Creating and Provisioning Users and Groups Using Shared Services

You can provision users and groups for Performance Scorecard using Shared Services. You can use existing user information for multiple Hyperion applications, or to provision multiple users simultaneously.

To provision users for Performance Scorecard from existing users in Shared Services, you must select this as an option after installation, when you run the Configuration Utility. See the Hyperion System 9 Performance Scorecard Installation Guide. The Shared Services Administrator must also be provisioned to the Performance Scorecard application.

The provisioning process requires you to have the Shared Services server and Performance Scorecard configured and running. External authentication ensures that the applications can communicate seamlessly to provision users easily and accurately.

Refer to these sections for detailed instructions:

● “Access Permissions” on page 52

● “Before You Begin” on page 53

● “Creating Users Using Shared Services” on page 53

● “Provisioning a New User Using Shared Services” on page 55

● “Creating a New Group Using Shared Services” on page 61

● “Provisioning a New Group Using Shared Services” on page 64

● “Modifying a Group Using Shared Services” on page 68

● “Deleting Groups Using Shared Services” on page 69


● “Deprovisioning Users or Groups Using Shared Services” on page 60

● “Migrating Multiple Users to Shared Services” on page 73

This chapter describes the Performance Scorecard portion of user provisioning only. For detailed instructions on using Shared Services, see the Hyperion System 9 Shared Services User Management Guide.

Access Permissions User provisioning through Shared Services requires configuration on the Shared Services server and Performance Scorecard applications. You can provision users and groups individually, or migrate users on Performance Scorecard to perform user provisioning for multiple users.

When you configure the application in the Configuration Utility after installing Performance Scorecard, use the Shared Services server, which automatically points to the Shared Services CSS.xml file for external authentication. This step enables Performance Scorecard and the Shared Services server to communicate seamlessly when provisioning users.

Note: The Shared Services Administrator is automatically provisioned to the Performance Scorecard application.

You can access Shared Services through Performance Scorecard or directly, using the URL to the User Management Console:

http://<server name>.hyperion.com:<port number>/interop

An overview of the process is presented inTable 9:

Table 9 Overview of User Provisioning Process

Environment Tasks Procedures

1. Configuration Utility

Select Shared Services, to automatically point to the Shared Services CSS.xml file for external authentication

Select user provisioning through Shared Services

Refer to the Hyperion System 9 Performance Scorecard Installation Guide

2. Shared Services Server

Create the project and application assignment through the Configuration Utility. Provision the users and groups on the Shared Services server and assign the appropriate security roles for the application. You can add individual users and groups, or you can migrate users from Performance Scorecard for bulk provisioning.

Refer to the Hyperion System 9 Shared Services User Management Guide


Before You BeginBefore you create and provision users using Shared Services, ensure these conditions have been completed:

● Performance Scorecard is registered on Shared Services

● Performance Scorecard is configured to use Shared Services-based provisioning, and to obtain the directory definition file from Shared Services (css.xml).

● Shared Services is running

● Performance Scorecard is running

● Performance Scorecard application is registered on Shared Services.

Registration is managed through the Hyperion® Configuration Utility™, and may be performed during installation or later. For instructions on configuring and registering Performance Scorecard applications with Shared Services, refer to the Hyperion System 9 Performance Scorecard Installation Guide.

Creating Users Using Shared Services You can create users for Performance Scorecard through Shared Services.

➤ To create users using Shared Services:

1 Ensure the Shared Services server is running.

2 Log on to Performance Scorecard with the user ID, admin, and the password, password.


3 From Performance Scorecard, select Administration > User Management.

The Hyperion System 9 Shared Services User Management Console is displayed.

3. Performance Scorecard

Synchronize Performance Scorecard user accounts with users created on Shared Services to update any changes in the users’ data with Shared Services. The provisioned users are displayed on the Users List in Performance Scorecard.

Refer to “Creating and Provisioning Users and Groups Using Shared Services” on page 51

Migrate multiple users from Performance Scorecard to Shared Services server

Refer to “Migrating Multiple Users to Shared Services” on page 73

Table 9 Overview of User Provisioning Process (Continued)

Environment Tasks Procedures


4 In the View pane, expand User Directories.

5 Select the directory in which the user is to be provisioned, for example, Native Directory.

6 From the directory list, select Users.

7 From the main User Management Console menu, select File > New > User.

The New User pane is displayed.

8 In the New User window, enter this information for the new user:

● Shared Services User ID

● First and Last Names

● Brief Description of the new user, such as Position, Department, and so on.

● E-mail address, in valid format, showing a name, @ symbol and extension, such as .com.


● Password for the User ID. Re-enter the password as confirmation.

9 Click Finish to complete the creation of the new user.

A Status message is displayed to advise the new user has been created, and the new user is displayed on the list of users.

After creating the new user, provision the user, as outlined in “Provisioning a New User Using Shared Services” on page 55.

Provisioning a New User Using Shared ServicesYou can create and provision users and groups for Performance Scorecard through Shared Services. The Shared Services administrator is automatically provisioned when the project is configured.

Note: To perform administrative tasks in Performance Scorecard, the admin user must be provisioned for use by the application. The registration process ensures that the admin user is automatically provisioned. Hyperion recommends that you use the Shared Services admin user to perform this task.

➤ To provision a new user using Shared Services:




3 From Performance Scorecard, select Administration > User Management.




5 Select the directory which contains the user who is to be provisioned.


7 From the list of user IDs in the View pane, select the name of the user who is to be provisioned.

You can select multiple users to provision simultaneously:

● To select a range of users, press Shift and select the first and last names in the range of users to be added.

● To select random users, press Ctrl and select individual users from the list.

8 From the main menu, select Administration > Provision.

The Provision User or Group window is displayed for the selected user.

9 Expand the available applications.

The available roles for each application are displayed.


10 Select the security role that contains the Shared Services level of permissions to be assigned to the selected user.

11 Click Save.

A Provision Summary is displayed to confirm provisioning of the user.

12 From the main menu, select Administration > View Report.

The View Report is displayed.


13 On the View Report, select the criteria which you want to use to generate the report:

● From Find all, select Roles.

● On For user, the user name is not selectable, because the user has already been selected for provisioning.

● Click Show Effective Roles to display the assigned roles on the report.

● From Group by, select whether you want to group the report entries by Application or User.

● Under In application, expand the tree and select the application for which you want to generate this report. Click Select All to include all applications.

14 Click Create Report.

The report displays the provisioning information as requested, including the project and application names, the user name and directory, and the user security role, if selected.

15 Optional: Click Print to print the report, or click Cancel to exit the report without printing.


16 From the View pane, select Projects, and expand the tree to select the project and application to which the newly provisioned user is assigned.

The Available Users and Groups for the selected project are displayed.

17 Select the name of the newly provisioned user from the list, and click Next.

18 On Manage Properties, click Select beside the newly provisioned user’s name.

The Select Employee dialog box is displayed.

19 From Select Employee, select the name of the Performance Scorecard user that is to be associated with the selected Shared Services user ID. This employee is the user to whom Performance Scorecard attributes are assigned.

20 Optional: From Primary Domain on the Manage Properties tab, select a Primary Domain for the user.


21 Under Security Roles, select the Performance Scorecard security role to be assigned to the user.

For detailed information on Performance Scorecard security roles, refer to “Security Roles” on page 23.

22 Click Finish to complete the provisioning of the user for Shared Services and Performance Scorecard.

23 Log on to Performance Scorecard.

24 FromObject View, select User Account List.

The list displays all Performance Scorecard users, including the newly provisioned user or group.

Deprovisioning Users or Groups Using Shared ServicesYou can deprovision users and groups for Performance Scorecard through Shared Services. When the user or group is deprovisioned, it is removed from all associated applications, but the user or group is not removed from the User Directories, and can be reprovisioned.

➤ To deprovision a user or group using Shared Services:




3 From the Performance Scorecard, select Administration > User Management.




5 Select the directory which contains the user or group that has is being deprovisioned.

6 From the directory list, select Users or Groups, as required.

7 From the list of user or group IDs, select the name of the user or group that is being deprovisioned.

The User pane is displayed, showing the basic information for the selected user.

8 From the main menu, select Administration > Deprovision.


Caution! The selected user or group will be deprovisioned for all associated applications.

9 Click OK.

A status message is displayed to advise that the selected user or group was successfully deprovisioned.


Creating a New Group Using Shared Services You can create and provision groups for Performance Scorecard through Shared Services.

Note: You must create the users for the application before creating any groups.

➤ To create groups using Shared Services:








5 Select the directory in which the group is to be provisioned, for example, Native Directory or LDAP.

6 From the directory list, select Groups.

7 From the main User Management Console menu, select File > New > Group.

The New Group page is displayed.

8 Enter this information:

● Name of the new group

● Brief Description of the purpose or membership for the group


9 Click Next.

The Group Members window is displayed.

10 From Provider, select the directory in which you want to add the new group, then click Go.

A list of all available groups for the selected directory is displayed in the top pane.

11 Select the new Group Name, then click Add.

The Group Name is added to the list in the lower pane.

12 Click Next.

The User Members window is displayed.


13 From Provider, select the directory that contains the users you want to add to the new group, then click Go.

A list of all available users for the selected directory is displayed in the top pane.

14 Select one or more users to add to the group, then click Add.

The selected users are added to the list in the lower pane.

15 Click Finish.

A Status message is displayed to advise the new group has been created.

After creating the new group, provision the group, as outlined in “Provisioning a New Group Using Shared Services” on page 64.

Provisioning a New Group Using Shared Services You can provision groups for Performance Scorecard through Shared Services.

➤ To provision a new group using Shared Services:




3 From the Performance Scorecard main menu, select Administration > User Management.



5 Select the directory which contains the group which is to be provisioned.


7 In Search, click Show All to display all available groups.


8 From the list of groups in the View pane, select the name of the group which is to be provisioned.




The Modify Group pane is displayed, showing the general information for the selected group.


The Provision Users or Groups window is displayed for the selected group.

10 Expand the list of applications.



11 Select the security role that contains the Shared Services level of permissions to be assigned to the selected group.

Users that are assigned to the group inherit the permissions of the provisioned roles.

12 Click Save.

A Provision Summary is displayed to confirm provisioning of the group.




14 Select the criteria which you want to use to generate the report:

● From Find all, select Groups.

● From For role, no name is selectable because the group has already been selected for provisioning.

● Click Show Effective Roles to display the assigned roles on the report.

● From Group by, select whether you want to group the report entries by Application or User.

● From In application, expand the tree and select the application for which you want to generate this report. Click Select All to include all applications.

15 Click Create Report.

The report displays the provisioning information as requested, including the project and application names, the user name and directory, and the user security role, if selected.



Modifying a Group Using Shared Services You can modify a group for Performance Scorecard through Shared Services.

➤ To modify a group using Shared Services:







5 Select the directory in which the group is to be provisioned, for example, Native Directory or LDAP.


7 Click Show All to display all groups for the selected directory, and select the group to be modified.

The Modify Group window is displayed.

Deleting Groups Using Shared Services 69

8 Optional: On the General tab of the Modify Groups window, change the name or description of the group.

9 Optional: Select the Group Members tab to add or remove additional groups from the main group.

10 Optional: Select the User Members tab to add or remove members from the group.

11 Click Save.

A Status message is displayed, advising that the group has been successfully modified.

12 Provision any added users, as outlined in “Provisioning a New User Using Shared Services” on page 55.

Deleting Groups Using Shared ServicesYou can delete a group for Performance Scorecard through Shared Services. Before deleting the group, ensure the group is no longer in use.

➤ To delete a group using Shared Services:








5 Select the directory in which the group to be deleted is located.


7 Click Show All to display all groups for the selected directory, and select the group to be deleted.

8 From the list, right-click the name of the group to be deleted.

Bulk Provisioning in Shared Services 71

9 Select Delete.


10 Click OK.

A Status message is displayed, advising that the group has been successfully deleted.

Bulk Provisioning in Shared ServicesYou can bulk provision users in Shared Services to create a large number of users in Performance Scorecard simultaneously.

Each of the items selected during bulk provisioning is assigned the same Shared Services security role. After saving the provisioned users, apply Performance Scorecard security roles individually to each user.

➤ To bulk provision users from Shared Services:



3 From Performance Scorecard, select Administration > User Management. to display the User Management Console.




5 Select the directory which contains the user who is to be provisioned.


7 From the list of enabled user IDs in the View pane, select the names of the users who are to be provisioned.




The User pane is displayed, showing the basic information for the selected user.


The Provision Users or Groups window is displayed for the selected users.

9 Expand the available applications to select the Shared Services role that is to be applied to all the selected users.


Migrating Multiple Users to Shared Services 73

10 Select the security role that contains the Shared Services level of permissions to be assigned to the selected user.

11 Click Save.

A Provision Summary is displayed to confirm provisioning of the users.



13 In Performance Scorecard, open each individual user that was provisioned from Shared Services, and apply the appropriate security role to each user, as outlined in “Creating User Accounts” on page 43.

Migrating Multiple Users to Shared ServicesWhen you have a large number of users to provision through Shared Services, you can perform a one-time bulk provisioning.

You can provision all members at once with the same security access. Subsequently, you can assign individual users who require access after the main transfer.

Caution! The Migration option is only available once. After migrating the bulk of your users in this one-time operation, the option is disabled and cannot be used again.

Before performing a migration, these tasks must be completed:

● Ensure that the Performance Scorecard Administrator exists in Shared Services, and has been assigned the security role of Provisioning Manager.

● Ensure that the Performance Scorecard application is registered and assigned to a project in Shared Services.


● Ensure that the e-mail addresses for all employees are in a valid and correct format, such as <user>@<provider>.com. Any users with incorrect e-mail addresses will not be migrated correctly.

When you are migrating users to a non-native authentication server, ensure these conditions are met:

● For NTLM, LDAP and MSAD authentication servers, ensure the users to be migrated already exist on the authentication server. For Native authentication, the migration automatically creates the users so they do not need to pre-exist.

● For NTLM, the Full Name field in the user account setup screen on the NTLM server must be specified in the following format:

'<Firstname> <Lastname>' (for example, John Smith)

Refer to the Hyperion System 9 Shared Services User Management Guide for detailed instructions.

➤ To migrate users to Shared Services from Performance Scorecard:



3 From Performance Scorecard, select Administration > User Provisioning Migration.

The Shared Services Administrator For Migration page is displayed.

4 Enter the User ID and Password for the Administrator. The migration administrator must exist in Shared Services, and have been assigned as the Provisioning Manager

The Pre-Migration Check page is displayed.


5 Click Perform Pre-Migration Check to verify data, and create the database tables for the migration.

A message is shown when the pre-migration progress check is complete.

6 Click OK.

7 Click Next.

The Externalize Users page is displayed, showing a list of all users in the model, their details and service provider. The Migration Action status is displayed as Migrate.

8 For each user that you DO NOT WANT to include in the migration, complete these steps:


a. Click Edit.

The Migration dialog box is displayed.

b. From Migration Action, select Do Not Migrate for the selected user, then click Save.

This user will not be included in the one-time migration. If the user subsequently needs to be added to the Shared Services list, add the user individually, as outlined in “Creating and Provisioning Users and Groups Using Shared Services” on page 51.

Caution! Because the Migration option is only available once, Hyperion recommends that you include as many users in the migration as possible. After migrating the bulk of your users in this one-time operation, the option is disabled and cannot be used again.

c. Repeat step a and step b for each user to be excluded from the migration.

9 Optional: When the list of users is complete, select Externalize Groups to select the groups to be migrated. The page shows a list of all groups in the model, the details and service provider. The Migration Action status is displayed as Migrate.


10 For each group that you DO NOT WANT to include in the migration, perform these steps:

a. Click Edit.

The Migration dialog box is displayed.

b. From Migration Action, select Do Not Migrate for the selected group, then click Save.

This group will not be included in the one-time migration. If the group subsequently needs to be added to the Shared Services list, add the group individually, as outlined in “Creating and Provisioning Users and Groups Using Shared Services” on page 51.


c. Repeat step a and step b for each user to be excluded from the migration.

Caution! Because the Migration option is only available once, Hyperion recommends that you include as many users in the migration as possible. After migrating the bulk of your users in this one-time operation, the option is disabled and cannot be used again.

11 When the list of users is complete, click Next to display the Migration to Shared Services page.


12 Click Test migration.

A confirmation is displayed when the test migration process is successfully completed.

13 Click OK to dismiss the message.

If a problem is indicated in the migration status messages, correct any errors and try again.

14 Click Migrate to begin the migration process.

A message is displayed to advise the migration has been successfully completed.

15 From the Shared Services main menu, select Administration > Provision Report to confirm users have been migrated correctly.

All migrated users are displayed, and have the inherited Performance Scorecard attributes for their security roles.


Generating Results Using Analytic Services 81

C h a p t e r

3Generating Results Using

Analytic Services

This chapter describes how to generate Hyperion® System™ 9 BI+™ Analytic Services™ (Analytic Services) databases using Analytic Services or other Hyperion reporting tools, such as Interactive Reporting and Enterprise Metrics.

Depending on your requirements, you can retrieve generated results using these options:

● Generate a Star Schema database that provides pre-defined tables which contain a standard set of data from Performance Scorecard and is stored in relational database tables. You must generate Star Schema tables if you are going to generate reports in Interactive Reporting. Generate Star Schema tables as outlined in “Generating the Star Schema Tables” on page 85.

● Generate an Analytic Services multidimensional database that contains all requested Performance Scorecard data and is stored in Analytic Services multidimensional database tables. Generate an Analytic Services database as outlined in “Generating an Analytic Services Database” on page 89.

Note: This chapter explains how to create Analytic Services databases of application data on Windows. To generate databases on a UNIX system, refer to the Hyperion System 9 BI+ Analytic Services Integration Services documentation suite.

In This Chapter About Star Schema Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

About Hyperion System 9 BI+ Analytic Services Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Retrieving Results in Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Customizing Analytic Services Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Scheduling Automatic Database Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

82 Generating Results Using Analytic Services

About Star Schema TablesStar Schema tables are a number of pre-defined tables that can be used to transfer data from Performance Scorecard. You must generate these tables before you can create reports in Analytic Services or other Hyperion applications, such as Interactive Reporting or Web Analysis. The Star Schema tables are created in Performance Scorecard, but only populated if you generate the star schema, as outlined in “Generating the Star Schema Tables” on page 85.

These Star Schema tables are available:

● “HPS_STAR_FACT” on page 82

● “HPS_STAR_STATUS_SYMBOL” on page 83

● “HPS_STAR_MEASURES” on page 84

● “HPS_STAR_SCORECARDS” on page 84

● “HPS_STAR_DIM_<dimension_name>” on page 85

Use the columns in the Star Schema tables as the basis for your customized reports, adding more columns as required.

Note: When defining dimensional outlines in Analytic Services, there are restricted characters that may not be used for naming. If you plan to generate Star Schema tables only, you do not need to conform to the Analytic Services naming conventions. However, if you might generate Analytic Services multidimensional databases now or in the future, Hyperion strongly suggests that you review the Analytic Services naming conventions described in the Hyperion System 9 Performance Scorecard Application Designer’s Guide or the Hyperion System 9 BI+ Analytic Services Administrator’s Guide to view the latest restrictions.

HPS_STAR_FACTThe pre-defined HPS_STAR_FACT table is created in Performance Scorecard to facilitate the export of all data for measures and dimensional measures into Analytic Services. You can use this table to export large amounts of data, then create reports using the information. Values are calculated and stored in the fact table.

The HPS_STAR_FACT table is created with a separate row for each instance of a measure on a scorecard, including this information:

● scorecard_id

● measure_id

● weight of the measure

● null value_date

A daily row is dedicated to a measure’s result, targets and scores, and given a null scorecard_id. A daily row is also created for scorecards, showing the score for each target and a null measure_id.

About Star Schema Tables 83

HPS_STAR_STATUS_SYMBOLUse the HPS_STAR_STATUS_SYMBOL table to customize reports that display your performance indicators.

HPS_STAR_DIM_TIMEThis table contains the column, VALUE_DATE, with one row for each day on which reporting is permitted. Values are calculated and placed in the fact table.

Table 10 HPS STAR_FACT Table

Column Description

MEASURE_ID ID of each measure. If you selected Create with Weights Included during the Analytic Services database generation from Performance Scorecard, this column displays the associated perspective.

PTD Result of the period-to-date calculation applied to a measure when it was created. For example, this value could be the sum of results collected for a measure over a specific period of time, such as a year.

SCORECARD_ID ID of each scorecard.

VALUE_DATE Date for which the values are being calculated and stored in the fact table.

RESULT Value for a measure used in calculations for a day.

COLLECTED_ RESULT

Result for the measure; however, if measure data was not collected on a specified day, a <NULL> value is displayed.

<target> Value of the target on VALUE_DATE.

<target>_SCORE Value of score as calculated using target on VALUE_DATE.

Table 11 HPS_STAR_STATUS_SYMBOL Table

Column Description

ID Unique ID of the status symbol (performance indicator) for the selected measure.

Name Name of the status symbol (performance indicator) for the selected measure.

Description Description, such as good performance, of a measure’s status symbol.

Symbol_URL URL of the image used for the status symbol.


HPS_STAR_MEASURESThis table enables you to drill down into non-dimensional and composite measures and measure templates. This is a parent-child table; however, no parent-child relationship is displayed for dimensional measures.

HPS_STAR_SCORECARDSThis table contains information about scorecards.

Table 12 HPS_STAR_MEASURES Table

Column Description

MEASURE_ID Unique, system-generated key for the measure in the CHILD_NAME column. The MEASURE_ID is referenced in the HPS_STAR_FACT table.

CHILD_NAME Name of every non-dimensional child measure.

PARENT_NAME Depending on the type of generation selected for the database, the following information is displayed in the PARENT_NAME column:

● If you selected Create with Weights Included to generate the database, this column displays the Perspective ID, if available. Otherwise, the entry in this column displays <No perspective>.

● If you selected Create with Measure Hierarchies to generate the database, this column displays the name of the parent measure. The associated non-dimensional child measures that are used in the result formulas of the parent measure are displayed in the CHILD_NAME column.

Note: A dimensional measure that is used in a result formula will not be displayed.

CHILD_UNIT Name of the unit for the measure in the CHILD_NAME column.

CHILD_PTD_FREQUENCY Frequency with which period-to-date calculations are performed on measure results, such as semi-annually, monthly, or weekly.

Table 13 HPS_STAR_SCORECARDS Table

Column Description

OWNER Name of the employee who owns the scorecard in the CHILD_NAME column prefixed with the text string “Owner”

CHILD_NAME Name of each scorecard in the application.

PARENT_NAME Name of the scorecard that is the parent of that in the CHILD_NAME column.

SCORECARD_ID Unique, system-generated ID created for the scorecard in the CHILD_NAME column. This is a foreign key to SCORECARD_ID in HPS_STAR_FACT.


HPS_STAR_DIM_<dimension_name>This table is created for each user-defined dimension in an application.

Before You BeginBefore you generate Star Schema tables, all spaces on the database schema must be set to be auto-expandable to ensure there is sufficient space to accommodate data being transferred.

Although it is not necessary to follow Analytic Services naming conventions to generate Star Schema tables, if you may generate an Analytic Services database in the future, you must conform to the Analytic Services naming conventions. If necessary, members are automatically renamed by the application to conform to the naming conventions. Refer to the Hyperion System 9 Performance Scorecard Application Designer’s Guide for a list of restricted characters.

Generating the Star Schema TablesYou can generate Star Schema tables that provide you with a pre-defined set of Performance Scorecard data. To generate an Analytic Services database based on your selection criteria, refer to “Generating an Analytic Services Database” on page 89.

If you plan to regenerate the Performance Scorecard Star Schema tables on a regular basis, you can schedule the star schema generation to automatically initiate the generation process as outlined in “Scheduling Automatic Database Generation” on page 95.

Table 14 HPS_STAR_DIM_<dimension name>

Column Description

CHILD_MEMBER_ID ID of the member in the CHILD_NAME column. This is a foreign key to <dimension_name>_ID in HPS_STAR_FACT.

CHILD_NAME Name of each member in the dimension prefixed with “<dimension_name>.”

CHILD_ALIAS Alias for the member in the CHILD_NAME column.

PARENT_NAME Name of the Parent of the member in the CHILD_NAME column prefixed with “<dimension_name>.”


➤ To generate Star Schema tables:



2 From the Performance Scorecard main menu, select Administration > Star Schema Generation.

The Star Schema Generation page is displayed.

3 Under Time Options, for Date Range, select the option for the period of time for which you want to generate data to be included in the Star Schema tables:

● Calculate for All Dates.

● Calculate for Dates, with an associated date range.

Note: Unless you require all dates, Hyperion recommends that you select Calculate for Dates to transfer data for a restricted date range.

4 Optional: If you selected Calculate for Dates, set the date range:

a. Beside From Date, click the calendar .

The Date Selector is displayed.

b. Choose the first date in the range, then click OK.

The selected start date is displayed.

c. Beside To Date, click the calendar .



d. Choose the last date in the range, then click OK.


5 Under Time Options, for Generate Star Schema Rows, select the type of information you want to include in the Star Schema rows:

● When Result, Target, Score Changes for a Measure or Scorecard. This option is selected by default, and creates a row for any result, target or scorecard that has changed from the previous day for the measure or scorecard.

● For Days From Frequency displays the data for the selected frequency, such as Daily, Weekly, and so on. This option only generates data for a measure or scorecard if that data is available on the frequency date. To set a frequency, click Select and choose the required frequency from the dialog box, then click OK.

● Every Day displays the data for every day from the selected start date to the end date.

6 Under Star Schema Structure, select the option you are using to generate the Star Schema. Because the measure dimension in an Analytic Services database may contain composite measure hierarchies and perspective measure hierarchies, specify the settings you want to use to create the Star Schema:

● Select Create with Measure Hierarchies to generate a star schema that produces the default database containing composite measure structures. Use this option to include composite measures, or measures used in the result formulas of other measures, in the Star Schema.

● Select Create with Weights Included to create a Star Schema that generates a database that includes perspective-measure weightings. Use this option to present perspectives as level 1 entities and the measures they categorize as their children in the Star Schema.

● Optional: Select Include Measures Linked to External Datasources only if you are specifying an external data source that contains data that is to be included in the Star Schema. For additional information, refer to “Using External Data Sources” on page 101.


7 Optional: Click the Conform to Analytic Services Naming Restrictions check box to automatically format all names to match the Analytic Services naming conventions. This option may involve removing restricted characters from names, truncating long names, and so on.

Note: Select this option if you plan to generate Analytic Services multidimensional databases now or in the future, or want to use the Star Schema for manual import. To view these naming restrictions, review the Analytic Services naming conventions described in the Hyperion System 9 Performance Scorecard Application Designer’s Guide or the Hyperion System 9 BI+ Analytic Services Administrator’s Guide.

8 DO NOT check the Generate Analytic Services Cube check box, as this option is used to generate an Analytic Services database.

9 Click Create Database to generate the Star Schema for the selected criteria.

During the database generation process, Performance Scorecard generates the HPS_STAR relational database table. Access your database to view the results in the Star Schema tables.

You can now use the results to generate reports through Interactive Reporting, as outlined in “Extended Customized Reporting” on page 183.

About Hyperion System 9 BI+ Analytic Services DatabasesYou can generate Analytic Services multidimensional tables that provide you with as much selected data as you want to view. To generate a pre-defined set of Performance Scorecard data in Star Schema tables, refer to “About Star Schema Tables” on page 82.

Caution! Hyperion strongly recommends that you carefully review this section before generating the Analytic Services database.

Before You BeginBefore you generate Analytic Services multidimensional databases, ensure these tasks have been completed:

● If you installed Performance Scorecard, Analytic Integration Services, and the Analytic Services OLAP server on one computer, ensure that you followed the integration installation instructions to generate the correct configuration files for all three products.

● Ensure that the Analytic Integration Services server is running on the same computer as your application database server.

About Hyperion System 9 BI+ Analytic Services Databases 89

● Ensure that the Analytic Services OLAP server is running.

● Locate the directory where you want to house the Analytic Integration Services XML files. These files define the structure of the Analytic Services database that is created.

● Set up an ODBC connection to the Performance Scorecard database.

● Set up an ODBC connection to the database that houses the Analytic Integration Services metadata catalog.

● Set all spaces on the database schema to be auto-expandable to ensure there is sufficient space to accommodate data being transferred.

● Ensure the names specified for dimensions, dimension members, databases, aliases, and targets do not contain any illegal or restricted characters, as outlined in the Hyperion System 9 Performance Scorecard Application Designer’s Guide. If any illegal characters are used, the

Analytic Services database generation may fail.

Generating an Analytic Services DatabaseYou can generate an Analytic Services database that contains all available data, based on your selection criteria. To generate Star Schema tables that provide you with a pre-defined set of Performance Scorecard data, as outlined in “Generating the Star Schema Tables” on page 85.

If you plan to regenerate the Analytic Services database on a regular basis, you can schedule the generation process to automatically initiate the update as outlined in “Scheduling Automatic Database Generation” on page 95.

Caution! Any previously generated Analytic Integration Services catalogs should be renamed to avoid being overwritten.

➤ To generate an Analytic Services Database:

1 Log on to Analytic Services.



3 From Performance Scorecard, select Administration > Star Schema Generation.



4 Under Time Options, select the Date Range for the data you want to include in the Analytic Services database. Unless you require all dates, Hyperion recommends that you select Calculate for Dates to transfer data for a restricted date range.

5 Optional: If you selected Calculate for Dates, set the date range:

a. Beside From Date, click the calendar .


b. Choose the first date in the range, then click OK.


c. Beside To Date, click the calendar .


d. Choose the last date in the range, then click OK.


About Hyperion System 9 BI+ Analytic Services Databases 91

6 Under Time Options, under Generate Star Schema Rows, select the options for the information you want to include in the Analytic Services database:

● When Result, Target, Scorecard Changes for a Measure or Scorecard. This option is selected by default, and creates a row for any result, target or scorecard that has changed from the previous day for that measure or scorecard.

● For Days From Frequency displays the data for the selected frequency, such as Daily, Weekly, and so on. This option only uses a date for a measure or scorecard if that date is in the set generated by the user selected frequency. To set a frequency, click Select, and choose the required frequency from the dialog box, then click OK.

● Every Day displays the data for every available date.

7 Under Star Schema Structure, select the option for generating the Analytic Services database. Because the measure dimension in an Analytic Services database may contain composite measure hierarchies and perspective measure hierarchies in which perspectives are parents with measures as their children, specify the settings you want to use to create the database:

● Select Create with Measure Hierarchies to generate a multidimensional database that produces the default Analytic Services database containing composite measure structures. Use this option to include composite measures, or measures used in the result formulas of other measures, in the database.

● Select Create with Weights Included to create a multidimensional database that generates an Analytic Services database that includes perspective-measure weightings. Use this option to present perspectives as level 1 entities and the measures they categorize as their children in the star schema.

● Select Include Measures Linked to External Datasources only if you are specifying an external data source that contains data that is to be included in the database. For additional information, refer to “Using External Data Sources” on page 101.

8 Click Generate Analytic Services database. When you select this option, two actions are initiated:

● The check box Conform to Analytic Services naming restrictions is automatically checked, as this option is a requirement to generate the database.

● The screen expands to show the additional information that is required to generate a complete Analytic Services database.


9 Under Hyperion System 9 BI+ Analytic Services Information, complete this information:

● In Server, enter the name of the computer on which the Analytic Services server resides. Both the Performance Scorecard application and the AIS server must be on the same computer.

● In Application, enter the name for the new Analytic Services application you are generating. The name can be up to 8 characters in length, and must conform to the Analytic Services naming conventions.

● In Database, enter the name for the Analytic Services database you are generating. The database name can be up to 8 characters in length, and must conform to the Analytic Services naming conventions.

● In Login and Password, enter the login and password used to access the Analytic Services server.

10 Under Hyperion Analytic Integration Services (AIS) Information, complete these boxes:

● In Hyperion AIS XML File Location, enter the full path to the directory on the Performance Scorecard application server where you want the AIS XML files to be created. The directory you specify must exist on the Performance Scorecard server.

● In HPS Source ODBC DSN, enter the data source name (DSN) that is linked to the Performance Scorecard relational database.

● In Hyperion AIS Catalog ODBC DSN, enter the data source name (DSN) that is linked to the Analytic Integration Services relational database.

Caution! Any previously generated Hyperion® System™ 9 BI+™ Analytic Integration Services™ (AIS) catalogs should be renamed to avoid being overwritten.

Retrieving Results in Microsoft Excel 93

● In Hyperion AIS Catalog User, enter the database user name of the user who has access to the Analytic Integration Services relational database.

● In Hyperion AIS Catalog Password, enter the password of the user who is authorized to access this database.

11 Click Create Database to generate the Analytic Services database for the selected criteria.

Performance Scorecard writes several XML files to the directory specified in Hyperion AIS XML File Location. LOG files identifying any errors may also be produced.

You should be aware that it may take hours to generate the Analytic Services database, depending on the number of dimensions, members, and measure results in an application. HPSImport.log documents the generation process. Review this file if the Analytic Services database was not generated.

Note: If you have Analytic Services and Analytic Integration Services running on the same server as Performance Scorecard, the model, meta outline, database, and application are automatically loaded in Analytic Services. Also, note that the OLAP model and meta outline created in this process are called HPSModel and HPSMotl.

You can examine the outline of the generated Analytic Services database in the Analytic Services Application Manager.

For information about working with the data in Microsoft Excel, see “Retrieving Results in Microsoft Excel” on page 93.

For information about viewing or modifying the Analytic Services database, refer to the Hyperion System 9 BI+ Analytic Services documentation. Specific guides are mentioned in “Customizing Analytic Services Databases” on page 94.

Retrieving Results in Microsoft ExcelMicrosoft Excel offers one option to retrieve and display database results, using the Analytic Services add-in menu in Microsoft Excel.

Note: If the Hyperion Essbase menu is not displayed in Microsoft Excel, refer to your Hyperion System 9 BI+ Analytic Services documentation.

➤ To view result data in Microsoft Excel:

1 Launch Microsoft Excel.

2 From the Microsoft Excel main menu, select Essbase > Connect.

The Essbase System Login dialog is displayed.

3 From Server, select the server you are using.

4 Enter a valid user name and password.

5 Click OK.


The available Analytic Services (Essbase) databases are displayed in the Application/Database list.

6 Select the database from which you want to retrieve results and click OK.

7 Select Essbase > Retrieve.

The database dimensions are displayed at the top of the spreadsheet.

If you want to create a custom report, refer to your Microsoft Excel or Analytic Services documentation.

Customizing Analytic Services DatabasesAfter generating an Analytic Services Database, you can use Analytic Integration Services and the Analytic Integration Services Console to modify or regenerate your Analytic Services database based on custom mappings.

Instructions for customizing Analytic Services databases are beyond the scope of this guide and Performance Scorecard. For information about customizing your databases and working with Hyperion System 9 BI+ Analytic Integration Services, refer to any of these sources:

Table 15 Hyperion System 9 BI+ Analytic Services Documentation Suite

Analytic Services Tool Document

Analytic Services Hyperion System 9 BI+ Analytic Services Database Administrator’s Guide

Analytic Administration Services Hyperion System 9 BI+ Analytic Administration Services Installation Guide

Analytic Administration Services Hyperion System 9 BI+ Analytic Administration Servicess Installation Guide

Analytic Integration Services Hyperion System 9 BI+ Analytic Integration Services System Administrator’s Guide

Hyperion System 9 BI+ Analytic Integration Services Data Preparation Guide

Analytic Services Spreadsheets Hyperion System 9 BI+ Analytic Services Spreadsheets Installation Guide

Scheduling Automatic Database Generation 95

Scheduling Automatic Database GenerationIf you plan to regenerate the Performance Scorecard Star Schema tables or the Analytic Services multidimensional database on a regular basis to keep custom reports up-to-date, you can schedule the database regeneration to run automatically at a convenient time.

Depending on your operating system, configure the GenerateCube.bat or GenerateCube.sh file before scheduling the database generation. If required, you can also run the appropriate GenerateCube file at any time.

➤ To schedule automatic database generation:

1 Depending on your operating system, navigate to the appropriate GenerateCube file:

● For a Windows operating system, navigate to the batch file: <HPS installation directory>\webappsconf\bin\generate_cube\ GenerateCube.bat

● For a UNIX operating system, navigate to the shell script file: <HPS installation directory>\webappsconf\bin\generate_cube\ GenerateCube.sh

2 Open the selected GenerateCube file in a text editor.

3 Modify the entries in the GenerateCube file to reflect your configuration for the database generation, as required. Depending on the operating system, each entry in the file is specified in the appropriate format:

● For Windows, the format is set <entry> = <value> For example, set HPS_Server=mainserver

● For UNIX, the format is setenv <entry> = <value> For example, setenv HPS_Server=UNIXserver

Refer to Table 16 for the available entries. Even if you do not plan to generate an Analytic Services database, you must leave a value for the Analytic Integration Services and Analytic Services-related entries; however, any non-blank value is acceptable.

Entries under the Required column on Table 16 are required when you generate the Star Schema or multidimensional database. Other entries are used to generate the multidimensional database only.

Caution! Only the fields listed in Table 16 should be modified. Do not modify any other information in the batch file.


Table 16 GenerateCube File Entries

Required Entry Type Description

X JAVA_HOME Directory Home directory of the JRE installation

X HPS_SERVER String Name of the machine that is hosting Performance Scorecard

X HPS_PORT Integer > 0 Port that Performance Scorecardis listening to. By default, this port is 18080.

X HPS_APPLICATION String Deployed name of the Performance Scorecard application under the application server. By default, this application is HPSWebReports.

X HPS_USER String Name of an administrator-level user in Performance Scorecard

X HPS_PASSWORD String Password for the user selected as HPS_USER

X XML_FILE Directory + Filename

Directory in which the XML files required by AIS to create the Analytic Services database are located

ESSBASE_SERVER String Name of the machine hosting the Analytic Services server

ESSBASE_ APPLICATION

String Name of the Analytic Services application under which the generated database will be placed. The application name must be 8 characters or less, and must conform to the Analytic Services Naming Conventions.

ESSBASE_CUBE String Name of the Analytic Services database that is to be generated. The name of the database must be 8 characters or less, and must conform to the Analytic Services Naming Conventions.

ESSBASE_USER String Analytic Services user, who has full access rights to the specified application and cube

ESSBASE_ PASSWORD

String Password for the user selected as the ESSBASE_USER

SOURCE_DSN String Name of the ODBC connection to the Performance Scorecard model database

CATALOG_DSN String Name of ODBC connection to the AIS Catalog database

CATALOG_USER String User with access rights to the AIS Catalog database

CATALOG_ PASSWORD

String Password for the user selected as the CATALOG_USER

GENERATE_CUBE Boolean Enter the appropriate value to generate the database:

● Enter True to generate the Analytic Services database

● Enter False to only generate the Star Schema tables. By default, this value is set to False.


X CUBE_TYPE

cubeMeasure String Generate the Analytic Services database using the hierarchical structure.

cubeWeights String Generate the Analytic Services database with Weights included.

X FROM_DATE Date Enter the start date for which the database rows are to be generated, in the format yyyy/MM/dd.

X TO_DATE Date Enter the last date for which the database rows are to be generated, in the format yyyy/MM/dd

CONFORM_TO_ ESSBASE_NAMING

Boolean Set to True to modify measure and scorecard names to conform to Analytic Services naming rules. By default, this value is set to false.

X ROW_FREQUENCY Integer Enter the appropriate value:

0 - Generate Star Schema rows only when result, targets or scores change

1 - Generate rows based on a frequency. If this option is selected, complete these fields:

FREQUENCY_CODE

SUB_FREQUENCY_CODE

INTERVAL

DAY_OF_PERIOD

2 - Generate a row for every day

X FREQUENCY_ CODE

Integer Required if ROW_FREQUENCY = 1. Enter the value for the frequency type:

0 - None

1 - Daily

2 - Daily MF (Monday to Friday, excluding weekends)

3 - Weekly

4 - Semi-Monthly

5 - Monthly

6 - Quarterly

7 - Semi-Annually

8 - Annually

9 - Monthly, Week Based

Table 16 GenerateCube File Entries (Continued)



X SUB_FREQUENCY_CODE

Integer Required if ROW_FREQUENCY = 1. Enter the value for the sub-frequency type:

0 - First

1 - Last

2 - Sunday

3 - Monday

4 - Tuesday

5 - Wednesday

6 - Thursday

7 - Friday

8 - Saturday

9 - First Sunday

10 - First Monday

11 - First Tuesday

12 - First Wednesday

13 - First Thursday

14 - First Friday

15 - First Saturday

16 - Last Sunday

17 -Last Monday

18 - Last Tuesday

19 - Last Wednesday

20 - Last Thursday

21 - Last Friday

22 - Last Saturday

23 - User Defined

24 - No Weekend

X INTERVAL Integer Required if ROW_FREQUENCY = 1. Enter the value for the interval, The value must be greater than 0.

X DAY_OF_PERIOD Integer Required if ROW_FREQUENCY = 1. Enter the value for the sub-frequency type in the format “xth day of period.” The value must be greater than 0.

X LOG_LEVEL String Level of information provided by the generation process. The Log Level can be set to one of these values:

ERROR

WARN

INFO

DEBUG

By default, this value is set to WARN.

Table 16 GenerateCube File Entries (Continued)



4 Save the GenerateCube file.

5 Schedule the database generation as outlined below for your operating system:

● To schedule database generation on the Windows operating system, select Start > Programs > Accessories > System Tools > Scheduled Tasks > Add Scheduled Task.

The Scheduled Task Wizard is displayed. Follow the steps in the Wizard to create a schedule for executing the GenerateCube batch file. During this process, you navigate to the GenerateCube file, select a frequency, then set the date and time to start the task.

● To schedule Star Schema generation on the UNIX operating system, use the cron utility. For detailed instructions, refer to the UNIX product documentation.

The Star Schema or multidimensional database generation will be run at the scheduled time. Any errors encountered during the generation, either locally or from the server, are posted to

the console.


Using External Data Sources 101

C h a p t e r

4Using External Data Sources

You can use external data sources, such as Hyperion® System™ 9 BI+™ Analytic Services™ (Analytic Services) or Hyperion® System™ 9 BI+™ Enterprise Metrics™ (Enterprise Metrics) to populate a Hyperion System 9 Performance Scorecard model.

The outlines and dimensional configuration are mapped, and configuration and data selection are completed through the Performance Scorecard Administrator’s work space. Time hierarchies in the external data sources are aligned with the Performance Scorecard calendar and period configuration.

Note: If you are using Analytic Services with Performance Scorecard, ensure that the names specified for dimensions, dimension members, databases, aliases, and targets do not contain any illegal or restricted characters. For the Analytic Services naming conventions, refer to the Hyperion System 9 Performance Scorecard Application Designer’s Guide or the Hyperion System 9 BI+ Analytic Services Administrator’s Guide for the latest restrictions.

In This Chapter About External Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Analytic Services Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Working with External Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Defining an External Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Synchronizing Analytic Services with Imported Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Modifying an External Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Deleting an External Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

102 Using External Data Sources

About External Data SourcesExternal data sources, such as Analytic Services or Enterprise Metrics, can be used to populate a model with metadata and data. You can use data from multiple external data sources to generate a single Performance Scorecard database. Dimensional measures that retrieve their data from external data sources must already exist within the Performance Scorecard model.

Note: If you are using Analytic Services, you can make changes in the source or destination and the changes are reflected instantly; however, if you are using Enterprise Metrics, make your changes in the Enterprise Metrics source data, and import the changes into Performance Scorecard.

To use the external data sources, you must define the outlines and dimensional configuration for Performance Scorecard, and align the time hierarchies in the external data sources with the Performance Scorecard calendar and period configuration.

Through the Performance Scorecard Administrator’s work space, you select the dimensions that are to be imported into Performance Scorecard, and the depth of information that is required. These general steps are required to set up the external data source:

● Define the general attributes of the Data Source, including the name and connection information

● Select the Measure dimensions that are to be imported into Performance Scorecard

● Select the Values dimension to specify the dimensions that identify the results and targets, and the Results Member that contains the results.

● Map the time dimensions in the external data source to the time dimensions in Performance Scorecard to enable results and targets to be successfully retrieved.

● Select additional Other dimensions to be imported to Performance Scorecard, and the depth of dimensions you want to include.

● Select the Pinned dimensions to be used for static values, such as currency. These dimension provide perspective to the other values.

After defining the external data sources, you point to those external data sources through the Measure Template Setup and Target Setup pages in Performance Scorecard. If required, you can select a Data Writable option to ensure any changes made in Performance Scorecard are written back to the external data source. If changes are made in the external data source, you can synchronize the metadata and data with Performance Scorecard.

When selecting dimension to import, a dimension can only be selected once. After it is used, the same dimension cannot be selected again.

To maximize performance, Hyperion recommends that you perform any calculations in the external data source, and then import the calculated values. This option enhances the import time, and ensures that complicated calculations are accomplished in the application to which they are best suited.

External dimensions are not displayed in the Dimension Setup page, and cannot be modified within Performance Scorecard.

Defining an External Data Source 103

Analytic Services Database RequirementsIf you are using an Analytic Services multidimensional database as an external data source, you must meet these requirements:

● The database must have a single dimension containing the members that correspond to measures used in Performance Scorecard, such as the Accounts dimension.

● The database must have a single dimension containing the members corresponding to targets used in Performance Scorecard, such as the Results.

● The dimension in the database that corresponds to time must use one of these conventions:

❍ A single dimension, or

❍ Two dimensions: one dimension for intra-year periods, such as months or quarters, and one dimension for the years. Members corresponding to individual years must be placed at the leaves.

● The database must place the results within the intersection of the dimensions, or have a member in the Values dimension that corresponds to results

● The database may not have time elements that are more frequent than daily.

Working with External Data SourcesYou must configure an external data source to import metadata and data into Performance Scorecard. Refer to these procedures for detailed instructions on working with external data sources:

● “Defining an External Data Source” on page 103

● “Synchronizing Analytic Services with Imported Data” on page 113

● “Modifying an External Data Source” on page 115

● “Deleting an External Data Source” on page 115

Defining an External Data SourceWhen you use existing external data sources to populate a Performance Scorecard model, the external data sources must be defined so Performance Scorecard can access and use their metadata and data.

Although Performance Scorecard and Enterprise Metrics use multidimensional databases, there may be slight differences between the external data source tabs, based on requirements. For example, Enterprise Metrics does not require specification of the Measures and Values dimensions.


Caution! If you are using an Analytic Services database as your external data source, ensure the Analytic Services server is running before you start your application server; otherwise, the application tries to connect to Analytic Services, which creates a string of exceptions in the console.

To define an external data source, complete the series of tabs on the External Data Sources window to provide the required information. An overview of the entire process includes these steps:

● Creating a new data source on the Data Source General tab

● Selecting the Measures dimension for the external data source. This step is not required for Enterprise Metrics.

● Selecting the Value dimension for the external data source. This step is not required for Enterprise Metrics.

● Mapping the time dimensions in the external data source to Performance Scorecard. This option is required for Analytic Services only.

● Selecting the Other dimensions to be included, such as Measure, Value and Time.

● Defining any Pinned dimensions, such as currency or a version number, that are not imported but are used to provide perspective to the database.

After defining the external data source, the imported information is available directly in Performance Scorecard.

Note: If you are using Analytic Services, you can make changes in the source or destination and the changes are reflected instantly; however, if you are using Enterprise Metrics, make your changes in the Enterprise Metrics source data, and import the changes into Performance Scorecard.

➤ To define an external data source:


2 From the main menu, select Administration > Data Source List.

The Data Source List is displayed.


3 Click Add to add a new external data source to the list.

The Data Source tab is displayed.

4 Under Data Source Type Specification, select the type of data source you want to add to the list of

available data sources, then click Next.

The General Attributes tab is displayed, showing the Data Source General page.


5 Enter the details for the external data source:

6 After entering all the details for the selected data source, click Test Connection to ensure you can connect to the external data source.

If there is no connection, an error message is displayed. Verify your connection details, and re-enter the information. You can test your connection at any time, from any page on which the button is available.

Table 17 External Data Source Details

Text Box Description

Name The unique name to use when referencing this external data source. This name is used when you select the external data source on the Measure Template Setup page, as outlined in step 31 on page 112. This field is required.

Description A brief explanation of the contents or purpose of this external data source.

Server The name of the machine that is hosting the server. This field is required.

Port The number of the port of the Analytic Services or Enterprise Metrics server. By default, 1423 is displayed. This field is required.

Application The name of the Analytic Services application that contains the multidimensional database. This field is required for Analytic Services; however, it is not visible for Enterprise Metrics.

Analytic Services Database

The name of the database that contains the data. This field is not displayed for Enterprise Metrics.

User Name The user ID that is required to log in to the remote server. This field is required.

Password The password that is required to log in to the remote server. This field is required.

Confirm Password Re-enter the password to confirm. This field is required.


7 Click Next.

Depending on the external data source type you selected, continue with the appropriate steps:

● For Analytic Services, the Measure Dimension tab is displayed, showing Accounts by default. Continue with step 8 on page 107 to set the Measure and Value dimensions.

● For Enterprise Metrics, continue with step 13 on page 108 to define the time mappings.

8 Under Measure Dimension, click Select to display the Measure Dimension List, showing all available dimensions in the database. Select the measure dimensions that are to be imported into Performance Scorecard. Dimensions such as Time, Values, and Measures, are not included on the list. Dimensional measures that retrieve their data from external data sources and the dimension members to which they relate must exist in the Performance Scorecard model.

Note: After a dimension is imported into Performance Scorecard, it cannot be modified within the application.

9 Click Next.

10 Depending on the external data source you selected, continue with the appropriate step:

● For Analytic Services, the Values Dimension tab is displayed. Continue with step 11.

● For Enterprise Metrics, continue with step 13 on page 108. The Value Dimension tab is not used for the Enterprise Metrics Server.

11 From Value Dimension, select the name of the Analytic Services dimension that was set as the Values dimension.


The Values Dimension tab is used to specify which of the dimensions in the external database identify the results and targets, and the depth of detail that is to be presented to the Performance Scorecard designers.

12 Under Result Member, click Select to choose the name of the member from the Values dimension that contains the results you want to use.

The Result Member dialog box is displayed, showing all available dimensions in the database. Dimensions such as Time, Values, and Measures, are not included on the list. Select the appropriate Results Member. Dimensional measures that retrieve their data from external data sources and the dimension members to which they relate must exist in the Performance Scorecard model.

13 Click Next.

The Time Mapping tab is displayed. This tab is used to select the dimensions that identify time in

the external data sources, and how the dimension members can be mapped so Performance Scorecard can retrieve results and targets. For Enterprise Metrics, only Period Generation is

displayed.

14 From Number of Time Dimensions, select the appropriate value to set the time dimension:

● Select 1 to hide the Year Dimension and Select Year Dimension elements. This option is set as the default.


● Select 2 to show the Year Dimension and Select Year Dimension elements. The Year Dimension shows the name of the dimension that signifies years in the external data source. The Select Year Dimension enables you to select a list of all dimensions in the Analytic Services database, except measures or comparator, to set the year dimension label to the chosen dimension.

15 Under Period Dimension, click Select.

16 From the Period Dimension List, set the period dimension label to the selected dimension.

17 Under Start Date, click the calendar to display the Date Selector.

The current time dimension start date, if one exists, is displayed. From the Date Selector, select the Start Date that maps to the first member in the time and year member.

18 Under Period Generation, click Select.

The Select Dimension Member dialog box is displayed.

19 Select the member from the dimension to represent the generation or depth of the dimension to be used in Performance Scorecard. For example, if you select “January,” the monthly generation is used. If you select “week 1,” the weekly generation is used.

20 From Period Generation Significance, select the required frequency for the time dimension generation, such as Day, Week, Month (default) or Quarter.

Performance Scorecard uses these attributes to provide default Scorecard date values for each row. If these attributes are changed, Performance Scorecards regenerates this table with default values.

21 On the manual mapping table at the bottom of the page, review the dates for the pairs of time members displayed on the table. These members are taken automatically from the Analytic Services database, showing the generation level that you selected.

If required, click the calendar to manually select a different date for individual members. If you want to remove one or more members from the generated database, click Delete.

22 Click Next.

The Data Source Other Dimension page is displayed on the Other Dimensions tab.


External dimensional measures are created from the intersections of dimensions other the Measure, Value and Time dimensions; however, some of these dimensional measures may not be applicable to Performance Scorecard. The Other Dimension tab enables you to specify which of these other dimensions should be imported to be attached to Performance Scorecard measures.

23 Click Add.

The Other Dimension List dialog box is displayed, showing a list of the names of all available external data source dimensions, except Attribute dimensions or any dimensions that have already been specified as Measure, Values or Time.

24 Select the name of the other dimension to be imported.

The dialog box is closed, and a new row is added to the Dimension Table.

25 From Dimension Depth, select the number of levels of data to be imported for the newly added dimension. Zero (0) represents the root level of the dimension.

When selecting the number of levels of data, be aware that additional levels added in the future may require you to redefine the external data source to accommodate the extra levels. For example, if you select the highest depth of 3 for three levels, even if additional levels are added, only three levels are reported. However, the selection “No Restriction” returns values for all levels, and automatically adds any future extra levels.

26 Click Next.

The Pinned Dimensions tab is displayed.

Pinned dimensions contribute the same status members to all data queries to Analytic Services multidimensional databases. For example, if the multidimensional database contains a “Scenario” dimension, and they only want to view the “Current” scenario within Performance Scorecard, you can pin the dimension “Scenario” to “Current.”

These dimensions do not need to be imported into Performance Scorecard, but may be required to provide perspective to data queries. Using the Pinned Dimensions tab, you can specify the pinned members for non-attribute dimensions, such as Measures, Values or Time.


27 Click Select.

The Dimension Member List is displayed.

28 Select the name of the dimension in the external data source to update the “Pinned Member” label, then

click Save.

The Pinned Member is the name of the member that is used in data queries to provide perspective for the database view, for example, a currency or version.

29 Click Save.

30 Create the new target for the external data source:

a. From the Object View tab, select Target List to display the Target Setup page.

b. Create one or more new targets, as outlined in the Hyperion System 9 Performance Scorecard Application Designer’s Guide.

c. On the Datasources tab, click Edit.

The selected Dimension member is displayed on the Datasources tab.

d. Click Save to save the new target.


31 Create the Measure Template for the new external data source:

a. From the Object View tab, select Measure Template List.

b. Click Add to display the Measure Template Setup page.

c. Create the new measure template, as outlined in the Hyperion System 9 Performance Scorecard Application Designer’s Guide.

Note: When creating the measure template, it is not necessary to enter a name because the name of the selected measure is automatically used.

d. Under Data Source, select the external data source from the list. The pane expands to show the Member option.

e. Beside Member, click Select to display the Select Dimension Member list.

f. Select the appropriate member. The member name is displayed.

g. Optional for Analytic Services only: Click Data Writable if you want to write data back to the external data source. This option is not available for Enterprise Metrics.

h. On the Dimension/Member table, click Add.

The Select Dimension Member hierarchy is displayed.

Synchronizing Analytic Services with Imported Data 113

i. Select the dimension.

j. The dimension is added to the Dimension/Member table.

k. Click Save.

After the Measure Template is saved, the results are available on the Browser View tab.

32 From the Browser View tab, expand Measure.

33 Select the measure template that you created.

When you click on the measure template, the results for the imported measure, as they exist in Analytic Services, are displayed on the Trending Table report.

Synchronizing Analytic Services with Imported DataIf changes are made in the external data source, you must synchronize the metadata and data with Performance Scorecard in these circumstances:

● Changes to metadata involve modifications to the multidimensional database outline or structure. For example, to add a new department to the corporate organization would require changes to the outline.

● Changes to data involve modifications to the values for an item. For example, you might want to modify figures in your Budget to reflect an increase or decrease in the budget values.


➤ To synchronize Performance Scorecard with the external data source:


2 From the Performance Scorecard main menu, select Administration > Data Source List.


3 Select the external data source which needs to be synchronized with changes in Performance Scorecard.

4 Depending on the type of changes made in the external data source, synchronize Performance Scorecard:

● Click Metadata Synchronize if the metadata in the structure of the database has been modified. For example, if the corporate structure is realigned, the new organizational structure must be reflected in the database outline.

● Click Data Synchronize if the data in the database has been modified. For example, if your budget value is increased, click Data Synchronize to show the new values on the imported

measure template.

If changes have been made to the both metadata and data, perform both operations. If no matching external data source is found, an error message is displayed. Review the external data source settings, and try again.

A confirmation message is displayed when the synchronization is complete.

Deleting an External Data Source 115

Modifying an External Data SourceYou can modify an external data source to change the depth restriction, members or other information.

➤ To modify an external data source:


2 From the main menu, select Administration > Data Source List.


3 Select the name of the external data source to be modified.

4 Click Modify.

The Data Source General page is displayed.

5 Select each tab and change the information to be modified.

6 Click Save.

Deleting an External Data SourceAlthough you can delete an external data source, Hyperion recommends that you delete the associated measure templates before deleting the external data source.

Caution! If you delete an external data source, all measures remain withinPerformance Scorecard, but all associated data is deleted.

➤ To delete an external data source:


2 From the Object View tab, select Measure Template List.

The Measure Template List is displayed.

3 Select the measure template that is to be deleted, and click Delete.



The selected measure template is deleted and removed from the Measure Template list. Any measures associated with the template revert to local measures, and associated data is deleted.

5 From the Performance Scorecard main menu, select Administration > Data Source List.

The Data Source General page id displayed.

6 Select the name of the external data source to be deleted.

7 Click Delete. A confirmation message is displayed.



The external data source and any related measures and results are deleted from Performance Scorecard. Also, the pointer to the external data source on the Measure Template page, and the target on the Target Setup are also removed.

Promoting and Migrating Application Data 117

C h a p t e r

5Promoting and Migrating

Application Data

This chapter describes how to migrate application data from one environment, such as development, to another, such as testing.

You cannot promote application data if you delete the records in the HPS_AUDIT_TRAIL database table; however, you can use the Compare Audit Trails function to compare the records in the HPS_AUDIT_TRAIL database table and still retain the ability to promotion. Refer to “Using the Audit Report” on page 209 on instructions to invoke the function.

In This Chapter About Promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Before Promoting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Promoting Application Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

118 Promoting and Migrating Application Data

About PromotionPromotion enables you to transfer application data to a different environment. It ensures that changes made to a source application are reflected in a target, or secondary environment.

You can migrate application data between platforms, databases, and Web application servers supported by Performance Scorecard. For example, you can promote an application created in a development environment on UNIX using IBM DB2 and WebSphere to a Microsoft Windows test environment that uses Oracle and WebLogic.

Although you can promote a domain object, you cannot promote domain relationships. For example, although you can promote the Domain called Sales, you cannot promote the users or other object within that domain.

These sections describe the role of external application profiles, and identify the business objects that cannot be promoted:

● “External Application Profiles” on page 118

● “Non-Promotable Business Objects” on page 118

External Application ProfilesPerformance Scorecard keeps track of the server to which business objects are promoted using external application profiles. These profiles contain the parameters used to connect and promote data to a different, target environment. These connection parameters include the target application’s host name, port number, user ID, and password.

Non-Promotable Business ObjectsAlthough you can promote most business objects in an application, some business objects such as measure results and target values, should not be promoted because the information they contain is typically entered by users.

These business objects cannot be promoted:

● Measure results and target values

● User accounts, security roles, permissions, and restrictions

● Initiatives

● Notes

● Variable values

● Uploaded attachments and files

Although you can promote a domain object, you cannot promote domain relationships. For example, although you can promote the Domain called Sales, you cannot promote any users in that domain.

Promoting Application Data 119

Before Promoting DataYou must perform these tasks before promoting application data:

1. Ensure that a relational application database exists in the target environment to which you are promoting application data. This database does not have to be empty.

2. Assign the admin security role to the user whose user ID is used as the server login in the target promotion environment.

3. Ensure that all users have finished making changes to application business objects and have logged off Performance Scorecard.

4. Ensure that you have the following information about the environment to which you are promoting:

❍ Name of the computer hosting the target database

❍ Port number of the web server

❍ Username and password used to access the Performance Scorecard application on the target computer to whose database you are promoting data

Promoting Application DataDepending on the size of the application, the first time you promote data, the promotion process may be lengthy. The process is much faster the next time you promote to the same environment.

➤ To promote application data:

1 Navigate to http://<computer name>:<port number>/HPSWebReports.



3 Select Administration > Promotion.

The Configured External Application list is displayed, identifying any external application you may have already defined. Each external application contains the parameters needed to connect to the environment to which you want to promote data. You can use Edit and Delete to modify the list, if required.


4 Click Add.

The External Application Setup page is displayed.

5 In Name, enter the name of the external application, for example, Testing, Production and so on.

6 In Description, enter a description of the location of the external application, such as an environment or office.

7 In Server Name, enter the name of the server on which the target Performance Scorecard application you want to update is running.

8 In Server Port, enter the port number for the server.

9 From Server Protocol, select the appropriate server protocol.

Promoting Application Data 121

Note: Because HTTPS protocol lengthens the promotion process, only use it if necessary.

10 In Application Name, enter the name for the application. Usually, this name would be HPSWebReports.

11 In Server Login, enter the user ID used to log on to the external target Performance Scorecard application.

Note: The user whose ID you specify must have the admin security role assigned to their account in the target application.

12 In Password, enter the password used to log on to the external target Performance Scorecard application. Re-enter the password in Confirm Password.

13 Optional: If the external application uses LDAP or NTMLM security directories, in Domain, enter the domain.

14 From Promotion Profile, select the promotion profile.

15 Optional: Click Test Connection to verify that all the connection information is correct, and the system can connect to the target application.

16 Click Save to return to the External Application List.

17 Select the external application that you created and click Promote to Selected Application.

A progress page is displayed, showing the progress of the promotion and the result. A message is displayed to advise when the promotion is complete.

Note: You should reuse this application server entry for future promotions to the same application server.


Backing up and Restoring Attachment Files 123

C h a p t e r

6Backing up and Restoring

Attachment Files

File attachments for objects such as measures, notes and annotations are stored in a folder on the Web application server. If you upgrade Hyperion System 9 Performance Scorecard or uninstall the Web application server, these files are lost unless they are backed up.

Hyperion recommends that you regularly back up these files to another local or network directory. This backup directory can be restored if you upgrade the product or uninstall the Web application server.

In This Chapter Backing up Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Restoring Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

124 Backing up and Restoring Attachment Files

Backing up AttachmentsHyperion recommends that you create a backup directory of all the attachment files used in an application to which you can revert if necessary, or before you uninstall the application.

➤ To back up attachment files:

1 Create a local or network backup directory.




4 Select Administration > Attachment Backup.

The Backup Directory page is displayed.

5 In Backup Directory, enter the path to the backup folder you created.

6 Click Backup.

All attachment files are placed in this directory.

Restoring AttachmentsThis section explains how to restore attachment files from a backup directory after reinstalling or upgrading the Web application server.

➤ To restore attachments:



The Performance Scorecard Administrator opens.

3 Select Administration > Attachment Backup.

The Backup Directory page is displayed.

4 In Backup Directory, enter the path to the backup directory and click Restore.

The attachment files are available to the Web application server and are displayed in applications.

Managing Shared Services Models 125

C h a p t e r

7Managing Shared Services

Models

This chapter describes Hyperion System 9 Shared Services models as they are shared between multiple Hyperion products.

Shared Services functionality is programmed into products, such as Hyperion® System™ 9 Planning™, Hyperion® System™ 9 Financial Management™, and Hyperion System 9 Performance Scorecard. Shared Services integrates the products to provide these functionalities:

● User provisioning

● External authentication definition

● Metadata synchronization

● Data synchronization

● Task flow management

User provisioning functionality is described in the Hyperion System 9 Shared Services User Management Guide available on the Hyperion Download Center. External authentication definition is described in the Hyperion System 9 Shared Services Installation Guide available on the Hyperion Download Center. All other Shared Services functionality is described in the administrator’s and user’s guides for the products that implement Shared Services. Products that implement Shared Services functionality require access to a Shared Services server running Shared Services client and server software, and to a database dedicated to Shared Services.

For product-specific information about how to use Shared Services with Performance Scorecard, refer to the sections in this chapter.

For information about user provisioning for security roles in Performance Scorecard and Shared Services, refer to “Managing User Accounts and Authorization” on page 21

In This Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

About Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Registering Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

About Managing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

About Sharing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

About Sharing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

126 Managing Shared Services Models

Working with Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Working with Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Sharing Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

OverviewShared Services enables multiple applications to share information within a common framework. This table lists the high-level tasks that you can perform with Shared Services.

About ModelsShared Services provides a database, organized into applications, in which applications can store, manage, and share metadata models. A model is a container of application-specific data, such as a file or string.

There are two types of models:

● Ddimensional hierarchies such as entities and accounts

● Nnondimensional objects such as security files, member lists, rules, scripts, and Web forms.

Some Hyperion products require that models be displayed within a folder structure (similar to Windows Explorer). Folder views enable the administrator to migrate an entire folder structure or a portion of a folder structure easily using Shared Services.

The process of copying a model or folder from a local application to Shared Services is known as exporting. The process of copying a model or folder from Shared Services to a local application is known as importing.

Prerequisites Shared Services supports external directories for user authentication. To use Shared Services functionality, configure Performance Scorecard to use Shared Services user directory definitions.

Note: After installation of Shared Services, configure external authentication. For more information about installation and configuration of Shared Services, see the Hyperion System 9 Shared Services Installation Guide.

Task For Information

Managing Models “About Managing Models” on page 127

Sharing Metadata “About Sharing Metadata” on page 128

Sharing Data “About Sharing Data” on page 128

About Managing Models 127

To work with Shared Services, the Performance Scorecard user requires an admin or designer security role. From Shared Services, the admin must assign the correct Shared Services roles to work with applications in Shared Services:

● Manage Model role enables the user to work with models and manage projects and applications. See “About Managing Models” on page 127.

● Create Integrations role enables the user to create and control integrations. See “About Sharing Data” on page 128.

● Run Integrations role enables the user to run scheduled integrations. See “About Sharing Data” on page 128

For information about user provisioning for security roles in Performance Scorecard and Shared Services, refer to “Managing User Accounts” on page 43.

Registering ApplicationsBefore you can use Shared Services, register your product with Shared Services using the Configuration Utility. For more information about using the Configuration Utility to register your product with Shared Services, see the Hyperion System 9 Performance Scorecard Installation Guide.

About Managing ModelsShared Services enables you to store metadata models and application folders. A separate application is provided for each product.

Shared Services provides some of the basic management functionality for models and folders:

● Version tracking

● Access control

● Synchronization between models and folders in the application and corresponding models and folders in Shared Services

● Ability to edit model content and set member properties of dimensional models

● Ability to rename and delete models

Users must be assigned the Manage Models user role to perform the preceding actions on Shared Services models.

Note: The Manage Models user must have Manage permission for a model via the Shared Services Model Access window to assign permissions to it.

For information about models, see “Working with Models” on page 133 .

For information about assigning user roles, see the Hyperion System 9 Shared Services User Management Guide.


About Sharing MetadataShared Services enables products to store private applications, nonshared models, and to share common models through common applications. Shared applications free multiple applications from maintaining a web of connections. To share an application, Administrators first share the applications using the common application by exporting the model to the application directory in Shared Services, then specify the shared models. Because filters specify the model during import, they also enable the sharing of asymmetric models between applications.

See “Working with Shared Applications” on page 129 for the basic process of setting up and implementing sharing among applications.

About Sharing DataIn addition to sharing application metadata, Shared Services enables you to move data between applications. The method used to move data is called data integration.

Data integration definitions specify the data moving between a source application and a destination application, and enable the data movements to be grouped, ordered, and scheduled. A data integration wizard is provided to facilitate the process of creating a data integration.

Users must be assigned the Create Integrations user role to create Shared Services data integrations. As a Create Integrations user, you can perform these actions on data integrations:

● Assign access to integrations

● Create an integration

● Edit an integration

● Copy an integration

● Delete an integration

● Create a data integration group

● View (including filtering the view of) an integration

To view and run Shared Services data integrations, users must be assigned the Run Integrations user role. As a Run Integrations user, you can perform these actions on data integrations:

● View (including filtering the view of) an integration

● Run, or schedule to run, an integration

● Run, or schedule to run, a group integration

Before data can be moved between applications, the models for the source and destination application must be synchronized between Shared Services and the product.

For details about moving data between application, see “Sharing Data” on page 160.

For information about assigning user roles, see the Hyperion System 9 Shared Services User Management Guide.

Working with Applications 129

Working with ApplicationsMetadata models are stored in directories in Shared Services. Shared Services provides two types of applications:

● Private applications that are used by applications to store their models

● Shared applications that enable private applications to share models with other applications.

Working with Private ApplicationsShared Services manages models at the application level. Each application that is registered with Shared Services has a corresponding application in Shared Services, in which it stores its Shared Services models. An application has exclusive use of the application models.

To put a local copy of a model under control of Shared Services, export the model to the application directory in Shared Services. To make a model in Shared Services available to an application, import the model to the application.

Use Hyperion System 9 Shared Services to manage models, including these tasks:

● Track model versions

● Control access to models

● Edit member properties in dimensional models

● Synchronize models between the application and Shared Services

See “Working with Models” on page 133 for detailed information about how to manage models.

Working with Shared ApplicationsShared applications enables you to share models among applications and with other products. Shared Services uses shared applications to support sharing models. A shared application defines the information that is common between two or more applications. Within a shared application, an application can contain private models or shared models.

This example outlines the process for sharing models between applications or products:

1. App1 exports its models to Shared Services. The models are stored in the private application for App1 in Shared Services.

2. App1 selects a shared application to share with, for example, Common.

3. App1 designates specific models for sharing. When a model is shared, it is available for use with other applications.

4. App2 selects the Common.Shared application (the same application that is shared by App1).

5. App2 selects models in the shared application.


The shared models are displayed in the Model Listing view for App2.

An application that is shared can contain private and shared models in the Model Listing View. Private models are for the exclusive use of the individual application. Shared models are available to any application that shares the same shared application.

Filters enable you to designate which part of a shared model to use in an application. In this way, you can share models with other applications if the models share a core set of common members; the models are not required to be identical. When you import a shared model, the filter removes members that you have not designated as common. See “Filtering the Content of Models” on page 149 for information on creating filters.

Managing Applications for Metadata SynchronizationShared Services enables you to create, rename, and delete shared applications for metadata synchronization.

You can view a list of all applications on the Manage Applications Browse tab. The Share tab enables you to manage sharing of an application.

Figure 2 Manage Applications Browse Tab

Creating ApplicationsShared Services enables you to create shared applications.

Shared Services provides one shared default application called Common. Should additional shared applications be needed, they must be created by application users or administrators.

Working with Applications 131

➤ To create shared applications:

1 From the Performance Scorecard Administration menu, select Manage Projects.

2 If it is not already selected, select the Browse tab.

3 Click Add.

The Add Application window is displayed.

4 In the Shared Application Name text field, type a name for the application.

See “Application Naming Restrictions” on page 132 for a list of restrictions on application names.

5 Click one of these options:

● Add to add the application

● Cancel to cancel the operation


Application Naming RestrictionsApplication names are restricted by the following rules:

● The maximum length is limited to 80 characters regardless of the application in which you are working.

● Names are not case-sensitive.

● All alphanumeric and special characters can be used, with the exception of the forward slash (/) and double quotation (“) characters.

Deleting ApplicationsYou need Manage permission on an application to delete an application.

Note: Users must have the appropriate product-specific user roles to delete an application. For a listing of product user roles, see the appropriate product-specific appendix in the Hyperion System 9 User Management Guide.

➤ To delete an application:



Ensure that each of the applications currently using the shared application are no longer sharing access to the application to be deleted.

3 Select the application to delete and click Delete.

4 Click OK to confirm deletion of the application.

Sharing ApplicationsTo be able to share models with other applications, you must share a private application with a shared application in Shared Services.

Figure 3 shows a sample Select Shared Application window.

Figure 3 Select Shared Application Window

Working with Models 133

➤ To share an application with a shared application in Shared Services:


2 If it is not already selected, select the Share tab.

A list of shared applications is displayed, including Common, which is the default shared application provided by Shared Services.

3 Select the application with which you want to share.

4 Click Share to begin sharing the application with the shared application that you specified.

After setting up access to a shared application, designate models to be shared. See “Sharing Models” on page 147.

You can stop sharing access to a shared application at any time. When you do so, models that are shared with the current application are copied into the application.

➤ To stop sharing with a shared application:

1 From the Performance Scorecard Administration menu, select Administration→Manage Projects.

2 Select Share.

A list of shared applications is displayed.

3 Select the application with which you want to stop sharing.

4 Click Stop Share to stop sharing with the designated application.

Working with ModelsShared Services enables you to store and manage models in Shared Services. The Manage Models Browse tab lists the models that are in the product.

➤ To list the models that are in Shared Services:



Figure 4 shows a sample Manage Models Browse tab.

Note: Some Hyperion products do not display folders in the Manage Models Browse tab.


Figure 4 Manage Models Browse Tab

Note: If the current application is new, the view might not show models. Application models are displayed in the Browse tab after you explicitly export them to Shared Services. See “Synchronizing Models and Folders” on page 135 for information.

All models are displayed in ascending order. The Manage Models Browse tab provides information about each model in Shared Services:

● Model name

● Model type

● Last time the model was updated

● Whether the model is locked and who locked it

● If a filter is attached to the model and whether the filter is enabled:

indicates a filter that is enabled

indicates a filter that is disabled

You can see only the models to which you have at least Read access. If you cannot access a model, it is not displayed in the Manage Models Browse tab.

Icons indicate where models are located:

indicates a private model

indicates a shared model

Some Hyperion products require that models be displayed within a folder structure (similar to Windows Explorer). Folder views enable the administrator to migrate an entire folder structure or a portion of a folder structure easily using Shared Services. Folders are visible on the Manage Models Browse tab, Manage Models Sync tab, and Manage Models Share tab. Path information for folders is displayed directly above the column headers and path text is hyperlinked to refresh the page within the context of the selected folder.

Icons indicate where folders are located:


indicates a private folder

indicates a shared folder

From the Manage Models Browse tab, you can perform any of these operations:

● View and edit members and member properties in dimensional models. See “Viewing and Editing Model Content” on page 141.

● Filter content that is imported to an application from a shared model. See “Filtering the Content of Models” on page 149.

● Compare the latest application version of a model to the latest version stored in Hyperion System 9 Shared Services. See “Comparing Models” on page 139.

● Track model history. See “Tracking Model History” on page 151.

● View model properties. See “Viewing and Setting Model Properties” on page 158.

● Rename models. See “Renaming Models” on page 146.

● Delete models. See “Deleting Models” on page 146.

You can synchronize the Shared Services version of a model with the application version, by importing the model from Shared Services to the application, or by exporting the model from the application to Shared Services. To do so, select the Manage Models Sync tab. See “Synchronizing Models and Folders” on page 135.

You can share a model with other applications. To do so, select the Manage Models Share tab. See “Sharing Models” on page 147.

Synchronizing Models and FoldersThe Manage Models window lists the latest version of each model in Shared Services. Shared Services also tracks models in the application and determines whether a version of each model resides in the Performance Scorecard application only, in Shared Services only, or in both places.

When the latest version of a model resides in the Performance Scorecard application and in Shared Services, the applications are said to be synchronized, or in sync, with regard to that model.

If a model is out of sync, you can synchronize it by importing the model to the application or exporting the model to Shared Services, depending on where the latest version resides.

You need Write permission to synchronize a model.

Note: Models within folders can also be synchronized using the Shared Services sync operation. If a folder is selected, then all models within that folder and within any subfolders will be synchronized.


➤ To synchronize models and folders:


2 Select the Sync tab.

Figure 5 shows a sample Sync Preview Models window.

Figure 5 Sync Preview Models Window

The Sync Preview window lists all models and folders in Shared Services and in the Performance Scorecard application. The Sync Operationis recommended for each model or folder. See “Sync Operations” on page 137.

3 Optional: For models with Select Sync Operation, click Compare to compare the latest version of the model in Shared Services to the model in the application.Before clicking Compare, select a Sync Operation.

The latest version of the model in Shared Services is compared to the latest version in the application. The contents of the two models are shown line-by-line in a side-by-side format. Shared Services Version refers to the model in Shared Services. Application Version refers to the model in the application. For information on resolving differences between the models, see “Comparing Models” on page 139.

After resolving the differences in a model, you are returned to the Sync Preview page.

4 Select each model to be synchronized.

For models with Select Sync Operation, select a Sync Operation depending on whether the application or Shared Services has the latest version of the model.

Note: Before exporting a model from an application to Shared Services, check “Model Naming Restrictions” on page 139 to verify that the model names do not violate Shared Services naming restrictions.


5 Synchronize the selected models.

a. Click Sync.

A window is displayed that enables you to enter comments for each of the selected models.

b. Optional: Type comments for each model, or type comments for one model and click Apply To All to apply the same comment to all models.

c. Click Sync.

A progress message is displayed during the sync operation.

6 Click Report to see a report of the operations that have been completed.

7 Click Refresh to update the message.

8 Click Close to return to the Sync Preview window.

Sync OperationsThe Sync Preview window lists all models in Shared Services and in the application. The Sync Operation field provides a recommended operation to apply to each model:

● If a model exists in the application but not in Shared Services, the sync operation is Export to Hyperion Hub. You cannot change this operation. If you select the model, when you synchronize, the specified model is copied to Shared Services.

Note: Keep in mind when exporting that Shared Services supports dimensions that contain up to 100,000 members.

● If a model exists in Shared Services but not in the application, the sync operation is Import From Hyperion Hub. You cannot change this operation. If you select the model, when you synchronize, the specified model is copied to the application.

● If a model exists in the application and Shared Services, the sync operation is selectable. Select from one of these options:

Note: Remember these factors when deciding which compare operation to perform. With export, the compare operation considers the application model to be the “master” model. With import, the compare operation considers the Shared Services model to be the “master” model. In the following descriptions, the “master” model is underlined.

● Export with Merge — Merges the application model content with the content in Shared Services. Notice the following factors:

❍ This option considers any filters during the merge process and ensures that filtered members are not lost.

❍ If a property only exists in the application model, then the property is retained in the merged model.

❍ If a property only exists in the Shared Services model, then the property is retained in the merged model.


❍ If a property exists in both models, the value of the property in the application model will be retained in the merged model.

❍ A member in the application model but not in the Shared Services model will be retained in the merged model

❍ A member in the Shared Services model but not in the application model will not be retained in the merged model.

❍ A member which exists in the Shared Services model and in the application model, but in different generation levels, will be merged and the position in the application model will be maintained.

❍ If an application system member exists only in a Shared Services model, export with merge will not delete this member. If an application system member exists in a Shared Services model and in the application model, export with merge will merge the properties as usual and take the system member-specific attributes from the application model. See “About Application System Members” on page 145.

For properties with attributes, the merge is based on the attribute value. For example, if the following “Alias” attribute exists in the Shared Services model:

<Alias table=“French“>Text in French<\Alias>

and if the following “Alias” attribute exists in the application model:

<Alias table=“English“>Text in English<\Alias>

then the merged result will contain both attributes and will look like the following example:

<Alias table=“French“>Text in French<\Alias>

<Alias table=“English“>Text in English<\Alias>

If the value for both “Alias” attributes is the same in both models, then the value for the application model will be retained in the merged model.

● Export with Overwrite — Replaces the Shared Services model with the application model.

● Import and Merge — Merges the content from the Shared Services model with the application model content.

● Import and Replace — Replaces the application model with the Shared Services model.

● Clear before Import — Removes the content of the application model and replaces it with the content from the Shared Services model.


Model Naming RestrictionsThe following list specifies restrictions on model names:

● The maximum length is limited to 80 characters regardless of the application in which you are working.

● Names are not case-sensitive.

● You can use all alphanumeric and special characters, with the exception of the forward slash (/) and double quotation (“) characters. Therefore, you cannot export a dimension to Shared Services that contains forward slash or double quotation characters.

Note: The restrictions on names listed in this section are enforced explicitly by Shared Services. Performance Scorecard may enforce additional restrictions on names. If you are sharing models with one or more other products, you should be aware of additional naming restrictions that may be enforced by those products.

Comparing ModelsAt any time, you can compare a model in Shared Services to its corresponding version in the application. The latest version in Shared Services is compared to the model in the application. To compare different versions in Shared Services, see “Tracking Model History” on page 151.

➤ To compare the application representation of a model with the Shared Services representation of the model:

1 From the Performance Scorecard Administration menu, select Manage Models.

2 Select the Sync tab.

The Sync Preview window lists all models in Shared Services and in the application. The Sync Operation field provides a recommended operation to apply to each model or folder. For more information about sync operations, see “Sync Operations” on page 137.

3 Select Sync Operation for the model of interest.

4 Click the Compare button next to the Sync Operation box.

The latest version of the model in the application is compared with the latest version in Shared Services.

5 Perform any compare operations.

For a detailed description of the compare operations, see “Compare Operations” on page 140.

6 Click OK to return to the Sync Preview window.


Compare OperationsThe contents of the two models are shown line-by-line in a side-by-side format. Application Version refers to the model in the application. Application versions of a model are displayed on the left side of the Resolve Models (Compare) window. Shared Services Version refers to the model in Shared Services. Shared Services versions of a model are displayed on the right side of the Compare Models window.

Figure 6 shows a sample Resolve Models (Compare) window.

Figure 6 Resolve Models (Compare) Window

By default, the Resolve Models window displays up to 50 rows per page, displays any folders in an expanded format, and displays only those models with differences.

Color coding highlights any differences between the content of the two models:

● Red indicates that the element has been deleted from the model.

● Green indicates that the element has been inserted into the model.

● Blue indicates that the element has been changed.

Note: The compare operation filters out any application system members that are not relevant to the product being viewed. For example, if viewing HFM models, Shared Services will filter out any application system members that are not valid for HFM. For more information about application system members, see “About Application System Members” on page 145.

Table 18 describes the Resolve Models (Compare) window elements.


Viewing and Editing Model ContentThe Shared Services interface provides an editor that enables you to view and edit the content of models directly in Shared Services. You can use the editor only with dimensional mode. You need Read permission to view the content of a model. You need Write permission to edit or delete a model.

Figure 7 shows a sample View Model window.

Table 18 Resolve Models (Compare) Window Elements

Element Description

Expand All button Click to display the selected member and any children under the selected member in an expanded format (default)

Collapse All button Click to display the selected member and any children under the selected member in a collapsed format

<<FirstDiff button Click to jump to the first model element with a difference

<PrevDiff button Click to display the difference immediately previous to the current difference

NextDiff> button Click to display the next difference after the current difference

LastDiff>> button Click to jump to the last model element with a difference

View All button Click to display all model elements, not just the elements with differences

Show Diff Only button Click to display only the model elements with differences (default)

Note: For contextual purposes, Show Diff Only also displays the members immediately previous to and immediately after the member with a difference.

View button Click to display the member property differences for a selected element

<-- A red arrow indicates a deleted element in the Application Version of a model

--> A green arrow indicates an inserted element in the Application Version of a model

Click to jump to the first page of the model

Click to display the previous page of the model

Page Select a page to display in the Taskflow Listing area.

Click to display in the Taskflow Listing area the page you selected in Page.

Click to display the next page of the model

Click to jump to the last page of the model

Rows The number of rows displayed on each page (default is 50)


Figure 7 View Model Window

The editor enables you to manage dimension members by performing these tasks:

● View all members for a model, including application system members

● Add a sibling or a child to a member

● Change the description of a member

● Rename a member

● Move a member up or down in the hierarchy

● Move a member left or right (across generations) in the hierarchy

● Edit dimension member properties

● Enable or disable a filter

If you are renaming a member, keep these rules in mind:

1. You cannot rename a shared member.

2. You cannot create a duplicate member name (the rename operation performs a uniqueness check).

3. You cannot rename an application system member.

Note: Renaming a member and moving a member across generations within Shared Services enables products to retain the member properties for a shared model. Therefore, if you want to retain member properties across all products for a shared model, perform the rename or move member operation within Shared Services rather than within the individual product.

➤ To view or edit dimension members:



3 Select a model and click View.

Editing Member Properties 143

The dimension editor shows the members of the selected model, including any application system members. See “About Application System Members” on page 145.

4 Use the editing keys to make these changes:

● Add a child or sibling member

● Rename a member (notice the rules about renaming members in the previous section)

● Delete a member

● Move a member up, down, left, or right in the dimensional hierarchy

● Edit member properties

For more information about editing member properties, see “Editing Member Properties” on page 143.

● If a filter exists for a model, enable or disable a filter

For more information about filters, see “Filtering the Content of Models” on page 149.

Note: If you click on a member and it is not editable, then the member is an application system member. For more information about application system members, see “About Application System Members” on page 145.

5 Click Validate to perform a simple validation check.

The validation check verifies the following facts and lists any exceptions:

● That you have not created names that are too long (for example, 20 characters for Hyperion Financial Management, 80 characters for Hyperion Planning)

● That you have not created any duplicate names

Note: Shared Services does not perform validations for Alias/UDA uniqueness.

6 Click Save to save the changes and create a new version of the model in Shared Services.

Editing Member PropertiesYou can edit the member property settings of dimensional models, and save the changes to a new version of the model.

➤ To edit member property settings:


2 Select Browse.

3 Select a model name and click View.

The dimension editor shows the members of the selected model, including any application system members. See “About Application System Members” on page 145.

4 Select a member and click Edit.


The Edit Member window provides separate tabs for properties that are unique to a product. For example, the HP tab contains properties used by Hyperion Planning and the HFM tab contains properties used by Hyperion Financial Management. Each tab also displays properties that are common or shared between multiple products. Shared properties are preceded by an

icon, , that indicates that a property is shared.

Note: You cannot edit properties for an application system member. For more information about application system members, see “About Application System Members” on page 145.

To view which products share a property, hover the cursor over the shared property icon. A tool tip is displayed with the names of the products that share the property.

5 Select a tab and use the editing keys to change member property settings as you prefer.

Note: Alias properties may be displayed in a different order in Hyperion System 9 Shared Services than in Performance Scorecard. See the discussion following the procedure for details.

6 In Edit Member, click Save.

7 Click Close to close the window.

Note: The Edit Member window remains open unless you manually close it.

About Application System Members 145


● Save to save the changes you have made and create a new version of the model

● Close to return to the Model Listing view

If a member has an alias property, all the aliases and alias table names for the member are displayed in the Edit Member window. For example:

Performance Scorecard:

<Alias table="English">MyAlias in English</Alias><Alias table="German">MyAlias in German</Alias> <Alias table="French">MyAlias in French</Alias>

Shared Services:

Alias (English): MyAlias in EnglishAlias (German): MyAlias in GermanAlias (French): MyAlias in French

The order in which Shared Services reads the alias tables is not necessarily the order in which the aliases are shown in Performance Scorecard, which can be changed by user preferences.

About Application System MembersApplication system members store critical system information such as currency rates and ownership information. Each product has certain application system members that, when exported to Shared Services, are displayed in the model hierarchy.

You can view the details and properties of an application system member, however you cannot delete, edit, add children to, or rename an application system member in Shared Services.

Application system members are filtered out of the hierarchy if they are not relevant to the product being viewed. The compare operation filters any application system members that are not valid for your product. For example, if you are viewing HFM models, Shared Services filters out any application system members that are not valid for HFM. See “Compare Operations” on page 140.

You can import and export models that contain application system members. Consider the following conditions while performing sync operations:

● Import operations only import application system members if they are valid for your product. For instance, if a shared model has a system member called “active” which is only valid for HFM, when this model is imported by Planning, it will ignore this member.

● Export with Overwrite replaces the Shared Services model with the application model, including any application system members.

● Export with Merge merges the application model content with the content in Shared Services. Notice the following factors:

❍ If an application system member exists only in Shared Services, export with merge will not delete this member.


❍ If an application system member exists in Shared Services and in the product, export with merge will merge the properties as usual and take the system member-specific attributes from the product side of the model.

❍ All other export with merge scenarios behave the same way for system members as for normal members. See “Sync Operations” on page 137.

Renaming ModelsShared Services enables you to rename models in Shared Services. For example, you might want to rename a model if two applications want to share dimensional models that are named differently. For example, one application uses plural dimension names and the other application uses singular names. To share the models requires renaming one or both of them to a common name.

Renaming a model changes the name only in Shared Services. The internal representation of the name does not change. If you import a new version of a renamed model to the application, the new version retains the original name.

You need Write access to a model to rename it.

➤ To rename models:


2 Select Browse.

3 Select a model and click Rename.

4 In New Name, type a new name.


● Rename to save the new name

● Cancel to cancel the name change

See “Model Naming Restrictions” on page 139 for a list of restrictions on model names.

Deleting ModelsYou can delete a model if you have Write access to it.

➤ To delete models:


2 Select Browse.

3 Select a model and click Delete.

4 Click OK to confirm the deletion.

Sharing Models 147

Sharing ModelsYou set up the sharing of models between applications by designating a common shared application to be used by two or more applications. See “Working with Shared Applications” on page 129 and “Sharing Applications” on page 132 for details about shared applications.

You can select two types of models to share:

● Designate models in the private application in Shared Services to share with other applications.

● Select models from a shared application that have been made available for sharing by another application.

Note: Models within folders can also be shared using the Shared Services share operation. If a folder is selected, then all the models within that folder and within any subfolders will be shared.

➤ To share models:


2 Select Share.

The Share Models window lists private and shared models.

Icons indicate whether a model is shared:

indicates a private model that is not shared

indicates a shared model

indicates a model with a conflict (model exists in the private application and in the shared application in Shared Services)


The Share Operation column provides a recommended operation to apply to each model:

Note: The Share Operation column displays only the first 10 characters of the shared application name. If the shared application name exceeds 10 characters, then Shared Services appends ellipses (...) to the end of the application name.

● Share to <shared_application_name> — Copies the content of the model in the private application to the shared application. The share operation also deletes the model in the private application and creates a link in the private application to the model in the shared application.

● Unshare from <shared_application_name> — Copies the content of the model in the shared application to the private application and removes the link to the shared application.

Note: The model remains in the shared application. A copy of this previously shared model will be available in the user’s private/working application.

● If there is a conflict and the model exists in a private application and a shared application, the share operation is selectable. This conflict sometimes occurs because a model was previously shared and then unshared. Selecting a share operation enables you to reshare a model that was previously shared.

Select one of these options from the list:

❍ Share from <shared_application_name> (Overwrite) — Deletes the model in the private application and creates a link to the model in the shared application.

❍ Share to <shared_application_name> (Merge) — Merges the content of the model in the private application with the content of the model in the shared application. The model in the private application is then deleted and a link is created to the model in the shared application.

❍ Share to <shared_application_name> (Overwrite) — Replaces the content of the model in the shared application with the content of the model in the private application. The model in the private application is then deleted and a link is created to the model in the shared application.

1. Select one or more models to share and, if the share operation for a model is selectable, choose a share operation.

2. Click Share to begin the sharing operation.

3. Click Refresh to update the status of the operation.

4. Click Report to view information about the status of the operation, including whether it was successful and the reason for failure if the operation failed.

5. Click OK to return to the Share Models view.

You can stop sharing a model at any time. When you stop sharing a model, a copy of the model is created in the private application in Shared Services.

Filtering the Content of Models 149

➤ To stop sharing models:


2 Select Share.

3 In Share Models, select one or more models to remove from sharing.

4 Click Share.

5 When the status is complete, click OK.

The selected models are stopped from sharing and a copy of each model is made to the private application in Shared Services.

Filtering the Content of Models When you share models with other applications or products, it is possible that the models have some, but not all, all members in common. Shared Services enables you to write a filter that retains specified members of the shared model to remove when the model is imported to an application.

For example, a Hyperion Financial Management application exports an account dimension and shares it in a common shared directory. A Hyperion Planning application decides to use the account dimension from the Hyperion Financial Management application and links to the shared account dimension.

The Hyperion Planning application conducts budgeting on profit and loss accounts only and therefore does not require any balance sheet accounts from the account dimension. The Hyperion Planning application writes a filter that removes the Total Assets member and all of its descendants and the Total Liabilities member and all of its descendents.

You can write filters for dimensional models only, and, you cannot have multiple filters on a dimension. Writing filters requires Write access to a model.

➤ To create or modify filters:


2 Select Browse.

3 Select a model and click Filter.

In the Create/Edit Filter window, the Members List area shows the members of the model and Filtered Out Members shows members that are to be retained in the model on import.


4 From Members List, select a member.

5 Click Add to move the selected member from Members List to Filtered Out Members.

Select Member indicates how much of the hierarchy is to be filtered:

● Descendants (Inc). Filters the selected member and all of its descendants.

● Descendants. Filters descendants of the selected member (but not the member itself).

● Member. Filters the selected member only.

You can move selected members back to Members List from Filtered Out Members with the Remove and Remove All buttons.

6 Repeat the step 4 and step 5 until you have selected as many members as needed.


● Save to save the filter

● Close to cancel the changes you have made

The filter icon, , in the Model Listing view indicates that a model has an attached filter.

After a filter is applied to a model, you see only those members within a model that are not filtered out. If you would like to see all the members in a filtered model, disable the filter and then, after viewing, enable the filter again.

Tracking Model History 151

➤ To disable filters:


2 Select Browse.

3 Select a filtered model and click Filter.

4 Click Disable.

5 Click Save.

The disabled filter icon, , in the Model Listing view indicates a model has an attached filter, but the filter is disabled.

➤ To enable filters:


2 Select Browse.

3 Select a filtered model with a disabled filter icon and click Filter.

4 Click Enable.

5 Click Save.

The enabled filter icon in the Model Listing view, indicates that the filter is enabled.

➤ To delete filters:


2 Select Browse.

3 Select a filtered model and click Filter.

4 Click Delete.

5 Click OK to confirm deletion of the filter.

Tracking Model HistoryShared Services maintains a version history for each model in the product, if versioning is enabled for the model. To see if versioning is enabled for a model and to enable versioning if it is not enabled, see “Viewing and Setting Model Properties” on page 158.


➤ To view the version history of a model in Shared Services:


2 Select Browse.

3 Select a model and click History.

Shared Services displays a list of model versions, including the name of the person who updated the version, the update date, and comments for each model.

4 From the version list, you can perform any of these tasks:

● View the contents of any model.

1. Click a version.

2. Click View.

See “Viewing and Editing Model Content” on page 141 for more information.

● Compare any two model versions to each other.

1. Select any two versions.

2. Click Compare.

The contents of the two model versions are shown line-by-line in a side-by-side format. See “Comparing Models” on page 139 for more detailed information.

● Replace the current model in the application with a version in the list.

1. Select any version.

2. Click Import.

The specified version is imported to the application and replaces the current model. If a filter was applied to a previous version of a model, the model is imported with the filter applied.

● View the properties of any model.

1. Click a version.

2. Click Properties.

See “Viewing and Setting Model Properties” on page 158 for more information.

Managing Permissions to Models 153

Managing Permissions to ModelsShared Services enables you to manage access permissions to models in applications independent of any Performance Scorecard application. You assign permissions on a model-by-model basis to individual users or to groups of users. You can also assign permissions at the application level.

User names and passwords are managed by an external authentication provider, so they must be created externally—using NTLM, LDAP, or MSAD—before they can be added to Performance Scorecard. The Shared Services administrator adds authenticated users to Shared Services by using the Shared Services User Management Console. The Shared Services administrator also creates and manages groups by using the User Management Console. See the Hyperion System 9 Shared Services User Management Guide for details.

When applications are created in the Shared Services respository, all permissions are denied for all users, except the user who created the application. The creator of the application or the administrator (the admin user) must assign permissions for the new application.

When data integrations are created, all permissions are denied for all users (via a group called Users), except the user who created the data integration. To change the default setting for a user, add the user to the DataBroker application and apply the desired access rights.

Note: To override the DataBroker application access settings, it is possible to apply access rights to individual integration models. This can be done in the Manage Models page that displays the integration models in the DataBroker application. How each product navigates the user to this page is different so refer to each product's documentation for instructions on accessing the Manage Models page.

To access specific models in Shared Services, users must be assigned access rights individually or inherit access rights by being part of a group that is assigned access rights. If an individual user is assigned to a group and the access rights of the individual user conflict with those of the group, the rights of the individual user take precedence.

To give users access to models other than their own, an administrator must add the users and assign their permissions.


About PermissionsModel management provides these types of permissions:

● Read. The ability to view the contents of a model.

You cannot import a model if you have only Read access to it.

● Write. The ability to change a model.

Write access includes the ability to export, import, and edit a model. Write access does not automatically include Read permission. You must assign Read permission explicitly, in addition to Write permission, if you want a user to have these permissions.

● Manage. The ability to create new users and change permissions for users.

Manage access does not automatically include Read and Write permissions. You must assign Read and Write permissions explicitly, in addition to Manage permission, if you want a user to have all these permissions.

This table summarizes the actions that a user can take in regard to a model with each of the permissions.

Table 19 Access Permissions

Access Permission

Action Read Write Manage

Sync No Yes Yes

Import No Yes Yes

Export No Yes Yes

View Yes Yes Yes

Filter No Yes Yes

Compare Yes Yes Yes

History Yes Yes Yes

Set Properties No Yes Yes

Assign Access No Yes Yes

Share No Yes Yes

Assign Permissions No No Yes

Edit No Yes Yes

Rename No Yes Yes

Delete No Yes Yes


You can apply permissions to groups and to individual users. Users are automatically granted the permissions of the groups to which they belong. You can, however, explicitly add or deny permissions to a user to override group permissions.

For each type of access permission (Read, Write, and Manage), apply one of the following permissions:

● Grant. Explicitly grant the permission to the user or group.

Granting permissions to a member of a group overrides permissions inherited from the group. For example, if a group is denied a permission, you can explicitly grant the permission to a member of the group.

● Deny. Explicitly deny the permission to the user or group.

Denying permissions to a member of a group overrides permissions inherited from the group. For example, if a group is granted a permission, you can explicitly deny the permission to a member of the group.

● None. Do not apply the permission to the user or group.

Not applying a permission is different from denying a permission. Not applying a permission does not override permissions inherited from a group. Specifying None for permissions for individual users enables you to apply permissions on a group basis.

Note: If a user belongs to groups with mutually exclusive permissions to the same model, permissions that are assigned override permissions that are denied. For example, if a user belongs to a group that denies Read access to a model and belongs to another group that assigns Read access to the model, the user in fact is granted Read access to the model.

Assigning Permissions to ModelsYou assign permissions on individual models in applications. You assign permissions on the models to individual users or to groups of users. You must have Manage permission for a model to assign permissions to it.

Users inherit the permissions of the groups to which they belong. Permissions that you assign to an individual user, however, override any group permissions that the user inherits.

Note: The following procedure can be used to assign permissions to metadata models or to data integrations. To assign access to metadata models, begin the procedure when metadata models are displayed. To assign access to integrations, begin the procedure when integrations are displayed.

➤ To assign permissions to models:


2 Select Browse.

3 Select a model and click Access.

You can view the permissions that are assigned to users and groups for the selected model in the Model Access window.


4 To add users or groups, click Add.

The Add Access window is displayed. The Available Users/Groups lists users who are authenticated as Shared Services users. If a user is missing from the list, contact the Shared Services administrator. The administrator can use Shared Services Configuration Console to add authenticated users.

5 In Available Users/Groups, select users or groups to assign to this model. Click Add to move the selected users and groups to Selected Users/Groups or click Add All to move all users and groups to Selected Users/Groups.

Note: Group names are preceded by an asterisk (*).


6 Assign permissions to the selected users and groups by selecting one of the Grant, Deny, or None option buttons for the Read, Write, and Manage permissions.

Note: Assigning (or denying) a permission does not implicitly assign (or deny) any other permissions; that is, assigning Write permission does not implicitly assign Read permission, and assigning Manage permission does not implicitly assign Read and Write permissions. Likewise, denying Read permission does not implicitly deny Write and Manage permissions, and denying Write permission does not implicitly deny Manage permission. Assign all permissions for the user .

See “About Permissions” on page 154 for details about the Read, Write, and Manage permissions and the Grant, Deny, and None actions that you can apply to each permission.

7 Click Add to assign the new permissions.

Editing Permissions to ModelsYou can edit the permissions of individual users and groups on individual models. You must have Manage permission for a model to change permissions for it.

➤ To edit permissions to models:


2 Select Browse.

3 Select a model name and click Access.

You can view the permissions that are assigned to users and groups for the selected model.

4 Select the check box next to one or more users or groups and click Edit.

The window shows the permissions currently assigned to the selected users or groups.

Note: The icon indicates an individual user and the icon indicates a group of users.

5 Change permissions for the selected user or group by selecting one of the Grant, Deny, or None option buttons for the Read, Write, and Manage permissions.

See “About Permissions” on page 154 for details about the Read, Write, and Manage permissions and the Grant, Deny, and None actions that you can apply to each permission.



● Update to accept the changes

● Close to cancel the changes

To view any changes made to model access, log out of the product application, close the browser, and then re-login to the product application.

Deleting Permissions to ModelsYou can delete all permissions for users and groups to individual models. You must have Manage permission for a model to delete access to it.

➤ To delete access to a model:


2 Select Browse.

3 Select a model name and click Access.

You can view the permissions that are assigned to users and groups for the selected model.

4 Select the check box next to one or more users or groups and click Delete.

Note: When you click Delete, the permissions are immediately removed without a warning message being displayed.

Viewing and Setting Model PropertiesShared Services provides property data for each model in the product. You can view all model properties and set selected properties.

Figure 8 Model Properties Window

Viewing and Setting Model Properties 159

Shared Services displays these model properties:

● Creator. Name of the user who created the model

● Updated By. Name of the person who updated the model

If there have been no updates, the name of the creator is listed and the Updated Date is the same as the Created date.

● Create Date. The date on which the model was created in (exported to) Shared Services

● Updated Date. The date on which the model was last updated in Shared Services

● Versioning. Whether versioning is enabled

If versioning is not enabled, you can enable it by changing this setting. Once versioning is enabled, however, you cannot disable it.

● Lock Status. Whether the model is locked or unlocked

You can change this setting to lock the model for your exclusive use or to unlock the model to allow other users to work with it. Models are locked for only 24 hours. After 24 hours, the model is automatically unlocked.

● Share Information. Is provided if the model is shared with a shared application

❍ Source Project. The name of the shared project

❍ Source Model. The path to the model in the shared application

❍ Transformation. The name of the transformation, if any, that Shared Services applies to the model to make it usable to the application

● Dimension Properties. Is provided only if the model is a shared dimension model

❍ Dimension Type. The name of the dimension type.

If the Dimension Type value is None, then you can select a new dimension type in Dimension Type next to Change To.

❍ Change To. Only shown if the Dimension Type value is None.

Click the Change To button after selecting a new dimension type value in Dimension Type.

❍ Dimension Type. Only shown if the Dimension Type value is None.

Select a new dimension type from the list, then click Change To to change the dimension type.

You need Read access to view model properties and Write access to change model properties.


➤ To view or change model properties:


2 Select Browse.

3 Select a model and click Properties.

You can view the properties for the model.

4 Make these changes:

● If versioning is not enabled, click Enable (next to Versioning).

After versioning is enabled, model management maintains a version history for the model. You cannot disable versioning for a model after it is enabled.

● To lock or unlock the model, click Lock or Unlock next to Lock Status.

● If the Dimension Type value is None, select a new dimension type from the list box next to Change To. After selecting a new dimension type, click Change To and accept the resulting confirmation dialog box to invoke the change.

5 Click Close to save any changes.

Sharing Data Shared Services enables you to move data between applications. The method used to move data is called data integration. A data integration specifies the following information:

● Source product and application

● Destination product and application

● Source dimensions and members

● Destination dimensions and members

A data integration wizard is provided to facilitate the process of creating a data integration.

Whoever has write access to the DataBroker.DataBroker application can create data integrations. Users with read access to the DataBroker.DataBroker application can run data integrations. Access rights to this application are granted through the Shared Services User Management Console. See the Hyperion System 9 Shared Services User Management Guide.

By default, all Shared Services users have full access (Read, Write, and Manage) to all integrations.

A data integration can be run manually or scheduled to run at a specific time. Data integrations can also be placed in groups and run sequentially.

Prerequisites for Moving Data Between ApplicationsBefore data can be moved between applications, the models for the source and destination application must be synchronized between Shared Services and the application. See “Synchronizing Models and Folders” on page 135 for instructions on synchronizing models.

Sharing Data 161

Although Performance Scorecard and Shared Services provide tools to create integrations, the movement of data between applications requires that you be very familiar with the data.

Assigning Access to IntegrationsYou assign access to integrations using a similar process to assigning access to metadata models.

Note: By default, all users except the creator of the integration are denied access rights to data integrations (via a group called Users). To change the default setting for a user, add the user to the DataBroker application and apply the desired access rights. To override the DataBroker application access settings, it is possible to apply access rights to individual integration models. See “Assigning Permissions to Models” on page 155.

➤ To assign access to integrations:

1 From Performance Scorecard, with the Integrations page displayed, click Administration > Manage Models.

2 Go to “Assigning Permissions to Models” on page 155 and complete the procedure to assign permissions to integrations of your choosing.

Accessing Data Integration FunctionsWrite privileges are required to perform most data integration functions. A user with Read only privileges can view (including filtering the view) and run integrations. A user with Write privileges, however, can view, run, create, edit, copy, and delete an integration.

Note: To block a user from seeing a specific integration model, the user must be explicitly assigned Deny Read at a minimum (Write and Manage can be any setting) for the DataBroker application.

➤ To access all data integration functionality, select Administration > Manage Data.

The Manage Data window is displayed.

A list of integrations is displayed. The list includes names, source applications, and destination applications. An application name identifies a product, application, and a shared application in the form: <Product.Application.Shared Application>, for example, HFM.App1.beta.


Note: When viewing a list of integrations, performance may become slower as you add more integrations and as more users view the list.

Group integrations do not have a source and destination; each integration in a group specifies

its individual source and destination. A group icon, in the source and destination column identifies a group integration. The link, View group details, lists the integrations in the group.

You can perform any of these functions from the Integrations page:

● Create, edit, or copy an integration (see “Creating or Editing a Data Integration” on page 163)

● Create a data integration group (see “Grouping Integrations” on page 174)

● Delete an integration (see “Deleting Integrations” on page 169)

● Run, or schedule to run, an integration (see “Scheduling Integrations” on page 170)

Filtering Integration ListsIn a list, by default, all available integrations are displayed. You can filter the list, based on the source product and application, or the destination product and application.

➤ To filter an integration list:

1 From Performance Scorecard, select Administration > Manage Data.

A list of integrations is displayed. The integrations for all products and applications are shown by default.

Two combination boxes, Source and Destination, are displayed above the Filter View button. Each combination contains two lists — the first to specify a product and the second to specify an application.

Note: A list of integrations is displayed when you create an integration group. If you are creating a group, begin with step 2.

2 Select a product from the product Source or Destination or from the product Source and Destination.

The second Source or Destination is populated with the applications for the selected product.

3 Select an application or leave All Registered Applications selected.

You can select only one application.

4 Click Filter View to update the list based on the selections that you made.

Sharing Data 163

The filter enables the display of integrations that act on a source product or application, or on a destination product or application, or on a combination of both. For example, if you specify Performance Scorecard as the source application and Hyperion Planning as the destination application, the list includes all integrations whose source is Performance Scorecard or whose destination is Hyperion Planning.

The following examples illustrate the different combinations of product and application that you can specify in the Source and Destination combination boxes

● If a source product is specified and the three boxes specify all, the list displays all integrations with the specified source product.

● If a source product and a source application are specified and the two destination boxes specify all, the list displays all integrations with the specified source application.

● If a source product and destination product are specified and the two application list boxes specify all, the list displays all integrations from the given source product to the given destination product. If an integration is bidirectional (can be transposed) and either source-to-destination or destination-to-source matches the given products, the integration is listed.

Creating or Editing a Data IntegrationShared Services provides a data integration wizard to enable the process of moving data between applications.

Note: To create data integrations, you must have Write access to the DataBroker application. Access rights to this application are granted through the Shared Services User Management Console. See the Hyperion System 9 Shared Services User Management Guide.

➤ To create or edit an integration:


A list of integrations is displayed.


● To create an integration, click New.

● To edit an integration, select an integration and click Edit.

Note: Locking of integration models in edit mode is not supported. As a consequence, it is possible for multiple users to simultaneously open an integration and make changes. If more than one administrator edits the same integration simultaneously, the last one to save takes precedence. The entire integration is overwritten with the last version saved. No warning message is displayed.

● To use an existing integration to create an integration, select the integration and click Copy.


Note: Action buttons (New, Edit, Delete, Copy, and Run) that are enabled for a user are defined at the DataBroker application level and not at the model level. However, for existing integration models, the actions that a user can perform are controlled at the model level. For example, if a user has full access rights to the DataBroker application, but Read access to a specific integration model, all buttons are enabled but when the user tries to edit and save this integration, an error is displayed.

The Create or Edit Integration window is displayed.

For a new integration, the fields are blank. For an integration to be edited or copied, the fields are populated with values.

3 Enter information, and select or clear check boxes.

Item Description

Integration Name A unique name for the integration. For an edited integration, the name is read-only and cannot be changed.

To rename an integration, copy the integration to a new name, and delete the original integration.

Source A combination text box to identify the source for the data. The first box contains a list of products registered with Shared Services. When you specify a product, the second box is populated with applications belonging to the product. When you specify an application, the third box is populated with data sources.

Data sources include elements like Hyperion Planning Plan Type. If you select an application that does not require or support data sources, “Default Data Source” is displayed in a disabled field that you cannot change.

Sharing Data 165

4 Click Next.

The second page of the Create Integration wizard enables you to specify the dimensions that are equivalent (shared) for purposes of the current integration.

By default, the wizard identifies dimensions of the same name (in source and destination applications) as shared. A line between dimensions indicates that they are shared.

To optimize performance, when creating an integration that has more than one shared dimension, dimension order is important. The order of shared dimensions in the integration is controlled by the order in which you share dimensions. In general, you should place the one shared dimension that has the largest number of selected members for that integration as the last shared dimension. To do this, it is best to determine first what members for each dimension will be used in an integration. Of those dimensions that will be shared, identify the one where your member selection yields the largest number of members. On page 2 where you identify shared dimensions, if that dimension is automatically shared, unshare it. Then share all desired dimensions except for that one dimension. Then share that one remaining dimension last before moving on to third page of the wizard. This will ensure that this dimension is displayed last in the Shared Dimension Members panel on the third page of the wizard.

5 Perform one or more of these actions:

● If you want to specify the shared dimensions, select one or more pairs of dimensions (in source and destination applications) and click Share.

Destination A combination text box to identify the destination for the data. The first box contains a list of products registered with Shared Services. When you specify a product, the second box is populated with applications belonging to the product.

Data sources include elements like Hyperion Planning Plan Type. If you select an application that does not require or support data sources, “Default Data Source” is displayed in a disabled field that you cannot change.

Bidirectional A check box that determines the direction in which the integration can be run. If the box is not checked, data is moved from the source to the destination. If the box is checked, the user can choose a direction (source to destination or destination to source) when scheduling or running the integration.

System Override A check box that enables writing to read-only fields in the destination application.

Suppress Empty A check box that enables the integration, for performance reasons, not to transfer missing cell (#missing) values. If the box is checked, to ensure that data is transferred successfully, Prepare the destination database before running the integration. See “Prerequisites for Moving Data Between Applications” on page 160 for details.

Scale The multiplier for the data. Enter a value with which you want to scale the integration data. For example, to convert data from a positive to negative value during the data transfer, specify a scale value of -1. Each transferred data value is then multiplied by -1, in effect, converting them to negative values.

Notes Optional comments and notes.

Item Description


A dimension can be shared with only one dimension in the other application. A line is drawn between any two dimensions that are shared.

● If you want to unshare any dimensions that are shared by default, select one or more dimensions in either application and click Unshare; or click Unshare All to remove sharing from all dimensions.

● If you want to return to the default shared dimensions, click Default.

Note: You are not required to identify every identical dimension. The reason to identify shared dimensions is to specify the dimensions for which you want to move a range of members. For any integration, if you are interested in only one member for a dimension, you can leave the dimension unshared.

6 Click Next.

The third page of the wizard enables you to pick ranges of members from the shared dimensions to define the slice of data that will be transferred.The window displays dimensions in these categories:

● Shared Dimension Members. Dimensions identified as shared on the previous wizard page

● Common POV. Dimensions not identified as shared, that can only be mapped one member to one member.

● Dynamic POV. Dimensions not identified as shared, that can be mapped to multiple members.

Each POV (point of view) uses the same background POV members and a unique set of dynamic POV members. You specify the dynamic POVs.

7 Select shared dimension members:

a. Next to a shared dimension, from which you want to select members, select the Select Members menu control.

b. Select From Source or From Destination.

A list of members from the appropriate application (source or destination) is displayed.

c. Select one or more members.

d. Click Select.

You can also specify a function to identify a set of members. For example, type Match(*) or AllMembers() to specify all members of the same name and the same dimension in the source and destination applications.

When you run an integration with a function, the function transfers data only for members that are common to applications. For both the source and destination applications, however, the integration must iterate through every member identified by the function. For example, the following table shows members from a time dimension for two applications:

Sharing Data 167

If you specify an AllMembers() function, the integration must check all 11 members; however, data is transferred only for 1999, 2000, and 2001, because these years are common to both applications. Warning messages are returned for the other years.

Note: Select at least one member from each dimension in Common Members or specify a function that identifies a common member.

When using double quotation marks (“) and parentheses () in member names in the Create Integration Wizard, follow these guidelines:

These examples illustrate valid use of these characters in member names:

abc

“abc”

func(abc)

“func(abc)”

“func(a,b,c)”

“func(a(b)c)”

func(a(b)c)

These are examples of invalid member strings:

func(a”b”c)

func(a,b,c)

func(a(b)c)

func(“abc)

If you select invalid member names from the Data Integration Wizard, it automatically adjusts the syntax to be valid before passing the name on. However, if you manually type an incorrect name, the wizard does not correct the invalid name, and an error is returned.

The following members may be valid within an application, but may behave differently:

a,b,c will be treated as three members, not one named “a,b,c”.

Application 1 (Source) Application 2 (Destination)

1997 1999

1998 2000

1999 2001

2000 2002

2001 2003

-- 2004


Different styles can be mixed in a single shared pair of dimensions’ value input box, for example:

a, b, c, “abc”, ”Children(a,b,c)”, iDescendants(a(b)c), “Ancestors(a(bc)”

8 Optional: Create POVs.

You can create one or more POVs:

● Create a single POV using background POV dimensions

● Use dynamic POVs to create multiple POVs,

● Leave the POV dimensions blank.

The Common POV area shows all dimensions not identified as shared on the previous wizard page. Dimensions from the source and destination applications are shown in separate columns.

Initially, all dimensions are in the Background POV area and the Dynamic POV area is blank.

a. Next to a dimension in the source application select the magnifying glass.

b. From the list of members select a single member.

c. Repeat steps step a and step b for all other dimensions in the source application for which you want a member selected.

Note: You can leave background POV dimensions blank if the application does not require a value for them.

d. Next to a dimension in the destination application, select the magnifying glass.

e. From the list of members select a single member.

f. Repeat steps step d and step e for all other dimensions in the destination application for which you want a member selected.

Note: You can leave background POV dimensions blank if the application does not require a value for them.

g. Click Dynamic POV next to a dimension to move the dimension from the Background POV area to the Dynamic POV area.

h. Click Add to create a POV that is based on the static and dynamic members that you have selected.

i. Optional: If you want to create another POV, select a different member and click Add.

Repeat this step by selecting different members for the dynamic POV and clicking Add for each selection.

The numbering in the lower right corner identifies the POV, for example, POV 3 of 5. You can navigate to each POV by using the left and right arrow keys.

You can also move the dimension in the Dynamic POV area back to the Background POV area and move a different POV to the dynamic area and create another set of POVs.

j. Optional: If you want to replace the content of any POV to which you have access, complete these steps.

Sharing Data 169

i. Use the arrow keys in the lower right corner to navigate to a POV.

ii. Change the content in one of the Dynamic POV areas.

iii. Click Replace.

When the integration is run, it copies the data from the dimension member or members in the source application list to the dimension member or members in the destination application list.

9 Optional: If you want to see a list of POVs, click View All.

10 Optional: If you want to remove a POV, complete these steps.

a. Click the left (<) or right (>) paging icon to navigate to a POV.

b. Click Remove.

11 Save the integration, or cancel the changes that you made by taking one of these actions:

● Click Save to save the integration.

The Create Integration window remains open. You can make additional changes to the integration and save it again when finished.

● Click Save and Close.

The integration is saved and the list of integrations is displayed. To schedule the new integration to run, see “Scheduling Integrations” on page 170.

● Click Save and Run.

The integration is saved and the page to schedule an integration to run is displayed, see “Scheduling Integrations” on page 170.

● Click Close.

Any changes that you made since the last save are lost. Any new group that has not been saved is not created.

Note: Case-sensitivity in integration and integration groups is handled differently depending on the relational database. For Oracle configurations, if you save a new integration or group with a name comprised of the same characters but different case, such as “ABC” overwriting “Abc,” you are prompted to overwrite the existing one. After overwriting, two integrations are created: “Abc” with the old contents and a new integration or group named “ABC” with the new contents. In the case of non-Oracle configurations, if you try to overwrite “Abc” with “ABC”, an initial message warning about overwriting is displayed. If you continue to overwrite, an exception is displayed stating that the name already exists and you are forced to select a new name.

Deleting IntegrationsYou can delete integrations that are no longer useful.

➤ To delete an integration:




Note: If the integration of interest is not displayed, check the Filter View Source and Destination boxes to see if the list of integrations is filtered. See “Filtering Integration Lists” on page 162 for information about how to filter an integration list.

2 Select one or more integrations to delete.

3 Click Delete.

A delete confirmation message is displayed.


● OK to delete the selected integration or integrations

● Close to cancel the delete operation

Scheduling IntegrationsYou can run an integration immediately or schedule it to run at a specific date and time. You can also place an integration in a group and schedule the group to run. See “Grouping Integrations” on page 174 and “Scheduling Group Integrations” on page 176.

➤ To schedule an integration to run:


A list of integrations and integration groups is displayed.

Note: If the integration of interest is not displayed, check the Filter View Source and Destination boxes to see if the list of integrations is filtered. See “Filtering Integration Lists” on page 162 for information about how to filter the integration list.

2 Select an integration to run.

Note: You can select one integration only at a time to schedule for running.

3 Optional: If the integration is bidirectional, the source and destination application can be reversed. Selecting an application from Source and Destination automatically shows the other application that will be used as the destination.

Note: If the source and destination applications are the same, it can be confusing with a bidirectional integration to know which way the data is being moved. The first entry in Source is the original, default source application.

4 Click Run.

A popup window is displayed to schedule the integration to run.

Figure 9 shows a sample Run Integration window.

Sharing Data 171

Figure 9 Run Integration Window

5 To run the integration immediately, click OK.

Immediately is selected by default.

6 Click Schedule for and scroll to select the month, day, and time in the list boxes to schedule the integration to run at a specific time.


● OK to schedule the integration

● Close to cancel the operation

The integration you scheduled is added to the list of scheduled integrations. For information on viewing scheduled integrations, see “Viewing the Status of an Integration” on page 172.

Managing Scheduled IntegrationsWhen you schedule an integration, the integration is added to the list of scheduled integrations. The scheduled integration list includes integrations that are waiting to run (pending), integrations that are currently running (running), integrations that have been cancelled (cancelled) and integrations that have already run (completed or failed). Integrations remain on the list until you remove them.

You can perform these actions on integrations on the scheduled integration list:

● View the status of a running, completed, or failed integration; see “Viewing the Status of an Integration” on page 172.

● Cancel a running integration; see “Canceling an Integration” on page 172.

● Run a copy of an integration; see “Copying an Integration to Run” on page 173.

● Reschedule an integration; see “Rescheduling an Integration” on page 173.

● Remove an integration from the list of scheduled integrations; see “Removing an Integration” on page 174.


Viewing the Status of an IntegrationThe scheduled integration page lists all integrations that are scheduled or have been run.

➤ To view all scheduled integrations, select Administration > Scheduled Integrations.

The Scheduled Integrations window is displayed. The Status column indicates whether an integration is pending, running, completed, or failed.

➤ To view details about a completed or failed integration, click the Failed or Completed link in the Status column.

Note: Data integrations that contain members with parentheses in the name, for example “Account1()”, will fail. If this is the reason for the failure, you will see an “Unknown function name Account1” error.

Canceling an IntegrationYou can cancel an integration that is scheduled to run or in progress (running).

➤ To cancel integrations:

1 From Performance Scorecard, select Administration > Scheduled Integrations.

2 Select an integration.

You can select a single integration only.

3 Click Cancel.



● OK to cancel the integration


Sharing Data 173

Copying an Integration to RunYou can schedule the same integration to run multiple times by making a copy of the integration and scheduling the copy to run.

➤ To schedule a copy of an integration to run:




3 Click Run Copy.

A popup window is displayed to schedule the integration to run.



5 To schedule the integration to run at a specific time, click Schedule for and scroll to select the month, day, and time.




The integration you scheduled is added to the list of scheduled integrations. You can schedule an integration multiple times, which results in the integration being listed multiple times on this page.

Rescheduling an IntegrationYou can reschedule an integration that is waiting to run to a different date or time.

➤ To reschedule an integration:




3 Click Run Copy.

A popup window is displayed to reschedule the integration to run.



The currently scheduled month, day, and time are displayed in the Schedule for combination boxes.

5 To schedule the integration to run at a specific time, click Schedule for and scroll to select the month, day, and time.





Removing an IntegrationYou can remove an integration that is pending to run or one that has already run (completed or failed).

➤ To remove an integration:



You can select multiple integrations to remove.

3 Click Remove.



● OK to remove the integration or integrations you have selected


Note: In some cases, removing an integration or group that has been run and then attempting to remove it from the Scheduled Integrations page results in a blank screen. In these cases, select the Back button in your browser and refresh your screen using F5 or your browser's Refresh button.

Grouping IntegrationsYou can create groups of integrations to run at the same time. Before creating a group, first create individual integrations that can be added to a group; see “Creating or Editing a Data Integration” on page 163. In the group, you specify the order in which to run the integrations.

Creating or Editing Integration Groups

➤ To create or edit integration groups:



2 Take one of these actions:

● To create a blank new group, click New Group.

A Create Integration Group page with blank fields is displayed.

● To create a group with a list of integrations, select one or more integrations from the list of saved integrations, and click New Group.

Sharing Data 175

A Create Integration Group page with populated fields is displayed.

● To edit a group, select the group and click Edit.

A Create Integration Group page with populated fields is displayed.

3 Enter the group name.

The name must be unique among group and integration names.

4 Optional: Under Notes, enter comments.

5 Click Next.

Note: If you click Save or Save and Close, the group (name and notes) is saved. You can edit the group later and add integrations.

6 From Available Integrations, select one or more integrations.

You can nest an integration group within another group. For an individual integration, the list displays the source and destination product and directory. For a group, click on the View group details link to see the integrations contained in the group.

Note: To filter the list of available integrations to show a more useful list, see “Filtering Integration Lists” on page 162.

7 Click Add to copy the selected integrations to Selected Integrations.

The selected integrations are copied, not moved, to Selected Integrations. You can add an integration multiple times if you want to run it more than once.

8 Optional: If you are editing a group, or if you have integrations to be removed, from Selected Integrations, select one or more integrations and click Remove to remove them from the group.

You can click Remove All to remove all integrations from the group.


9 Optional: Select an integration and click the up or down arrow keys to move the integration up or down in the list to change the order in which it is run. Integrations are run in the order in which they are displayed.


● Click Save to save the group.

The Create Integration Group window remains open. You can make additional changes to the group and save it again when finished.

● Click Save and Close.

The group is saved and the list of integrations is displayed. To schedule the new group to run, see “Scheduling Group Integrations” on page 176.

● Click Save and Run.

The group is saved and the page to schedule a group to run is displayed; see “Scheduling Group Integrations” on page 176.

● Click Close.

Any changes you made since the last save are lost. If it is a new group and it has not been saved yet, no group is created.

Scheduling Group IntegrationsYou can run an integration group immediately or schedule it to run at a specific date and time.

Note: If you selected Save and Run when you created the integration group, the page to run the integration group is displayed. Skip to step 4.

➤ To schedule a group to run:


A list of integrations and integration groups is displayed.

Note: If the group of interest is not displayed, check the Filter View Source and Destination list boxes to see if the list of integrations is filtered. See “Filtering Integration Lists” on page 162 for information about how to filter the integration list.

2 Select a group to run.

Note: You can select one group only at a time to schedule for running.

3 Click Run.

A page is displayed to schedule the group to run. Figure 10 shows a sample Run Group Integration window.

Sharing Data 177

Figure 10 Run Group Integration Window

4 To run the group immediately, click OK.


5 To schedule the group to run at a specific time, click Schedule for and scroll to select the month, day, and time in the list boxes.


● OK to schedule the group


The group you scheduled is added to the list of scheduled integrations. For information on viewing scheduled integrations, see “Viewing the Status of an Integration” on page 172.

Note: If one of the integrations within a group encounters an error while running, the entire group stops running.


Managing Alerts using the Alerter 179

C h a p t e r

8Managing Alerts using the

Alerter

This chapter describes how to manage alerts using the Hyperion System 9 Performance Scorecard Alerter (Alerter).

The Alerter is configured during the installation of Performance Scorecard. For detailed instructions on installing and configuring the Hyperion System 9 Performance Scorecard Alerter, refer to the Hyperion System 9 Performance Scorecard Installation Guide

In This Chapter Using Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Alerter Process Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

180 Managing Alerts using the Alerter

Using AlertsAlerts enable users to monitor corporate, business unit, and individual employee performance by notifying subscribers by e-mail when the performance of key business metrics falls within or outside of a defined acceptable range. Alerts also prompt subscribers when tasks such as measure result collection or initiative completion are approaching, due, or overdue.

There are two types of alerts:

● Personal alerts are created by a user to alert that individual about the status of a measure for which they are responsible. Personal alerts apply to only that user, and cannot be accessed by anyone else.

● Public alerts function like regular alerts except that public alerts can be subscribed to by other users.You can also use public alerts as templates to quickly generate new alerts that have common attributes.

After creating alerts, users or groups subscribe to them by creating a subscription or by using one-step subscription.

When an alert is triggered, alert notifications are sent by e-mail to each user subscribed to the alert to advise that the business object being monitored is in an alert state. The content and frequency of these alert notifications are specified when each alert is created. At this point, users can acknowledge the alert notification, unsubscribe from the alert to no longer receive notifications, or click the link provided in the notification to log on to their application to investigate the business object in alert. For information on working with alerts and subscriptions, refer to the Hyperion System 9 Performance Scorecard User’s Guide.

Use the Alerter Process Report to monitor alert and alert notification activity such as the number of alert notifications sent and when each notification was sent. For detailed information on the report, refer to “Alerter Process Report” on page 181.

Alerter Process Report 181

Alerter Process ReportThe Alerter Process Report monitors the alerts that have been triggered. Use the Alerter Process Report to monitor alert activity and each user’s response to the alerts that they receive. Only the Administrator can access the Alerter Process Report.

The Process Report provides the following information based on the most recent alerter process that was run:

● The time the alert was sent

● User or group to which the alert was sent

● The name of the alert

● The associated measure, scorecard or initiative that triggered the alert

● Value of the alert

● Status of the alert

● Acknowledgement status

➤ To access the Alerter Process Report:

1 Select Start > Programs > Hyperion Solutions > Hyperion System 9 Applications + > Performance Scorecard 4.1 > Start alerter on <your application server> to start the application server.


3 From the main menu, select Administration > Alerter > Alerter Process Report.

The Alerter Process Report is displayed.

182 Managing Alerts using the Alerter

The Process Report retrieves all alert activity that occurred during the specified dates and provides this information:

● Time each alert notification was sent and the target e-mail address

● The name of each alert that was triggered

● The triggering criteria that caused a business object to be placed in a state of alert and an alert notification to be sent

● The value of the business object that caused it to be in a state of alert

● The date and time each alert notification was acknowledged. This column is empty if the alert notification has not been acknowledged by a subscriber.

Review the report to monitor alert traffic and each user’s response to the alerts they receive.

Extended Customized Reporting 183

C h a p t e r

9Extended Customized Reporting

This chapter describes how to view Performance Scorecard data through Hyperion® System™ 9

BI+™ Interactive Reporting Studio™ (Interactive Reporting). Refer to “Extended Reporting through Interactive Reporting” on page 191 for detailed instructions.

For existing users, instructions are also provided to view Performance Scorecard data directly through Hyperion Intelligence Release 8.3. Refer to “Extended Reporting through Hyperion Intelligence” on page 200.

In This Chapter About Interactive Reporting Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Smart Cuts URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Default Generated Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Extended Reporting through Interactive Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Extended Reporting through Hyperion Intelligence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

184 Extended Customized Reporting

About Interactive Reporting IntegrationsYou can use Interactive Reporting Studio to directly access Performance Scorecard data through Performance Scorecard and Star Schema database tables. The reports are presented in a combination of tables that provide detailed and summary information, and graphical charting of those results.

By default, these pre-formatted Performance Scorecard reports are available through Interactive Reporting:

● “Scorecard Report” on page 187

● “Scorecard with Measure Trends” on page 188

● “Strategy Dashboard” on page 189

The Star Schema tables are used by an Administrator to generate Analytic Services databases and Interactive Reporting reports. The data that is displayed in the reports is obtained from the Star Schema tables that are generated in Performance Scorecard. For additional information, see “About Star Schema Tables” on page 82.

Note: Experienced Interactive Reporting or Hyperion Intelligence users can use the Star Schema database tables and modify the default reports in Performance Scorecard to create new, customized reports using Interactive Reporting.

Whether you are using Interactive Reporting or Hyperion Intelligence to generate the reports, you follow the same basic steps:

1. Create an ODBC connection, and add the connection to the DAS service.

2. Create a database connection (also called an.oce file), which describes your connection to the external database. The integration retrieves results from the Interactive Reporting or Intelligence Server, using BQY files that are also created in Interactive Reporting. For detailed instructions on creating the .oce file, refer to the Hyperion System 9 BI+Interactive Reporting documentation.

3. Publish the .oce file.

4. Publish the BQY file, which contains the queries and display parameters for the information to be generated for the report. You can use the default BQY files, or create your own. For detailed instructions on creating BQY files, refer to the Interactive Reporting documentation.

5. After the files have been set up in Interactive Reporting or Hyperion Intelligence, launch Performance Scorecard to generate the Star Schema database, and create the custom report links to view the reports.

About Interactive Reporting Integrations 185

Smart Cuts URLsTo add external reports to Performance Scorecard, it is necessary to reference the Interactive Reports individually through a URL, or Smart Cut. The Smart Cut points directly to the published Interactive Reporting BQY file.

The unique URL for each report is generated in Interactive Reporting, but additional parameters must be manually added. The additional parameters are appended to the URL to reference the correct information about the Hyperion System 9 BI+ Interactive Reports Server, the BQY file it is referencing, and the specific Performance Scorecard parameters to be passed to the report.

For detailed information on Smart Cuts formats for customized reports, refer to the Hyperion System 9 BI+ Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis Developer's Guide.

➤ To create the custom report Smart Cut URL:


The Performance Scorecard Administrator page is displayed.

2 Select File Application Preference.

The Application Preferences page is displayed.

3 Select the Reports tab.

4 Under Add External Reports, click Add.

A blank line is added to the table.

5 Under Reports Name, enter a unique name for the Interactive Reporting Studio or Hyperion Intelligence report.


6 Under Reports URL, enter the Smart Cut URL to the Interactive Reporting Studio or Intelligence server and the report using the following format:

http://<BIPlus Server Name>:<BIPlus Server Port Number>/ <Path to BQY file in Interactive Reporting Studio> <Date Range from which data will be retrieved in mmddyyyy format>

7 Attach the custom Performance Scorecard parameters to the Smart Cut URL by adding the parameters to the end of the URL:

The final Smart Cut URL resembles the following example:

http://BIPlusServer:19000/workspace/browse/get/HPS41Beta/ ScorecardDashboard.bqy?bqtype=ihtml&Toolbar=Standard &ScorecardName=Taylor,Frank&Date1=10012004&Date2=11012004

For detailed information on Smart Cuts formats for customized reports, refer to the Hyperion System 9 BI+ Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis Developer's Guide.

Default Generated ReportsBy default, the following pre-formatted Performance Scorecard reports are available:

● “Scorecard Report” on page 187

● “Scorecard with Measure Trends” on page 188

● “Strategy Dashboard” on page 189

Each report is generated by a pre-formatted BQY file that specifies the Smart Cut parameters used to generate the report.

You can modify the BQY files used for the default reports as a starting place to create your own customized reports.

For detailed information on Smart Cuts formats and generating customized reports, refer to the Hyperion System 9 BI+ Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis Developer's Guide.

Table 20 Custom Performance Scorecard Parameters for Smart Cut URL

Parameter Description

bqtype=ihtml Class of file

Toolbar=Standard Type of toolbar

ScorecardName= Details of the scorecard reference

Date Reference to the date for the data, in the format mmddyyyy.

Default Generated Reports 187

Scorecard Report The Scorecard Report is generated by the Scorecard.bqy. This BQY file uses these Smart Cut parameters:

● ScorecardName is the name of the individual scorecard as it is displayed in Performance Scorecard

● Date is the reporting date for the scorecard, in the format MMDDYYYY, where MM starts at 01 for January.

The Scorecard Report provides the details of the selected employee scorecard. You can view all, or some of the available scorecards. The details are presented in table and graphical format.

Use the list to select individual measures on the report for review.

The Employee Scorecard Report provides this information:

● Scorecard name

● Perspective, if available

● Measure name

● Measure unit

● Measure Target

● Measure Result

● Measure Score

● Performance Indicator

For more detailed description of the displayed information, refer to “Accessing the Detail Report for a Scorecard” in the Hyperion System 9 Performance Scorecard User’s Guide.


Scorecard with Measure TrendsThe Scorecard with Measure Trends Report is generated by the Scorecard_withTrend.bqy. This BQY file uses these Smart Cut parameters:

● ScorecardName is the name of the individual scorecard as it is displayed in Performance Scorecard

● Date1 - Date6 requires at least one of the six dates

The Scorecard Report with Measure Trends provides the Trending Table details for one or more measures on the selected scorecard. You can view all, or some of the available scorecards. The details are presented in a table format, and the values and performance indicator enable you to evaluate the trend for the selected measure for the specified date or date range.

The Display Measure list displays all of the measures that are listed on the report. Use the list to select an individual measure from the report for review.

Default Generated Reports 189

The Employee Scorecard Report with Trends provides this information:

● Measure name

● Performance Indicator

● Measure score, result and target for each selected date

For more detailed description of the displayed information, refer to “Accessing Trending Tables” in the Hyperion Performance Scorecard User’s Guide.

Strategy DashboardThe Strategy Dashboard Report is generated by the StrategyDashboard.bqy. This BQY file uses the following Smart Cut parameters:

● ScorecardName is the name of the strategy as it is displayed in Performance Scorecard

● Date1 - Date6 requires at least one of the six dates

The Strategy Dashboard Report provides an overview of the components of the strategic objectives, including a graphic display of the current results versus targets for a selected measure. The dashboard offers the opportunity to view the current progress of the strategy, add notes regarding the analysis, opportunities and issues that apply to the strategy, and to view actions or strategic initiatives.

Use the Measure list to select individual measures on the report for review. The Results versus Targets are displayed in a graphical format.


The Strategy Dashboard provides this information:

● Selected dates or date range for the strategy

● Strategy owners

● Strategy Name and description

● Perspective, if available

● Theme

● Name of the associated measures, available from the list

● Bar chart that illustrates the Results versus Target for the selected measure for the strategy

● Notes and comments on various subjects relating to the strategy to provide analysis of the strategy, opportunities for improvement or change, or issues that must be addressed.

● Current Actions and Strategic Initiatives that are associated with this strategy

For more detailed description about using strategies, refer to the Hyperion System 9 Performance Scorecard User’s Guide.

Extended Reporting through Interactive Reporting 191

Extended Reporting through Interactive Reporting You can generate reports through the Interactive Reporting from the Performance Scorecard database, as outlined in these procedures:

● Create an Interactive Reporting database connection (.oce file), as outlined in “Creating the .oce File” on page 191.

● Import the Open Catalog Extension (.oce) file, as outlined in “Importing the .oce File through Workspace” on page 193.

● Publish the BQY file, as outlined in “Importing the BQY File through Workspace” on page 195.

● Generate the Star Schema database and the report, as outlined in “Generating an Interactive Reporting Report” on page 198.

● View the reports, as outlined in “Viewing Generated Reports” on page 200.

Before You BeginBefore you can generate any reports through an Interactive Reporting integration, complete these steps:

● Configure access to an Interactive Reporting Server and Services.

● Configure access to Performance Scorecard.

● Configure Shared Services single sign-on between Interactive Reporting and Performance Scorecard. See the Hyperion System 9 Performance Scorecard Installation Guide.

Creating the .oce FileAn Interactive Reporting database connection (formerly called an Open Catalog Extension or .oce file) is a portable file that describes the connection to your data source for the relational or Analytic Services database. The.oce file can be created in Interactive Reporting, and stores information about the BQY’s (queries) database connections, such as user names and passwords.

If you frequently generate the same report, you only require one .oce file. If you create custom reports that access data from multiple sources, you may require multiple .oce files for one report.


➤ To create an Interactive Reports .oce file:

1 Create an ODBC connection on the Interactive Reporting computer to the database that is to be used by the report.

2 Select Start > Programs > System 9 BI+ >Utilities and Administration > Service Configurator to open the local Service Configurator.

Select the DAS service and add the ODBC connection information including the connection type (ODBC), database type and the name of the data source, which is the ODBC connection name. For detailed instructions, refer to the Hyperion System 9 BI+ Workspace documentation.

3 Select Start > Programs > Hyperion System 9 BI+ >Interactive Reporting Studio to launch Interactive Reporting Studio to create the .oce file.

The Database Connection Wizard is displayed.

4 Under Create a New Document, click A New Database Connection File, and select Repository Document from the list.

5 Complete the wizard screens to define the database connection information:

● Select ODBC as the type of connection software.

● Select the type of database you are using, such as MS SQL Server.

● Enter the database User Name and password

● Enter the IP address or name of the ODBC database host

6 Click Finish.

7 Save the .oce file.

8 Close the Interactive Reporting Studio.

After creating the .oce file, publish the .oce file to the Interactive Reporting Server, as outlined in “Importing the .oce File through Workspace” on page 193.


Importing the .oce File through WorkspaceAfter creating the .oce file, it must be imported to the Hyperion System 9 BI+ server for use in generating the reports.

➤ To import the .oce file:

1 Launch Workspace, using the following URL:

http://<server name>:<port number>/Hyperion/browse/workspace

2 Log on to Workspace as an Administrator, and ensure these Interactive Report services are running:

a. HPS_SuperService1

b. HPS_IntelligenceService1

c. HPS_DataAccessService1

3 In the View pane, select Explore and navigate to the location of the repository.

4 Right-click to display the shortcut menu, and select New Folder to create a folder for the file that is being imported. If you do not want to create a folder, leave the file under the Root (/:).

The Create New Folder dialog box is displayed.

5 Enter the name of the new folder, then click OK.

6 From the View pane, select the new folder.


7 Right-click to display the shortcut menu, and select Import > File to publish the .oce file within Hyperion System 9 BI+ Interactive Reports.

The Choose File tab is displayed.

8 Under File on the Choose File tab, click Browse to navigate to the location of the .oce file.

By default, the file is located in c:\hyperion\BIPlus\bin\Open Catalog Extensions.

9 Click Next.

The Advanced tab is displayed.

10 Under Processing OCE Options, select these options and information:

● From Data source access, select Use the username/password specified below.


● Enter the Username and Password for the database.

● Select Allow pass-through where end user’s authentication system is enabled for it.

11 Click Finish.

The .oce file is published and available for the integration.

12 Publish the BQY file, as outlined in “Importing the BQY File through Workspace” on page 195.

Importing the BQY File through WorkspaceWithin Hyperion System 9 BI+ Interactive Reports, a report is stored as a BQY file. This file contains the formatting and structure for the report.

Performance Scorecard provides three sample BQY files:

● Scorecard.bqy. See “Scorecard Report” on page 187

● Scorecard_withMeasureTrend.bqy. See “Scorecard with Measure Trends” on page 188

● StrategyDashboard.bqy. See “Strategy Dashboard” on page 189

You can modify the BQY files used for the default reports as a starting place to create your own customized reports. For detailed information on Smart Cuts formats and generating customized reports, refer to the Hyperion System 9 BI+ Financial Reporting, Interactive Reporting, Production Reporting, and Web Analysis Developer's Guide

➤ To import a BQY file:

1 Log on to Workspace as an Administrator.

2 From the View Pane, navigate to the location of the .oce folder.

3 Right-click on the folder to display the shortcut menu, and select Import File to access the sample Performance Scorecard BQY reports.

The Choose File tab is displayed.


4 Under File on the Choose File tab, click Browse to navigate to the location of the selected BQY file, then click Next. By default, the sample files are located in <HYPERION_HOME>\hps\4.1\AppServer\InstallableApps\common\Reports\

Template.

5 Click Next.

The Advanced tab is displayed.

6 From the Advanced tab, click Edit Permissions to display the Properties page to set the access level for the reports.

7 Select the users, roles or groups who are to be given access to the report from the Available Users, Groups and Roles list.

8 Click the add arrow to move the identified users to the Selected Users, Groups and Roles list.

9 Click Edit to open the Edit Permissions dialog box.


10 From Edit Permissions, select the appropriate level of Access to File, such as No Access or Full Control.

11 Select the Adaptive State, or the level of access the user will have to modify the report, such as View Only or Query and Analyze.

12 Under Favorite, select Empty.

13 Click OK to close the Edit Permissions dialog box.

14 From the Properties dialog box, click OK to save the new permissions.

15 Click Next.

The IR Properties tab is displayed. This tab is used to associate the queries with the BQY file.

16 From the Set all queries to obtain the username/password: list, select From OCE Default.

17 From Connection, select the configured .oce file for each Query/Data Model Name.

The Username Password and Options information is automatically populated from the .oce file.

18 Under Interactive reporting Options, select Enable IR for use in HTML.

19 Click Go.


The Username Password and Options information is automatically populated from the .oce file. The Performance Scorecard report is now published and available for generation in Performance Scorecard, as outlined in “Generating an Interactive Reporting Report” on page 198.

Generating an Interactive Reporting ReportAfter the .oce and BQY files have been created and imported to Interactive Reporting, you can generate the selected report.

➤ To generate a report through Interactive Reporting:

1 Launch Workspace, using the following URL:

http://<server name>:<port number>/Hyperion/browse/workspace

2 Log on to Workspace as an Administrator, and ensure these Interactive Report services are running:

a. HPS_SuperService1

b. HPS_IntelligenceService1

c. HPS_DataAccessService1



4 From the main menu, select Administration > Star Schema Generation.


5 Select the settings you require to generate the Performance Scorecard Star Schema tables:


● Under Time Options, select the appropriate dates for which you want to view results. If you do not need data for all dates, Hyperion recommends that you select Calculate for Dates from Date, and select a date range from the calendar pop-up.

Note: The dates specified in the Smart Cut URL must exist in the set of data that you are saving to the Performance Scorecard Star Schema tables.

● Under Generate Star Schema Rows, select the dates that you require data to be generated for the report.

● Under Star Schema Structure, select the appropriate option. If you have weights specified for your measures, select Create with Weights Included.

● DO NOT check these options:

i. Conform to Analytic Services Naming Restriction

ii. Generate Analytic Services Database

6 Click Create Database.

7 Select File > Application Preference to display the Application Preferences screen.


9 Under Add External Reports, click Add. A blank line is added to the table.

10 Enter a unique name for the Interactive Reporting Report, and the Smart Cut URL to the Interactive Reporting Server and the report. The Reports URL may appear in the following format:

http://<BIPlus Server name>:<Interactive Reporting Server port number>/<path to BQY file> <Date range from which data will be retrieved, in mmddyyyy format>


For example: http://BIPlusServer:19000/workspace/browse/get/HPS41/ScorecardDashboard.bqy?bqtype=ihtml&Toolbar=Standard& ScorecardName=Taylor,Frank&Date1=10012004&Date2=11012004

The date range for the data must be entered in the format mmddyyyy.

11 Click Save to save the URL.

Note: You can modify the parameters on the default reports to pass different parameters by entering a different value in the Smart Cut URL.

Viewing Generated ReportsAfter generating the custom reports through Interactive Reporting, you can view the reports in Performance Scorecard.

If you add or modify a measure, scorecard or performance indicator, regenerate the Star Schema to view the changed information.

Note: If you use custom performance indicators, you may need to manually configure the BQY file to set the indicators to display properly.

➤ To view a generated report:

1 Launch Performance Scorecard.

2 From the Performance Scorecard main menu, select Reports > Custom Reports.

3 Select the customized Intelligence report that you added to your preferences. The name of the report is the name that you entered when generating the report.

4 View the report in the Contents pane.

Extended Reporting through Hyperion IntelligenceYou can generate reports through Hyperion Intelligence from the Performance Scorecard database, as outlined in these procedures:

● Create an Interactive Reporting database connection (.oce file), as outlined in “Creating an .oce File in Hyperion Intelligence” on page 201.

● Publish the Open Catalog Extension (.oce) file, as outlined in “Publishing an .oce File to the Hyperion Intelligence Server” on page 202.

● Publish the BQY file, as outlined in “Publishing a BQY File through Hyperion Intelligence” on page 202.

● Generate the Star Schema database and the report, as outlined in “Generating a Hyperion Intelligence Report” on page 204.

● View the reports, as outlined in “Generating a Hyperion Intelligence Report” on page 204.

Extended Reporting through Hyperion Intelligence 201

Before You BeginBefore you can generate any reports through a Hyperion Intelligence integration, complete these steps:

● Configure access to the Hyperion Intelligence Server and Services.

● Configure access to Performance Scorecard.

● Configure single sign-on between Hyperion Intelligence and Performance Scorecard. See

the Hyperion System 9 Performance Scorecard Installation Guide.

Creating an .oce File in Hyperion IntelligenceA Hyperion Intelligence database connection (formerly called an Open Catalog Extension or .oce file) is a portable file that describes the connection to your data source for the relational or Analytic Services database. The .oce file can be created in Hyperion Intelligence, and stores information about the BQY’s (queries) database connections, such as user names and passwords.

If you keep generating the same report, you only require one.oce file. If you create custom reports that access data from multiple sources, you may require multiple .oce files for one report.

➤ To create an .oce file:

1 Create an ODBC connection on the Hyperion Intelligence computer to the database that is to be used by the report.

2 Select Start > Programs > Hyperion Solutions > Hyperion Performance Suite > Foundation Services > Service Configurator to open the local Service Configurator.

Select the DAS service and add the ODBC connection information including the connection type (ODBC), database type and the name of the data source, which is the ODBC connection name. For detailed instructions, see the Hyperion Performance Suite documentation.

3 Launch Hyperion Intelligence to create the .oce file.

4 In Hyperion Intelligence, add a new file for the database connection information.

5 Select ODBC as the connection software.

6 Select the database type, then click Next.

7 Enter the database username, password and the ODBC connection name, then click Next.

8 Save the .oce file.

9 Close Hyperion Intelligence.

10 Publish the .oce file, as outlined in “Publishing an .oce File to the Hyperion Intelligence Server” on page 202.


Publishing an .oce File to the Hyperion Intelligence ServerAfter creating the .oce file, publish the .oce file to the Hyperion Intelligence Server.

➤ To publish an .oce file:

1 Launch the Hyperion Intelligence Server and services.

The Service start order is as follows:

a. BrioPlatform_<machine name><port number>)

b. BI2_<machine name><port number>)

c. DAS_<machine name><port number>)

In these commands, <machine name> is the name of the machine where Hyperion Intelligence is installed, and <port number> is the port number that was specified during the installation of Hyperion Intelligence.

2 Log on to Hyperion Intelligence, using this URL:

http://<server name>:<port number>/Hyperion/browse

Browse should be selected on the list. You may add a folder to publish the file, or leave the file under the Root.

3 Click Publish File.

4 Navigate to the .oce file you created in “Creating an .oce File in Hyperion Intelligence” on page 201.

By default the path is Brio8/Client/Program/Open Catalog Extensions. You may enter a name, or leave the default name.

5 Click Next.

6 Under Processing OCE Options, select Use username/password specified below from the list.

7 Enter the database username and password to connect to the Performance Scorecard database.

8 Click Finish.

The .oce file is published and available for the integration.

Publishing a BQY File through Hyperion IntelligenceAfter publishing the .oce file, publish the query BQY file to the Hyperion Intelligence Server.

➤ To publish a BQY file:

1 Launch the Hyperion Intelligence Server and services.


a. BrioPlatform_<machine name><port number>)

b. BI2_<machine name><port number>)

c. DAS_<machine name><port number>)


In these commands, <machine name> is the name of the machine where Hyperion Intelligence is installed, and <port number> is the port number that was specified during the installation of Hyperion Intelligence.

2 Log on to Hyperion Intelligence, using this URL:

http://<server name>:<port number>/Hyperion/browse

Browse should be selected on thelist. You may add a folder to publish the file, or leave the file under the Root.

3 Click Publish File.

4 Navigate to the BQY file that was copied to your machine.

You may enter a name, or leave the default name.

5 Click Next.

The Performance Scorecard Access Control pane is displayed.

6 Set the Access Control using the following conditions:

● Select Full Control for Access to File for users who can access the report

● Select View and Process for Adaptive State.

7 Click Next.

8 The BQY Properties screen is displayed.


9 Under Connection, select the correct .oce file for each Query/Data Model Name.

10 Under Connecting to Data Sources, from the Set all queries to obtain the username/password list,

select OCE Default field, then click Go.

When you select the required .oce files, the appropriate username and password are populated.

11 Under Intelligence Server Options, click Show for Pre-Generate HTML Options.

12 Select Pre-generate the following sections, and select the appropriate options.

13 Click Finish to complete publishing of the BQY file.

Generating a Hyperion Intelligence ReportAfter the .oce and BQY files have been created and published to the Hyperion Intelligence Server, you can generate the selected report.

➤ To generate a report through Hyperion Intelligence:

1 Launch the Interactive Reporting Server and services.


a. Interactive Reporting Super Service (for example, BrioPlatform_<machine name> <port number>)

b. Business Intelligence Server (for example, BI2_<machine name><port number>)

c. Data Access Service (for example, DAS_<machine name><port number>)

In these commands, <machine name> is the name of the machine where Interactive Reporting is installed, and <port number> is the port number that was specified during the installation of Interactive Reporting.




3 From the main menu, select Administration > Star Schema Generation.


4 Select the settings you require to generate the Performance Scorecard Star Schema tables:

● Under Time Options, select the appropriate dates for which you want to view results. If you do not need data for all dates, Hyperion recommends that you select Calculate for Dates from Date, and select a date range from the calendar pop-up.

Note: The dates specified in the Smart Cut URL must exist in the set of data that you are saving to the Performance Scorecard Star Schema tables.

● Under Generate Star Schema Rows, select the dates that you require data to be generated for the report.

● Under Star Schema Structure, select the appropriate option. If you have weights specified for your measures, select Create with Weights Included.

● DO NOT check these options:

i. Conform to Analytic Services Naming Restriction

ii. Generate Analytic Services Database

5 Click Create Database.

6 Select File > Application Preference.

The Application Preferences screen is displayed.



8 Under Add External Reports, click Add.

A blank line is added to the table.

9 Enter a unique name for the Interactive Reporting Report and the Smart Cut URL to the Interactive Reporting Server and the report, as outlined in “Smart Cuts URLs” on page 185.

10 Click Save to save the URL.

Note: You can modify the parameters on the default reports to pass different parameters by entering a different value in the Smart Cut URL.

Viewing Generated Intelligence ReportsAfter generating custom reports through Hyperion Intelligence, you can view the reports in Performance Scorecard.

If you add or modify a measure, scorecard or performance indicator, regenerate the Star Schema to view the changed information.

Note: If you use custom performance indicators, you may need to manually configure the BQY file to set the indicators to display properly.

➤ To view a generated report:


2 From the Performance Scorecard main menu, select Reports > Custom Reports, and select the customized Intelligence report that you added to your preferences. The name of the report is the name that you entered when generating the report.

3 View the report in the Contents pane.

Managing and Monitoring Application Business Objects 207

C h a p t e r

10Managing and Monitoring

Application Business Objects

This chapter describes several reports that can be used to monitor the application:

● Locked Business Object report can be used to break locks applied to business objects that are in use or that have been frozen

● Audit Report is used to track changes made to application business objects

● User Session Report provides details about active and historical user sessions

In This Chapter Using the Locked Business Objects Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Using the Audit Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Using the User Session Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

208 Managing and Monitoring Application Business Objects

Using the Locked Business Objects ReportUse the Locked Business Objects report to break any lock applied to a business object.

Business objects become locked when a user is modifying them. Locks are cleared in these circumstances:

● When a business object is saved

● If the user editing a business object cancels changes or navigates to another page

● The user logs off Performance Scorecard

If a user forgets to log off, business objects they had open may be left in a locked state.

Note: If you unlock a business object that is currently being modified by a user, the user cannot save their changes.

➤ To unlock a business object:




3 Select Administration > Locked Business Objects Report.

The Locked Business Object Report is displayed, listing objects that are in use or locked.

4 Beside the business object to be unlocked, click Break.

Users can now edit the unlocked business object.

Using the Audit Report 209

Using the Audit ReportAll modifications made to application business objects are flagged in the Audit Report. Use this report to determine what applications business objects have been modified, when the changes were made, and by whom.

➤ To open the Audit Report:




3 Select Administration > Audit Report.

The Audit Report is displayed.

You can perform various queries using these criteria:

● Name or ID of the business object that may have been modified

● ID of the user who may have made the changes

● Date on which changes may have been made

4 Select the kind of query you want to perform as outlined in this table.

Table 21 Query Options in the Audit Report

Option Description

by object name Returns data for an object whose name you enter.

by user ID Returns information about application business objects accessed or modified by the selected user ID.

by object ID Returns data about how the selected business object was accessed or modified.

by date range Returns all changes made to an application during a selected period of time. Click the calendar icon to select a start and end date for the range.


5 Click Execute Query.

The Audit Report displays the results of your query.

Note: Depending on the size of the application, the query results may take some time to display.

Based on the queries that you performed, the report presents the following information:

● Date and time a business object was accessed or modified

● Login ID of the user who accessed or modified a business object

● The action taken on a business object (created, deleted etc.)

● Name of the business object accessed or modified

● Class name of the business object that was modified (for example, Measure)

This information enables you to inspect the database tables directly. The class name is also useful because two different business objects may have the same name and the class name enables you to distinguish them.

● The ID of the business object that was accessed or modified.

This is a unique, system generated name that is automatically applied to each business object.

6 Optional: Click Compact Audit Trails to permanently compact records before a selected date.

From the Date Selector calendar, select the date BEFORE which you want to compact the records. A confirmation message is displayed. Click Yes to compact the records. A progress window is displayed to indicate the progress of the action, and the result.

Using the User Session Report 211

Using the User Session ReportThe User Session Report enables the Administrator to view details about active and historical user sessions. The Administrator can query the report to display information for a user ID and date range, and can limit the report to currently active sessions only.

A user is considered active if a session exists within the application server that is associated with the user, and has not been terminated due to logout or timeout.

➤ To generate a User Session Report :

1 From the Performance Scorecard main menu, select Administration > User Session Report.

The User Session Report is displayed.

Table 22 User Session Report

Column Description

Process Displays the server machine name and optional cluster ID of the Performance Scorecard to which the user has logged on

User Displays the ID of the user account that owns the session

Name Displays the full name of the associated employee. If the user account does not have an associated employee, this column is blank.

Email Displays a link to the e-mail address of the associated employee, if available. If the link is clicked, the user’s e-mail is launched.

Login Displays the server time that the user account logged into the session.

Logout Displays the server time that the session ended, by logout or timeout. If the session timed out, an icon is displayed to the right of the timestamp.

Actions Provides a link to the Audit Trail report, which displays all actions for the day of the session’s log in time for the associated user.


2 Optional: Under Query Clauses, complete one or more of these query clauses to refine the report:

● Select User ID and enter the user ID to restrict the report to activity for one user.

● Select Within Date Range to restrict the report to activity within the selected date range. Click the Calendar icon to display the Date Selector calendar and choose the From and To dates.

● Select Currently Active Sessions Only to restrict the report to activity for currently active sessions. A user is considered active if a session exists within the application server that is associated with the user and has not been terminated due to logout or timeout.

Note: A session may remain active if it was not terminated by logout or timeout when the server was restarted.

You can select one or more of the query clauses to control the contents of the report.

3 Optional: Click Customize to modify the default information provided by the report.

The Customize pane is displayed in the report window.

Using the User Session Report 213

4 Select the information to be displayed on the User Sessions Report.

5 Optional: Click Set System Defaults to set the default report format.

6 Click Save.

7 Click Execute.

The report is generated, and the results are displayed in the table at the bottom of the window.

8 Review the report.

9 Optional: Under Actions, click Action to link directly to the Audit Report.

10 Optional: Click Truncate User Session Table to permanently remove all user session records before a selected date.

From the Date Selector calendar, select the date before which you want to delete the records. A confirmation message is displayed. Click Yes to delete the records.


Customizing Hyperion System 9 Performance Scorecard and the Alerter 215

A P P E N D I X

ACustomizing Hyperion System 9 Performance Scorecard and the

Alerter

Although it is not usually necessary to modify the properties files for Performance Scorecard, you can customize some functional and visual properties for Hyperion System 9 Performance Scorecard and the Alerter through the appropriate properties files.

To customize other elements of Performance Scorecard, you can also use the Application Preferences and individual preferences within the application. Refer to the Hyperion System 9 Performance Scorecard Application Designer’s Guide and the Hyperion System 9 Performance Scorecard User’s Guide for additional information.

In This Appendix Customizing Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Customizing the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

216 Customizing Hyperion System 9 Performance Scorecard and the Alerter

Customizing FunctionalityYou can modify various aspects of how Performance Scorecard and the Alerter work by modifying HPSConfig.properties and AlerterConfig.properties. These topics are covered:

● “Customizing Hyperion System 9 Performance Scorecard” on page 216

● “Customizing the Alerter” on page 219

Customizing Hyperion System 9 Performance ScorecardThis section describes how to modify the HPSConfig.properties file to customize certain aspects of Performance Scorecard.

➤ To customize Performance Scorecard:

1 From <Web application server>\webappsconf\config open the Performance Scorecard HPSConfig.properties in any text editor.

2 By default, the file is installed in the following location: C:\Hyperion\hps\9.2\AppServer\InstalledApps\common\webappsconf\config

3 Identify entries in the file you can change to customize Performance Scorecard, using Table 23 “Customizing Hyperion System 9 Performance Scorecard” on page 216.

4 Save your changes in the HPSConfig.properties file.

Table 23 Customizing Performance Scorecard: Entries in HPSConfig.properties

Entry Description

Persistence and Query Settings

hyperion.hps.audit_trail.is_required Set this to false if you want do not want to save extra auditing information in the data store.

CAUTION! If set to false, the Alerter and support for deployment in a clustered environment will not work, and will not be able to use promotion.

hyperion.hps.prefetch Change this entry to false if you want Performance Scorecard to only fetch the appropriate data objects for each page you open. This will improve application startup time but may make Performance Scorecard slow the first time you log on, since objects are fetched as needed.

If set to true, all objects will be pre-fetched from the database when you start Performance Scorecard. This results in slower application startup time, but better and more consistent performance.

CAUTION! If you change this setting to false, you cannot use the Performance Scorecard Adapter.

Note: If you need to selectively turn off pre-fetching by object type, contact Hyperion Support for assistance.

Customizing Functionality 217

Synchronizing User Accounts with Employees

hyperion.hps.user_account_automatic_id_ computer_class

A customer user-id generation algorithm can be implemented as a java class and then its full-package-name specified for this parameter.

This java class must conform to the com.hyperion.pmd.hps.model.authorization.UserIDFromEmployeeComputerInterface interface (see below) and be available on the classpath.

public interface UserIDFromEmployeeComputerInterface { /** @param emp Employee business object to base the construction of the user ID upon. @return The user ID that should correspond to the given employee. */ public String computeUserID(Employee emp);}

Notes Settings

hyperion.hps.notes.home This entry contains the absolute directory path to a directory in which the notes subsystem to keep temporary files.

hyperion.hps.notes.minimum_db_connections Using an integer greater than 0, this entry states the minimum number of database connections open for the notes subsystem database connection pool. We recommend that you have at least one connection.

hyperion.hps.notes.maximum_db_connections Using an integer greater than 0, this entry contains the maximum number of database connections that can be opened for the notes subsystem database connection pool. We recommend that you have at least four connections available.

Modify this entry to increase the speed of notes-related functions such as fetching.

Attachments Settings

hyperion.hps.objectAttachmentsFolder Provides the directory where Performance Scorecard stores uploaded attachments from employees, notes, initiatives, etc. We do not suggest modify this entry or changing the directory.

Table 23 Customizing Performance Scorecard: Entries in HPSConfig.properties (Continued)

Entry Description


Password-Related

hyperion.hps.password_constraint Modify this entry to customize the syntax of passwords using regular expressions.

After changing this entry, modify webreports.password_change.password_ not_match_constraint in the ApplicationResources_*.properties file so the warning message reflects the constraint.

Performance-Related

hyperion.hps.formula.value-caching_limits Modify this entry to increase caching limits for formula computations.

Miscellaneous

hyperion.hps.host_name If you want to deploy your application on a different computer, specify the name of the new computer after “hps.” For example: Hyperion.hps.qelab2.

hyperion.hps.main_data_store.driver_class_name Provides the Java driver class name from the data store vendor used to access the application database. For example:

hyperion.jdbc.sqlserver.SQLServer Driver

Modify this entry if you have switched database types.

hyperion.hps.main_data_store.user_name Provides the user name or account that connects to the data store (application database). This value is encrypted and cannot be manually changed.

hyperion.hps.main_data_store.password Contains the password for the account used to log into the database. This value is encrypted and cannot be manually changed.

hyperion.hps. authentication_ service.logon_params

Contains the log on input fields used to authenticate users. These input field names are separated with blank spaces.

Possible input field names are:

● {user_name, password, domain}

● For basic authentication: user_name password

● For NTLM authentication: user_name password domain

hyperion.hps.data_watcher_ service.change_check_ interval_seconds

For users in a clustered environment: Modify the default value of 150 to increase or decrease the amount of time that elapses before changes made to one instance of an application are reflected in all applications.

The number you specify instead of 150 is the maximum number of seconds that elapse before the application database shared by multiple applications in a clustered environment is refreshed so changes to one application are reflected in all others.


Entry Description

Customizing Functionality 219

Customizing the AlerterThis section describes how to modify the form of delivery the Alerter uses to send alert notifications. However, this requires java programming skills and the creation of new java classes. To perform these tasks, contact Hyperion Support for assistance:

● Change the alert notification delivery form by modifying at.hyperion.hps.alerter.delivery.class_name

● Remove or add custom options used on alert notification message by modifying hyperion.hps.alerter.message_decorator

hyperion.hps. displayed_element_ title_in_name

Use this entry to specify whether the title and name of accountability and strategy elements are displayed in reports and details pages.

hyperion.hps.request_blocker.class_name This class is set automatically during installation to block all requests to Performance Scorecard during a HAL load, promotion, and so on.

During installation, you select the type of environment to which Performance Scorecard is being installed:

● Non-clustered (single process), or

● Clustered (multiprocess)

The Request Blocker class name is automatically set to the appropriate value:

● com.hyperion.pmd.hps.SingleProcessRequest Blocker

● com.hyperion.pmd.hps.MultiProcessRequest Blocker

This value should not be modified unless instructed by Support.

hyperion.hps.object_id_generator.block_size Modify this entry to increase the block size of the object ID generator. The ID generator will immediately reserve a block of IDs (in the amount set by this entry) in a pool and generate the next ID from the pool. After the reserved IDs are consumed, the generator will try to reserve another block of IDs. The higher value will result in better performance in a writing access dominated system. CAUTION: Because IDs that are reserved but not yet used will not be allocated to any object after rebooting the server, an unnecessarily high value will waste too much IDs if the server is often restarted.


Entry Description


Customizing the User InterfaceThis section describes how to modify elements in the user interface by modifying applets or cascading style sheets. These topics are covered:

● “Working With Cascading Style Sheets” on page 220

● “Modifying UI Themes” on page 221

● “Available Cascading Style Sheets” on page 222

● “Working With Style Sheets: Tips and Recommendations” on page 223

Note: To customize the masthead with a corporate logo, refer to the Preferences chapter in the Hyperion System 9 Performance Scorecard User’s Guide.

Working With Cascading Style SheetsCascading style sheets define the desktop user interface (UI) themes, which create the appearance of the desktop. You can customize a Performance Scorecard cascading style sheet for your business environment by performing these tasks:

● Using a different desktop color schema

● Modifying fonts or creating a new color-coding scheme

● Changing background colors

Changes to the cascading style sheet must be made on the Web application server and will consequently affect all users connected to the Web application server.

Caution! Hyperion recommends only those with a working knowledge of cascading style sheets and familiar with style sheet editor tools perform these customizations. Changes to a cascading style sheet must be made on the Web server. The changes will affect all users connected to the Web server.

These topics are covered:

● “Modifying UI Themes” on page 221

● “Available Cascading Style Sheets” on page 222

● “Using client.css” on page 222

● “Using global.css” on page 223

● “Working With Style Sheets: Tips and Recommendations” on page 223

Customizing the User Interface 221

Modifying UI ThemesPerformance Scorecard supports multiple visual themes, and enables end-users to select the theme they wish to use. Each theme contains a set of cascading style sheets and images that is used to create the graphical look when that theme is selected. Many visual aspects of the application are controlled by these themes, such as fonts, colors, icons, backgrounds, and so on.

Performance Scorecard uses two UI themes: Hyperion and Hyperion Alternate. These UI themes are very similar, with Hyperion Alternate offering a higher-contrast look for enhanced visibility. You can select a UI theme as your preference, as outlined in the Preferences chapter in the Hyperion System 9 Performance Scorecard User’s Guide.

Modify the existing Hyperion UI theme, or add a new theme to a deployed Hyperion Performance Scorecard application. See “To add a new theme based on an original theme:” on page 221.

➤ To add a new theme based on an original theme:

1 Navigate to the location of the Hyperion UI theme. By default, the themes are located in the following path:

\Hyperion\hps\9.2\AppServer\InstalledApps\Tomcat\5.0.28\ webreportsDomain\webapps\HPSWebReports\ui_themes\tadpole

2 Copy the Hyperion theme to a new directory at the same level, for example, new_theme.

3 Open the \HPSWebReports\WEB-INF\classes\ThemeConfig.properties file in any text editor, and add a new line to identify the name of the new theme directory you created, using the following format:

new_theme.key=theme.new

The name, theme.new, is a key that uniquely identifies the newly created theme. The name must be different from any of the other keys in the file.

4 Save and close the \HPSWebReports\WEB-INF\classes\ThemeConfig.properties file.

5 Open the \HPSWebReports\WEB-INF\classes\ApplicationResources .properties file in any text editor.

6 Under the section, Theme names, add the theme key you created in step 3, to the properties file, and create a name for the theme. This is the name that will be displayed in the application when selecting the theme to use. For example:

theme.new=New Theme For Testing Purposes

7 Modify the new theme to meet your requirements, as outlined in the “Using client.css” on page 222 and “Working With Style Sheets: Tips and Recommendations” on page 223, then save the changes.

8 Restart Performance Scorecard.

The new UI theme is now available for users.


Available Cascading Style SheetsThe cascading style sheets for Performance Scorecard are located in the following directory: <HPSWebReports>\ui_themes\tadpole

Performance Scorecard primarily uses the following cascading style sheets:

● client.css - Defines Web UI elements specific to the customer style sheet customization. See “Using client.css” on page 222.”

● productContent.css - Defines Web UI elements specific to Performance Scorecard. This style sheet should not be modified by customers.

● global.css - Defines Web UI elements common to multiple Hyperion products. See “Using global.css” on page 223.

Caution! The global.css file must not be modified.

Note: For Accessibility, Hyperion provides an alternate theme called tadpole_hc that provides high-contrast colour customizations. This theme is found in the directory \HPSWebReports\ui_themes\tadpole_hc.

Using client.cssThe client.css file is an empty file, that is available for you to add your style customizations for Performance Scorecard. Make any modifications or style sheet customization to this file, and they are automatically implemented in the application.

To override a style from the productContent.css or global.css files, copy the section to client.css, and then change the section. Copy only those styles that you need to change.

When the productContent.css and the global.css files are updated with Performance Scorecard changes, the changes you have made in the client.css file will be unaffected.

Customizing the User Interface 223

Using global.cssTable 24 identifies portions of global.css that you can modify. Sections that Hyperion urges you not to modify are noted.

Working With Style Sheets: Tips and RecommendationsHere are some helpful hints for working with Hyperion cascading style sheets:

● Before making any changes to a cascading style sheet, back up the original version.

● Styles that are common across multiple products can be found in the global.css file.

● Styles for products requiring unique styles can be found in a product.css file.

● Some of the user interface's controls are components that are part of third party technologies used in our products. Changing the styles of these third party controls requires changes in their associated files.)

● Avoid making changes to styles that will affect layout of these elements:

❍ Padding

❍ Borders

❍ Text and Vertical Align

❍ Position

❍ White-space

● Keep in mind that “color” changes the font color and “background” changes the color of elements, such as buttons.

● Change the color of text that is hyperlink text using the hyperlink style (a:link, a:hover, a:visited).

Table 24 Global.css

Customizable Are Non-Customizable Area

● Non-Navigation Styles

● Content Area

● Logon Styles

● Tabs

❍ Tab Anchor Tags

❍ Tab Body

● TaskTabs

● Task Tab Body

● Groupboxes

❍ Groupbox Anchor Tags

● Buttons

❍ When Drawing Buttons in HTML

❍ When Using Button Tag

❍ When Using Input Tag

● Tadpole Menubar

❍ Tadpole Menuitem

❍ Menu Styles (RM) (order is important)

● Tadpole Minimized Masthead

● Tadpole Toolbar

● Tadpole View Pane (also called the Object Palette)

● Tadpole Tree


● Consider carefully any changes to toolbar buttons, because the changes may require editing all the buttons in the product.

● Hyperion toolbar buttons rely on a dark-blue background to be displayed properly.

Common Member Attributes for Shared Services 225

A P P E N D I X

BCommon Member Attributes for

Shared Services

This section provides the common name for attributes used in Hyperion System 9 Shared Services and their equivalent member attributes in Hyperion System 9 Performance Scorecard and other Hyperion products. Only attributes that are different between Shared Services and other Hyperion products are identified.

Note: In the tables, NA indicates that the attribute is not used by the Hyperion product.

In This Appendix Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Configuration Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Account Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Account Type Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Entity Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Scenario Member Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Version Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Year Member Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Consolidation Method Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Container Model Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Element Model Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Measure Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Variable Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Employee Model Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Accountability Element or Strategy Element Model Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Unit Model Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

226 Common Member Attributes for Shared Services

Member Attributes

Configuration Attributes

Table 25 Common Member Attributes

Shared Services AttributeFinancial Management Attribute Planning Attribute

Performance Scorecard

Hyperion Business Modeling Attribute

Alias Description Alias NA Name

SharedMember NA DataStorage NA NA

DataStorage2 NA Reserved for future use NA NA

DataStorage4 NA Reserved for future use NA NA

UDA1-n UserDefined1-3 UDAs (Reserved for future use) NA NA

Consolidation NA AggSymbol (plantype1) NA NA

Consolidation2 NA AggSymbol (plantype2) NA NA

Consolidation4 NA AggSymbol (plantype3) NA NA

MemberFormula2 NA Reserved for future use NA NA

MemberFormula4 NA Reserved for future use NA NA

DataStorage - StoreData IsCalculated=No Stored NA NA

DataStorage - SharedMember NA SharedMember NA NA

DataStorage - Dynamic Calc NA Dynamic & Calc NA NA

DataStorage - Dynamic Calc And Store

NA Dynamic-Calc & Store NA NA

DataStorage - None NA PlanType NA NA

Table 26 Common Configuration Attributes

Shared Services Attribute Planning AttributePerformance Scorecard Attribute


DefaultCurrency DefaultCurrency NA CurrencyName

WeeksDistribution Support445 NA NA

FullName UseFullName NA NA

EmailServer EmailServer NA OutgoingEmail Server

StartYear First_year NA NA

EndYear NA NA NA

Account Type Attributes 227

Account Member Attributes

Account Type Attributes

NumberOfYears Num_year NA NA

CurrentYear Current_year NA NA

BaseTimePeriod Base_time_period NA TimelineType

PeriodsInYear Periods_in_year NA NA

Table 27 Common Account Member Attributes



DefaultAccountType NA NA Type

PlanningAccount Type

AccountType NA NA

Consolidation AccountType

NA NA NA

Table 28 Common Account Type Attributes



Expense Expense NA Cost

Revenue Revenue NA Revenue

LabelOnly LabelOnly NA NA

Table 26 Common Configuration Attributes (Continued)




Entity Member Attributes

Scenario Member Attributes

Version Member Attributes

Year Member Attributes

Table 29 Common Entity Member Attributes



Currency BaseCurrency CurrencyCode NA

Table 30 Common Scenario Member Attributes



DefaultFrequency NA NA NA

ConsolidationType NA NA NA

EnableProcess Management

EnabledForPM NA NA

Table 31 Common Version Member Attributes



EnableProcess Management

EnabledForPM NA NA

VersionType BottomUp, Target NA NA

Table 32 Common Year Member Attributes



Name Name Name ID or Name

Measure Model Attributes 229

Consolidation Method Attributes

Container Model Attributes

Element Model Attributes

Measure Model Attributes

Table 33 Common Consolidation Method Attributes



ConsolidationMethod NA NA NA

Comment Comment NA NA

Table 34 Common Container Model Attributes



UserName NA NA LoginUserName

Password NA NA Login Password

Table 35 Common Element Model Attributes



TagSet NA NA Application

Table 36 Common Measure Model Attributes



Unit NA Unit NA

IsTemplate NA IsTemplate NA


Variable Model Attributes

Employee Model Attributes

Accountability Element or Strategy Element Model Attributes

Unit Model Attributes

Table 37 Common Variable Model Attributes



Unit NA Unit NA

Table 38 Common Employee Model Attributes



FirstName NA FirstName NA

LastName NA LastName NA

UserId NA UserId NA

Table 39 Common Accountability Element Model Attributes



MapName NA Unit NA

Table 40 Common Unit Model Attributes



ScalingFactor NA ScalingFactor NA

Frequently Asked Questions 231

C h a p t e r

CFrequently Asked Questions

This section provides answers to questions frequently asked by Hyperion System 9 Performance Scorecard (Performance Scorecard) Administrators.

In This Chapter Increasing Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Increasing Startup Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Increase Data Caching Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Allocating Physical Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Tuning Garbage Collection for Sun JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

232 Frequently Asked Questions

Increasing Session TimeoutYou can modify the session timeout setting to extend the amount of time the application allows to elapse before prompting you to log on again.

➤ To extend the default time-out:

1 Shut down Performance Scorecard.

2 From <Web application server>\webapps\HPSWebReports\WEB-INF, open web.xml.

3 Modify the default value of 30 (minutes) in the code below as needed to increase the session time-out.

<session-config> <session-timeout>30</session-timeout></session-config>

Note: If you extend this value beyond 60, and have enabled Performance Scorecard for single sign-on and external authentication, you must also modify the HyperionCSS.xml file in <Web application server>\webapps\HPSWebReports\WEB-INF\config.

4 Modify the default value of 60 (minutes) in the code as required to increase or decrease the timeout token:

<token><timeout>60</timeout></token>


6 Restart the Web application server and Performance Scorecard.

Increasing Startup SpeedYou can increase the startup speed for Performance Scorecard by modifying the Database Connection Pool setting in the main configuration file.

➤ To increase the start up speed:



3 Add the following code to the Database Connection Pool Setting section of the file:

hyperion.hps.main_data_store.pool.max_active=10hyperion.hps.main_data_store.pool.when_exhausted_action=2hyperion.hps.main_data_store.pool.max_wait=30000hyperion.hps.main_data_store.pool.max_idle=5hyperion.hps.main_data_store.pool.connection_cleanup_sleep_ time=60000hyperion.hps.main_data_store.pool.connection_timeout=900000hyperion.hps.main_data_store.pool.valid_connection_select=null="true"

Allocating Physical Memory 233


5 Restart the Web application server.


Increase Data Caching LimitsYou can increase data caching limits to improve the performance of Performance Scorecard.

➤ To increase data caching limits:



3 Modify the value of the hyperion.hps.formula. value-caching_limits up to a value of 1000000 to increase caching limits.


5 Restart the Web application server.


Allocating Physical MemoryYou can improve performance by allocating more physical memory to the Web application server. Refer to the appropriate section for your Web server type for detailed instructions:

● “For IBM WebSphere 5.0.1:” on page 233

● “For BEA WebLogic:” on page 233

● “For Apache Tomcat:” on page 234

➤ For IBM WebSphere 5.0.1:

1 In the WebSphere Administration Console, expand Servers in the left frame and click Application Servers.

2 In the right frame, select the server to be configured.

3 Click Process Definition and then Java Virtual Machine on the page that is displayed.

4 On the Configuration tab, scroll down to Maximum Heap Size and increase the setting as required.

5 Save your changes.

6 Restart WebSphere.

➤ For BEA WebLogic:

1 In any text editor, open startHps.bat.

By default, this file is located in <Web application server>\webreportsDomain.


2 Locate the following line of code, that contains the default memory settings:

set JAVA_OPTIONS=-server -Xms256m -Xmx1024m

3 Change 256 in this line of code to increase the available memory when WebLogic starts up.

4 Change 1024 in this line of code to reflect the increased amount of memory required.

Note: Hyperion recommends allotting physical memory minus 256 Mb for the operating system if the server is running only WebLogic. For example, a server with 1024 Mb, maximum memory allocation (the second number in the code string) should be no more than 768 Mb.


6 Restart WebLogic.

➤ For Apache Tomcat:

1 In any text editor, open startHPS.bat.

By default, this file is located in <Web application server>\webreportsDomain\bin.

2 Locate the following line of code which contains the default memory settings:

set CATALINA_OPTS=-server -Xms256m -Xmx1024M

3 Change 256 in this line of code to increase the available memory when WebLogic starts up.

4 Change 1024 in this line of code to reflect the increased amount of memory required.


6 Restart Tomcat.

Tuning Garbage Collection for Sun JVMIf you are using Sun JVM, you can improve performance by tuning the Garbage Collection (GC) parameters of the Web application server. Refer to the appropriate section for your Web server type for detailed instructions:

● “For BEA WebLogic:” on page 235

● “For Apache Tomcat:” on page 235

Tuning Garbage Collection for Sun JVM 235

➤ For BEA WebLogic:




set JAVA_OPTIONS=-server -Xms256m -Xmx1024m

3 Append the following parameters to the end of the line:

<Original line> -XX:NewSize=128m -XX:MaxNewSize=128m -XX:SurvivorRatio=16

Note: You can adjust these parameters and find the numbers that are best suited to your application.


5 Restart WebLogic.

➤ For Apache Tomcat:




set CATALINA_OPTS=-server –Xms256m -Xmx1024M

3 Append the following parameters to the end of the line:

<Original line> -XX:NewSize=128m -XX:MaxNewSize=128m -XX:SurvivorRatio=16

Note: You can adjust these parameters and find the numbers that are best suited to your application.


5 Restart WebLogic.


Glossary 237

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

Glossary

accountability map. A visual, hierarchical representation

of the responsibility, reporting, and dependency structure

of your organization. An Accountability map depicts how

each accountability team in your organization interacts to

achieve strategic goals. An accountability team is also

known as a critical business area (team, department, office,

and so on).

accountability element or team Usually used on an

Accountability map, the accountability element represents

the individuals or groups responsible for performing

specific tasks or taking ownership of specific strategy

elements.

action. A task or group of tasks executed to achieve one

or more strategic objectives. In a Performance Scorecard

application, each action box represents an activity or task

that helps to accomplish a strategic objective. Each action

is usually assigned measures.

admin security role. One of three default security roles

provided with the application. The admin security role

enables users to whose account it is applied to perform

administrative tasks such as creating domains, managing

user accounts, generating an Analytic Services database,

monitoring alert activity, enabling external authentication,

and using Shared Services.

administrator. A component of Performance Scorecard

that enables administrative users to perform tasks such as

managing user accounts, creating domains, promoting

application data, and tracking changes made to application

business objects.

alert. Object to which you subscribe to receive e-mail

notification when performance for business objects

departs from a defined acceptable range. Alerts can also be

created to prompt subscribers when application-building

tasks, such as measure result collection or initiative

completion, are approaching or past their specified

completion date.

alias. An alternative name that can be used for a member

or dimension in an Analytic Services outline. An alias is

often a more easily identifiable product name or product

description for a column in your application database.

Audit Report. An administrative feature that contains a

record of all modifications made to the application and

application components. Use the report to access

information about which applications or application

components have been modified, when, and by whom.

Balanced Scorecard®. A framework that emphasizes the

role of your organization’s strategy and the achievement of

strategic goals based on the use of financial, customer,

internal, and learning and growth perspectives.

business area. See critical business area (CBA). or

accountability element or team.

business object. Any application component, such as a

scorecard, measure, employee, variable, or framework.

Changes to business objects are tracked using the Audit

report.

cascading scorecard. A scorecard that uses the scores of

other, lower-level scorecards. For example, if you are

building a scorecard for an element or employee that is

responsible for, or whose performance should be affected

by a lower-level scorecard score, you can add the lower-

level scorecard to the scorecard you are building.

238 Glossary


cause and effect map. Depicts how the elements that

form your corporate strategy are interrelated and how they

work together to meet your organization’s strategic goals.

A Cause and Effect map tab is automatically created for

each of your Strategy maps.

child. An application component that is directly

connected to another (parent) component as seen on

Strategy maps, Accountability maps, and with scorecards.

collection extension. An additional number of days that

increase a measure’s frequency, during which a measure’s

result collector can enter or modify measure results before

the measure is locked. For example, for a measure with an

expected collection date of May 26th, giving a collection

extension of 3 days means that result collectors for the

measure have until May 29th to enter or modify result

values. After this date, May 30th and onward, the measure

is locked.

collection frequency. Generates a list of expected measure

result collection dates. For example, to collect measure

data twice a year, specify a collection frequency of semi-

annually. If the dates calculated by this frequency elapse

without a result being entered, and a collection extension

for the measure is not given, the measure becomes locked

and result collectors cannot enter result data.

comparator. Also called a target, a comparator is a

specific result value which a measure is expected or

anticipated to collect in a specific period of time. Use

multiple measure comparators to assess measure results

against a variety of internal or external values. For

example, you may want to establish a short and a long

term comparator for a measure.Comparator values are

entered using Performance Scorecard’s reports.

composite measure. A measure that uses other measure

result data to calculate its results. For example, employee

productivity can be expressed as a composite measure

because it can be assessed by examining: hours worked by

employee, quantity of employee work, and quality of

employee work.

critical business area (CBA). Also called accountability

team or business area, a CBA is an individual or a group

organized into a division, region, plant, cost center, profit

center, project team, or process.

critical success factor. (CSF) A capability that must be

established and sustained to achieve a strategic objective. A

CSF is owned by a strategic objective or a critical process

and is a parent to one or more actions.

designer security role. One of three default security role

provided, this role enables users to whose account it is

applied to build and modify business objects using the

object view.

designer. Security role assigned to users and employees

who build and modify applications and scorecards using

the Designer work area. A designer user account is also

provided with the product that can be used to log on and

use Performance Scorecard before specific user accounts

have been created.

dimension. Describes the type of measure data collected

by the application. Dimensions are used to identify data

groups. For example, the dimension Geography could

contain North America, Europe, and Australia.

dimensional measure. A measure to which dimensional

information is assigned. A dimension lets you group and

analyze measure logically.

dimension measure template. Template with one or more

associated dimensions that is a used to create dimensional

measures. Associating a dimension with a Dimension

Measure Template automatically creates a dimension

measure for each dimension member within the associated

dimension.

domain. Object defined by an administrator that

represents a functionally or geographically distinct

business area, such as a regional office, or a department

within an organization. Most business objects, such as

measures, employees, and scorecards are assigned to a

domain. For example, scorecards assessing employee

productivity may belong to the Human Resources domain.

employee. Users responsible for, or associated with,

specific business objects. Employees are also individuals

using Performance Scorecard that may not necessary work

for an organization, such as an analyst or consultant. An

employee must be associated with a user account for

authorization purposes.

employee profile report. Provides detailed information

about each employee in your application, including the

employee’s scorecard and responsibilities.

Glossary 239


equalize. A scorecard building feature that enables users

to assign the same weighting to all measures on a

scorecard.

external authentication. Process by which users are

authorized at logon using an external authentication

provider such as LDAP or NTLM.

external data source. An existing data source, such as

Analytic Services or Enterprise Metrics, that resides

outside of the Performance Scorecard application. The

data from this external source can be used to populate a

Performance Scorecard model with metadata and data.

framework. A methodology that facilitates a disciplined

approach to translate performance strategy into action.

Frameworks identify areas that are critical to the

achievement of organizational goals and performance

targets and outline how they must act to achieve the

mission and vision of the organization. Often called “The

pillars of success”. Commonly used frameworks include

Balanced Scorecard, Malcolm Baldridge, and Andersen

Value Dynamics.

frequency. Determines when, how often, and the latest

possible date on which measure results must be collected.

See collection frequency. and result frequency.

Hyperion Shared Services. Application enabling users to

share data between supported Hyperion products by

publishing data to Shared Services and running data

integrations.

initiative. A task or group of tasks that an organization

executes to achieve one or more strategic objectives. In a

Performance Scorecard application, each action box

represents an activity or task that helps to accomplish a

strategic objective. See action.

initiative status report. Lists the strategy and

accountability elements to which initiatives are attached

and the individuals or groups who are responsible for

carrying them out. The Initiatives Status report also

identifies the status, priority, and assigned completion date

of each initiative.

integration. Process that is run to move data between

Hyperion applications using Hyperion Shared Services.

Data integration definitions specify the data moving

between a source project and a destination project, and

enable the data movements to be grouped, ordered, and

scheduled.

Locked Business Object Report. Identifies and unlocks

business objects such as measures, targets, and reports that

are locked because they are being modified or have become

frozen.

measure. Objective, quantifiable data that indicates the

level of progress toward a performance target. Measure

results can be scalable (fall within a range of values) or

absolute. Measures are associated with strategy elements

and accountability teams.

measure performance report. Any application

component, such as a scorecard, measure, employee,

variable, or framework. Changes to business objects are

tracked using the Audit report that provides detailed

information about each measure.

member. Dimension members describe the individual

measures that can be categorized and analyzed by a

dimension. For example, the dimension Geography could

have North America, Europe, and Australia as its measure

members. Although members are created for dimensions,

you can create submembers for other members.

metadata. High level data describing or categorizing

lower-level data. For example, in Any application

component, such as a scorecard, measure, employee,

variable, or framework. Changes to business objects are

tracked using the Audit report a business object type such

as measure or employee is considered metadata, the name

of the measure, its result value, or the name of the

employee is considered data. Administrators map

metadata between Hyperion applications to ensure the

correct information is imported or exported to Hyperion

Shared Services.

mission. A statement that defines the immediate, key

business goals of the accountability teams or critical

business areas that form the structure of that organization.

multidimensional database. Multidimensional databases

examine data from several categories of data called

dimensions. Dimensions are subdivided into smaller

components called members. Multiple views of data sets

are supported.

normalize. This feature is a scorecard building option

that can be used if a scorecard’s weight must add to 100,

but users want to retain the different weighting ratio for

each measure and perspective on the scorecard.

240 Glossary


owner. The individual or group responsible for a strategy

element.

parent. An application component, such as an Entity or

strategic objective that has one or more application

components below it on a map that are directly connected

to it. These components are called its children. Scorecards

can also be parents if lower-level scorecards are attached to

them.

perspective. A category used to group measures on a

scorecard or strategic objectives within an application. A

perspective can represent a key stakeholder (such as a

customer, employee, or shareholder/financial) or a key

competency area (such as time, cost, or quality). A

measure is always associated with at least one perspective

but can also have a secondary perspective. A secondary

perspective is a perspective that is also effected by an object

but not as profoundly as a primary perspective

performance indicator. Also called status symbol,

performance indicators are image files used to represent

measure and scorecard performance based on a range you

specify. You can use the default performance indicators

provided or create an unlimited number of your own.

permission. Security role setting that defines a user’s

access to scorecards and measures.

pinned dimension. When working with external data

sources, pinned dimensions have a static value, such as a

currency or version number. These dimensions do not

need to be imported into Performance Scorecard, but may

be required to provide perspective to data queries.

primary measure. Primary measures are high priority

measures that are more important to your company and

business needs than many other measures. Primary

measures are displayed in the Contents frame and have

Performance reports.

promotion. Means of transferring application data to a

different environment or database server. Promotion is

essentially the replication of application data from one

environment such as development to another environment

such as production.

range. Scale or formula used to interpret measure results

and determine what performance indicators are displayed.

Each range is attached to a performance indicator and you

must specify the range for each performance indicator. For

example, to have the green performance indicator display

when measure results are higher than 90 but less than 100,

enter a range of 90 <x <100.

restriction. Means of denying access to specific measures,

scorecards, and web pages. Restrictions are applied to

security roles which are applied to user accounts.

result. Results are the values that the application collects

for measures. If you have the required permissions, you

can use the Result Collection report to enter or modify

measure results.

result formula. A measure’s result formula determines

how measure result data is calculated and assessed. For

example a result formula for the measure Net Income

could be: ((mResult(“Net Sales”) - mResult(“Cost of

Sales”)) - mResult(“Operating Expenses”).

result frequency. The algorithm used to create a set of

dates for the collection of data (collection frequency) or

the display of data (result frequency). The result

frequency's algorithm is defined by Major type (for

example, weekly, monthly, and so on), Minor type (for

example, first, last, last Friday, 5th day of period, and so

on) and Interval (for example, every one, every two, every

5, and so on).

result date. Day on which Performance Scorecard collects

a measure result value as determined by a measure’s

frequency, for use in reports collects a measure result value

as determined by a measure’s frequency, for use in reports

collects a measure result value as determined by a

measure’s frequency, for use in reports.

score. Indicates the level at which specified targets are

being achieved. It is usually expressed as a percentage of

the target for a given time period.

scorecard. Business Object used to represent the progress

of an employee, strategy element, or accountability

element toward specific goals. Scorecards ascertain this

progress based on the data collected for each measure and

child scorecard you add to the scorecard.

scorecard report. Presents the results and detailed

information about scorecards attached to employees,

strategy elements, and accountability elements.

Glossary 241


scoring formula. A score formula for a measure

determines how the measure’s results will be assessed to

produce a final measure score.

secondary measure. Secondary measures are low priority

measures that are less important to you than primary

measures. Secondary measures do not have Performance

reports but can be used on scorecards and to create

Dimension Measure Templates.

security role. Assigned to user accounts, security roles are

used to restrict or control access to scorecards, measures,

and Web pages. You can assign more than one security role

to a user account and create new security roles.

Shared Services. Application enabling users to share data

between supported Hyperion products by publishing data

to Shared Services and running data integrations.

Stern Stewart’s EVA Framework. Framework reputed to

capture the true economic profit of an organization by

calculating the net operating profit minus an appropriate

charge for the opportunity cost of all capital invested in an

enterprise. This framework is meant to provide the most

accurate measure of corporate performance over any given

time.

strategic objective (SO). A long-term goal defined for an

organization that is stated in concrete terms whose

progress is determined by measuring results. Each strategic

objective is associated with one perspective in your

application, has one parent, the entity, and is a parent to

critical success factors or other strategic objectives. It also

has measures associated with it.

strategic theme. High-level categories of strategy you can

use to group lower-level strategy elements on Cause and

Effect maps.

trend graph. Depicts measure performance by a date

range that you specify.

user. Any person interacting with Performance Scorecard

or any employee in an application. Users must have at least

one account with which an employee is associated to

authorize access to business objects. A default user account

is provided with the product.

user security role. One of three default security roles

provided with the product, the assigned role grants access

to Performance Scorecard reports and alerts.

variable. A value that changes due to external influences

that is used in composite measure calculations. Examples

of variables are inflation rate and currency exchange rates.

vision. Definition created by a business or organization of

its goals and business strategies.

242 Glossary

Index A 243


Index

Aaccess permissions

Shared Services, 52

accessibility, 222

Accountability team/element

definition, 238

administrator (admin)

modify security role, 41

overview, 15

security role, 23

tasks, 16

Web page restrictions, 40

Alerter

Alerter Process Report, 181

customizing, 219


Alerter Process Report, 181

alerts

overview, 181

Analysis View


Analytic Services

customizing databases, 94

data writable, 102

external data sources, 101

generate multidimensional database, 81

naming conventions, 85, 89

Other dimensions, 102

pinned dimensions, 102

prerequisites

prerequisites, 88

retrieving results, 93

retrieving results in Excel, 93

setting the date range, 90

time dimensions, 102

application data

promoting to another environment, 117

application management. See Shared Services applications.

attachments

backing up, 124

restore, 124

Audit Report, 209

using, 209

authorization

priorities, 24

priority rules, 24

auto-expandable spaces, 85

Bbackup notes and attachments, 124

BQY file, 184

BQY reports

importing, 193

Scorecard, 187

Scorecard with Measure Trends, 188

Strategy Dashboard, 189

bulk provisioning, 65, 71

business objects

non-promotable, 118

Ccascading style sheets, 220

available style sheets, 222

Child, definition, 238

client.css, 222

commands

Help menu, xii

configuration

244 Index D


external authentication, 21

consulting services, xiv

Critical Success Factor

definition, 238

CSS.xml

samples, 51

custom mappings, 94

custom password syntax, 47

custom properties

Alerter, 219

allocating physical memory, 233

increasing data caching limits, 233

increasing session timeout, 232

increasing startup speed, 232

Performance Scorecard, 216

tuning garbage collection, 234

user interface, 220

custom reports

viewing generated reports, 200

Ddata caching limits, 233

data integration, 128

definition, 128

data integrations. See Shared Services data integrations.

data writable option, 102

data, promoting to another environment, 117

database schema

auto-expandable spaces, 85

date range, 90

default security roles, 31

designer


security role, 23


dimensional hierarchy, 126

dimensional measures

definition, 238

dimensions


documentation

accessing, xi

conventions, xiii

feedback, xiv

domains, 24

creating, 26

deleting, 29

explicit access, 25

implicit access, 25

modifying, 28

parent, 25

promotion, 117

setting access, 25

Eeducation services, xiv

e-mail address

format, 50

employee scorecards

removing links, 41

employees

assigning to a user account, 45

authorization

authorization

employees, 24

automatically generating user accounts, 49

removing links from scorecards, 41

Enterprise Metrics


Entity, definition, 238

explicit access, 25

export, 126

external applications

profiles, 118

promoting application data to, 119

external authentication

configuration, 21


Fformat

e-mail address, 50

formulas

result, definition, 240

score, 241

frequency

definition, 239

Index G 245


Ggarbage collection for Sun JVM, 234

global.css, 222

groups

create using Shared Services, 61

modify using Shared Services, 68

provision using Shared Services, 64

provisioning using Shared Services, 51

HHelp Menu commands, xii

HPS_AUDIT_TRAIL, 117

HPS_STAR_DIM_, 85

HPS_STAR_DIM_TIME, 83

HPS_STAR_FACT, 82

HPS_STAR_MEASURES, 84

HPS_STAR_SCORECARDS, 84

HPS_STAR_STATUS_SYMBOL, 83

Hyperion

Consulting Services, xiv

Education Services, xiv

product information, xiv

support, xiv

Technical Support, xiv

Hyperion Download Center

accessing documentation, xi

Hyperion Essbase. See Analytic Services, 93

Hyperion Hub applications. See Shared Services applications.

Hyperion Hub data integrations. See Shared Services data integrations.

Hyperion Hub models. See Shared Services models.

Hyperion Intelligence

Smart Cuts URLs, 185

Hyperion Performance Scorecard

customizing, 216

Iimplicit access, 25

import, 126

importing models. See Shared Services models.

integrating data. See Shared Services data integrations.

Intelligence Reports

Smart Cuts URLs, 185

Interactive Reporting

generating reports, 193

reports, 191

integrations, 183

overview, 184

reports, 183

Interactive Reports


Llinks

removing, 41

Locked Business Object Report

about, 208

using, 208

Locked Business Objects Report, 208

Mmeasures

assigning permissions, 38

memory


Microsft Excel

retrieving Analytic Services results, 93

migrating application data, 117

migration

application data, 117

model management. See Shared Services models.

models

private, 130

shared, 130

multidimensional database, 81

multidimensional databases

customizing databases, 94

Nnaming conventions, 85, 89

nondimensional objects, 126

non-promotable business objects, 118

notes

backing up, 124

restore, 124

246 Index O


OOpen Catalog Extension (.oce) file, 184, 191

creating, 191

importing, 193

other dimensions, 102

owner

definition, 240

Pparent domain, 25

parent, definition, 240

password syntax, 47

passwords

syntax, 45

Performance Scorecard


data caching limits, 233

startup speed, 232


user roles, 31

permission

priority rules, 24

permissions

applying to security roles, 32

assigning, 34

assigning to measures, 38

domains, 25

measures, 39

scorecard, 35

Shared Services, 52

Web pages, 39

personal alerts, 181

physical memory, 233

pinned dimensions, 102

prerequisites


generating user accounts, 49

Interactive Reports, 191

promoting application data to another environment, 119

priority rules for authorization, 24

private applications. See Shared Services applications.

private models, 130

productContent.css, 222

profiles

external applications, 118

promoting data

about, 184

before, 119


overview, 118

requirements, 119

promotion, 117


promotions

prequisites, 119

properties

customizing Alerter, 219

customizing Performance Scorecard, 216

customizing user interface, 220

provision users

Shared Services, 55

provision users through Shared Services, 60

public alerts, 181

Rrelational database, 81

Reports

Audit, 209

reports

Alerter Process, 181

Audit Report, 209

customized, 183

default generated reports, 186

Interactive Reporting, 183

Locked Business Objects, 208

Scorecard, 187

Scorecard Report, 186

Scorecard with Measure Trends, 186, 188

Smart Cuts, 185

Stragey Dashboard, 189

Strategy Dashboard, 186

User Session, 211


restore notes and attachments, 124

restrictions

links to scorecards, 41

result collection


retrieving results, 93

Index S 247


Ssample configurations, 51

Scorecard Report, 186 to 187

Scorecard with Measure Trends, 186

Scorecard with Measure Trends Report, 188

Scorecard.bqy, 187

Scorecard_withTrend.bqy, 188

scorecards

removing links, 41

security role

assigning access to Web pages, 39

deprovision user, 60

security roles

applying permissions, 32


creating, 32

customized, 32

default, 31

deleting, 42

editing, 41

modifying, 41

overview, 23

setup, 34

session timeout, 232

shared models, 130

shared models. See Shared Services models.

Shared Services

access permissions, 52

bulk provisioning, 65, 71

create groups, 61

creating a new user, 53

data integration definition, 128

deprovisioning users or groups, 60

migration of multiple users, 73

modify groups, 68

provision groups, 64

provisioning users, 55

provisioning users and groups, 51

user provisioning, 52

user roles, 31


Shared Services applications

common shared application, 130

creating, 130

deleting, 132

naming restrictions, 132

overview, 129

overview of private applications, 129

overview of shared applications, 129

process for sharing, 129

sharing, 132

stopping sharing, 133

Shared Services data integrations

accessing, 160

accessing functions, 161

assigning access, 128, 161

Create Integrations user role, 128

creating, 163

deleting, 169

described, 128

editing, 163

filtering integration lists, 162

overview, 160

prerequisites, 160

Run Integrations user role, 128

scheduling group integrations, 176

user roles, 128

viewing integrations, 161

Shared Services models

access permissions, 154

application system members, 145


compare operations, 140

comparing, 139

configuring for external authentication, 126

deleting, 146

deleting permissions, 158

described, 126

dimensional hierarchies, 126

editing content, 141

editing member properties, 143

editing permissions, 157

filtering content, 149

Manage Models user role, 127

managing permissions, 153

naming restrictions, 139

non-dimensional hierarchies, 126

overview, 126

permissions, 153 to 154

248 Index T


private, 130

properties, viewing and setting, 159

registering applications, 127

renaming, 146

setting properties, 159

shared, 130

shared applications, 128

sharing, 132, 147

sharing data, 128

sharing metadata, 128

sync operations, 137

synchronizing, 135

system members, 145

tracking version history, 151

types of permission, 154

user authentication, 153

user roles, 127

versioning, 151

viewing, 133

viewing properties, 159

Smart Cuts, 185

Star Schema, 81

HPS_STAR_DIM_, 85


HPS_STAR_FACT, 82




naming conventions, 85

prerequisites

prerequisites

generating Star Schema tables, 85

star schema

HPS_STAR_DIM, 85





startup speed, 232

Strategic Objective

definition, 241

Strategic Themes

adding to framework, 241

definition, 241

Strategy Dashboard, 186, 189

StrategyDashboard.bqy, 189

SunJVM


Ttechnical support, xiv

themes

modifying the user interface, 221

time dimensions, 102

timeout token, 232

UUI themes, 221

unlocking business objects, 208

URLs

Smart Cuts, 185

user

authorization, 24

create using Shared Services, 53


provision through Shared Services, 55

security role, 23

user accounts, 43

creating, 43

deleting, 48

editing, 47

e-mail address format, 50

generating automatically, 49

generating multiple accounts, 50

modifying, 47

user interface

cascading style sheets, 220

customize, 220

modifying UI themes, 221

user provisioning

deprovisioning user or group, 60

multiple groups, 65

Shared Services, 52

User Session Report, 211

users

assigning to a user account, 45

migrate multiple users, 73

provision multiple users, 71

provisioning using Shared Services, 51

Index V 249


Vversioning. See Shared Services models.

WWeb pages

assigning access, 39

remove links to scorecards, 41

restricting access, 39

XXML

sample configurations, 51

250 Index X

Documents

Hyperion System 9 Performance Scorecard 9.2 Administrator ...“Managing User Accounts and Authorization” on page 21 describes the default security used by Performance Scorecard