What’s New

in
BrioQuery 6.0
What’s New in BrioQuery 6.0 © 1999 Brio Technology, Inc.
Refer to the Brio Technology License Agreement in this package before
installing or using the product. This product and related products and
documentation are protected by copyright and are distributed under
licenses restricting their use, copying, distribution, and decompilation.
No part of this product or related documentation may be reproduced in
any form by any means without prior written permission of Brio
Technology, Inc., and its licensors.
Brio Technology, Inc.
3460 West Bayshore Road
Palo Alto, CA 94303
(650) 856-8000
support@Brio.com
sales@Brio.com
www.Brio.com
For updates and corrections, see www.brio.com/documentation

Trademarks
Trademarks: Brio Enterprise, BrioQuery , BrioQuery Designer ,
TM TM

TM TM TM
BrioQuery Explorer , BrioQuery Navigator , Brio.Quickview ,
Brio.InsightTM, BrioQuery.Server™, Brio OnDemand Server™, Brio
Broadcast Server™, and Brio Enterprise Server™ are trademarked or
registered names. All trade names of companies and products used in
this book are registered trademarks or trade names of their respective
holders and are used in an editorial fashion only, with no intention of
infringement of any kind.

Acknowledgements
Written by Dan Jewett. Edited by Andreas Ramos, Technical Publications
manager.
PN 1200051 (Rev. 6/1999)
Contents

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

1 User Interface ................................................................................... 1

User Interface .................................................................................................1
Overview.................................................................................................1
Microsoft Office 2000 Look and Feel ............................................................2
Browser-Influenced Navigation....................................................................3
Source-Left, Target-Right ..............................................................................3
Toolbars, Outliners, Palettes .........................................................................3
General Options .............................................................................................3
Default Document Directory .................................................................3
Document Passwords.............................................................................4
Y2K Epoch Setting ..................................................................................4

2 Data Access....................................................................................... 5
OLAP Query...................................................................................................5
Overview.................................................................................................5
Offline Access to OLAP Server Data.....................................................7
Flexible Query Options ..........................................................................7
Hardwire vs. Process Query Mode .......................................................7
Double-click Drill Down and Drill Up..................................................8
Level Skipping ........................................................................................8
Slicer Tool................................................................................................8
Member Selection ...................................................................................8

What's New in Brio Enterprise 6.0 iii

 Filter Box .................................................................................................9
Full Web Interaction.............................................................................10
Native Server Features .........................................................................10
Query (Relational)........................................................................................10
Multiple Queries per Document..........................................................10
Master Data Models .............................................................................11
Importing SQL Files .............................................................................12
Unions and Subqueries ........................................................................12
Limit Joins .............................................................................................13
Predefined Drill Paths ..........................................................................14
Drill to Detail ........................................................................................14
Metadata Integration ...................................................................................16
‘Snap In’ Metadata Templates .............................................................16
New Remarks Interface........................................................................16
Alternate Metadata Connection...........................................................17
Connectivity .................................................................................................17
Connection Wizard...............................................................................17
ODBC - SQL Server Stored Procedure Support..................................18
New Database and Middleware Software ..........................................19

3 Analytic Application Construction................................................. 21

Overview ......................................................................................................21
EIS Section ....................................................................................................22
Embedded Sections......................................................................................23
Extended EIS Controls .........................................................................24
Layout Aids ..........................................................................................25
Object Model and Scripting.........................................................................25
JavaScript ..............................................................................................25

iv Contents
 Programmability and the Object Model..............................................26
Script Building Tools............................................................................28

4 Reporting and Analysis .................................................................. 31

Report Designer ...........................................................................................31
Overview...............................................................................................31
Report Components .............................................................................32
Layout ...................................................................................................33
Advanced Features...............................................................................34
Table and Results Sections .........................................................................35
Overview...............................................................................................35
Break and Grand Totals .......................................................................36
Table Formatting ..................................................................................38
Computed Columns .............................................................................39
Chart Section ...............................................................................................40
General Additions ................................................................................40
Pivot Section ................................................................................................41
General Additions ................................................................................41

5 Server Enhancements..................................................................... 43
Brio OnDemand Server ...............................................................................43
Enhanced Scalability ............................................................................43
Load Balancing and Failover ...............................................................44
Application Look and Feel...................................................................44
Local Browser Values Available to Plug-in Scripting ........................47
Log Files and Options ..........................................................................47
Brio Broadcast Server...................................................................................48
Storing Brio Broadcast Server Documents in the File System ...........48
Email Signature Customization...........................................................48

What's New in Brio Enterprise 6.0 v

 Brio Web Clients ..........................................................................................48
New Look..............................................................................................49
Proxy Server Support ...........................................................................49
Web Client Scheduling Capability ......................................................49
SSL Support ..........................................................................................49
Setup .............................................................................................................49
Automatic Configuration for Microsoft IIS 4......................................50
Enhanced Upgrading ...........................................................................50
Improved Uninstall ..............................................................................50
UNIX Web Server Support ..................................................................50
Server Admin OEM-able......................................................................50

Index 53

vi Contents
Figures

Figure 1 New Look and Feel shows the Document Map, Section Bar, and browser-
style navigation. ...................................................................................................2
Figure 2 The new OLAP Query section allows users to quickly view data from high
performance servers.............................................................................................6
Figure 3 The Filter Box is one way to access server-side functions such as top N, top
N%, and others. ....................................................................................................9
Figure 4 A document with three queries and a Data Model. They use two RDBMSs
and one OLAP server.........................................................................................11
Figure 5 A chart built from the Sales Query. The user is about to use Drill to Detail
which will automatically build and run a new, limited query in the
background.........................................................................................................15
Figure 6 The new Remarks interface can display as many descriptions for Topics and
Items as needed. .................................................................................................17
Figure 7 The new Remarks interface can display as many descriptions for Topics and
Items as needed. .................................................................................................18
Figure 8 An example of a Web-ready Analytical Application built with BrioQuery 6.0.22
Figure 9 EIS Controls........................................................................................................24
Figure 10 EIS Object Models ..............................................................................................26
Figure 11 Using the BrioQuery object model from the Visual Basic for Applications
editor within Excel 97. .......................................................................................27
Figure 12 Report Designer’s Interface ...............................................................................32
Figure 13 The Expression Bar.............................................................................................34
Figure 14 Pre-computed Fields ..........................................................................................35
Figure 15 Table section derived from Results section with rich formatting and break
totals to display the top five ranked product sales for Q1 1999. .....................37
Figure 16 Computed Columns...........................................................................................39
Figure 17 Brio OnDemand Server’s HTML Start Page.....................................................45
Figure 18 Search Capability in Brio OnDemand Server...................................................46

What's New in Brio Enterprise 6.0 vii

viii List of Figures
Preface

