Vous êtes sur la page 1sur 392

BusinessObjects XI R1/R2:

 

Universe Design

   
   
   

Instructor's

Guide

DM310R2

Copyright

Patents

Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352.

Trademarks

Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of

Business Objects SA or its affiliated companies

in the United States

and other countries. All other names mentioned herein may be trademarks of their respective owners. Product specifications and program conditions are subject to change without notice.

Copyright

Copyright © 2005 Business Objects SA. All rights reserved.

c

o

N

T

E

About this Course

N

.T

s

Course objectives

 

xvi

Course audience

xvi

Prerequisite

education

xvi

Prerequisite

knowledge/experience

xvi

Course success

factors

 

xvii

Training facility setup

xvii

Course materials

xvii

Learning

process

xviii

Recommended

education

 

xix

Facilities Setup

 

Introduction

xxii

Facilities

Setup

xxii

Setting up for the activities

 

xxiv

Before class begins

v-xxiv

Getting Help

xxxii

Lesson 1

 

Understanding

BusinessObjects

Universes

Understanding

BusinessObjects

universes

 

1-2

Introduction

1-2

What is a universe?

1-2

Universes

Classes

are used to query the database

 

1-2

and objects

1-3

How universes

are used

 

1-3

Advantages

of a universe

1-3

Metadata

and the semantic

layer

1-4

BusinessObjects

Universe

Designer

components

1-5

Using the Quick Design Wizard

1-7

Using Designer

module commands

1-8

Saving and exporting

a universe

1-11

Opening,

importing,

and exporting

universes

1-11

Importing

a universe

1-11

Giving all users access to a universe

1-13

Activity:

Viewing

a universe

in Designer

 

1-14

Copyright

© 2005 Business

Objects.

All rights reserved.

iii

Using the Universe

Development

Development

Cycle

1-15

The Universe

Cycle

1-15

Activity:

Plan a universe

1-17

Lesson

summary

1-18

Quiz: Understanding

BusinessObjects

Universes

 

1-18

Lesson 2

 

Creating the Course Universe

 

and universe

 

2-2

The course database Introduction

 

2-2

Course

database

description

2-2

Assumptions

2-2

Analysis

of reporting

requirements

 

2-3

Development

plan

 

2-4

Creating

the universe

2-5

Introduction

 

2-5

Defining

universe

parameters

2-5

Setting the database

connection

 

2-6

Viewing

available

connections

 

2-12

Universe

parameters

2-13

Universe

Parameters

dialog box

 

2-13

Summary

tab

 

2-14

Strategies

tab

2-15

Controls

tab

2-16

SQL tab

2-17

Links tab

2-18

Parameters

tab

2-19

Lesson

summary

2-21

Quiz: Creating the Course Universe

 

2-21

Lesson 3

 

Building

the Universe Structure

 

Populating

the universe

structure

3-2

Designing

Schema

a schema

creation

 

3-2

design and the universe

process

3-3

Adding

Viewing

tables

3-4

data from the Table Browser

3-5

Organizing

your tables

 

3-7

Changing

table display

3-7

Viewing

table values

3-7

Activity:

Building

the universe structure

 

3-9

Defining joins in a universe

3-10

About joins and SQL Where clauses

3-10

Creating joins

 

_

3-11

Tracing joins manually

in the schema

 

3-11

Creating

the join by defining properties

3-12

Editing the join expression

 

3-14

Detecting

joins

3-16

Setting join cardinalities

3-17

About cardinality

3-17

Detecting

cardinality

automatically

 

3-21

iv

Universe

Design-instructor's

Guide

Best practice for setting join cardinality

 

3-23

Join types

3-24

Equi-joins

3-25

Outer joins

3-26

Theta joins

3-27

Shortcut joins

3-28

Self-restricting

joins

3-28

Using List Mode

3-29

Checking

3-30

Activity:

integrity Building the universe

structure

3-32

Lesson summary

Structure

 

3-34

Quiz: Building the Universe

3-34

Lesson 4

 

Creating

Dimension

Obj eets

 

Objects

and classes

4-2

Introduction

 

4-2

Objects

4-2

Classes

4-4

Creating

classes

and objects

4-5

Introduction

 

4-5

Creating

classes

4-5

Creating

an object

4-6

Defining

a new object as a detail object

4-7

Creating

classes or objects

by dragging tables or columns

4-8

Working

with classes and sub-classes

 

4-10

Editing the object properties

4-11

Copying

and pasting objects

4-18

Find and replace

4-18

Checking

integrity

4-20

Viewing

parent tables

4-20

Testing

4-21

Activity:

objects Creating and testing

classes and objects

4-22

Objectives:

 

4-22

Lesson summary

4-27

Quiz: Creating

Dimension

Objects

4-27

Lesson 5

 

Creating

Measure

Obj eets

 

What are measure

objects?

 

5-2

Defining

measure objects

5-2

Levels of aggregation

5-3

Creating

measure

objects

5-7

Creating

measure objects

 

5-7

Testing

measure

objects

5-8

Activity:

Create and test measure

objects

5-10

Lesson summary

5-12

Quiz: Creating

Measure

Objects

5-12

Table of Contents-instructor's

Guide

v

vi

Lesson

6

Using Lists of Values

Creating

a list of values

6-2

What is a List of Values?

 

6-2

Using a LOV

 

6-2

Working

with LOVs in Designer

 

6-5

Creating

a cascading

LOV

6-13

Setting

up a cascading

LOV

6-13

Using the cascading

LOV in Web Intelligence

6-15

Activity:

Using LOV

6-17

Lesson

Summary

6-18

Quiz: Using Lists of Values

 

6-18

Lesson

7

Resolving

Loops in a Universe

 

Understanding

loops

 

7-2

Introduction

7-2

Recogni~ng~ops

7-2

Problems caused by loops

 

7-3

Loops in a universe

schema

and not in the database

7-3

What is the loop doing?

7-3

Resolving

loops

 

7-4

How Designer

deals with loops

 

7-4

Resolving

loops using aliases

7-5

Introduction

 

7-5

About aliases

7-5

Detecting

loops and inserting

aliases

7-6

Inserting an alias manually

7-9

Redefining

objects

 

7-9

Listing and renaming

aliases

7-10

Choosing

which alias method to use

7-10

Resolving

self-join

loops using aliases

7-11

Resolving

loops using shortcut joins

 

7-14

Introduction

 

7-14

Using a shortcut join

7-14

Activity:

Resolving

loops with aliases

7-16

Resolving

loops using contexts

 

7-18

Introduction

 

7-18

About contexts

7-18

Detecting

and creating

contexts

7-22

Creating

objects for each context

 

7-25

Editing a context

 

7-25

Testing

contexts

7-27

Updating

contexts

7-29

Activity:

Resolving

loops using contexts

7-30

   

7-33

Lesson summary Quiz: Resolving

Loops in a Universe

7-33

 

Universe Design-instructor's

Guide

Lesson 8

Resolving

SQL Traps

Understanding

SQL traps and universes

8-2

Resolving

chasm traps

8-3

Chasm traps

8-3

Detecting

chasm traps

8-4

The Chasm trap scenario

8-4

Resolving

chasm traps

8-6

Using multiple

SQL statements

for each measure

to resolve chasm traps

8-7

Using

contexts to resolve

chasm traps

8-10

Activity:

Resolving

chams traps

8-11

Resolving

fan traps

8-14

Fan traps

8-14

Detecting

fan traps

8-15

The fan trap scenario

8-15

Resolving

fan traps

8-17

Using aliases and contexts

to resolve fan traps

 

8-18

Another

solution

using aliases and contexts

8-21

Avoiding

fan traps

altogether

8-23

Activity:

Resolving

fan traps

8-24

Lesson summary

SQL Traps

8-27

Quiz: Resolving

8-27

Lesson 9

Applying

Restrictions

on Objects

Restricting

the data returned

by objects

9-2

Defining data restrictions

9-2

Methods

Applying

Applying

of restricting

restrictions

restrictions

data in Web Intelligence

 

9-4

to objects

9-5

to objects

9-5

An alternative

to applying

restrictions

to objects

9-7

Applying

restrictions

using condition objects

 

9-9

Restrictions

using condition

objects

9-9

Applying

Applying

restrictions

restrictions

to tables

 

9-11

using the tables button

9-12

Applying

each type of restriction

9-14

Activity:

Applying

restrictions

9-15

Lesson

Summary

9-17

Quiz: Applying

Restrictions

on Objects

9-17

Table of Contents-Instructor's

Guide

vii

Lesson 10

Using Functions with Objects

Using @ Functions

10-2

Defining

@Functions

10-2

@Prompt

10-3

@Prompt

syntax

10-3

@Select

10-5

 

@Where

10-7

Activity:

Using @Functions

10-10

Lesson Summary

with Objects

10-12

Quiz: Using Functions

10-12

Lesson 11

Using Hierarchies

 

Understanding

hierarchies

and universes

11-2

Hierarchies

11-2

Natural hierarchies

11-3

Logical hierarchies

11-3

Working with hierarchies

11-4

Default hierarchies

11-4

Viewing

default hierarchies

11-5

Creating

custom

hierarchies

11-8

Creating

a custom

hierarchy

11-9

The effect of custom hierarchies

on default hierarchies

11-10

Editing types of hierarchies

11-12

Time hierarchies

11-13

Creating

time hierarchies

11-13

Time hierarchies

based on database

functions

11-17

Table-based

time hierarchies

11-19

Activity:

Using hierarchies

11-21

Lesson summary

11-23

Quiz: Using Hierarchies

11-23

Lesson 12

Aggregate Awareness

 

Understanding

aggregate

awareness

and universes

12-2

What is Aggregate

Awareness?

12-2

 

Summary

Tables

12-3

Summary

Tables and SQL

12-4

Applying

aggregate

awareness

to objects

12-5

Setting

up Aggregate

Awareness

12-5

Step 1: Insert a summary

_ table and set joins cardinality

12-5

Step

2: Set the contexts

12-6

Step 3: Redefine the objects

12-7

Step

4: Define incompatible

objects

12-9

Using aggregate

awareness

_ to resolve fan traps

12-12

Testing

aggregate

awareness

12-13

Activity:

Aggregate

awareness

12-14

Lesson summary

Awareness

12-16

Quiz: Aggregate

12-16

viii

Universe

Design-instructor's

Guide

Lesson 13

Derived Tables and Indexes

Using derived

tables

13-2

What is a derived table?

13-2

 

Advantages

of using derived tables

13-2

Adding

derived

tables

13-3

Activity:

Derived tables

13-6

Applying

index awareness

13-7

What is index awareness?

13-7

Setting

up index awareness

13-8

Activity:

Index awareness

13-12

Lesson summary

13-13

Quiz: Derived

Tables and Indexes

13-13

Lesson 14

Linking Universes

 

Understanding

linked universes

14-2

What are linked universes?

14-2

Using linked universes

14-3

 

Possible

linking strategies

14-3

Advantages

and limitations

to linking

14-4

Creating

links between

universes

14-5

Linking universes

structure

14-5

Editing the derived

14-7

 

Including

one universe within another

14-8

When to link and when to include?

14-10

Activity:

Linking universes

14-11

Lesson summary

14-12

Quiz: Linking

Universes

14-12

Lesson 15

Securing Universes

 

Setting access

restrictions

on a universe

15-2

About security

and universes

15-2

What is a restriction

set?

15-2

 

Creating

a restriction

15-4

Applying

a restriction

set to users

15-14

Setting

restriction

group priority

15-17

Viewing

user and group

restrictions

15-18

Activity:

Setting access restrictions

15-19

Lesson summary

15-20

Quiz: Securing

Universes

15-20

Table of Contents-instructor's

Guide

ix

Lesson 16

Managing

Universes

 

Documenting

universes

 

16-2

Printing

universe

details

16-2

Printing

options:

General

section

16-4

Printing

options:

List components

section

16-4

Printing

options:

Full description

section

16-5

Deploying

universes

16-6

About deploying

a universe

 

16-6

How do other users access the universe?

16-6

What happens

when you export a universe

16-7

Exporting

a universe

16-10

Importing

a universe

16-11

Working

with multiple

designers

16-13

Understanding

version control

16-13

Locking

a universe

16-14

Maintaining

universes

16-15

Reasons

for universe

maintenance

 

16-15

Changes

to the target database

16-15

Adding

new tables to an existing

universe

16-18

The effect of changing

objects

 

16-18

Activity:

Managing

universes

16-20

Lesson

Summary

16-21

Quiz: Managing

Universes

 

16-21

Lesson 17

 

Creating Universes

from Metadata

 

Creating

a universe

from an XML metadata

file

17-2

Which metadata

sources

are supported?

17-2

