Post on 06-Apr-2018
transcript
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 196
Universal Drill Through Service Guide
Universal Drill Through Service 61
Windows
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 296
2 Universal Drill Through Service Guide
Copyright No part of the computer software or this document may be reproduced or transmitted in any form
or by any means electronic or mechanical including photocopying recording or by any
information storage and retrieval system without permission in writing from Business
Objects SA
The information in this document is subject to change without notice If you find any problems
with this documentation please report them to Business Objects SA in writing atdocumentationbusinessobjectscom
Business Objects SA does not warrant that this document is error free
Copyright copy Business Objects SA 2003 All rights reserved
Printed in France
Trademarks The Business Objects logo WebIntelligence BusinessQuery the Business Objects tagline
BusinessObjects BusinessObjects Broadcast Agent Rapid Mart Set Analyzer Personal
Trainer and Rapid Deployment Template are trademarks or registered trademarks of Business
Objects SA in the United States andor other countries
Contains IBM Runtime Environment for AIX(R) Java(TM) 2 Technology Edition Runtime
Modules (c) Copyright IBM Corporation 1999 2000 All Rights ReservedThis product includes code licensed from RSA Security Inc Some portions licensed from IBMare available at httposssoftwareibmcomicu4j
All other company product or brand names mentioned herein may be the trademarks of their
respective owners
Use restrictions This software and documentation is commercial computer software under Federal Acquisition
regulations and is provided only under the Restricted Rights of the Federal AcquisitionRegulations applicable to commercial computer software provided at private expense The use
duplication or disclosure by the US Government is subject to restrictions set forth insubdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252227-
7013
Patents US Patent Numbers 5555403 6247008 and 6578027
Part Number 372-10-610-01
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 396
Universal Drill Through Service Guide 3
Contents
Contents
Preface Maximizing Your Information Resources 7
Information resources 9
Services 11
Useful addresses at a glance 12
About this guide 14
Chapter 1 About Drill Through 15
What does the administrator do 17
What does the administrator need to know 19
What is drill through 20
Setting up drill through 27
Chapter 2 Drill Through Requirements 29
Normalized relational databases 31
Star schemas 32
What is a Business Objects universe 34
How cubes and universes relate 35
Chapter 3 Designing the Target Universe 41
Designing the target database 43
Designing a star schema database 44
Creating the target universe from the database 46
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 496
4 Universal Drill Through Service Guide
Contents
Chapter 4 Building Translation Maps 47
What is UDS Designer 49
What are translation maps 50
Mapping from cubes to universes 53
Building translation maps using UDS Designer 54
Importing data sources 56
Creating a translation map 60
Working with existing translation maps 75
Making translation maps available to WebIntelligence 78
Chapter 5 WebIntelligence in Drill Through 79
Creating WebIntelligence target reports 81
Drill through workflow 82
Chapter 6 Managing and Maintaining a Drill Through Environment 89
Why maintenance is necessary 91
Changes that require updates 92
Problems caused by outdated translation maps 93
Source cube and target cubeuniverse locations 94
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 596
Universal Drill Through Service Guide 5
Examples
Examples
What are the unit sales of different brands of soccer cleats in 2001 Q1 21
Selecting multiple measure cells 91Selecting member labels from different dimensions 91
Selecting member labels at the same level 92
Selecting member labels from the same and different dimensions 92
Selecting member labels and values 92
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 696
6 Universal Drill Through Service Guide
Examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 796
p r e f a c e
Maximizing Your InformationResources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 296
2 Universal Drill Through Service Guide
Copyright No part of the computer software or this document may be reproduced or transmitted in any form
or by any means electronic or mechanical including photocopying recording or by any
information storage and retrieval system without permission in writing from Business
Objects SA
The information in this document is subject to change without notice If you find any problems
with this documentation please report them to Business Objects SA in writing atdocumentationbusinessobjectscom
Business Objects SA does not warrant that this document is error free
Copyright copy Business Objects SA 2003 All rights reserved
Printed in France
Trademarks The Business Objects logo WebIntelligence BusinessQuery the Business Objects tagline
BusinessObjects BusinessObjects Broadcast Agent Rapid Mart Set Analyzer Personal
Trainer and Rapid Deployment Template are trademarks or registered trademarks of Business
Objects SA in the United States andor other countries
Contains IBM Runtime Environment for AIX(R) Java(TM) 2 Technology Edition Runtime
Modules (c) Copyright IBM Corporation 1999 2000 All Rights ReservedThis product includes code licensed from RSA Security Inc Some portions licensed from IBMare available at httposssoftwareibmcomicu4j
All other company product or brand names mentioned herein may be the trademarks of their
respective owners
Use restrictions This software and documentation is commercial computer software under Federal Acquisition
regulations and is provided only under the Restricted Rights of the Federal AcquisitionRegulations applicable to commercial computer software provided at private expense The use
duplication or disclosure by the US Government is subject to restrictions set forth insubdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252227-
7013
Patents US Patent Numbers 5555403 6247008 and 6578027
Part Number 372-10-610-01
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 396
Universal Drill Through Service Guide 3
Contents
Contents
Preface Maximizing Your Information Resources 7
Information resources 9
Services 11
Useful addresses at a glance 12
About this guide 14
Chapter 1 About Drill Through 15
What does the administrator do 17
What does the administrator need to know 19
What is drill through 20
Setting up drill through 27
Chapter 2 Drill Through Requirements 29
Normalized relational databases 31
Star schemas 32
What is a Business Objects universe 34
How cubes and universes relate 35
Chapter 3 Designing the Target Universe 41
Designing the target database 43
Designing a star schema database 44
Creating the target universe from the database 46
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 496
4 Universal Drill Through Service Guide
Contents
Chapter 4 Building Translation Maps 47
What is UDS Designer 49
What are translation maps 50
Mapping from cubes to universes 53
Building translation maps using UDS Designer 54
Importing data sources 56
Creating a translation map 60
Working with existing translation maps 75
Making translation maps available to WebIntelligence 78
Chapter 5 WebIntelligence in Drill Through 79
Creating WebIntelligence target reports 81
Drill through workflow 82
Chapter 6 Managing and Maintaining a Drill Through Environment 89
Why maintenance is necessary 91
Changes that require updates 92
Problems caused by outdated translation maps 93
Source cube and target cubeuniverse locations 94
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 596
Universal Drill Through Service Guide 5
Examples
Examples
What are the unit sales of different brands of soccer cleats in 2001 Q1 21
Selecting multiple measure cells 91Selecting member labels from different dimensions 91
Selecting member labels at the same level 92
Selecting member labels from the same and different dimensions 92
Selecting member labels and values 92
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 696
6 Universal Drill Through Service Guide
Examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 796
p r e f a c e
Maximizing Your InformationResources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 396
Universal Drill Through Service Guide 3
Contents
Contents
Preface Maximizing Your Information Resources 7
Information resources 9
Services 11
Useful addresses at a glance 12
About this guide 14
Chapter 1 About Drill Through 15
What does the administrator do 17
What does the administrator need to know 19
What is drill through 20
Setting up drill through 27
Chapter 2 Drill Through Requirements 29
Normalized relational databases 31
Star schemas 32
What is a Business Objects universe 34
How cubes and universes relate 35
Chapter 3 Designing the Target Universe 41
Designing the target database 43
Designing a star schema database 44
Creating the target universe from the database 46
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 496
4 Universal Drill Through Service Guide
Contents
Chapter 4 Building Translation Maps 47
What is UDS Designer 49
What are translation maps 50
Mapping from cubes to universes 53
Building translation maps using UDS Designer 54
Importing data sources 56
Creating a translation map 60
Working with existing translation maps 75
Making translation maps available to WebIntelligence 78
Chapter 5 WebIntelligence in Drill Through 79
Creating WebIntelligence target reports 81
Drill through workflow 82
Chapter 6 Managing and Maintaining a Drill Through Environment 89
Why maintenance is necessary 91
Changes that require updates 92
Problems caused by outdated translation maps 93
Source cube and target cubeuniverse locations 94
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 596
Universal Drill Through Service Guide 5
Examples
Examples
What are the unit sales of different brands of soccer cleats in 2001 Q1 21
Selecting multiple measure cells 91Selecting member labels from different dimensions 91
Selecting member labels at the same level 92
Selecting member labels from the same and different dimensions 92
Selecting member labels and values 92
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 696
6 Universal Drill Through Service Guide
Examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 796
p r e f a c e
Maximizing Your InformationResources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 496
4 Universal Drill Through Service Guide
Contents
Chapter 4 Building Translation Maps 47
What is UDS Designer 49
What are translation maps 50
Mapping from cubes to universes 53
Building translation maps using UDS Designer 54
Importing data sources 56
Creating a translation map 60
Working with existing translation maps 75
Making translation maps available to WebIntelligence 78
Chapter 5 WebIntelligence in Drill Through 79
Creating WebIntelligence target reports 81
Drill through workflow 82
Chapter 6 Managing and Maintaining a Drill Through Environment 89
Why maintenance is necessary 91
Changes that require updates 92
Problems caused by outdated translation maps 93
Source cube and target cubeuniverse locations 94
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 596
Universal Drill Through Service Guide 5
Examples
Examples
What are the unit sales of different brands of soccer cleats in 2001 Q1 21
Selecting multiple measure cells 91Selecting member labels from different dimensions 91
Selecting member labels at the same level 92
Selecting member labels from the same and different dimensions 92
Selecting member labels and values 92
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 696
6 Universal Drill Through Service Guide
Examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 796
p r e f a c e
Maximizing Your InformationResources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 596
Universal Drill Through Service Guide 5
Examples
Examples
What are the unit sales of different brands of soccer cleats in 2001 Q1 21
Selecting multiple measure cells 91Selecting member labels from different dimensions 91
Selecting member labels at the same level 92
Selecting member labels from the same and different dimensions 92
Selecting member labels and values 92
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 696
6 Universal Drill Through Service Guide
Examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 796
p r e f a c e
Maximizing Your InformationResources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 696
6 Universal Drill Through Service Guide
Examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 796
p r e f a c e
Maximizing Your InformationResources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 796
p r e f a c e
Maximizing Your InformationResources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 896
8 Universal Drill Through Service Guide
Maximizing Your Information Resources
Overview
Information services and solutions
The Business Objects business intelligence solution is supported by thousandsof pages of documentation available from the products on the Internet on CDand by extensive online help systems and multimedia
Packed with in-depth technical information business examples and advice ontroubleshooting and best practices this comprehensive documentation setprovides concrete solutions to your business problems
Business Objects also offers a complete range of support and services to helpmaximize the return on your business intelligence investment See in thefollowing sections how Business Objects can help you plan for and successfully
meet your specific technical support education and consulting requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 996
Universal Drill Through Service Guide 9
Information resources
Information resources
Whatever your Business Objects profile we can help you quickly access thedocumentation and other information you need
Where do I start
Below are a few suggested starting points there is a summary of useful webaddresses on page 12
Documentation Roadmap
The Documentation Roadmap references all Business Objects guides andmultimedia and lets you see at a glance what information is available fromwhere and in what format
View or download the Business Objects Documentation Roadmap at
wwwbusinessobjectscomservicesdocumentationhtm
Documentation from the products
You can access electronic documentation at any time from the product you areusing Online help multimedia and guides in Adobe PDF format are availablefrom the product Help menus
Documentation on the web
The full electronic documentation set is available to customers with a validmaintenance agreement on the Online Customer Support (OCS) website atwwwbusinessobjectscomservicessupporthtm
Buy printed documentation
You can order printed documentation through your local sales office or from theonline Business Objects Documentation Supply Store atwwwbusinessobjectscomservicesdocumentationhtm
Search the Documentation CD
Search across the entire documentation set on the Business ObjectsDocumentation CD shipped with our products This CD brings together the full setof documentation plus tips tricks multimedia tutorials and demo materials
Order the Documentation CD online from the Business Objects DocumentationSupply Store or from your local sales office
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1096
10 Universal Drill Through Service Guide
Maximizing Your Information Resources
Multimedia
Are you new to Business Objects Are you upgrading from a previous release or expanding for example from our desktop to our web solution Try one of our multimedia quick tours or Getting Started tutorials All are available via the OnlineCustomer Support (OCS) website or on the Documentation CD
How can I get the most recent documentation
You can get our most up-to-date documentation via the web Regularly check thesites listed below for the latest documentation samples and tips
Tips amp Tricks
Open to everyone this is a regularly updated source of creative solutions to anynumber of business questions You can even contribute by sending us your owntips
wwwbusinessobjectscomformstipsandtricks_loginasp
Product documentation
We regularly update and expand our documentation and multimedia offeringsWith a valid maintenance agreement you can get the latest documentation ndash inseven languages ndash on the Online Customer Support (OCS) website
Developer Suite Online
Developer Suite Online provides documentation samples and tips to thosecustomers with a valid maintenance agreement and a Developer Suite licensevia the Online Customer Support (OCS) website
Send us your feedback
Do you have a suggestion on how we can improve our documentation Is theresomething you particularly like or have found useful Drop us a line and we willdo our best to ensure that your suggestion is included in the next release of our documentation documentationbusinessobjectscom
NOTE
If your issue concerns a Business Objects product and not the documentationplease contact our Customer Support experts For information about Customer Support visit wwwbusinessobjectscomservicessupporthtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1196
Universal Drill Through Service Guide 11
Services
Services
A global network of Business Objects technology experts provides customer support education and consulting to ensure maximum business intelligencebenefit to your business
How we can support you
Business Objects offers customer support plans to best suit the size andrequirements of your deployment We operate three global customer supportcenters
bull Americas San Jose California and Atlanta Georgia
bull Europe Maidenhead United Kingdom
bull Asia Tokyo Japan and Sydney Australia
Online Customer Support
Our Customer Support website is open to all direct customers with a currentmaintenance agreement and provides the most up-to-date Business Objectsproduct and technical information You can log update and track cases from thissite using the Business Objects Knowledge Base
Having an issue with the product
Have you exhausted the troubleshooting resources at your disposal and still not
found a solution to a specific issueFor support in deploying Business Objects products contact WorldwideCustomer Support at wwwbusinessobjectscomservicessupporthtm
Looking for the best deployment solution for your company
Business Objects consultants can accompany you from the initial analysis stageto the delivery of your deployment project Expertise is available in relational andmultidimensional databases in connectivities database design tools
customized embedding technology and more
For more information contact your local sales office or contact us atwwwbusinessobjectscomservicesconsultinghtm
Looking for training options
From traditional classroom learning to targeted e-learning seminars we can offer a training package to suit your learning needs and preferred learning style Findmore information on the Business Objects Education websitewwwbusinessobjectscomserviceseducationhtm
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1296
12 Universal Drill Through Service Guide
Maximizing Your Information Resources
Useful addresses at a glance
Address Content
Business Objects Documentation
wwwbusinessobjectscomservicesdocumentationhtm
Overview of Business Objects documentation Linksto Online Customer Support Documentation Supply
Store Documentation Roadmap Tips amp TricksDocumentation mailbox
Business Objects Documentation
mailbox
documentationbusinessobjectscom
Feedback or questions about documentation
Product documentation
wwwbusinessobjectscomservicessupporthtm
The latest Business Objects product
documentation to download or view online
Business Objects product information
wwwbusinessobjectscom
Information about the full range of BusinessObjects products
Developer Suite Online
wwwtechsupportbusinessobjectscom
Available to customers with a valid maintenanceagreement and a Developer Suite license via theOnline Customer Support (OCS) website Providesall the documentation latest samples kits and tips
Knowledge Base (KB)
wwwtechsupportbusinessobjectscom
Technical articles documents case resolutions
Also use the Knowledge Exchange to learn whatchallenges other users ndash both customers andemployees ndash face and what strategies they find to
address complex issues From the KnowledgeBase click the Knowledge Exchange link
Tips amp Tricks
wwwbusinessobjectscomformstipsandtricks_loginasp
Practical business-focused examples
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1396
Universal Drill Through Service Guide 13
Useful addresses at a glance
Online Customer Support
wwwtechsupportbusinessobjectscom
wwwbusinessobjectscomservices
Starting point for answering questions resolvingissues
Information about registering with Worldwide
Customer Support
Business Objects Education Services
wwwbusinessobjectscomserviceseducationhtm
The range of Business Objects training options andmodules
Business Objects Consulting Services
wwwbusinessobjectscomservicesconsultinghtm
Information on how Business Objects can helpmaximize your business intelligence investment
Address Content
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1496
14 Universal Drill Through Service Guide
Maximizing Your Information Resources
About this guide
This guide describes the Universal Drill Through Service and associated toolUDS Designer
Audience
This guide is intended for administrators who need to set up drill through betweenWebIntelligence reports
Conventions used in this guide
The conventions used in this guide are described in the table below
Convention Indicates
This font Code SQL syntax computer programs For example Select(CountryCountry Id)This font is also used for all paths directoriesscripts commands and files for UNIX
Some code
more code
Placed at the end of a line of code the symbol ( )indicates that the next line should be enteredcontinuously with no carriage return
$DIRECTORYPATHNAME The path to a directory in the Business Objectsinstallationconfiguration directory structure For
examplebull $INSTALLDIR refers to the Business Objects
installation directory
bull $LOCDATADIR refers to a subdirectory of theBusinessObjects installation directory calledlocData
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1596
c h a p t e
r
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1696
16 Universal Drill Through Guide
About Drill Through
Overview
Universal Drill Through Service (UDS) is a technology that allows users to drilldown into a WebIntelligence Relational report or another WebIntelligence OLAPreport from a WebIntelligence OLAP report With UDS users can seamlesslycarry over their data analysis from report to report The user selects the cell or cells in the OLAP cube for drilling and UDS presents them with a list of WebIntelligence Relational or OLAP reports that provide more detailed drill downdata UDS lsquoremembersrsquo the point at which the user left the cube and carries thiscontext across to the target WebIntelligence report
UDS allows users to move from navigation of summarized OLAP cubes to moredetailed query reporting and analysis within the same framework Users canperform dynamic multidimensional cube analysis and access lower level details
stored in the target reportAs administrator you need to map the source OLAP cube to the universe or target OLAP cube and create reports that are appropriate for the differentcontexts at which the user might drill through from report to report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1796
Universal Drill Through Guide 17
What does the administrator do
What does the administrator do
As the UDS Administrator it is your job to ensure that drill through is seamlessfor the user You need to carry out some or all of the following tasks to ensurethis seamlessness
bull Design a star- or snowflake-schema database that will consolidate all the dataneeded by the universe-based reports
bull Migrate data from RDBMSs andor flat files into this database
bull Design a universe for target user reports
bull Create a translation map using UDS Designer that tells the Drill ThroughService how to translate the context from the OLAP cube to the universe onwhich the WebIntelligence Relation target reports are based
bull Build target reports built against the target universe
Design a star- or snowflake-schema databaseIf your source cube is already based on a star- or snowflake-schema databasethen you will not need to design a database specifically for drill through In thiscase you will use the existing database and you will also have no need for datamigration
Design a universe for target user reports
If your users are drilling from OLAP cubes to universe-based relational reports
you need to design a WebIntelligence universe whose structure maps to thestructure of the source cube The universe must contain objects that correspondto the levels hierarchies and members in the cube in all contexts at which theuser will be able to drill through from the cube
Create a translation map
A translation map is an XML file that tells the Drill Through Service how totranslate the context from the source to the target report when the user drills
through Because maps are XML you could use any XML editing tool to createone However you are much more likely to use UDS Designer a specializedXML tool designed specifically for building translation maps
You build a map by assigning objects to a hierarchical map model and settingvarious properties associated with these objects
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1896
18 Universal Drill Through Guide
About Drill Through
Design target reports
You build WebIntelligence target reports against the target universe or OLAPcube that contains detailed data The Drill Through Service opens these reportsautomatically when the user chooses to drill through from a context specified ina translation map Target reports provide data at a more detailed level than thedata available in summarized and aggregated OLAP cubes
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 1996
Universal Drill Through Guide 19
What does the administrator need to know
What does the administrator need to know
As the large number of different tasks in the previous section indicates you needa wide range of knowledge and experience to set up a UDS environment Youshould have experience in most or all of the following areas depending on theenvironment in which you are setting up drill through
bull Advanced SQL
bull Designing star or snowflake database schemas
bull Data migration
bull OLAP cubes
bull Creating OLAP cubes
bull Designing and building BusinessObjects universes
bull Creating universe-based WebIntelligence reports
You can get further information from the following sources For information onstar or snowflake schema databases and data warehouses see Ralph KimballThe Data Warehouse Toolkit Practical Techniques for Building Dimensional
Data Warehouses (John Wiley amp Sons 1996) and The Data Warehouse Lifecycle
Toolkit Tools and Techniques for Designing Developing and Deploying Data
Warehouses (John Wiley amp Sons 1998) For creating OLAP cubes usingHyperion Integration Server see the Hyperion Integration Server Desktop OLAP
Model Userrsquos Guide For designing and building BusinessObjects universes seethe BusinessObjects Designerrsquos Guide For creating universe-based
WebIntelligence reports see the Getting Started with WebIntelligence guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2096
20 Universal Drill Through Guide
About Drill Through
What is drill through
Drill through provides integration between data sources that contain related butdifferent data stored in different data sources The scenarios that drill throughcurrently supports are
This means that the following general drill through scenarios are possible
bull OLAP to relational (BusinessObjects universe)
bull OLAP to OLAP
In the OLAP to OLAP scenario the target cube could bebull a different cube in a different database
bull adifferent cube in the same database
bull the same cube
When the user drills through from source to target drill through carries thecontext of the source report to the target report
A user can drill through from a value cell or cells or a dimension member or
members When the user drills on value cells drill through includes thedimension members from the row and column axes that intersect at the cell(s)When the user drills on member(s) drill through includes only that member(s) Inboth cases drill through also includes members from dimensions on the filter axis
Drill through provides integration between data sources that contain related butdifferent data In most enterprises data is stored in numerous sources but it isoften necessary to access more than one source when analyzing this data
Without drill through this is a tedious and time-consuming task On reaching thelimit of the data in one source the analyst needs to do the following
1 Identify the data source containing the data necessary for further analysis
2 Start the query tool used to access this data
3 Navigate the data to arrive at the same lsquocontextrsquo reached in the first datasource
4 Continue data analysis using the new query tool
Source Target
Microsoft and EssbaseDB2 OLAP Relational (BusinessObjectsuniverses)
Microsoft and EssbaseDB2 OLAP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2196
Universal Drill Through Guide 21
What is drill through
EXAMPLE
What are the unit sales of different brands of soccer cleats in 2001 Q1
In this example the data analyst needs to work with two data sources an OLAPcube that provides unit sales data down to the level of the type of sportsequipment (soccer cleats golf shoes baseball uniforms) and a WebIntelligenceuniverse that breaks down sales by each different brand of cleat shoe uniform
etc Using the cube the analyst has drilled down as far as producing a reportshowing the sales of cleats by quarter However he now wishes to investigatefurther the sales of individual brands of cleat by quarter To do this he must
1 Start WebIntelligence
2 Load the appropriate universe containing data down to the level of unit salesof cleats by quarter
3 Create a report showing sales of soccer cleats by quarter for the year 2001
4 Drill down into this data to analyze sales figure by quarter by brand
With drill through this complex process becomes straightforward Whilebrowsing the data in the OLAP cube the analyst simply elects to drill-down intothe data showing unit sales of brands by quarter Even though this data is not inthe cube Universal Drill Through Service (UDS) opens the appropriateWebIntelligence report built against the appropriate universe and passes theanalystrsquos lsquocontextrsquo in the OLAP cube to this report The analyst can then continuedrilling into the data in the WebIntelligence report
Drill through components
The following sections describe the components that make up drill through
Universal Drill Through Service
Universal Drill Through Service is the name for the technology that translates auserrsquos context in a source report to a target report using the information providedin a UDS map (see the section UDS maps below)
OLAP source cube
The source cube contains data at an aggregated level
OLAP target cube
The target cube contains data at a lower level of detail
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2296
22 Universal Drill Through Guide
About Drill Through
UDS maps
Maps are files that tell the Drill Through Service exactly how to carry the drillcontext from the source cube to the target universe (see Chapter 5 BuildingTranslation Maps on page 81) You create UDS maps using UDS Designer (seebelow) For more details on how UDS maps fit into the overall drill througharchitecture see Drill through architecture on page 22
UDS Designer
UDS Designer is the graphical tool used to build UDS maps (see Chapter 5 Building Translation Maps on page 81)
Target database
In an OLAP-to-relational scenario the target database is the database on whichthe target universe is built Ideally this database should be configured in a star or snowflake schema (see Designing the Target Database on page 78) This
makes mapping OLAP cube members to universe objects simpler However theonly hard criterion for target database design is that it must be possible to mapthe members in the OLAP cube to the objects in the target universe
Target universe
In an OLAP-to-Relational scenario the target universe is a Business Objectsuniverse built against the target database It must be configured to match thestructure of the source cube (see Drill Through Requirements on page 65)
Target reports
Target reports are the WebIntelligence reports invoked by the Drill ThroughService when the analyst drills outside the data contained in the source cubeEach possible lsquocontextrsquo at which you wish to allow the analyst to drill through tothe target universe must be covered by a target report (see CreatingWebIntelligence Target Reports on page 119) A general rule of thumb is thateach measure in the OLAP cube will require its own target report This is becausethe OLAP measures contain data at a summarized level the reportcorresponding to each measure therefore provides more detailed data for thatmeasure
Drill through architecture
It is possible to examine the drill through architecture from several angles overallarchitecture WebIntelligence architecture and runtime architecture
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2396
Universal Drill Through Guide 23
What is drill through
Overall drill through architecture
The following diagram illustrates the relationships between the differentcomponents of drill through
Drill through implementation in WebIntelligence
The following diagram illustrates the relationships between the differentcomponents of drill through as implemented in WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2496
24 Universal Drill Through Guide
About Drill Through
Run time architecture
The following diagram shows the run time implementation of the drill througharchitecture This highlights the two data packages that the Drill Through Serviceuses the drilled data package and the translation map
Why drill through was difficult before
Until recently databases across an enterprise were rarely synchronizedmeaning that the dimensions and levels in an OLAP cube would be unlikely to
map to a relational data source within the same enterprise In this situation drillthrough is extremely complex time-consuming and maintenance-heavybecause the source and target data sources do not share similar metadata
As a result drill through has thus far existed in two niches only complex custom-built drill through solutions or proprietary drill through solutions provided byvendors Proprietary solutions solve the problem of incompatible metadata at thecost of supporting drill through from the vendorrsquos cubes only to the vendorrsquosrelational source only
Furthermore different vendorsrsquo OLAP and relational solutions differ considerablyin their metadata models Thus a single drill through model was not feasible asit would need to account for the metadata models of all the supported source andtarget data sources
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2596
Universal Drill Through Guide 25
What is drill through
Why drill through is possible now
Today database designers recognize the need to synchronize data sourcesacross an enterprise In particular they are now basing OLAP cubes on relationaldata sources If a cube is built from a star- or snowflake-schema relationalsource both the cube and the relational database share similar metadata Thisis essential if drill through is not to be prohibitively complex
How Business Objects enables drill throughWith WebIntelligence Business Objects has both a standard OLAP model and astandard model for accessing relational data (the BusinessObjects universe)This greatly simplifies communication between OLAP-OLAP or OLAP-relationaldata sources because drill through needs to deal with at most two metadatamodels - the BusinessObjects OLAP model and the BusinessObjects relationalmodel (universe)
OLAP object model
WebIntelligence uses a universal OLAP object model to access OLAP cubeshosted on many different OLAP servers By placing this layer of abstractionbetween the OLAP server and the client tool WebIntelligence removes thecomplexity from querying OLAP cubes It sees cubes hosted on different OLAPservers through the same object model and the object model handles thecomplexity of translating user actions into MDX the query language understoodby OLAP servers
Business Objects universe
A universe - Business Objectsrsquo patented rsquosemantic layerrsquo - provides a layer of abstraction between WebIntelligence and relational data sources in the sameway that the OLAP model insulates WebIntelligence from the OLAP cube Theuniverse abstracts the database structure into a set of hierarchically-organizedobjects that represent the real-world objects about which the database storesdata The universe translates user queries into SQL shielding the user from the
often complex database-specific structures in which data about these objects arestored
Because the hierarchical nature of a WebIntelligence universe closely resemblesthe structure of an OLAP cube drill through is a good-fit technology for WebIntelligence
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2696
26 Universal Drill Through Guide
About Drill Through
NOTE
For more information on universes see What is a Business Objects Universeon page 70
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2796
Universal Drill Through Guide 27
Setting up drill through
Setting up drill through
In order to set up a Drill Through environment you need to carry out the stepsdescribed in What does the administrator do on page 17
Example drill through environment
WebIntelligence comes with a comprehensive set of materials to demonstrate a
Drill Through environment These arebull Source cubes
bull Source report (OLAP Drill-Through Report)
bull Target universe database (MS Access)
bull Target universe (Retail2002)
bull Target Report (MonthCustNameProdDepSales)
bull Target report
This manual will refer to this material for all examples and demonstrations For further details see Installing the Drill Through Samples on page 33
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2896
28 Universal Drill Through Guide
About Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 2996
c h
a p t e
r
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3096
30 Universal Drill Through Guide
Drill Through Requirements
Overview
This chapter looks at the design requirements for a successful drill throughenvironment For Drill Through to function correctly each component must bedesigned according to specific guidelines and the designs of the variouscomponents are interrelated For example if you are using OLAP-relational drill
through the design of the universe on which the target reports are built needs tomirror the design of the source OLAP cube and the database should be in a star schema to facilitate the universe design
The design requirements for a drill through environment are as follows
For OLAP-relational drill through
bull The target relational database is ideally in a rsquodenormalizedrsquo a star or snowflake schema although any schema that supports mapping to the OLAP
cube is workable (The following sections describe the differences betweennormalized and star schema databases)
bull The classes and objects in the target universe map to the levels anddimensions in the source OLAP cube
For OLAP-to-OLAP drill through
OLAP-to-OLAP drill through is very similar to OLAP-to-relational drill throughexcept that the target universe objects are replaced by target OLAP levels
The rest of this chapter examines the issues surrounding relational databases inOLAP-to-relational drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3196
Universal Drill Through Guide 31
Normalized relational databases
Normalized relational databases
In 1970 database researcher EF Codd formulated a series of rules for thedesign of relational databases Further researchers added additional rulescollectively these rules are referred to as normalization rules Normalization isdesigned to eliminate data rendundancy (the storing of the same piece of data inmore than one place in a database) and therefore reduce the risk of errors when
writing to and reading from a database In a correctly-normalized database eachtable stores data about one thing and one thing only The lsquothingsrsquo in questionmight be tangible like employees or departments or more abstract likerelationships or events Coddrsquos earlier rules deal with tangible things while thelater rules deal with the abstract
A normalized relational database is ideal for data input However the retrieval of data from such a database is often slow Because the data has been normalizedinto many tables a complex query might require data from a large number of
tables This process of joining the data from different tables in order to present aquery result is an intensive database operation
Normalized databases are usually found in On-Line Transaction Processing(OLTP) systems the primary purpose of which is data entry Car rentalreservation systems or Point of Sale (POS) systems are examples of OLTP
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3296
32 Universal Drill Through Guide
Drill Through Requirements
Star schemas
The star schema is an alternative database design that is optimized for dataoutput Star schemas violate normalization rules spectacularly but they alsospeed up data retrieval by a significant degree As a general rule they are usedstrictly for reporting rather than data input
Star schema databases are populated from OLTP databases The OLTP data is
transformed to fit into the star schema and the database is refreshed periodicallyfrom the OLTP systems
The star schema maps closely to the structure of an OLAP cube As a result datain OLAP cubes is often drawn from data warehouse databases designed as star schemas
Fact tables dimension tables and hierarchies
A star schema consists of a central lsquofactrsquo table joined to numerous lsquodimensionrsquotables which radiate around it The fact table contains numeric data with whichyou can measure business performance for example numbers of products sold
Dimension tables join to the fact table and relate these measures to differentaspects of the business A star schema almost always includes a table or tablesthat store time data because the primary purpose of such databases is to allowfor the analysis of trends over time For example a database might contain TimeProduct and Customer dimensions linking to a fact table storing unit sales In this
case it would be possible to examine unit sales by product customer and timeperiod
Dimensions usually contain hierarchies As you move down through thehierarchy its data becomes progressively more specific For example a Productdimension might contain hierarchy levels such as Product Category ProductSubcategory and Brand Name A Product dimension table containing all this datais a good example of the kind of highly denormalized table found in star schemasIn a normalized structure these three distinct lsquothingsrsquo would probably be stored
in three tables
Snowflake schemas
A snowflake schema is similar to a star schema except that the hierarchies in thedimension table are lsquonormalized outrsquo to some extent
Snowflake schemas are less common because the database space saved bynormalization is small (in a large star schema database approximately 95 of the space is occupied by the fact table) and the joining of the snowflaked tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3396
Universal Drill Through Guide 33
Star schemas
adds additional overhead The example database is predominantly in a star schema although the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3496
34 Universal Drill Through Guide
Drill Through Requirements
What is a Business Objects universe
Universes are Business Objectsrsquo patented rsquosemantic layerrsquo that sits between theBusinessObjects client tool and its relational data source Universes insulateusers from the complexities of SQL and relational data structures by presentingthe data in terms familiar with the user
The hierarchical organization of data in universes is very similar to the
organization of data in an OLAP cube which makes mapping between the twodata sources possible
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3596
Universal Drill Through Guide 35
How cubes and universes relate
How cubes and universes relate
OLAP cubes and Business Objects universes are both hierarchical structuresthat are used to identify specific pieces of numerical data for example thenumber of soccer cleats sold in California in Q2 2001 To find this information inan OLAP cube the analyst would explore the Customer dimension in order to findCalifornia the Product Dimension in order to find Cleats and the Accounts
dimension in order to find the unit sales To do the same information in aWebIntelligence universe the analyst would navigate to the California objectwithin the Customer class the Soccer Cleats object within the Product class andthe Unit Sales measure The classes and objects in universes therefore map tothe dimensions and hierarchy levels in an OLAP cube
The basic type OLAP-relational mapping provided by UDS is level translationrdquoIn level translation a dimension level is mapped to a universe object where all themembers for a dimension level map to a universe object and the member namecorresponds exactly to the universe object value (eg 2000Q1 = 2000Q1)
Design requirements
The following sections examine the structures of the cube universe anddatabase in the demonstration material more closely in order to demonstrate thestructure of the components in a drill through environment
Relational database
Ideally the database should be in a star or snowflake schema although anyschema that allows mapping of cube members to universe objects is workableThe following figure shows the schema for the example MS Access database that
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3696
36 Universal Drill Through Guide
Drill Through Requirements
ships with WebIntelligence This database is predominantly in a star schemaalthough the Product dimension is lsquosnowflakedrsquo into the PRODUCT andPRODUCT_CLASS tables
Making member names unique
When building your database you need to account for the fact that members inEssbaseDB2 OLAP cubes must be unique throughout the entire cube For example a Time dimension containing data for multiple years cannot containmultiple members called lsquoMarchrsquo You solve this by creating a composite namefor such members A composite name is built from the member name qualifiedby the names of parent members For example the member lsquoMarchrsquo in the year 2001 could be named lsquo2001Q103rsquo In this case the month is qualified by both thequarter and the year in order to make the member name unique
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3796
Universal Drill Through Guide 37
How cubes and universes relate
You need to account for this when designing your database In the exampledatabase the TIME_PERIOD table contains the columns ess_month (in the formlsquo2001Q103rsquo) to uniquely identify the month and ess_quarter (in the formlsquo20001Q1rsquo) to uniquely identify the quarter
NOTE
You can also solve the problem of unique member names at the universe level
See the next section
Universe
The classes objects and measures in the universe must match the dimensionslevels and measures in the source cube However the universe can containadditional items not in the source cube The table below shows examplemappings from the demo universe and cube shipped with WebIntelligence
You can see this mapping by examining the demonstration translation mapsupplied with WebIntelligence Open the map using ltsmalcapgtUDS Designer
(see the chapter Building Translation Maps on page 81 for instructions on usingthis tool)
Cube Universe
Dimension Product Class Product
Level Product Family Object Product Family
Member Sportswear Value Sportswear
The translation mapmaps the cube level
Product Family to the
universe classobject
ProductProduct
Family
rsquoSportsWearrsquo is a
member in the cube
level and a value of
the universe object
38 U i l D ill Th h G id
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3896
38 Universal Drill Through Guide
Drill Through Requirements
Designing for unique members
If your source cube is an EssbaseDB2 OLAP cube you will need to take thecubersquos unique member names into account In EssbaseDB2 OLAP eachmember name must be unique throughout the entire cube Cube designers solvethis by qualifying member names with the names of one or more parentmembers
The time dimension members are often named in this way If the time dimension
contains data for more than one year the names of the months in the year mustbe qualified with the year to make them unique For example the March 2001member cannot be named rsquoMarchrsquo it needs a name like rsquo2001Marchrsquo
Creating universe objects to map to unique members
You can create universe objects that map to the unique members in a cubeBecause universes provide a layer of abstraction between the database and theuser you can add objects to the universe that derive from various objects in the
database For example you could create a universe object called EssbaseQuarter that concatenates the quarterrsquos parent year followed by the quarter inthe form 2000Q1 This is what the object definition would look like in Designer
Universal Drill Through Guide 39
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 3996
Universal Drill Through Guide 39
How cubes and universes relate
Cube
There are no restrictions on cube design other than the normal restrictionsimposed by EssbaseDB2 OLAP (for example the need to have unique member names) The cube design carries over to the design of the universe and targetdatabases and places restrictions on those components as described in theprevious sections
40 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4096
40 Universal Drill Through Guide
Drill Through Requirements
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4196
c h
a p t e
r
Designing the Target Universe
42 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4296
g
Designing the Target Universe
Overview
This chapter describes the WebIntelligence target universes on which you baseyour drill through target reports in OLAP-to-Relational drill through
Universal Drill Through Guide 43
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4396
Designing the target database
Designing the target database
If you are basing your target universe on the same database that populates your source cube you do not need to design a target and populate a target database
If you are designing a new database for your target universe you must be awarethat for the OLAP dimensions that you wish the user to be able to drill throughfrom the target universe needs to map exactly to the structure of the OLAP cube
The ideal design for the underlying database for this universe is a star or snowflake schema These schemas map closely to OLAP cubes (and are oftenused to feed data to cubes in OLAP databases) as a result such a schema isalso ideal for a universe that maps to the structure of an OLAP cube
NOTE
The target database does not need to map to the structure of the whole sourcecube just to those dimensions that you wish users to be able to drill through from
After you have designed your database you will need to populate it How you dothis depends on factors such as the operating system and RDBMS on which thedatabase is hosted If you use views in the target database you do not need toperform as much data migration
44 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4496
Designing the Target Universe
Designing a star schema database
In a star schema the numeric data (the Accounts dimension in an EssbaseDB2OLAP cube) is stored in a central lsquofactrsquo table The dimension tables (equivalent tothe dimensions in an OLAP cube) radiate around this fact table and are joined toit via foreign keys (See Star Schemas on page 68 for more details) The exampledrill through database that ships with this guide (see Example Drill Through
Environment on page 63) is arranged almost entirely in a star schema althoughthe Product dimension has been split (or lsquosnowflakedrsquo) into the PRODUCT andPRODUCT_CLASS tables Databases in which the dimensions are partly re-normalized into separate tables are known as snowflake-schema databases
EssbaseDB2 member naming restrictions
In an EssbaseDB2 OLAP cube each member name must be unique throughoutthe entire cube EssbaseDB2 OLAP cube designers typically work around this
restriction by qualifying the name of the member with the names of its parentmembers
For example it is not possible to have a member called lsquoQ2rsquo if the cube containsdata for more than one Q2 (which is likely) In this situation the cube designer could qualify the name of the quarter with the name of the year in order to makethe member name unique The member name for Q2 of 2001 would be 2001Q2
You can account for this in the database by adding additional columns wherenecessary to allow for mapping to uniquely named-members You can see this in
the TIME_PERIOD table of the example database which contains the columnsess_quarter (uniquely-named quarters) as ess_month (uniquely-namedmonths)
NOTE
You can also account for unique members at the universe level See Creatinguniverse objects to map to unique members on page 74 for more details
The Accounts dimension
An EssbaseDB2 Accounts dimension might contain data that is not in therelational data source The Accounts dimension can contain aggregates whilethe relational data might contain the lowest-level numerical data only In thisscenario it is not possible to map the Accounts dimension to the database
Universal Drill Through Guide 45
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4596
Designing a star schema database
This should not present an issue as the mapping of an Accounts dimension israrely useful The purpose of Drill Through is to allow the user to retrieve lower-level numerical data from the database than is available in the cube To do thisDrill Through needs to map dimensions and levels between the cube anddatabase Numerical data is retrieved based on the dimensions and levels thatthe user is querying - in itself it is not relevant to drill through context
46 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4696
Designing the Target Universe
Creating the target universe from the database
In the target universe the classes must map to the dimension in the OLAP cubethe objects must map to the levels and the values of those objects must map tothe cube members The following table shows some example correspondancesbetween the example cube and universe shipped with WebIntelligence
Cube Term Cube Data Universe Term Universe Data
Dimension lsquoProductrsquo Class lsquoProductrsquo
Level lsquoBrand Namersquo Object(dimension or detail)
lsquoBrand Namersquo
Member lsquoCleatsrsquo Value lsquoCleatsrsquo
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4796
c h
a p t e
r
Building Translation Maps
48 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4896
Building Translation Maps
Overview
This chapter describes UDS translation maps and how to build them using UDSDesigner Translation maps tell the Drill Through Service how to translate thecontext from an OLAP source cube to a universe (OLAP-to_relational drillthrough) or OLAP target cube (OLAP-to-OLAP drill through) Drill through
currently supports Microsoft SQL Analysis Services and EssbaseDB2 OLAP asOLAP sources
Universal Drill Through Guide 49
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 4996
What is UDS Designer
What is UDS Designer
UDS Designer is a graphical tool that you use to build translation mapsTranslation maps are XML files UDS Designer is a specialized XML editor specifically tailored to building maps However you can build translation mapswith any XML editing tool
[UDS Designer installation details]
50 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5096
Building Translation Maps
What are translation maps
A translation map is an XML file (with the extension UDM) that tells the DrillThrough Service how to translate the context from the source cube to the targetWebIntelligence report (which can be based on a universe or an OLAP cube)when the user drills on a cell or cells It describes how the values in the cuberelate to the values in the report
You build a translation map by specifying which structures in the originating datasource you want to translate and what their equivalents are in the target datasource Because the originating data sources are OLAP cubes this means thatthe map is structured like a cube it consists of dimensions hierarchies andlevels
There are two basic translations possible within a map level translations andmember translations
Level translationsA level translation is a general rule that applies to all members at a particular levelin an OLAP cube It has the following components
bull Target universe class - in an OLAP to relational translation the universe classthat an OLAP member translates to
bull Target universe objects - in an OLAP to relational translation the universeobjects that an OLAP member translates to
bull Target OLAP level - in an OLAP to OLAP translation the OLAP level that anOLAP member translates to
bull Translation rule - a rule that specifies how to manipulate the member whenpassing it from the source to the target
bull Parent translation - an additional translation rule used to qualify the member with its parent member or members where the name of the member alone isnot enough to uniquely identify it in the universe
Member translations
You use member translations to exclude specific members that you do not wantto be translated as part of a level translation For example the dynamic timeseries members in an Essbase cube (Quarter to Date) have no equivalent in arelational database To prevent this member from being translated you assign amember translation to it and disable translation for the member
Universal Drill Through Guide 51
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5196
What are translation maps
What is in a translation map
A translation map contains the following information
bull Details of the originating data source (OLAP cube)
bull Details of the target data source (WebIntelligence report)
bull Details of each dimension and its associated hierarchies and levels andwhether these are enabled for drill through
bull The level and member translations associated with the levels
bull The target reports based on the target cube or universe
Workflow for building a translation map
To build a translation map you do the following
Step Description For further
information see
Import the source cube Loads the source cubemetadata into UDSDesigner
Importing the sourcecube on page 56
Import the targetuniverse
Loads the targetuniverse metadata intoUDS Designer
Importing the targetuniverse on page 58
OR
Import the target cube Loads the target cubemetadata into UDSDesigner
Importing the targetcube on page 59
Add the translations tothe map
Adds the translationsthat describe the cube-to-universe mapping tothe translation map
Specifying member translations on page 67
Specify the targetreports
Adds theWebIntelligence targetreports to the translationmap
Specifying target reportson page 73
52 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5296
Building Translation Maps
Import the source cube
When you load the source OLAP cube you make its metadata (dimensionshierarchies levels and members) available to UDS Designer You can then addthese metadata objects to the translation map
Import the target universe
When you load the target universe you make its metadata (classes and objects)available to UDS Designer for the same reason
Import the target cube
When you load the target cube you make its metadata available to UDSDesigner
Add the translations to the map
This is the key process in which you tell the Drill Through Service how to translatethe context from the source cube to the target WebIntelligence report You do this
by adding translation objects to the map and setting their properties
Specify WebIntelligence target reports
After you have added all the translations to the map you specify the targetWebIntelligence reports to which the map applies These are the reports that theuser will drill through to from the source OLAP cube
Universal Drill Through Guide 53
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5396
Mapping from cubes to universes
Mapping from cubes to universes
Data is structured in universes in a design that is very similar to the structure of OLAP cubes The dimensions levels and members in a cube correspond to theclasses objects and object values in a universe For example the Customer dimension in the demonstration cube contains the City level and one of themembers of this level is lsquoSan Diegorsquo This maps to the Customer class in thedemonstration universe which contains the City object One of the values of thisobject is lsquoSan Diegorsquo
For drill through to work you must be able to map the structure of the source cubeto the structure of the target universe This means that the values of thedimensions levels and members in the cube must correspond exactly to theclasses objects and values in the universe This simple mapping is known asstructure mapping
There are two flavors of structure mapping The simpler form is 11 mapping and
the more complicated form is qualified 11 mapping
Simple 11 mapping
In simple 11 mapping the cube members map exactly to equivalent objects inthe WebIntelligence universe The table below gives examples from the Rtl2002cube and Rtl2002 universe supplied with the Drill Through Service
In simple 11 mapping there is no need to qualify the source member in thetranslation map because the target objects in the universe are unique and
unambiguous
Qualified 11 mapping
In qualified 11 mapping the target objects in the universe are not unique In order to map the source OLAP members to the target universe objects unambiguouslyit is necessary to qualify the member with the name of one or more of its parentmembers This situation commonly occurs when translating members in the Timedimension If a relational data source contains data for more than one year the
child objects of the year (for example the quarters and months) will not be uniquein the database March 2001 and March 2002 will both be stored as rsquoMarchrsquo
Because a translation map must uniquely associate each cube member with acorresponding universe object you need to use a Parent Translation object toqualify the name of the member with the name of its parent
54 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5496
Building Translation Maps
Building translation maps using UDSDesigner
This section describes how to build a UDS Map using UDS Designer The UDSDesigner main interface is shown below
The Properties areaallows you to change
the properties of the
currently-selected
object in the
translation map
The OLAP SourceInformation pane
shows the
dimensions
hierarchies and
levels in the
source cube
TheUniverse Target
Information pane
shows the classes
and objects in the
target universe
The Map Model
pane displays the
translation map
You use the Add and Delete
buttons to add or remove ob-
jects from the translation
map
The Mapping Parts
pane contains thedifferent objects
that you can add toa translation map
Universal Drill Through Guide 55
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5596
Building translation maps using UDS Designer
Navigating translation maps
You navigate a translation map in the Map Model pane UDS Designer displaysthe map hierarchically in a tree format You select objects in this hierarchy andchange their properties in the Properties area When you select an object theProperties area changes to display the properties that are relevant to that object
56 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5696
Building Translation Maps
Importing data sources
Your first step in creating a translation map is to import the metadata from boththe source cube and the target cubeuniverse To do this you need to connect toboth the OLAP database containing the cube and the WebIntelligence repositoryor OLAP database containing the universetarget cube
NOTE
When working with a previously-saved translation map that you open using UDSDesigner it is not possible to change the data sources
Importing the source cube
To import the source cube do the following
1 Select New from the File menu
The Map Types dialog box appears
2 Click OLAP to Relational or OLAP to OLAP then click OK
Universal Drill Through Guide 57
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5796
Importing data sources
The Olap Source Information dialog box appears
3 Enter the name of the OLAP server in the OLAP Server box
4 Select the OLAP server type from the Server Type dropdown list
5 Enter your OLAP server username and password in the User Name andPassword boxes (This step does not apply to MS OLAP)
6 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
7 Select the database containing the cube you want to access from theDatabases dropdown list box
8 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
9 Select the cube that you want to connect to from the Cubes dropdown list box
10Click Load Cube
11The OLAP Source Information pane is populated with the dimensions levelsand hierarchies in the source cube In addition the translation map ispopulated with all the dimensions hierarchies and levels in the cube
58 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5896
Building Translation Maps
NOTE
You can also import a source cube when you already have a translation maploaded In this case UDS Designer does not automatically assign all thedimensions hierarchies and levels to the translation map
Importing the target universe
If you selected OLAP to relational translation the Choose Universe dialog boxopens automatically after you have loaded the source cube
Enter your User Name and Password and click OK If the connection to therepository succeeds you will see the Universe Target Information dialog box
If you cannot connect to the repository check that the repository database isavailable and that you have the correct middleware installed to access it
Select a universe from the Universes dropdown then click Load Universe UDSDesigner populates the Universe Target Information with the classes and objectsfrom the universe
Universal Drill Through Guide 59
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 5996
Importing data sources
Importing the target cubeIf you selected OLAP to OLAP translation the OLAP Source Information dialogbox appears again You follow the procedure described above to connect to thesource cube
Security
Drill through security is handled entirely by the originating and target query toolsThe displayed cube members and values are based on the user ID used toconnect to the OLAP cube Universe security is governed entirely by the user IDused to connect to WebIntelligence
60 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6096
Building Translation Maps
Creating a translation map
Once you have loaded the source and target metadata you are ready to startbuilding your translation map When you loaded the cube metadata UDSDesigner automatically loaded all the cube dimensions hierarchies and levelsinto the translation map Now when you select an object in the Map Model panethe Properties area on the right displays the properties of the selected object TheProperties area changes to reflect the properties appropriate to the object you
select You can then modify these properties
You can add additional objects to be associated with an object in the translationmap These objects come from three sources
bull The OLAP Source Information pane
bull The Universe Target Information pane
bull The Mapping Parts pane
To add an object to the translation map do the following
1 Select the object in the translation map
2 Select the object to be added in the OLAP Source Information UniverseTarget Information or Mapping Parts panes
3 Click the Add button to add the object to the translation map
4 Use the Properties area to specify the properties of the added object
Adding deleting replacing and enabling dimensionsThe Map Model pane shows dimensions hierarchically beneath the map objectin the Map Model pane You can perform four tasks relating to a dimensions adda new dimension delete a dimension replace a dimension and enabledisablean existing dimension
Universal Drill Through Guide 61
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6196
Creating a translation map
62 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6296
Building Translation Maps
Adding removing and replacing dimensionsYou can add remove or replace dimensions in the translation map To add adimension
1 Select the Map object in the Map Model pane
2 Select the dimension in the OLAP Source Information pane
3 Click Add
The dimension is added to the translation map
Universal Drill Through Guide 63
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6396
Creating a translation map
To remove a dimension1 Select the dimension in the Map Model pane
2 Click Remove
The dimension is removed from the translation map
To replace a dimension
1 Select the dimension to be replaced in the Map Model pane
2 Select the replacing dimension in the OLAP Source information pane
3 Click AddThe dimension is replaced with the new dimension from the source cube
Enabling dimensions for translation
When you load the source cube for a new translation map UDS Designer addsall the cube dimensions to the translation map Initially all dimensions are notenabled for translation You need to enable the dimensions that you wish to betranslated To enable a dimension
1 Click the dimension in the Map Model pane
The Properties area shows the dimension properties
2 Select Translation Enabled to enable translation for the dimension
NOTE
To disable an enabled dimension select Translation Enabled again
Adding deleting replacing and enabling hierarchies
You work with hierarchies by selecting dimensions and hierarchies in the MapModel pane You can add remove replace and enabledisable hierarchies for translation in the translation map
To add a hierarchy
1 Select the dimension to which you want to add a hierarchy in the Map Model
64 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6496
Building Translation Maps
pane2 Select the hierarchy in the OLAP Source Information pane
3 Click Add
The hierarchy is added to the dimension in the translation map
To remove a hierarchy
1 Select the hierarchy in the Map Model pane
2 Click Remove
The hierarchy is removed from the translation map
To update a hierarchy
1 Select the hierarchy to be updated in the Map Model pane
2 Select the replacing hierarchy in the OLAP Source information pane
3 Click Add
The hierarchy is replaced with the new hierarchy from the source cube
Enabling hierarchies for translation
To enable a hierarchy for translation
1 Click the hierarchy in the Map Model pane
The Properties area shows the hierarchy properties
2 Select Translation Enabled in the Properties area to enable translation for thehierarchy
NOTE
To disable an enabled hierarchy select Translation Enabled again
Universal Drill Through Guide 65
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6596
Creating a translation map
Adding deleting replacing and enabling levelsYou work with levels by selecting the levels in the Map Model pane
You can add remove or replace levels in the translation map To add a level
1 Select the dimension hierarchy to which you want to add a level in the MapModel pane
2 Select the level in the OLAP Source Information pane
66 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6696
Building Translation Maps
3 Click AddThe level is added to the dimensionhierarchy in the translation map
To remove a level1 Select the level in the Map Model pane
2 Click Remove
The level is removed from the translation map
To update a level
1 Select the level to be updated in the Map Model pane
2 Select the replacing level in the OLAP Source Information pane
3 Click Add
The level is replaced with the new level from the source cube
Universal Drill Through Guide 67
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6796
Creating a translation map
Enabling levels for translationTo enable a level for translation
1 Click the level in the Map Model pane
The Properties area shows the level properties
2 Select Translation Enabled to enable translation for the level
NOTE
To disable an enabled level select Translation Enabled again
Populating translation objects automatically
UDS Designer can populate the class and object properties automatically whenyou add a level translation To add a level translation and automatically populatethese properties do the following
1 Select the level in the Map Model pane
2 Select the universe object in the Target Universe information pane
3 Click Add
Because you specified a target universe object in step 2 the Universe Classand Universe Object properties of the level translation are automatically
populated with the universe objectrsquos parent class and object namerespectively
Specifying member translations
A level translation applies to all members at a level If you need to specify atranslation for a particular member you can do so by adding a member translation
68 Universal Drill Through Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6896
Building Translation Maps
To add a member translation1 Select the memberrsquos level in the Map Model pane
2 Select Member Translation in the Mapping Parts pane
3 Click Add
UDS Designer adds a level translation (if one is not already present) and amember translation to the level
4 Specify the class and object properties for the level translation
Universal Drill Through Guide 69
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 6996
Creating a translation map
5 Select the Source Member Unique Name component of the member translation
6 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
7 Select the Target Unique Value component of the member translation in the
70 Universal Drill Through Guide
M M d l
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7096
Building Translation Maps
Map Model pane
8 Type the member name in the Member Unique Name box in the Propertiesarea
The source member is updated in the Map Model pane
Universal Drill Through Guide 71
Deleting member translations
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7196
Creating a translation map
Deleting member translationsTo delete a member translation
1 Select the member translation in the Map Model pane
2 Click Delete
The member translation is removed from the translation map
Adding parent translations
You might need to qualify a member with at least one parent member in order tomake translation to the target universe possible For example the source cubemight contain the member rsquoQ4rsquo in the Time dimension You would need to qualifythe name of this member with the name of the parent member (for examplelsquo2000rsquo) in order to create a unique member name In this case the contextpassed by the Drill Through Service would be lsquo2000Q4rsquo To do this you need toadd a Parent Translation object to the level
You can add a Parent Translation Object only after you have added a level
translation To add a Parent Translation Object1 Select the level translation in the Map Model pane
2 Select Parent Translation in the Mapping Parts pane
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7296
Universal Drill Through Guide 73
Specifying target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7396
Creating a translation map
Specifying target reportsAfter you have added the translations to the map you need to specify theWebIntelligence target reports to which the map applies To do this
1 Click Define Target Reports on the toolbar
The Document Information dialog box appears
2 Type the name of the report in the Document Name box
3 Type the document caption in the Document Caption box
4 Type a comment in the Comment box
5 Click Add
The report appears in the Assigned Documents list
6 Click OK
NOTE
The caption and comment are optional
74 Universal Drill Through Guide
Editing a target report
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7496
Building Translation Maps
g g pTo edit a target report
1 Select the report in the Assigned Documents list
The Add button becomes a Set button
2 Modify the document name caption or comment as necessary
3 Click Set
Deleting a target report
To remove a report from the target reports list1 Select the report in the Assigned Documents list
2 Click Remove
The report is removed from the list
Universal Drill Through Guide 75
Working with existing translation maps
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7596
Working with existing translation maps
Working with existing translation mapsYou can use UDS Designer to open and modify an existing translation mapBecause there is no file association between UDS Designer and UDM files youcannot open translation maps by double-clicking them in Windows Explorer
To open a translation map
1 Select Open on the File menu
The Open Translation Map dialog box opens
2 Select a translation map and click OK
The translation map is loaded into UDS Designer
76 Universal Drill Through Guide
Changing the originating and target data sourcesAft h b ilt t l ti h it d t t
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7696
Building Translation Maps
g g g g gAfter you have built a translation map you can change its source andor targetdata sources
To change the originating data source
1 Click Change Originating Data Source on the Data Sources menu
The OLAP Source Information dialog box appears
2 Enter the name of the OLAP server in the OLAP Server box
3 Select the OLAP server type from the Server Type dropdown list4 Enter your OLAP server username and password in the User Name and
Password boxes (This step does not apply to MS OLAP)
5 Click Connect
UDS Designer attempts to connect to the server using the information youhave given If connection is successful the DataBases dropdown list box ispopulated with names of the OLAP databases available on the server
6 Select the database containing the cube you want to access from the
Databases dropdown list box
7 The Cubes dropdown list box is populated with the names of all the cubesavailable in the database you selected
8 Select the cube that you want to connect to from the Cubes dropdown list box
9 Click Load Cube
Universal Drill Through Guide 77
The OLAP Source Information pane is populated with the dimensions levels andhierarchies in the source cube In addition the translation map is populated with
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7796
Working with existing translation maps
p p pall the dimensions hierarchies and levels in the cube
NOTE
When you change the originating data source the current map information is lost
To change the target data source
1 Click Change Target Data Source on the Data Sources menu
The OLAP Source Information dialog box appears if your are working with anOLAP to OLAP map
The Universe Target Information dialog box appears if you are working withan OLAP to relational map
2 Follow the procedure outlined in To change the originating data source onpage 76 to select a different OLAP cube or select the universe and clickChange Originating Data Source to select a different universe
78 Universal Drill Through Guide
Making translation maps available toW bI t lli
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7896
Building Translation Maps
g p WebIntelligence
After you have built your translation maps you need to make them available toWebIntelligence so that the Drill Through Service can translate the userrsquos contextwhen they click on a drillable cell To do this place your maps (UDM files) in theData folder in your WebIntelligence installation for example CProgram
FilesBusiness ObjectsBusiness Objects Enterprise 6OLAPDataUDSMapsYou then need to stop and restart the WebIntelligence DTS Service to load thetranslation map To do this
1 Click Update UDS on the toolbar
The Universal Drill Through Service Update dialog box appears
2 Type the name of the server and the port number then click Update
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 7996
c h
a p t e
r
WebIntelligence in Drill Through
80 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8096
WebIntelligence in Drill Through
This chapter concentrates on the WebIntelligence side of drill through It looks atcreating WebIntelligence target reports as well as the workflow that the user follows when drilling through to a target report
Universal Drill Through Service Guide 81
Creating WebIntelligence target reports
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8196
Creating WebIntelligence target reports
Filters conditions and prompts
The Universal Drill Through Service applies drill contexts to target reportsthrough the use of filters For example if you drill on the Fashion member of theProduct dimension the Drill Through Service applies a condition that restricts theProduct dimension to Fashion
The Drill Through Service deletes any existing filters on a report before applyingdrill filters This is to avoid conflicting filters For example a report alreadycontains a filter restricting Country to lsquoUSrsquo then the Drill Through Service adds afilter restricting Country to lsquoFrancersquo The resulting filter - Country = lsquoUSrsquo andlsquoFrancersquo - returns no data
As a result you should create new reports to use with drill through rather thanuse existing reports that might contains filters that you want to retain
Prompts
Prompts work by applying filters to a report Your target reports should notcontain prompts on dimensions that are enabled for translation in the translationmap The prompt filter might combine with the drill filter in the way describedabove to filter all data from the report
Sample target report
The best way to understand drill through target reports and their relationship to
source documents is to refer to the samples provided with WebIntelligence Thesample source reports are based on the Retail2002 OLAP cube and providedata at a more detailed level than the data in the cube The Universal DrillThrough Service applies filters to the reports depending on where the user chooses to drill in the source cube
Making target reports available for drill through
You make target reports available by uploading them to the rsquoCorporate
Documentsrsquo area of WebIntelligence then refreshing the list of corporatedocuments The reports can then be accessed by users who need to drill throughfrom OLAP cubes
82 Universal Drill Through Service Guide
Drill through workflow
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8296
WebIntelligence in Drill Through
This section describes what happens in WebIntelligence when a user drillsthrough from an OLAP cube to a universe
Where can the user drill in a report
UDS supports single or multiple-cell drill through from both measure and member cells For example the user might choose to drill down into sportswear revenues
in California in Q1 2000 (measure cell) or drill down into fashion products(member cell)
Measure cell
Member
cell
Universal Drill Through Service Guide 83
Starting drill throughTo start drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8396
Drill through workflow
1 Select the cell in the report
The cell is highlighted
Cell selected for drill
through
84 Universal Drill Through Service Guide
2 Click the Drill Through button on the toolbar
The Drill Through dialog box appears
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8496
WebIntelligence in Drill Through
3 Select a target report from the list and click OK
Universal Drill Through Service Guide 85
The target report opens at the context where you started drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8596
Drill through workflow
The target report
In the example above you drilled on the cell showing sales revenues for sportswear products California for Q1 of 2000 The Drill Through Servicetherefore applied filters to restrict the target report to 2000Q1 sportswear andCalifornia As a result the target report displays sales revenue by productdepartment by month by sales person within these restrictions
Drilling on multiple cells
Drilling on multiple cells works on the same principle The Drill Through Servicebuilds a filter based on the cells you selected These cells can be valuesmembers or a combination of the two They do not have to be contiguous in thereport
The following examples show various multiple-selection scenarios and the thefilters generated by the Drill Through Service
86 Universal Drill Through Service Guide
EXAMPLE
Selecting multiple measure cells
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8696
WebIntelligence in Drill Through
In this situation the filter generated by the Drill Through Service is
(2000 and Fashion) or (2000 and Work)
EXAMPLE
Selecting member labels from different dimensions
In this situation the filter generated by the Drill Through Service is
100 and West
Universal Drill Through Service Guide 87
EXAMPLE
Selecting member labels at the same level
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8796
Drill through workflow
In this situation the filter generated by the Drill Through Service is
West or Central
EXAMPLE
Selecting member labels from the same and different dimensions
In this situation the filter generated by the Drill Through Service is
2001 and (Sportswear or Work)
EXAMPLE
Selecting member labels and values
In this situation the filter generated by the Drill Through Service is
((2000 or 2001) and Fashion) or (2001 and Sportswear)
88 Universal Drill Through Service Guide
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8896
WebIntelligence in Drill Through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 8996
c h
a p t e r
Managing and Maintaining a Drill
Through Environment
90 Universal Drill Through Service Guide
Overview
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9096
Managing and Maintaining a Drill Through Environment
This chapter describes the ongoing maintenance tasks that you will need to carryout to keep a drill through environment up-to-date and functioning correctly
Universal Drill Through Service Guide 91
Why maintenance is necessaryYou design your translation maps to work with the current structures of your so rce c bes and target c bes ni erses b t it is rare for the str ct re of
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9196
Why maintenance is necessary
source cubes and target cubesuniverses but it is rare for the structure of databases to remain the same for long If the structure of your source cube or target cubeuniverse changes after you have installed your translation maps youwill need to modify the maps to take account of the changes If you do not it islikely that drill through will no longer work correctly You need to be aware of
changes to both cube levels and individual cube members that might affect drillthrough
NOTE
Remember that after you have modified a translation map you need to stop andthen restart the drill through service (see Making translation maps available toWebIntelligence on page 78)
92 Universal Drill Through Service Guide
Changes that require updatesChanges to either levels or specific members require that translation maps beupdated
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9296
Managing and Maintaining a Drill Through Environment
updated
Level changes
The following changes will require you to update your translation map
bull A cube dimension is added removed or renamed
bull A cube hierarchy is added removed or renamedbull A cube level is added removed or renamed
bull Any universe class or object referenced by the translation map is removed or renamed
Member changes
Any of the above changes affect member translations also You must alsoaccount for new members that require additional member-specific translationrules If such members are added to the source cube you will need to addcorresponding member translations to the translation map
Universal Drill Through Service Guide 93
Problems caused by outdated translation mapsThe problems caused by failing to update a translation map depend on thechanges made to the source cube or target universe If a source cube dimension
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9396
Problems caused by outdated translation maps
changes made to the source cube or target universe If a source cube dimensionhierarchy or level or a target universe class or object referenced by a translationmap is removed or renamed drill through will fail If additional levels hierarchieslevels members are added in the source cube or additional classes and objectsare added in the target universe the Drill Through Service will simply ignore them
because it will not be aware of their existence
94 Universal Drill Through Service Guide
Source cube and target cubeuniverse locationsTranslation maps are based on cube and universe metadata not on the cubesand universes themselves This means that any cube can be a drill through
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9496
Managing and Maintaining a Drill Through Environment
and universes themselves This means that any cube can be a drill throughsource as long as its metadata is compatible with the metadata in the translationmap The same applies to target universes and cubes You will not necessarilyrsquobreakrsquo a translation map by using different cubes and universes from the onesyou used to build the map in the first place The source and target datasources
must have the same names as the ones specified in the map (the Drill ThroughService passes these names during drill through) but their physical locations areirrelevant
Universal Drill Through Service Guide 95
Index
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9596
Index
BBusiness Objects
consulting services 11 13
documentation 10Documentation Supply Store 9support services 11training services 11 13
Cconsultants
Business Objects 11customer support 11
Ddemo
materials 9Developer Suite 10 12documentation
CD 9feedback on 10
on the web 9printed ordering 9roadmap 9search 9
Documentation Supply Store 9drill through
and Business Objects 25architecture 22-24components 21-22
defined 20-21previous difficulty of 24
drill through samplesdescribed 27
Eeducation see training
Ffeedback
on documentation 10
KKnowledge Base 12
Mmultimedia
quick tours 10
OOLAP source cube
design requirements 39Online Customer Support 11
Rrelational database
normalized 31
snowflake schema 32star schema 32
Ssearch
documentation 9support
customer 11
Ttarget database
design requirements 35designing 43Essbase Accounts dimension 44Essbase member-naming restrictions 44
96 Universal Drill Through Service Guide
target reports
defined 18target universe
creating from the target database 46design requirements 37
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18
832019 webintelligence_uds
httpslidepdfcomreaderfullwebintelligenceuds 9696
Index
Tips amp Tricks 10training
on Business Objects products 11translation maps
defined 17
UUDS 16 21UDS Designer 48-75Universal Drill Through Service see UDS 16universes 25 34
relation to cubes 35
Wweb
customer support 11getting documentation via 9useful addresses 12
WebIntelligence administrator required knowledge 19tasks 17-18