Welcome! This document details the tremendous number of

enhancements made to the BrioQuery product family in the 6.0 release.
BrioQuery 6.0 is for organizations that want to optimize their operational
and strategic decision-making. BrioQuery 6.0 is an enterprise business
intelligence suite and an analytical application development platform
that facilitates timely and effective business decisions for companies to
gain competitive advantage. BrioQuery 6.0 is the only solution that
allows customers to quickly deploy rich analyses and applications to a
wide range of end-users with a single integrated product that works the
same across the Web and client server (C/S) supporting both connected
and disconnected analysis.
This document is organized with a logical flow through the product,
starting with the user interface, moving onto data access (including the
new OLAP Query section,) then showing you the tremendous new
capabilities for constructing analytical applications. You will also learn
about the wealth of enhancements for reporting and analysis. Changes to
our scalable, cross platform server products are also detailed. Finally,
changes to the setup programs are explained.
We trust that this document is useful in understanding the tremendous
benefit of BrioQuery 6.0 in helping your organization to deliver the
business value of information.

ix
x Preface
1 User Interface

User Interface

Overview
The BrioQuery client experience has been greatly enhanced by the
introduction of a new, easier than ever user interface. While retaining the
defining characteristics and being immediately recognizable as Brio, the
interface has been modernized and streamlined. The overhaul is more
than skin-deep -- although it is quite visually pleasing, the re-design was
undertaken to enhance usability in general, and specifically to allow
more sophisticated features to be exposed in a user-accessible manner.
The most noticeable visual change is the replacement of the document
section tabs across the bottom of the screen with the vertical Document
Map at the left-edge of the screen. This new Document Map provides for
quicker navigation of the sections within the document, especially for
documents with many sections.

1
 Figure 1 New Look and Feel shows the Document Map, Section
Bar, and browser-style navigation.

Microsoft Office 2000 Look and Feel

Standards set forth by the Microsoft Office product suite drove the
design of the new look and feel. This provides users with a familiar
desktop experience, shorter learning curves, and more natural
integration into custom application environments. Toolbar design has
been updated to the latest look as found in Office 2000 and Internet
Explorer 5.0. Menu structures have been reworked to be more consistent
with common Office terminology and placement, and dialog boxes have
been updated, including the addition of Wizards to facilitate easier user
completion of complex tasks.

2 Chapter 1: User Interface

Browser-Influenced Navigation
Navigation inside the document has borrowed concepts from web
browser standards. The document map is a common navigation
technique seen on web pages with framed navigation bars on the left
edge of the page. The Section bar (a horizontal banner running across the
top of each section) includes single click buttons to navigate forward and
back, and the main toolbar has a “Home” button that returns users to the
default EIS section of a document.

Source-Left, Target-Right
A new paradigm for creating content has been introduced. The area on
the left, below the Document Map, is the Catalog Pane. New users
simply need to be taught to drag items from this source area on the left
and drop them in the Content Pane on the right. The Content Pane may
be a Data Model, a Query, a Report, a Pivot, a Chart, or an EIS section.

Toolbars, Outliners, Palettes

While the interface has been designed to be more efficient to use,
personal choice and habits are not ignored. Toolbars, Outliners, and
palettes can all be detached and dragged as floating windows to any
location on the screen. These objects may be hidden from view to reclaim
screen space for report viewing and EIS applications.

General Options
Several general options have been added to make working with
documents easier. These settings include:

Default Document Directory

This setting specifies the starting directory for document open and save
actions. Whenever the File | Save or File | Open dialog is used, it will
start in this default directory.

What's New in Brio Enterprise 6.0 3

Document Passwords
Documents may now be saved (optionally) with a password. Entering
the password is required when re-opening the document.

Y2K Epoch Setting

The pivotal year in Y2K date entry calculations is customizable via the
program options dialog. This epoch setting sets a pivotal year that
defines any two-digit date as either a twentieth century or twenty-first
century year. For example, an epoch setting of 30 instructs BrioQuery to
treat two-digit year values of 30 or less as in the twenty-first century
(2000-2030) while two-digit year values greater than 30 are in the
twentieth century (1931-1999.)

4 Chapter 1: User Interface

2 Data Access

OLAP Query

Overview
BrioQuery 6.0 introduces a powerful new section for navigating
(querying) multidimensional databases (MDD.) When connecting to a
multidimensional database (MDD,) the document immediately opens an
OLAP Query section. The OLAP Query section displays the structure of
the MDD as a hierarchical tree in the Catalog Pane. Queries are built by
dragging dimension members and measures directly into the Outliner.
This method of querying fills a Pivot-style structure directly with the
slice of the cube retrieved from the MDD.
The OLAP Query section leverages the power, speed, and calculation
engine of the MDD servers it connects to by retrieving ‘slices’ of the cube
as requested. Each addition to the OLAP Query pivot report re-queries
the MDD for a new slice. This interactive connection to the MDD
requires an active connection to the database.

5
 Figure 2 The new OLAP Query section allows users to quickly
view data from high performance servers.

Supported multidimensional databases include:

• Microsoft SQL Server 7.0 OLAP Services (formerly known as Plato)
• Hyperion Essbase
• Informix MetaCube
• IBM DB2 for OLAP
• Other databases compliant with the OLE DB for OLAP (ODBO)
standard.
Brio has tested the following databases for compatibility
• WhiteLight
• SAS MDDB
• NCR TeraCube

6 Chapter 2: Data Access

 • SAP BW
• Applix TM1

Offline Access to OLAP Server Data

The Brio tradition of supporting disconnected analysis for busy
knowledge workers continues in the new OLAP Query section. To
support offline analysis when working with OLAP servers, a slice of the
MDD cube retrieved into the OLAP Query section can be downloaded to
a traditional Brio Result section within the document. By doing this,
users can exercise the full capabilities of Brio’s Chart, Pivot, Table, and
Report sections to work with data from the MDD.

Flexible Query Options

The new interface exposes the natural hierarchy defined in the server
cube in a number of ways, yet unique features are available in BrioQuery
which allow more flexible use of server cubes. These flexible options
make Brio the ideal client to OLAP servers for organizations with mixed
environments of full clients, Web clients, remote dial-in clients, and
mobile users.

Hardwire vs. Process Query Mode

This setting controls whether Brio clients retrieve information from the
cube automatically or manually after each interaction with the Outliner.
Hardwire Query mode queries the OLAP server after every change to
the Outliner. This mode automatically bursts a request to the server to
retrieve cube slices. Process Query mode allows the user to choose when
a request is sent to the server. They could introduce multiple items into
the Outliner before retrieving a cube slice. This allows users to build
larger OLAP Query reports without continuously bursting traffic to the
server.

What's New in Brio Enterprise 6.0 7