Working

in the Metadata

Exchange

panel

17-3

Creating

a universe from metadata

17-4

Activity:

Creating

universes

from metadata

17-9

Lesson

summary

17-10

Quiz: Creating

Universes

from Metadata

 

17-10

Appendix

A

 

End of Course Challenge

The Challenge

 

A-2

x

Universe

Design-Instructor's

Guide

A

G

E

N

D

Universe Design

A

Introductions,

Course Overview

 

30 minutes

Lesson

1

 

Understanding

BusinessObjects

Universes

30 minutes

o

Understanding BusinessObjects universes

o

Using the Universe Development Cycle

o

Lesson summary

 

Lesson

2

 

Creating the Course Universe

 

45 minutes

o

The course

database

and universe

 

o

Creating

the universe

o

Lesson summary

 

Lesson

3

 

Building

the Universe Structure

1 hour

o

Populating

the universe structure

 

o Defining joins in a universe

o

Lesson summary

Lesson

4

 

Creating Dimension

Objects

 

2 hours

o

Objects

and classes

o

Creating

classes

and objects

o Lesson summary

 

Lesson

5

 

Creating Measure Objects

 

30 minutes

o

What are measure

objects?

o

Creating

measure

objects

o

Lesson summary

Copyright

© 2005 Business

Objects.

All rights reserved.

xi

Lesson 6

Using Lists of Values

 

30 minutes

o

Creating

a list of values

o

Working

with LOVs in Designer

 

o

Creating

a cascading

LOV

o

Lesson Summary

Lesson 7

 

Resolving Loops in a Universe

 

3 hours

o

Understanding

loops

o

Resolving

loops using aliases

 

o

Resolving

loops using shortcut

joins

o

Resolving

loops using contexts

o

Lesson summary

Lesson 8

 

Resolving SQL Traps

 

1.5 hours

o

Understanding SQL traps and universes

o

Resolving chasm traps

o

Resolving fan traps

o

Lesson summary

Lesson 9

 

Applying Restrictions on Objects

1 hour

o

Restricting

the data returned

by objects

o

Lesson Summary

Lesson 10

 

Using Functions with Objects

 

45 minutes

DUsing

@ Functions

 

o

Lesson Summary

Lesson 11

 

Using Hierarchies

 

45 minutes

o

Understanding

hierarchies

and universes

o

Working

with hierarchies

 

o

Lesson summary

Lesson 12

 

Aggregate Awareness

 

1 .5 hours

o

Understanding

aggregate

awareness

and universes

o

Applying

aggregate

awareness

to objects

o

Lesson summary

xiiUniverse Design-instructor's

Guide

Lesson 13

Derived Tables and Indexes

1 hour

o

Using derived tables

 

o

Applying

index awareness

o

Lesson summary

 

Lesson 14

 

Linking Universes

 

30 minutes

o

Understanding

linked universes

 

o Creating

links between

universes

 

o

Lesson summary

 

Lesson 15

 

Securing Universes

 

45 minutes

o

Setting access

restrictions

on a universe

o

Lesson summary

Lesson 16

 

Managing Universes

 

45 minutes

o

Documenting

universes

 

o

Deploying

universes

o

Maintaining

universes

o

Lesson Summary

 

Lesson 17

 

Creating Universes from Metadata

30 minutes

o

Creating

a universe from an XML metadata

file

o

Lesson summary

o

The Challenge

Agenda-instructor's

Guide

xiii

xivUniverse Design-instructor's

Guide

About this Course

This section explains the conventions used in the course and in this training guide.

Copyright © 2005 Business Objects. All rights reserved.

xv

Course objectives

BusinessObjects

XI R1/R2 Universe Design is a classroom-based

course

where participants learn to design and maintain BusinessObjects

. The course includes presentation of concepts, demonstration of features, facilitated discussions, practice activities, and reviews.

After completing this course, learners will be able to:

universes .

Understand BusinessObjects universes

Set universe parameters

Populate the universe structure

Define joins and set their cardinalities Create universe classes, and create dimension, detail and measure objects Create a list of values

Resolve loops in a universe

Resolve SQL chasm and fan traps

Apply restrictions to objects

Create hierarchies, use aggregate awareness, derived tables and index awareness features

Link universes

Manage universes and apply security Create universes from metadata sources

Course audience

The target audience for this course is universe designers.

Prerequisite

education

To be successful, learners who attend this course must have attended the following offerings:

Prerequisite

Not applicable for this offering

knowledge/experience

To be successful, learners who attend this course must have working knowledge of:

xvi

Good working knowledge of SQL and/or relational database management systems.

Familiarity with the type of data and the logical structure of the databases in their organization.

Familiarity with BusinessObjects and report building.

Web Intelligence, Desktop Intelligence

Universe Design-instructor's

Guide

Course success factors

Your learning experience will be enhanced by:

Activities that build on the life experiences of the learner

Discussion that connects the training to real working environments

Learners and instructor working as a team

Active participation by all learners

Training facility setup

Refer to the Facility Setup section of this training guide for details on hardware, software, classroom, course material, and course-specific requirements. These items must be set up before the first day of class.

Course materials

The materials included with the course materials are:

Point out the feedback form located at the back of the training guide to the learners as part of the course intro- duction and again at the end of last day of class.

Name card

Instructor's Guide The Instructor's Guide contains an agenda, lessons, and practice activities. The Instructor's Guide outlines detailed contents as well as instructor notes, which do not appear in the Learner's Guide, for teaching this course.

Learner's Guide The Learner's Guide contains an agenda, learner materials, and practice activities.

The Learner's Guide is designed to assist students who attend the classroom-based course and outlines what learners can expect to achieve by participating in this course. Evaluation form At the conclusion of this course, instruct the learners to provide feedback on the course content, instructor, and facility through the evaluation process. Their comments will assist us to improve future courses.

Additional information for the course is provided on the resource CD or as a hard copy:

Sample files The sample files on the resource CD can include required files for the course activities and/or supplemental content to the training guide.

Overview webinar(s)

Additional resources include:

Online Help and User's Guide As an instructor, encourage the learners to retrieve information and find answers to questions using the online Help and/or the User's Guide that are included with the product.

About this Course-Instructor's

Guide

xvii

Learning

process

Learning is an interactive process between the learners and the instructor. By facilitating a cooperative environment, the instructor guides the learners through the learning framework.

What's specific to BusinessObjects

XI Release 2?

The audience for this course may consist of BusinessObjects XI Release 1and