Double-click Drill Down and Drill Up
Connecting to a server-based cube provides information to BrioQuery
about the structure of the data, such as the hierarchies. Following this
strict hierarchy is a rule imposed by the server cubes which allows
knowledge of the next level down in any particular dimension. Any label
(side or top) can be used to drill into the next level down the hierarchy
by simply double-clicking the label. Drill up is just as easy: double-click
on any label, except for the innermost label.

Level Skipping
Typical MDD Query tools require queries to include all levels of a
dimension from the top down to the desired level of granularity. For
example, when querying the Time dimension, a user must start at ‘Year’,
then go to ‘Quarter’, then go to ‘Month’. BrioQuery is different. While
certainly supporting this navigation, BrioQuery users can skip levels! For
example, an OLAP Query may jump directly from Year to Month in the
Time dimension.

Slicer Tool
The Slicer tool is an easy way to limit the scope of the server cube from
which you are requesting data. The Slicer defines a logical slice of the
server cube by instructing the server to ignore all values that are not part
of your slice. For example, if you wanted to limit the view of a cube to
just data for 1998, you would drag the member value ‘1998’ from the
‘Year’ dimension into the Slicer tool. The member values in the Slicer do
not appear in your report as a top or side label.

Member Selection
Member selection is another way to limit the data retrieved form the
server cube. Member selection is similar to the Slicer, with the key
distinctions that member selection introduces the member value in your
report, and multiple members may be selected from a single hierarchy. A

8 Chapter 2: Data Access

 Member Selection is created by dragging individual member values from
the Catalog Pane into the OLAP Query Outliner.

Filter Box
The Filter Box lets users define limits to the report after levels have been
introduced into the report. Double clicking on a level name in the
Outliner will display the Filter Box. The Filter Box allows setting
comparison operators on the values for that member. Additional server
specific functions are available in the Filter Box. Each OLAP server
supports a native list of powerful server-side analytical functions.

Figure 3 The Filter Box is one way to access server-side functions

such as top N, top N%, and others.

What's New in Brio Enterprise 6.0 9

Full Web Interaction
The Brio OnDemand Server and the Brio Web clients (Brio.Insight and
Brio.Quickview) fully support OLAP Query reports. Brio.Insight
supports the dimension and measure tree navigation and all other query
features. Brio.Quickview supports Query processing. Web clients have
only Process Query mode to minimize network traffic.

Native Server Features

BrioQuery leverages the native functions of MDD cubes. Some of the
server specific features and functions supported are:
• OLE DB for OLAP (computed columns, Top/Bottom N, Top/Bottom
N%)
• Essbase (User-Defined Attributes)
• MetaCube (Filters)

Query (Relational)

Multiple Queries per Document

A single BrioQuery document can now contain multiple query sections.
These query sections can access a wide range of data sources (relational
database queries, OLAP server queries, imported data sets, and local-join
queries.) Each query section has its own Results section (OLAP Query
does not have a Results sections unless the user chooses the “Download
to Results” option.) Each query may be associated with the same
database or different databases (in other words, each query defines
independently what OCE or Data Model to use.)
When processing documents that include multiple queries, the user has
several options:
• Process the currently active query only
• Process all queries in the document

10 Chapter 2: Data Access

 • Process a custom set of the queries in a document, which the user
defines
Multiple results in a single document allow users to create complex
reports that integrate data from the multiple data sources. Users may
create reports with data from different data sources within a single
interface or they can group different queries together in a single package.

Figure 4 A document with three queries and a Data Model. They

use two RDBMSs and one OLAP server.

Master Data Models

The traditional Query section is a combination of a Data Model and the
Request/Limit/Sort Line region. BrioQuery 6.0 introduces a new,
optional concept, which allows reuse of Data Models across multiple
queries inside a document. Any Data Model built by a BrioQuery

What's New in Brio Enterprise 6.0 11

 Designer or BrioQuery Explorer user may be promoted to a Master Data
Model. This promotion creates a new Data Model-only section in the
document. Data Model sections do not contain a Request Line or Sort
Line.
Each time a new Query is inserted into a document which contains a
Master Data Model, the user is asked if the new Query should be linked
to the Master Data Model. Query sections inherit any changes made to
their Master Data Model. They also have their visual Data Model display
locked from modification.

Importing SQL Files

BrioQuery now has the ability to import SQL statements from text files
into a Query section. The imported SQL cannot be modified inside
BrioQuery. When the file is imported, it is scanned to determine the
number of columns that will be returned by the SQL, and the request line
is populated with a column indicator for each of the columns. The user
can modify the number of columns that are created. Request line items
can be modified to specify a user-friendly name and identify its data
type.

Unions and Subqueries

The drag-and-drop interface for query building now supports the
creation of Union queries (intersections and minuses, if your database
supports them,) sub-queries, and correlated sub-queries. Building these
complex queries follows a similar visual process as building a regular
query.

Unions, Intersections, and Minus Queries

These queries are the combined results of multiple queries, where the
results are a union (including intersection or difference) of the individual
query results. Union queries have strict rules mandated by the SQL
language, the primary rules is that each query taking part in a union
must have the same number of columns, in the same order, and the same
data type. BrioQuery performs validation of these rules before
attempting to process such a query.

12 Chapter 2: Data Access

 To add a Union query, build the first query as normal, and then select
the Append Query item from the Query menu. This will introduce a
Union Controller line ready to be populated with a second query.

Subqueries
Using the result from an inner query as the value of a limit for an outer
query is called a subquery. This allows for comparisons such as “find all
states whose total population is greater than the average state
population.” The inner query is needed to calculate the average state
population, while the outer query uses that value to limit the retrieval of
state names.
In BrioQuery, the Limit dialog box is used to start a subquery. Selecting
the Advanced button will expand additional options, including the
subquery option that introduces an additional Query section in the
document. This new query can include as many limits and other query
techniques in the subquery as needed. When you process the query, the
subquery is included in the SQL sent to the database.

Correlated Subqueries
A correlated subquery is related to the subquery in that it uses an inner
query to feed result values to the outer query. A normal subquery
executes the inner and outer queries once, returning the value(s) from
the inner query to the outer query. A correlated subquery executes the
inner query multiple times, once for each row returned by the outer
query. BrioQuery supports the graphical building of correlated
subqueries by introducing the outer query back into the definition of the
inner query in the subquery building process.

Limit Joins
A limit join is a more advanced form of the BrioQuery local join. Rather
than independently running two queries and then locally joining the
data at the desktop, a limit join runs the first query to retrieve a list of
values and then uses those values in a limit on a column in the second
query. The limit join processes the queries separately; meaning two
different databases may be used. For example, a query may be run from
an inventory table in an Oracle database to retrieve a list of part numbers

What's New in Brio Enterprise 6.0 13

 that are out of stock. The resulting part number list may be used as a
limit join to define the list of values retrieved from the work-in-process
table in another database to determine the status of the stock
replenishment.

Predefined Drill Paths

BrioQuery 6.0 adds an additional method for defining user drill paths in
Pivot and Chart sections. An administrator may define drill paths in the
Data Model, which are inherited in all Pivots and Charts created from all
queries associated to the Data Model. This predefined drill path specifies
the hierarchy within dimension tables, allowing quick navigation up and
down the drill path in the reports. This capability may be used to
augment the existing Drill Anywhere capability of BrioQuery, or the
administrator may elect to disable Drill Anywhere and leave users the
ability to drill up and down this predefined path only.
The definition of drill paths in the Data Model or Query sections
modifies Topics to identify whether it is a dimension or fact table. Items
in dimension tables become part of the predefined path based on the
order in which they appear in the dimension. Any individual item may
be flagged as a fact, which excludes it from the drill path. Drill path
specifications may be applied to Topics or Meta Topics.

Drill to Detail
With Drill to Detail, users may drill into items that are in the current
Data Model but not on the request line. This gives interactive querying of
the database from the pivot or the chart section. When Drill to Detail is
selected, a copy of the current report and associated Data Model is
automatically added to the document where these modifications are
made. This copy is made to preserve the original query and report. Drill
to Detail additionally applies limits to the new query based on drill
selection. This allows Brio to scale more elegantly to much larger fact
tables by only retrieving a small number of rows for highly aggregated
data. For example, the original query may include ‘product family, by
quarter, by region’ and then allow the user to drill further to see a
particular product family in a particular region by month.

14 Chapter 2: Data Access

Figure 5 A chart built from the Sales Query. The user is about to
use Drill to Detail which will automatically build and run
a new, limited query in the background.

Combining Predefined Drill Paths with Drill to Detail creates a scenario

called incremental drilling. This allows the end users to safely (from a
database performance point of view) navigate large relational start
schemas in a similar fashion that users navigate multidimensional cubes.

What's New in Brio Enterprise 6.0 15

Metadata Integration

‘Snap In’ Metadata Templates

BrioQuery now enables customers to quickly reuse the metadata created
and captured by the leading metadata vendors. Several ‘Snap In’
metadata templates are included and are available to users via the Meta
Connection Wizard, which is a part of the Connection Wizard discussed
below. These templates are the definitions required for the Remarks
interface to access and display the metadata from the most popular
metadata sources. The Snap In Templates provided with BrioQuery 6.0
can work with the following:
• Ardent DataStage
• Broadbase
• IBM Visual Warehouse
• Informatica PowerMart
• Prism Solutions
The information for the Snap In Templates is customizable and shareable
by administrators.

New Remarks Interface

BrioQuery’s integration with third-party metadata has been greatly
extended with the new Remarks dialog. The administrator can now
define as many different elements of metadata to be displayed, as they
need. The end user will see these metadata elements in the new Remarks
dialog that has multiple tabs, one for each element of metadata. For
example, a Remarks dialog on an item may have separate tabs
displaying the definition of the column, the last update date of the table,
the number of rows in the table, transformation rules applied to the data,
and the source system from which the column originated. For
administrators there is an expanded Remarks definition dialog which
allows for the definition of each tab to be displayed including its name,
and the source for the metadata information (in the form of a SQL
statement.)

16 Chapter 2: Data Access

 Figure 6 The new Remarks interface can display as many
descriptions for Topics and Items as needed.

Alternate Metadata Connection

The metadata accessed by BrioQuery when generating table lists, column
lists, and remarks information may now be stored in any database on
your network. Part of the definition of a connection file (OCE) is to select
a connection to use specifically for accessing metadata. The definition of
an alternate metadata connection is part of the new Connection Wizard
for building connection files.

Connectivity

Connection Wizard
A new Connection Wizard has simplified the process of creating
connection files (OCEs.) The user is stepped through the process of
selecting middleware and databases, and any optional or advanced
settings, such as metadata, that they wish to use. The often confusing
process of getting connected to a database is easy now with the Wizard.

What's New in Brio Enterprise 6.0 17

 Figure 7 The new Remarks interface can display as many
descriptions for Topics and Items as needed.

ODBC - SQL Server Stored Procedure Support

Microsoft and Sybase SQL Server database Stored Procedures are now
supported when connecting to these databases via ODBC connections
(prior versions of BrioQuery supported stored procedures only when
using Open Client.) These Stored Procedures are also supported from the
Brio.Insight and Brio.Quickview web clients.

18 Chapter 2: Data Access

New Database and Middleware Software
Version 6.0 adds support for the following databases and middleware
software:
• Essbase 5.x on Windows and UNIX
• MetaCube 4.x
• Microsoft SQL Server 7
• Microsoft OLAP Services (Plato)
• Microsoft’s OLEDB for OLAP

What's New in Brio Enterprise 6.0 19

20 Chapter 2: Data Access
3 Analytic Application Construction

Overview
A major new initiative is the development of the BrioQuery 6.0 to be the
foundation for users to build and deploy analytic applications.
Analytical applications focus on delivering significant prepackaged
business content that is encapsulated within an application. With
BrioQuery 6.0, customers and independent software vendors can
leverage their knowledge of industry-specific best practices and
assemble their own analytical applications for deployment to end users
via the Web.

21
 Figure 8 An example of a Web-ready Analytical Application built
with BrioQuery 6.0.

EIS Section
The EIS section of Brio documents supports robust application building.
Three significant focus areas within the EIS section open up a range of
possibilities for constructing analytic applications:
• Embedded Sections include live Brio report components into EIS
displays.
• Extended EIS Controls contains a wide array of controls to include in
an application interface.

22 Chapter 3: Analytic Application Construction

 • Object Model and Scripting integrates the industry-standard
JavaScript language with a rich new object model that can control
most aspects of BrioQuery.
An application developer can combine embedded report sections with
new UI controls in a visual layout tool and then create interactivity
between these controls and the native Brio application to quickly create a
wide variety of analytic applications. A sample of the types of
applications which will be commonly constructed include:
• Simple forms to collect multiple input parameters for a report
• Executive dashboard applications, complete with visual drill-down
from high-level metrics to underlying data content
• Browser-style navigation pages to assist users in navigating large
documents

Embedded Sections
Brio reports (Pivot, Chart, Results, Table, and OLAP Query sections)
may be embedded into an EIS section. For example, if you embed a chart,
the chart will be visually drawn on the EIS screen. All embedded reports
keep a live connection with the data content and the formatting from its
original section. Reprocessing the query or modifying the original report
will automatically update both the content and display of that report in
the EIS section.
Embedded reports carry a property defining them as view-only, active,
or a hyperlink to the original.
• View-only reports are a static image of the report on the EIS. It
appears as currently defined in the original section. The user has no
interaction capabilities with the report.
• Active reports allow the user to interact with the report directly in
the EIS section simply by clicking on the report. Clicking a live
report activates it in-place for drill down, pivoting, and other
common analysis functions.
• Hyperlink reports follow the browser model of a single-click
jumping directly to the original section.
Embedded reports may be sized independently to facilitate the layout of
the EIS section. In a chart section, the chart will display in the full