BusinessObjects

XI Release 2 customers. This icon has been placed

throughout the guide to identify features that are specific to BusinessObjects

XI Release 2.

Introduction

Why am I here? What's in it for me?

The learners will be clear about what they are getting out of each lesson.

Objectives

How do I achieve the outcome?

The learners will assimilate new concepts and how to apply the ideas presented in the lesson. This step sets the groundwork for practice.

Practice

How do I do it?

The learners will demonstrate their knowledge as well as their hands-on skills through the activities.

Review

How did I do?

The learners will have an opportunity to review what they have learned during

the lesson. Review reinforces why it is important to learn particular concepts

or skills.

Summary

Where have I been and where am I going?

The summary acts as a recap of the learning objectives and as a transition to the next section.

xviii

Universe Design-Instructor's

Guide

Recommended

education

This course is not part of a certification path.

Facilities Setup

This section

lists the facilities

setup

requirements

for the course.

Duration: approximately two and a half hours per machine (duration varies depending on whether the operating system is already installed).

Copyright

Recommendation

for Business

Begin

setting

up the facility

two days

© 2005 Business

Objects.

All rights reserved.

Objects training customer

before

training

is scheduled

to start.

xxi

Introduction

The purpose of this setup guide is to provide the information necessary to correctly set up the environment for this course, and ensure the necessary course files are installed on each computer.

This document provides:

Hardware and software requirements for Business Objects training

Guidance for facilities setup for Business Objects training

It is the responsibility of the training customer to ensure the training classroom is set up according to these requirements.

Assuming that all sections must be completed, the approximate time to complete this facilities setup for 12 students and one instructor is between 4-8 hours. Less time will be necessary if the operating systems are already installed.

Facilities Setup

The classroom should have the following:

This section

Learners' Guides, one per student

is to

be

Note: Learners' Guides should be delivered to the training site three business days before the training class is scheduled to begin.

computer

A whiteboard and a variety of erasable markers and eraser

A flip chart and a variety of markers

A non-laser pointer

One computer for the instructor and one computer for each learner taking the course (maximum of 12 learners in a classroom) with the minimum hardware and software requirements

The minimum hardware requirements are:

completed by

the Business

Objects An overhead display panel/projector connected to the instructor's

training

customer.

Allow 8-12

hours to

complete this

section.

Pentium3 700 MHz or higher processor required 512 MB RAM, 1 GB Recommended CD-ROM or DVD drive Software

xxii

The software required for this course is:

Operating system = Microsoft 2000,2003,

Note: For a complete list of supported operating systems for servers and client components, refer to the Platforms.txt with your product installation.

Microsoft Office 2000, 2003 or XP

Microsoft SOL Server 2000 SP 3a or higher

A web application server Note: For a compiete list of supported web servers, refer to the Platforms.txt with your product installation.

or XP

Universe Design-instructor's

Guide

BusinessObjects

Enterprise XI Release 2 Professional Edition

including:

InfoView (portal to Web Intelligence)

Web Intelligence (application used for reporting in this course)

To install

BusinessObjects in this course)