What's New in Brio Enterprise 6.0 23

 document window – on an EIS section that embedded chart may be
scaled to fit in a small region of the display. This allows a great deal of
flexibility in creating dashboard-type applications.

Extended EIS Controls

The set of controls in the EIS section has been expanded to a complete set
of elements for building analytic applications. The list of controls now
includes buttons, radio buttons, check boxes, text (edit) boxes, list boxes,
and dropdown list boxes. The text box, list box, and dropdown list box
controls may be populated with values at design time or dynamically
populated with values by the new scripting language. Similarly,
checkbox and radio buttons can be set at design time or run time.

Figure 9 EIS Controls

24 Chapter 3: Analytic Application Construction

 Each of these controls may have scripts attached to them to trigger
events in the document. New events are available for the EIS section
itself–-onActivate and onDeactivate–-to trigger scripted actions when the
document section gains or loses focus. These elements provide the
necessary building blocks for creating polished analytic applications.

Layout Aids
Several new layout aids have been introduced to support precise
positioning of EIS controls.
• Rulers: Horizontal and vertical rulers are available to assist with
lining up items based on precise units of measure. To turn the ruler
on, select the menu item under the EIS menu. The ruler measure may
be set to inches, centimeters, or pixels by clicking on the measure
indicator at the intersection of the rulers.
• Grid: A layout grid automatically snaps all objects to the closest grid
spot. The grid may be turned on/off from the menu item under the
EIS menu.
• Design Guides: Design guides are similar to grids in that objects are
automatically snapped to line up with the design guides. Design
guides are placed at user-specified locations in the workarea. The
design guides appear as a blue line across the work area. Design
guides can be dragged to a new location. Multiple design guides
may be added by dragging from the ruler into the work area.
• Same Width/Height: Any two objects may be automatically resized
to the same width and/or height. When selecting multiple objects,
the width/height of the first object selected will be the reference for
resizing the objects.

Object Model and Scripting

JavaScript
JavaScript is the new scripting language for all of the BrioQuery
products. BrioQuery 6.0 has the Netscape JavaScript interpreter (version
1.4) embedded into the application. This addition allows application
developers to use the full functionality of this powerful, easy-to-learn

What's New in Brio Enterprise 6.0 25

 industry-standard scripting language to control Brio applications. Any
documents with the older Brio script language will have the scripts
automatically converted to JavaScript when the document is first
opened.

Programmability and the Object Model

A new object model allows manipulation by internal and external
programming languages. The BrioQuery application is composed of a
series of objects, each with methods and properties. For example, a
Query section in a document is an object. That Query Section appears
with the same name in the document map. The property of the object
and the command to Process the query is one of its many methods. Rich
sets of application objects have been exposed to the scripting system.

Figure 10 EIS Object Models

Typically, the object model is manipulated by the JavaScript language

from inside an EIS section to build self-contained analytic applications.
On Windows systems, the object model is also accessible via Automation
Interfaces (OLE Automation) allowing the BrioQuery application to be
controlled by external applications such as Excel, VB, C++, Delphi, or
any application capable of making OLE Automation calls.

26 Chapter 3: Analytic Application Construction

Figure 11 Using the BrioQuery object model from the Visual Basic
for Applications editor within Excel 97.

What's New in Brio Enterprise 6.0 27

Script Building Tools
Several tools are available to assist with writing JavaScript that can
manipulate the Brio Object Model.

Script Editor
Right-clicking an object in the EIS section and selecting the Scripts menu
choice will display the built-in Script Editor, a basic editor window used
to attach JavaScript to an EIS object.

Object Browser
While writing scripts, the left side of the Script Editor window displays
the Object Browser. This is a tree control of the objects, methods, and
properties available to be included in the script. The object browser is
dynamic, displaying the active state of the objects available in the
application at any point in time. Double-clicking a method or property in
the object browser inserts the JavaScript command to reference that
method/property into the script editor window.
For example, to write a script to hide the toolbars from display, navigate
the Object Browser and double-click on the Visible property of the
Standard Toolbar, which inserts the correct JavaScript reference. Your
remaining script work is to type “= false” after the reference, then repeat
the steps for the remaining toolbars.

Execution and Console Windows

These windows allow script builders a convenient way to test commands
and debug scripts. The immediate window allows an application
designer to type any JavaScript command and have it immediately
executed. This is useful to test the syntax or isolate a sequence of steps in
a complicated script. The console window displays error messages and
alert values generated by the JavaScript interpreter. During a script
debugging cycle, the application designer may write messages to the
console window to track the state of variables and the progress of the
script.

28 Chapter 3: Analytic Application Construction

What's New in Brio Enterprise 6.0 29
4 Reporting and Analysis

Report Designer

Overview
The Report Designer in BrioQuery 6.0 replaces its predecessor, the Detail
section. The design goals for the new Report Designer allow Brio users to
create more complex report layouts then ever before, yet to retain the
ease of use and highly intuitive visual building process. The strict
adherence to banded report layout has been lifted, allowing a more free
form and flexible layout of reports. The Report Designer retains
knowledge about categories and break-style boundaries, since those
concepts are the backbone of reporting. Extended functionality allows a
user to introduce new types of elements to create robust, complex, pixel-
perfect reports.

31
 Figure 12 Report Designer’s Interface

Older documents with Detail reports will not be lost – the detail reports
will be opened and displayed in read-only mode. To modify an existing
Detail report, it must first be converted to the new Report format.
Selecting the menu item Convert to Report from the Detail menu will
automatically convert the report. It is anticipated that the overwhelming
majority of Detail reports will be translated without problem, but it is
unavoidable that a few reports will not be able to migrate cleanly.

Report Components
The report structure is divided into group headers and body areas, with
each body area typically holding a table of data. Tables are created with
dimension columns and fact columns, where the distinction is typically

32 Chapter 4: Reporting and Analysis

 text versus numeric content. These tables are quite flexible structures in
that several tables may be introduced into each band; each sourced from
the same or different result sets in the document. Tables carry a rich set
of formatting options, described later.
In addition to introducing tables into the report, any other Pivot, Chart,
or Table report may be introduced into the new Report Designer. These
components may be introduced into the Group headers or directly into
the body of the report. They appear as free-floating objects within the
report area, which can be moved anywhere in the report by simply
dragging them.
Discrete text values, computed expressions, a set of predefined
computed fields, labels, and graphic objects may be introduced into the
report at any location to add to the rich content.

Layout
The visual construction of reports has several aids to facilitate layout:
• Page Layout Mode
Reports are displayed in a page layout mode, showing report
pagination, margins, headers, and footers.
• Report Setup
User-defined settings for page orientation, margins, number of
columns, and sizes of multi-column reports are available to identify
page sizes and formats.
• Headers/Footers
Headers and footers are treated as normal report areas allowing full
customization of the contents, including the introduction of other
report elements (Pivots, Charts…) text labels, and computed fields.
Special predefined computed fields are available to easily introduce
page number/total pages, date saved/processed/printed, date/time
now, and file/report names.
• Section Boundaries
Optional boundary lines for the group regions, header/footer
regions, and body areas may be displayed to make clear where the
respective areas begin/end for layout purposes.
• Design Tools

What's New in Brio Enterprise 6.0 33

 The same rulers, design grids, design guides, and zoom functions
that are available in the EIS section are available in the Report
Designer to build precision layouts.

Advanced Features
• Multiple Data Sources
Reports may be created which contain data from multiple, possibly
unrelated queries. In addition to including multiple tables in the
report (these tables may be from the same or different queries,) the
data in a single table may be ‘joined’ across queries in the report.
When using columns from multiple result sets in a single report
table, the report engine will match the data based on any common
keys found.
• Computed Fields
The new Expression Bar is a quick access line in the Report Designer
for building computed expressions. In addition to the built-in
functions that the expression bar exposes, JavaScript expressions
may be written to derive more advanced calculations.

Figure 13 The Expression Bar

• Pre-computed Fields
Sets of predefined computed fields are available to quickly introduce
common values into the report, including Page Number/Total, Date
Saved/Processed/Printed, Date/Time Now, and File/Report name.

34 Chapter 4: Reporting and Analysis

 Figure 14 Pre-computed Fields

Table and Results Sections

Overview
The Table is a new type of report section introduced in BrioQuery 6.0.
Tables are used to display tabular reports. While these reports can be
viewed and printed in their own right, they will most often be used as
building blocks for Report sections, EIS sections, and even other Table
reports. Tables are built by introducing items from a Results section in
the Catalog Pane to the Table section Outliner. Tables are single
dimension reports – displaying a data-grid view that can be richly
formatted. The Results section also uses this new formatting engine.
When a query is processed, the returned data is loaded into the Results
section. All of the returned Items are automatically loaded into the
Results section Outliner. This provides users with an immediate view of
the data grid. The Results section is a special version of the Table object,
serving as the highest level in the data chain. Limits, computed columns,

What's New in Brio Enterprise 6.0 35

 grouping columns, and other actions which modify the structure of the
data grid will be cascaded to all subsequent tables built from the Results
section. Subsequent tables introduced into the document will each carry
their own scope by inheriting their source data set from either the
Results section or the Table section they were spawned from. Inserting a
Table while the scope is at the Results section attaches the new Table
section to that Results section. When inserting a Table while a non-
Results section Table is in focus, the new Table section will derives its
data set from the Table section in focus. This nesting of Tables allows for
some very flexible reports to be built by cascading Table results into each
other.

Break and Grand Totals

Break totals and Grand totals are available for any column in the table. A
total on a numeric column applies the default ‘sum’ function, which may
be easily changed to any of the standard aggregate functions (minimum,
maximum, average…) or a custom break formula may be written. A total
on a character column will concatenate the unique values. Adding a
Break total will automatically sort the data by the break column.

36 Chapter 4: Reporting and Analysis

Figure 15 Table section derived from Results section with rich
formatting and break totals to display the top five
ranked product sales for Q1 1999.

What's New in Brio Enterprise 6.0 37

Table Formatting
Rich sets of formatting options are available in the Table section,
including:

Table Level
• Hide/Show - column titles, row numbers
• Totals – display break and grand totals below data
• Border – line width, color
• Background – primary and alternate row colors, alternate row
frequency
• Gridlines – line width, style, color properties for row and column
gridlines

Column Level
• Suppress duplicates
• Font – name, size, style, color
• Number format
• Alignment – horizontal, vertical, and text wrap

Column Title Level

• Font – name, size, style, color
• Alignment – horizontal, vertical, and text wrap
• Background – color

Total Row Level

• Font – name, size, style, color
• Number format
• Alignment – horizontal, vertical, and text wrap

38 Chapter 4: Reporting and Analysis

Computed Columns

Figure 16 Computed Columns

The following new functions have been added to the point-and-click

method of building computed columns.

New Statistical Functions

• Median
• Mode
• Percentile
• Rank descending
• Rank ascending
• Standard deviation of a sample
• Standard deviation based on the entire population

What's New in Brio Enterprise 6.0 39

 • Variance of a sample
• Variance based on the entire population

New Numeric Functions

• Non-null average
• Count distinct
• Null count
• Non-null count
In addition to these built-in functions, JavaScript expressions can be
written to define more complex computed columns.

Chart Section

General Additions
Many high-value formatting aids have been added to the Chart section.
Changes include:
• Logarithmic Axis Scaling
The value axis may now be scaled on a base-10 log scale. This allows
large data values to be plotted in a more comprehensible manner.
• Legend
The chart legend can now be freely resized to make best use of either
horizontal or vertical space within the chart area.
• Hover Tips
Hover tips have been introduced to display information about the
category and values of bars, line points, and pie slices. Pause the
mouse over a pie slice or a bar and a hover tip will appear to provide
feedback on the underlying value of that element.
• Chart Type Palette
A chart-type palette has been introduced as a separate gadget from
the Outliner. This palette is located on the Section Toolbar, which
can be turned on by selecting it from the View menu.
• Line Values

40 Chapter 4: Reporting and Analysis

 Line charts may now have the data values displayed on each plotted
point. The values can be displayed above, below, left, or right of a
line data point.
• Color Control
Color choices are now set via the format toolbar color controls. This
change makes for a more consistent model to select and apply colors
across the reporting components.
• Statistical and Numeric Functions
The new statistical and numeric functions added to the Results
section are available for use in computed columns in the Chart
section. Refer to the Computed Columns section in the previous
page of this document for details.
• Predefined Drill Paths and Drill to Detail
Drill down along predefined Drill Paths is available in Charts, if the
drill paths have been defined in the Data Model. If Drill to Detail has
been enabled in the Data Model, the Chart shortcut menu will
include the option to transparently drill back to retrieve more data
from the database. Refer to the Relational Query highlights in this
document for details on these new features.

Pivot Section