Designer (application used to create universes

required software

1 Install one of the following operating systems:

Windows 2000 (SP2)

Windows NT 4 Server (SP6a)

Windows XP Pro (SP1)

2 Install Microsoft Office 2000 or higher (Microsoft Word, Excel, PowerPoint, Access).

3 Install one of the following web servers:

Microsoft Internet Information Server (liS) 5.0 (ISAPI and CGI for Windows)

Microsoft liS 4.0 (NT 4 Workstation)

4 Install one of the following applications for your web server:

Java J2EE environment, 1.4 or higher

.NET framework 1.0 or higher WARNING: If you opt to install the .NET framework, there are multiple activities in the course that will not be possible. This course REQUIRES that the Java environment be installed.

Note: A prepackaged version of Tomcat with Apache web server is

provided during the BusinessObjects

Enterprise XI R2 installation.

5 Follow the installation procedures listed in the installation guide for BusinessObjects Enterprise XI R2.

The directions in the BusinessObjects

Enterprise XI R2 Installation

Guide should be followed accepting the defaults whenever possible.

Note: It is preferred that the classroom is set up with stand-alone installations however it is possible to install one server and have all students connect to that server.

Facilities Setup-instructor's

Guide

xxiii

Setting up for the activities

This section

is to

be

completed by

the

Business

Objects

training

customer. Allow 1 hour to complete this section.

Before class begins

The following setup needs to be completed prior to the instructor arriving on- site. The universes and reports below will be used during the classroom activities. The following setup instructions are NOT part of the course and must be completed prior to the course. If the items below are not completed prior to the instructor arriving on-site it WILL cause a delay in the delivery ofthe course

and you may be charged for the additional setup time required.

The directions below are step by step and can be followed with little knowledge

of the BusinessObjects

Enterprise XI development environment.

Upon completion of these items please contact your on-site instructor to let them know that the setup is complete.

Deployment of Universes

This course uses the following universes:

Motors2004

Staff2004

eFashion

The first two universes listed will be created during this course. Both universes access data that is stored in the Microsoft Access database, Motors2004.mdb. This database file, plus the final version of the Motors2004.unv and Staff2004.unv files are available on the course Resource CD.

The third universe, eFashion is installed by the Enterprise Setup program to the following location:

C:\Program Files\Business

Objects\BusinessObjects

Enterprise

11.5\Samples\en\Universes

In order to make the universes available to the users you must first redefine their connections to the appropriate data sources (Microsoft Access database files), then export the universes to the repository.

Before doing this, you first need to ensure that valid ODBC connections are present on the workstation.

The following instructions describe how to define a connection and export the eFashion universe. Once you complete this procedure, you must repeat the procedure for each of the other two universes, if you want to deploy the final versions of the universes that will be built during the course.

xxiv

To create an ODBC connection:

1

Click Start>

Programs>

Administrative Tools> Data Sources (ODBC).

2 Click the System DSN tab.

Universe Design-instructor's

Guide

Note: In order to deploy a universe, the connection to the data source must use a system DSN.

Fashion ashion

already exists.

already

exists

IF

THEN

Go to Step

Go to Step

10.

3.

Start here if an eFashion ODBC connection already exists.

3 Click eFashion.

4 Click Configure.

5 Click Select.

Note: The correct database mayor version of BusinessObjects

may not be selected. If a previous ever existed on the machine, the

connection may be left over from that version. Continue through steps 5 - 8 to verify the correct database is selected. The eFashion database in BusinessObjects Enterprise 11 is different than the database in previous versions.

6 Browse to the directory you installed BusinessObjects Enterprise 11 in \Business Objects\BusinessObjects Enterprise

11\Samples\En\Databases.

7 Select eFashion.mdb. Click OK.

8 Click OK to close the ODBC Microsoft Access Setup window.

9 Click OK to accept the ODBC changes.

10 Skip to step 18.

Start here if a new eFashion ODBC connection is required.

11 Click Add.

12 Select Microsoft Access Driver (*.mdb). Click Finish.

13 Type eFashion as the Data Source Name.

14 Click Select.

15 Browse to the directory you installed BusinessObjects Enterprise XI R2 in \Business Objects\BusinessObjects Enterprise

11.5\Samples\En\Databases.

16

Select eFashion.mdb. Click OK.

17

Click OK to close the ODBC Microsoft Access Setup window.

18

Click OK to accept the ODBC changes.

After creating I verifying the eFashion ODBC connection, continue to the instructions below.

To define the connection

in the universe

1

Click Start>

Enterprise> Designer. Log into BusinessObjects Designer. If you are using the default installation, you can use the username Administrator with NO password.

Programs>

BusinessObjects

11 > BusinessObjects

If the wizard opens, click Cancel.

2 Click File> Open.

Facilities Setup-Instructor's

Guide

xxv

3

Browse to the directory where BusinessObjects installed

Enterprise XI R2 was

\Business Objects\BusinessObjects

Enterprise

11.5\Samples\En\Universes.

4

Click eFashion.

5

Click Open. The universe will open in Designer.

6

Click File> Parameters.

7

On the Definition tab, click on New to add a new connection.

Note: The connection must be a "secured" connection prior to publishing to the repository.

8

The New Connection Wizard appears. Click on Next.

9

Double-click Microsoft.

10

Double-click MS Access 2002. (Or the appropriate MS Access version)

11

Click ODBC Drivers. Click Next.

12 Verify the Type: is Secured.

13 Type Secured eFashion as the Name.

14 Select eFashion as the Data source name. Your new connection window should look like this.

15 Click Next.

16 Click Test Connection. Verify that the test was successful. If you do not see the message 'The server is responding!" Click the < Back button and resolve the issue.

xxvi

Universe Design-instructor's

Guide

17

Click Next.

 

18

Click Next.

19

Click Finish. The secured eFashion connection is now shown.

20

Click OK.

21

Click Tools> Check Integrity.

22

Select the checkbox for Check All.

23

Click OK. The integrity check runs.

24

Verify that the Check Integrity Results match exactly as shown below.

 

e'c 2ai"",~g~~

 

?,:»:~Objebtt: OK

 

'Pl!lwJ~

OK

.

p&ti> C~8m'$:

OK

[#O_k

loop:OK

:£ffIJI\'m\1iIdi~

 

25

Click OK to close the window.

26

Click File> Export.

 

Facilities Setup-Instructor's

Guide

xxvii

The export universe window appears asking for confirmation of saving.

27 Click Continue.

28 Select the Folder.

29 Select the Groups (leave default if you are not sure).

30 Click OK.

The Universe successfully exported message appears.

31 Click OK.

32 Close BusinessObjects Designer.

33 Repeat this procedure for the two remaining universes used in this course.

Note: As stated previously, the final versions of the Motors2004 and Staff2004 universes and the Motors2004 database (used as data for both universes) are provided on the course Resource CD.

Testing the hardware and software setup

After exporting the eFashion universe, follow the steps below to verify that all

files are in place for the training class.

Verify users can log into the J5P version

11.

of BusinessObjects

Enterprise

1

2

Click Start> Programs> BusinessObjects XI Release 2> BusinessObjects Enterprise> BusinessObjects Enterprise Java InfoView.

Log in as a valid user. If running only the samples, log in as Administrator.

Administrator

does not have a password.

Verify

eFashion

universe

is available.

3

Click Web Intelligence Document from the New menu.

4

Verify that eFashion is listed as an available universe.

S

Click eFashion to create a new Web Intelligence document.

xxviii

Universe Design-Instructor's

Guide

6

If the security warning appears, click Yes to trust the applet.

7

Double-click Year.

S

Double-click Sales Revenue (in the Measures class).

9

Click Run Query. The results should match the image below.

10

Close the document without saving (click X in top right corner).

Verify sample Web Intelligence document is available.

11 Click + to expand Public Folders.

12 Click Web Intelligence Samples. Verify that the Web Intelligence Sample report is listed.

13 Click Web Intelligence Sample to open the report.

Facilities Setup-Instructor's

Guide

xxix

The report opens

14 Close the report without saving.

15 Repeat similar procedures for the remaining universes.

16 Log out of BusinessObjects The setup is now complete.

Enterprise.

Creating users and user groups in the CMS

During this course, in order to apply universe restrictions sets on users and groups of users authorized to access universes, you need to create users and user groups in the Business Objects Enterprise Central Management System (CMS).

To create users in the CMS

1 Click Start> Programs> BusinessObjects XI Release 2> BusinessObjects Enterprise> BusinessObjects Enterprise Java Administration Launchpad.

2 Click Central Management Console.

3 Log in as Administrator. Administrator does not have a password.

4 In the CMC, click Users.

5 Click New User.

6 Type Mary Manager in the Account Name field.

7 Select the Password never expires option.

8 Clear the User must change

9 Click OK. ·The CMC will autofill the Password text boxes with blank characters.

password

at next log~n option.

10 Click the Users link at the top of the page to return to the page where you create new users.

11 Create two other new users with the following names:

xxx

Hank HR

Stan Sales

Universe Design-instructor's

Guide

12

Return to the All Users page and verify that the three new users are in the list.

13

Return to the CMC Home page.

Now

you need to assign these users to appropriate groups.

To create user groups in the CMS

1 From the Home page, click Groups.

2 In the right corner of the All Groups page, click the New Groups button.

3 Type Managers_Group in the Group Name text box and click OK.

4 Create two other groups with the following names:

Employees_Group

Sales_Group

To assign users to groups

1

Return to the All Groups page

 

2

In the All Groups page, click the Managers of this group.

link to display the properties

3

Click the Users tab.

At present, there are no users assigned to this group because you just created it.

4

Click the Add Users button.

 

S

Add the Mary Manager user to this group and click OK.

6

Return to the All Groups

page.

7

Assign the Hank HR user to the Employees group, following the same procedure.

S

Assign the Stan Sales user to the Sales group, following the same procedure.

9

Return to the CMC Home page.

 

To authorize

the new users to use Web Intelligence

1

From the CMC Home Page, click BusinessObjects Applications.

Enterprise

2

Click Web Intelligence.

3

Click Add/Remove.

4

For each new group, click the Advanced name on the Web Intelligence page.

link to the far right of the group

S

Explicitly grant all Web Intelligence rights to these groups.

To test the new users

1 Log off the Central Management Console.

2 Log onto InfoView and try to create a new Web Intelligence document, to be sure that the new users are authorized to use Web Intelligence.

Facilities Setup-Instructor's

Guide

xxxi

If the new users do not appear to have been authorized to use Web Intelligence:

1 Log on to the CMC again.

2 Return to the BusinessObjects Intelligence page.

3 For each new user, click the Advanced link to the far right of the user name on the Web Intelligence page.

4 For each user, select the <User name> will inherit rights from it parent groups option. This ensures that all new users are authorized to use all Web Intelligence features.

Enterprise ApplicationslWeb

Getting Help

If you encounter difficulties while setting up your facility, contact your Business Objects Training Coordinator.

xxxii

Universe Design-Instructor's

Guide

Lesson 1

Understanding BusinessObjects Universes

To design effective and efficient universes for your business users, you need a general understanding of their structure and application. It is also important to become familiar with the process involved in building a successful universe.

In this lesson you will learn how to:

Understanding BusinessObjects universes

Using the Universe Development Cycle

Duration: 30 minutes

Copyright © 2005 Business Objects. All rights reserved.

1-1

Understanding BusinessObjects universes

Introduction

This lesson gives a general introduction to universes.

After completing this unit you will be able to:

Describe a universe

Describe BusinessObjects

Save, export and import universes

Universe Designer interface elements

What is a universe?

The BusinessObjects

users from the technical complexities of the databases where their corporate -

intormation is stored.

Universes are made up of objects and classes that map to data in the database, using everyday terms that describe the business environment. This means that by using a universe to create a query, users can retrieve exactly the data that interests them using their own business terminology.

A BusinessObjects

universe is the semantic layer that isolates business

,"

universe is a file that contains the following:

Connection parameters to a single data source.

SQL structures called objects that map to actual SQL structures in the database such as columns, tables, and database functions. Objects are grouped into classes.

A schema of the tables and joins used in the database. Objects are built from the database structures that you include in your schema.

Web Intelligence, Desktop Intelligence or Crystal Reports users select the universe they are authorized to access in order to build queries. They build a query by selecting objects defined in the universe, and in this way, they are not required to see or know anything about the underlying da!a structures in the database.

BusinessObjects Designer XI Release 2 now gives universe designers the ability to build universes from OLAP and metadata sources. It also offers the ability to build universes against Unicode databases and run reports that display data in multiple languages.

Universes

are used to query the database

The purpose of the universe is to provide an easy-to-use interface for non- technical business users to:

run queries against a database

create reports

perform data analysis

As the universe designer, you use Designer to create objects and classes that represent database structures.

tV

The objects you create in the universe must be relevant to the·end user's business environment and vocabulary. The role of objects is to present a

business-focused

front end to the SQL structures in the database.

Classes and objects

A universe contains the following structures:

Classes

Objects

Classes

A class is a logical grouping of objects within a universe. It represents a

category of objects. The name of a class should indicate the category of the objects that it contains. A class can be divided hierarchically into sub-classes.

Objects

An object is a named component that maps to data or a derivation of data in the database. The name of an object should be drawn from the business vocabulary of the targeted user group. Objects and classes are discussed in more detail in Lesson 4.

How universes

are used

Universes are used by Web Intelligence, Desktop Intelligence or Crystal Reports users. The connection to the database is defined in the universe. By selecting a universe when they create new documents, or edit existing documents, business users are automatically given access to the data. The access to data, in turn, is restricted by the objects that are avaiiable in the universe. These objects have been created by you, the universe designer, based on the needs profile for a defined user group.

Advantages

of a universe

The advantages of a universe are:

Only the universe designer needs to know how to write SQL and understand the structure of the target database.

The interface you use to create a universe is an easy-to-use graphical environment.

Data is secure. Users can see only the data exposed by the universe. Users can only read data, not edit it.

The results are reliable and the universe is relatively easy to maintain.

Users can use a simple interface to create reports. All users work with consistent business terminology.

Users can analyze data iocally.

Understanding BusinessObjects Universes-instructor's

Guide

1-3

Metadata and the semantic layer

Metadata and semantic layer are two terms that relate to universes. Essentially, a universe contains metadata and is considered the semantic layer.

The semantic layer is made up of a number of different types of objects that are named using end-user business terminology. For the ease of the end user, these objects are grouped into universes and sub-grouped into classes.

1-4

Human

Resources

Universe Design-Instructor's

Guide

Before launching Designer, it is a good idea to launch Web Intelligence and build a query against the eFashion universe. Select at least one dimension and measure object, and use a predefined query filter as well. Explain that this is what the learners will soon be building using Designer, and that users will use their universe to create reports like this.

BusinessObjects Universe Designer components

You create, modify, and update universes with Universe Designer. Designer provides a connection wizard that allows you to connect to your database middleware. You can create multiple connections with Designer, but only one connection can be defined for each universe. This database connection is saved with the universe.

Designer provides a graphical interface that allows you to select and view tables in a database. The database tables are represented as table symbols in a schema diagram. You can use this interface to manipulate tables, create joins that link the tables, create alias tables, contexts, and solve loops in your schema. Users do not see this schema.

Designer provides an object explorer view. You use the explorer tree to create objects that map to the columns and SQL structures that are represented in the schema view. Users select these objects to run queries against a database.

Starting Designer

Designer can only be used with a BusinessObjects repository. You must log into the repository before starting Designer.

After you start Designer, you can open a universe in one of the following ways:

Create a new universe.

Import a universe from the repository.

Open a universe directly from the file system.

A universe is available to Web Intelligence, Desktop Intelligence and Crystal Reports users once it has been exported to the repository. Importing a universe, making changes, then exporting the updated universe to the repository is the most common way of working with Designer.

Note: You can save a universe to the file system. You do this when you are in the process of developing the universe locally and when you want to share the universe with other users who may not have connection rights to the target repository.

Note: You can lock and secure a universe before sending it to the central repository.

Understanding BusinessObjects Universes-instructor's

Guide

1-5

To start Designer:

1 Click the Start button on the taskbar.

2 Select the Programs menu.

3 Click the Designer program from the StartlPrograms/BusinessObjects 11/BusinessObjects Enterprise program menu. The login dialog box for the repository appears.

tion

The default user name is Administrator The default password is left blank.

User Name

Password

Login information

I

System

authentication level

name of the repository server

your repository passwor.

your repository user name

Note: This information is normally provided to you by the Business Objects Enterprise administrator.

4 Click the OK button.

The Designer start-up screen appears, and an empty Designer session opens. The user name and repository name appear in the title bar.

Note: Depending on options set for Designer, the Quick Design Wizard can start automatically when you start in Designer. Click Cancel to close the wizard.

1-6

Universe Design-Instructor's

Guide

U sing the Quick Design

Wizard

When you start a Designer session for the first time, the Quick Design Wizard appears by default. You can use the wizard to quickly create a universe or to familiarize yourself with Designer. However, unless your data source is a very simple model, it is not an appropriate tool for creating a complete universe that responds to end-user reporting requirements.

Once you are familiar with Designer, you will probably decide to disable the wizard and and not use it to design universes. All the universe design, building, maintenance information, and procedures in this training manual are structured with the assumption that you have disabled the Quick Design Wizard.

Deactivating

the Quick Design Wizard

You can prevent the wizard from appearing automatically when you create a new universe as follows:

1 Select Tools> Options The Options dialog box opens to the General page.

2 Clear the Show Welcome Wizard check box.

Note: This check box is already cleared if you have cleared the Run this wizard at startup check box from the Startup Wizard Welcome page.

3 Clear the File/New Starts Quick Design Wizard check box.

4 Click OK.

Note: You can activate the Quick Design Wizard at any time by selecting the above check boxes from the General page of the Options dialog box.

Understanding BusinessObjects Universes-Instructor's

Guide

1-7

Using Designer

module

commands

There are three ways to issue commands in Designer:

Menu options

Toolbar buttons

Speed menus

Menu options

You can perform most tasks by choosing options from the menu. The Designer menu bar looks like this:

Toolbar buttons

The toolbar gives you quick access to many tasks. Designer has three tool bars:

the Standard toolba, the Editing toolbar, and the Formula tool bar

Right-click

menus

Drop-down menus display on your screen when you click the right mouse button. Drop-down menus usually give you access to options related to the task you are currently performing. For example, if you click the right mouse button in the Universe pane, a drop-down menu for creating classes and objects is displayed:

1-8

Universe Design-Instructor's

Guide

w.

the two

ion

Open the

Designer

universe and

parts of the

Designer window

The Universe window is made up of two segments.

On the right- hand side is the pane in which you insert the database tables and then view the universe structure that infers the FROM and SELECT clauses into a SELECT statement.

This is known as the Structure pane.

On the left-hand side is the pane in which you create the classes and objects that users will see when they build queries using this universe. The objects physically point to the tables you see in the Structure pane. This is known as the Universe pane.

Manipulating

the structure view

There are three ways to manipulate the Structure pane in the Designer window: toolbar buttons, drag and drop, and by using the Options panel.

Zoom

Often it is not possible to view the whole of the schema at normal magnification due to its size. Zoom in or out using the drop-down list to choose your percentage view for the schema.

Arrange

tables

You can select this button to have Designer automatically organize your tables sequentially and horizontally.

Note: You can undo only the last command. If you do not like the results, choose Undo from the Edit menu.

Drag and Drop

Different views of the universe structure can be achieved by a number of means using drag-and-drop technology. Generally, this involves pointing to an item or marking it and then applying a command by double-clicking and dragging and dropping or right-clicking. For example:

table or join

To move a table

To mark a single table

To mark a join

To mark all tables and joins

To mark more than one

Action

Ctrl-A.

Click the header of the table.

Click it.

you want to highlight.

Click the header of the table and drag and

Ctrl-click the header of each table (or join)

Procedure

drop the table to the desired position.

Understanding BusinessObjects Universes-instructor's

Guide

1-9

data content of the table

for a table in the database

a single column

To view the data values for

To view the columns of a

To roll up a table

To gain a partial view of the

To view the number of rows

table

umns

To view the remaining col-

appears on the right of the table.

the View Column Values option.

View Table Values option.

columns contained within that table, this is

If the view of a table does not show all the

Click the header of the table; a scroll bar

Action

Right-click the table header (or structure

segment background if you want the number

Right-click the table header and choose the

By default, the table header and a specified

Right-click the column required and choose

Note: To achieve this the table header must

j:'iiBiiii@~i§ffi@;t;ii@

first 100 rows of the table. This number can be

table.times

table as indicated below.

notprocess.be advisable due to the

signified by three dots at the bottom of the

not be highlighted.

timebase,itthistakesmayto

tablesnumbercontainedof its columnsin the areuniverseshownstructurefor all

header.soclickkeyindividualsegment.thatcolumnstwiceonlyDouble-clicktableThissothearethatviewbyheadershown,onlydouble-clickingcanoncetheisbeDouble-clickshown.totablealteredrollheaderupDouble-thefora tablethreetableanand

ofbottombottom

ofNumberrows forof allRowstables)in Tableand thenoption.choose the

Note: If you are front ending a large data-

Note: By default, data is only displayed for the

arrowAlternatively,marginmarginappears;downof the placetotableyouexpandthecanandpointerthenathedouble-headednumberdragon thethe

Options>Databaseexpanded or reducedtab.using the Tools>

columns shown in the table.

Procedure

,CLIENT_AREA

'CLIENT_ADDRESS

,CLlENT_AREA_CODE: CLlENT_PHONE_NO

'CLlENT_LASTNPME,CLlENTJIRSTNPME

,CLlENT_ID

; CLIENT_TOWN

. ,

,, ,

to return to an unrolled view of the

,

Saving and exporting a universe

You should regularly save your universes during a work session. When you save a universe, Designer stores it as a file with a .unv extension in your local file system. This is usually a universe folder in the BusinessObjects installation path. Any changes you have made to the universe file are saved locally but are not propagated to the universe version in the repository until you choose to export it.

When you export the universe, the updated version is also saved on the local file system, but it is copied to the BusinessObjects Enterprise repository as well. This version is then available to Web Intelligence, Desktop Intelligence and Crystal Reports users connecting to the universe.

It is also made available to other universe designers who are authorized by the Enterprise Administrator to access it.

You should regularly save your changes to a universe locally. Then when you have finished updating the universe, export the latest saved version to the repository.

Opening,

importing, and exporting universes

If a universe has been previously exported to BusinessObjects Enterprise, the universe file is associated with the Enterprise repository. The universe is deployed and available to other universe designers who are authorized to import it.

If you choose to browse to a copy of that universe file on your local file system and open it directly in Designer, the file may not be the latest version of the universe. If you want to make changes to a universe that has already been exported to the repository, you should not open a universe file directly using File> Open menu. Instead, you should use File>lmport to ensure that you are viewing the most recent version.

When you import a universe, the repository automatically copies the latest version of the universe to the local file system. This file is then opened in Designer. It is the latest version of the universe contained in the repository. You should always import a universe and then export it again when you have finished modifying it, if you want your changes to be available to the repository.

Importing a universe

When you import a universe, you import the latest version of the universe from the repository. The universe is copied to the local file system, and this file is opened in Designer.

You can import one or more universes stored in a universe folder in the repository.

To import

a universe:

1 Select the Import command from the File menu. The Import Universe dialog box appears.

2 Select a universe folder from the drop-down list

Understanding BusinessObjects Universes-instructor's

Guide

1-11

OR

Click the Browse

button and select a universe using the folder browser.

You want to import a universe from this folder.

3

If you want to lock the universe, double-click the universe name.

A locked universe appears with a padlock symbol. To unlock a universe,

double-click it again.

4

Click the universe name.

This is the universe that you want to import.

S

Verify the file path for the import folder in the Import Folder box. The universe is exported to this folder.

6

Click OK.

Universe file names as identifiers

You should not change the universe file name after reports have been created

based on that universe. If you change the file name, any report built on the universe with the old name does not point to the universe after its name has been changed.

To save a universe:

The universe name can be different from the .unv file name.

Designer XI no longer requires that

When you use Save As to save the universe under a new name, the new universe is not associated in the repository. You must export the new universe to the repository to create a version of the new universe.

the universe file name be

You can use the following methods to save a universe:

 

8 characters

1 Select File> Save from the menu bar.

or less.

2 Click the Save icon.

 

3 Press CTRL+S on the keyboard.

Note: Do not save two different universes with the same file name. This leads to conflicts when you attempt to export these universes to the repository.

Saving a universe definition

as PDF

You

can also save the universe information in Adobe PDF format. This allows

you

to save to a PDF file the same attributes that are defined for printing

 

purposes.

 

Note: You can view the default attributes by selecting the Tools>Options menu and selecting the PrinUPDF tab. The Options dialog box will be presented in detail in a later lesson.

The

attributes that you can print or save to a PDF file include:

 
 

General information - parameters, linked universes, and the graphical table schema.

Component lists - lists of components in the universe including objects, conditions, hierarchies, tables, joins, and contexts.

Component descriptions - descriptions for the objects, conditions,

 

hierarchies,

tables, joins, and contexts in the universe.

 

Saving these attributes as a PDF file may be helpful for troubleshooting maintenance purposes.

or

1-12

Universe Design-Instructor's

Guide

J

To save universe information

1

Select File>

Save As.

as a PDF file:

2 Select Portable

down list.

3 Click Save.

Document

Format (PDF) from the Save as type drop-

Giving all users access to a universe

If you want to make a universe available to universe designers who may not have access to your Central Management System, you must save the universe with an unsecured connection. Different types of connections are presented in a later lesson in this course.

To make a un!verse accessible to all Designer users:

1 Verify that the universe that you want to make available to all users does not have a secured connection.

2 4 3 5

Secured connections are required to export universes to the repository. If

a universe has a secured connection, select or create a new personal or shared connection.

Note: Creating connections is discussed in detail in a later lesson. Select File> Save As.

A File Save dialog box appears.

Select the Save For All Users check box.

Click OK.

Understanding BusinessObjects Universes-instructor's

Guide

1-13

Practice

Activity: Viewing

a universe

in Designer

Objectives

By the end of this activity, you will be able to:

Open a universe and identify universe elements in Designer.

Instructions

1

Open Designer.

2

Open the eFashion.unv file found in the default installation folder:

C:\Program Files\Business Objects\BusinessObjects

Enterprise

11.5\Samples\en\Universes

Or, find the same file on the Resource CD for this course.

3

Explore the menu options, toolbar buttons, and right-click drop-down menus.

4

Select View>Toolbars, and ensure that all three toolbars are selected.

5

Zoom to 125% (type directly into the field instead of using the drop-down list).

6

Click the Arrange Tables button to automatically organize tables.

7

Click the View List Mode button to list all Tables, Joins, and Contexts.

8

Click the Article_Color_Lookup table in the Tables list and to see it highlighted in the structure below.

9

Right-click the Article_Color_Lookup Table (Refresh row count for all tables).

table to view Number of Rows in

10

Right-click the Article_Color_Lookup Values.

table to view a sample of Table

11

Open the Product class to view the objects it contains.

12

Double-click the Color object (notice the name, description, and select fields).

13

Select Parameters on the File menu and change the universe long name to New eFashion.

14

Close the universe.

1-14

Universe Design-instructor's

Guide

Using the Universe Development Cycle

Introduction

Universe development is a cyclical process that includes planning, designing, building, distribution, and maintenance phases. Use Designer to design and build a universe. However, the usability of any universe is directly related to how successfully the other phases in the development cycle interact with each other.

After completing this unit, you will be able to:

Use the Universe Development Cycle.

The Universe Development

Cycle

This unit presents an overview of a universe designing methodology that you can use to plan and implement a universe development project.

The table below outlines the major phases in a typical Universe Development Cycle:

Phase

Analysis Planning

· · · ·

· ·

·

Understand limitations.

Identify what information the users need.

Identify the cardinality.

Understand the joins.

Identify a project strategy. For example, the number

Identify the user population and how it is structured.

Identify the target data 90urce and become familiar

Know what data is contained within each table of

Identify what standard reports users require.

Familiarize yourself with company business

· · ·

with its structure.

departmentFor example,orisbythetask?user group structured by

each of the target databases.

of universes that should be created and which ones

should have the capacity to be linked and to what

terminology so you can name objects sensibly.

Development

level.

Description

Preparation

Understanding BusinessObjects Universes-Instructor's

Guide

1-15