General Additions
• Statistical and Numeric functions
The new statistical and numeric functions added to the Results
section are available for use in computed columns in the Pivot
section. Refer to the Computed Columns section in the previous
page of this document for details.
• Predefined Drill Paths and Drill to Detail
Drill down along Predefined Drill Paths is available in Pivot reports,
if the drill paths have been defined in the Data Model. If Drill to
Detail has been enabled in the Data Model, the Pivot shortcut menu
will include the option to transparently drill back to retrieve more
data from the database. Refer to the Relational Query highlights in
this document for details on these new features.
• Color Control

What's New in Brio Enterprise 6.0 41

 Color choices are now set via the format toolbar color controls. This
change makes for a more consistent model to select and apply colors
across the reporting components.

42 Chapter 4: Reporting and Analysis

5 Server Enhancements

Brio OnDemand Server

Enhanced Scalability
Brio OnDemand Server scalability has been significantly enhanced.
Scalability improvements are found in both performance of query
processing and reduction of the system resources used by the Brio
OnDemand Server. Three key changes are responsible for the increased
scalability:
• The BrioQuery Daemon, which performs the database transactions
for the Brio OnDemand Server, has been streamlined to remove
unneeded function calls. This has resulted in decreasing the daemon
startup time and increasing database transaction performance, all
while decreasing the system resources used. This change also
eliminates the need for third party XVFB software on UNIX systems.
• The Brio OnDemand Server now streams documents from disk
directly back to the client rather than performing a more resource
and time expensive open action by a server-based BrioQuery
Daemon. This results in less work on the server and faster response
for clients.
• In version 6.0, the Brio OnDemand Server performs file serialization
inside the Node component rather than calling an external
serialization routine. This increases performance.

43
Load Balancing and Failover
The Brio OnDemand Server now supports load balancing and failover
across a cluster of servers. Each Brio OnDemand Server cluster is
comprised of a Manager and one or more Nodes. Transaction requests
are all received by the Manager, which distributes the request to one of
the Nodes in the cluster. If a Node fails while performing a transaction,
the manager automatically forwards the request to a different Node in
the cluster.
The configuration of hardware in the cluster is scaleable to allow
virtually unlimited expansion. The physical server where the Manager is
installed may also serve as a Node. Additional Nodes must each reside
on separate physical servers. Mixing a Windows NT Manager with
Windows NT and UNIX Nodes is fully supported.
The configuration information, documents and connection files are
automatically replicated from the Manager to all Nodes in the cluster.

Application Look and Feel

The Brio OnDemand Server default HTML interface has been
streamlined to allow for easier navigation and location of documents, as
well as being more customizable and easier to maintain. Significant
changes include:

New Start Page

The Brio OnDemand Server now ships with a starting HTML page that
provides a new application look for the server. This HTML page is fully
customizable. It can be implemented as a static HTML document, rather
than one that dynamically served by the Brio OnDemand Server.

44 Chapter 5: Server Enhancements

Figure 17 Brio OnDemand Server’s HTML Start Page

Floating Document List

Upon logging on, the list of available documents is presented as a
floating window. The HTLM has been restructured to allow customers to
easily create custom interfaces, or select from a choice of custom
interfaces for the end users. A user preference is available to allow the
same look as the previous version (a framed interface.)

What's New in Brio Enterprise 6.0 45

 Document List Array
The Brio OnDemand Server now has the option to return the document
information to the browser in the form of a JavaScript array. By
returning the document information in an array, the administrator has a
great deal of flexibility in designing custom solutions. An example of this
post-processing capability is the new search capability described below.

Search Capability
The document list now includes a search capability. The floating
document window includes a search field to allow searching for
documents containing any arbitrary text string in the document name or
description. Search results are displayed as a list of hyperlinks along
with the descriptions of the documents.

Figure 18 Search Capability in Brio OnDemand Server

46 Chapter 5: Server Enhancements

 Folders in the Document List
Documents registered to the Brio OnDemand Server may now be placed
in a folder structure, with an unlimited number of nested folders. The
document list presented to the user will display a Windows-Explorer-
like interface with cascading folders allowing the logical categorization
of documents by department, project, or any other logical grouping.

Zero-Admin Code Restructure

The JavaScript and Wizard dialogs used for the Zero-Admin Client
downloads have been restructured into multiple independent files to
easily support site-specific customization.

Local Browser Values Available to Plug-in Scripting

Local values available to the browser are now available for use in the
plug-in scripting language. Requests to the Brio OnDemand Server may
include the trigger to include these browser values to be accessible to the
script language. The local browser values that are available are HTML
form elements, URL string values, and client cookies. This capability
allows application designers to integrate the Brio web clients into a
custom solution that passes information for the outside application into
the Brio document. Once these external values are available to the Brio
scripting language, they may be used to set limits, set usernames,
identify request line items, or any other function available with
JavaScript and the Brio Object Model.

Log Files and Options

Additional log files and logging options are available for troubleshooting
the Brio OnDemand Server. Separate log files are kept for the
ODSManager and the ODSNode. Two logging levels are available –
standard and trace. Trace logging tracks all events processed by the Brio
OnDemand Server while standard is an abbreviated log format of the
most common events. Options to log activity of the ODSProcessFactory
and the ODSCGI have also been added.

What's New in Brio Enterprise 6.0 47

Brio Broadcast Server

Storing Brio Broadcast Server Documents in the File System

The Brio Broadcast Server may now be configured to store its input
documents on the server’s file system rather than always storing these
documents as binary segments in the database repository. This change
has two advantages:
• Performance in registering documents to the Brio Broadcast Server
will be dramatically improved in many cases. Rather than breaking
the document into binary ‘chunks’ and saving them in the
repository, the document is streamed directly to the server which
saves the file on the file system.
• To better integrate with custom and OEM solutions, Brio Broadcast
Server has become a more open application. A document may be
introduced to the Brio Broadcast Server system by simply copying it
to a specific directory on the server and updating the Brio Broadcast
Server Repository tables with text-only information. In prior
versions, the upload of the binary document to a database table was
a proprietary Brio process which external developers could not
automate.
Changing the configuration of your server to use the new file system
storage includes automatic migration of existing repository-based
documents the first time the job is executed by the new server.

Email Signature Customization

The email messages sent out by the Brio Broadcast Server now allow
customization of the signature. The default signature sent by all Brio
Broadcast Server-generated emails is “Auto Generated message from
Brio Broadcast Server, copyright 1999, Brio Technology, Inc." The server
administrator may now customize this message.

Brio Web Clients

48 Chapter 5: Server Enhancements

New Look
The Brio Web clients inherit the same overall new look as in the
BrioQuery application, in addition to some minor changes. The most
noticeable of these changes is the addition of a Brio menu bar in the
Windows plug-ins. In order to maximize the useable screen area, it is
recommended the browser plug-ins be opened into a full-size window
rather than a framed web page. The new default Brio OnDemand Server
pages have a preference to manage this setting, with full-size as the
default.

Proxy Server Support

To better work in large network environments or extranet solutions,
Brio.Insight and Brio.Quickview web clients now support proxy servers.
An option to record the location of the proxy server is available under
the Tools menu.

Web Client Scheduling Capability

Brio.Insight now has the capability to schedule jobs to the Brio Broadcast
Server. Documents loaded into Brio.Insight allow the user to request the
document to be scheduled, following the same permissions and
restrictions as a user of the BrioQuery client/server products.

SSL Support
Brio web clients now support SSL for all Brio OnDemand Server
communications with SSL-enabled web servers. This includes re-
processing a query to retrieve new results (a capability not supported via
SSL in prior releases.) The Brio web clients include encryption software
licensed from RSA Data Security, the leading supplier of SSL encryption
software. SSL support is transparently built-in for 64-bit keys, with a
server-side option to enable 128-bit keys.

Setup

What's New in Brio Enterprise 6.0 49

Automatic Configuration for Microsoft IIS 4
The Brio OnDemand Server setup includes a configuration utility to
complete the settings for certain versions of Microsoft IIS web servers.

Enhanced Upgrading
The server setup program identifies prior installations and upgrades
them.

Improved Uninstall
The server setup program will now uninstall all of the components of the
OnDemand and Brio Broadcast Server, including the removal of their
Windows NT services. Additionally, uninstall on UNIX has been
upgraded to be more intelligent and complete.

UNIX Web Server Support

The Brio OnDemand Server installation program now automatically
configures Netscape web servers. This eliminates the error-prone manual
modification of Netscape configuration files.
Full support for Apache UNIX Web servers is introduced in this release.
Apache Web servers use the Brio CGI Web Broker and are configured as
part of the installation process.

Server Admin OEM-able

The Server Administrator is now OEM-customizable, just like BrioQuery
and the Brio Web clients. The product name, splash screen, help file, and
other OEM settings can be defined by the OEM. The OEM configuration
is defined in the same bqoem.ini file as the other products. The new
section [ADMIN_CUSTOM] has been added to this file.

50 Chapter 5: Server Enhancements

51
Index

1 D
128-bit keys, 49 Data Model, 3
Default document directory, 3
Design
6 Guides, 25
64-bit keys, 49
Tools, 33
Detail section, 31
A Document list array, 46
Active reports, 23 Document map, 1, 3
Alternate metadata connection, 17 Drill Down, 8
Analytic applications, 21 Drill to Detail, 14, 41
Apache Web servers, 50 Drill Up, 8
Applix TM1, 7
Ardent DataStage, 16
E
EIS section, 3, 22
B Email signature customization, 48
Banded report layout, 31 Embedded sections, 22, 23
bqoem.ini, 50 Encryption, 49
Break totals, 36 Epoch setting, 4
Brio OnDemand Server, 43 Essbase 5.x on Windows and UNIX, 19
Brio Web clients, 49 Excel, 27
BrioQuery Daemon, 43 Execution windows, 28
Broadbase, 16 Expression bar, 34
Extended EIS controls, 22, 24
C
Catalog pane, 3 F
CGI Web Broker, 50 Failover, 44
Chart File serialization, 43
Section, 3, 40 Filter box, 9
Chart type palette, 40 Floating document list, 45
Color control, 41 Floating toolbars, 3
Computed columns, 39 Folder structure, 47
Computed fields, 34
Connection files, 17
Console windows, 28
G
Grand totals, 36
Convert to Report, 32
Grid, 25
Cookies, 47
Correlated subqueries, 13
Customization by OEM, 50 H
Customization of email signature, 48 Hardwire query mode, 7

What's New in Brio Enterprise 6.0 53

Headers/Footers, 33 Multidimensional databases, 5
Hide the toolbars, 28 Multiple data sources, 34
Home, 3
Hover tips, 40
HTML
N
Native server features, 10
Interface, 44
Navigation, 3
Start page, 44
NCR TeraCube, 6
Hyperion Essbase, 6
Netscape JavaScript, 25
Hyperlink reports, 23
Netscape web servers, auto configuration, 50
Nodes with NT and UNIX, 44
I Numeric functions, 40
IBM
DB2 for OLAP, 6 O
Visual Warehouse, 16
Object Browser, 28
Incremental drilling, 15
Object Model, 26
Informatica PowerMart, 16
Object Model and scripting, 23
Informix MetaCube, 6
OCEs, 17
Intersections, 12
ODBC connections, 18
ODBO, 6
J OEM customization, 50
JavaScript, 25 Offline access, 7
OLAP Query, 5
OLEDB for OLAP, 19
L Outliners, 3
Layout aids, 25
Legend, 40
Leverage knowledge of industry-specific P
practices, 21 Page layout mode, 33
Limit joins, 13 Palettes, 3
Line values, 40 Passwords, 4
Load balancing, 44 Pivot section, 3, 41
Local browser values, 47 Pivotal year, 4
Log files, 47 Plato, 6
Logarithmic axis scaling, 40 Pre-computed fields, 34
Look and feel, 2 Predefined drill paths, 14, 41
Prism Solutions, 16
Process query mode, 7
M Programmability, 26
Master Data Models, 11
Proxy Server Support, 49
MDD, 5
Member Selection, 8
MetaCube, 19 Q
Microsoft Query section, 3
IIS 4, automatic configuration, 50
Office 2000, 2
OLAP Services, 19
R
Remarks interface, 16
SQL Server, 6, 19
Report Designer, 31
Minus Queries, 12
Report section, 3

54 Index
Report setup, 33 Subqueries, 13
Reports Supported databases, 6
Problems with migration, 32
Resizing of objects, 25
Results Section, 35
T
Table formatting, 38
RSA data security, 49
Table Section, 35
Rulers, 25
Toolbars, 3

S U
SAP BW, 7
Uninstall, 50
SAS MDDB, 6
Unions and subqueries, 12
Scalability, 43
UNIX Web server support, 50
Script building tools, 28
Upgrading, 50
Script Editor, 28
Search capability, 46
Section V
Chart, 3, 40 View-only reports, 23
EIS, 3 Visual Basic for Applications, 27
Embedded, 23
Pivot, 3, 41
Query, 3
W
Web client scheduling capability, 49
Report, 3
WhiteLight, 6
Results, 35
Wizard
Table, 35
Meta connection, 16
Section bar, 3
Wizard, 47
Section boundaries, 33
Connection, 16, 17
Security, 49
Slicer tool, 8
Snap In metadata templates, 16 Y
SSL support, 49 Y2K, 4
Statistical and numeric functions, 41
Statistical functions, 39
Stored procedures, 18
Z
Zero-Admin Code, 47
Storing Brio Broadcast Server documents, 48

What's New in Brio Enterprise 6.0 55