Dim Eta Data Reports

Data Integrator Metadata Reports User’s
Guide
Data Integrator 11.5.1.5
for Windows and UNIX

Patents Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.
Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.
Third-party Business Objects products in this release may contain redistributions of software licensed
contributors from third-party contributors. Some of these individual components may also be available
under alternative licenses. A partial listing of third-party contributors that have requested or
permitted acknowledgments, as well as required notices, can be found at:
http://www.businessobjects.com/thirdparty
Copyright Copyright © 2005 Business Objects. All rights reserved.
Date February 28, 2006

Contents
Chapter 1 Introduction 7
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Who should read this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Business Objects information resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 2 Viewing Metadata Reports 11

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Repository reporting tables and views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Adding Metadata Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Opening Metadata Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 3 Impact and Lineage Analysis Reports 19

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Analysis options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table-level and column-level analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Impact and Lineage Analysis Settings control panel . . . . . . . . . . . . . . . . . 27
Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Refresh Usage Data tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Business Objects Connections tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 4 Operational Dashboard Reports 31

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Dashboards home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Data Integrator Metadata Reports User’s Guide 3

Contents
Job execution statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Current (snapshot) pie chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Historical (trend) bar chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Job execution duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Current (snapshot) speedometer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Historical (trend) line chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Operational dashboards Settings control panel . . . . . . . . . . . . . . . . . . . . . 41
Chapter 5 Data Quality Dashboard Reports 43

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configuring Data Quality dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating functional areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Creating business rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Enabling data quality statistics collection . . . . . . . . . . . . . . . . . . . . . . . 49
Validation transform level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Job execution level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Viewing Data Quality dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Functional area view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Functional area pie chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
History line chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Business rule view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Validation rule view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Validation rule bar chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Sample data view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Sample data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Data Quality dashboards Settings control panel . . . . . . . . . . . . . . . . . . . . . 56
Repository tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Functional area tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Business rule tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4 Data Integrator Metadata Reports User’s Guide

Contents
Chapter 6 Auto Documentation Reports 59

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Work flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Generating documentation for an object . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Auto Documentation Settings control panel . . . . . . . . . . . . . . . . . . . . . . . . 65
Index 67

Contents

Data Integrator Metadata Reports User’s Guide
Introduction
chapter
1 Introduction
About this guide
About this guide

This guide describes how to use Data Integrator’s metadata reporting tool.
Using the web-based metadata reporting tool, you can easily browse,
analyze, and produce reports on the metadata in your repositories.
Metadata Reports provides four modules for exploring your metadata:
• Impact and Lineage Analysis Reports
• Operational Dashboard Reports
• Data Quality Dashboard Reports
• Auto Documentation Reports
Who should read this guide

This guide is for Data Integrator users who want to use metadata reporting.
Business Objects information resources

Consult the Data Integrator Getting Started Guide for:
• An overview of Data Integrator products and architecture
• Data Integrator installation and configuration information
• A list of product documentation and a suggested reading path
After you install Data Integrator (with associated documentation), you can
view the technical documentation from several locations. To view
documentation in PDF format:
• Select Start > Programs > Data Integrator version > Data Integrator
Documentation and select:
• Release Notes—Opens this document, which includes known and
fixed bugs, migration considerations, and last-minute documentation
corrections
• Release Summary—Opens the Release Summary PDF, which
describes the latest Data Integrator features
• Technical Manuals—Opens a “master” PDF document that has
been compiled so you can search across the Data Integrator
documentation suite
• Tutorial—Opens the Data Integrator Tutorial PDF, which you can
use for basic stand-alone training purposes

Introduction
Business Objects information resources 1
• Select one of the following from the Designer’s Help menu:
• Release Notes
• Release Summary
• Technical Manuals
• Tutorial
Other links from the Designer’s Help menu include:
• DIZone—Opens a browser window to the DI Zone, an online resource for
the Data Integrator user community)
• Knowledge Base—Opens a browser window to Business Objects’
Technical Support Knowledge Exchange forum (access requires
registration)
• Select Help from the Data Integrator Administrator to open Technical
Manuals.
You can also view and download PDF documentation, including Data
Integrator documentation for previous releases (including Release
Summaries and Release Notes), by visiting the Business Objects
documentation Web site at http://support.businessobjects.com/
documentation/product_guides/%20default.asp.

1 Introduction
Business Objects information resources

Viewing Metadata Reports
chapter
2 Viewing Metadata Reports
Introduction
Introduction
The Web-based Metadata Reports application provides several convenient
graphical options for analyzing dependencies, managing job execution
performance, assessing source data quality, and producing documentation for
your Data Integrator projects.
Metadata Reports provide four modules for exploring your metadata:
• Impact and Lineage Analysis Reports—Allows you to easily browse,
analyze, and produce reports on the metadata for your Data Integrator
jobs as well as for other Business Objects applications associated with
Data Integrator
• Operational Dashboard Reports—Provides several standard graphical
dashboards that allow you to evaluate your job execution performance at
a glance
• Data Quality Dashboard Reports—Provide feedback that allows business
users to quickly review, assess, and identify potential inconsistencies or
errors in source data.
• Auto Documentation Reports—Offers a convenient way to create printed
documentation for the objects you create in Data Integrator by capturing
critical information so you can see an overview of the entire ETL process.
This chapter discusses:
• Repository reporting tables and views
• Requirements
• Adding Metadata Integrator
• Opening Metadata Reports
• Navigation
Repository reporting tables and views

The Data Integrator repository is a database that stores your application
components and the built-in Data Integrator design components and their
properties. The open architecture of the repository allows for metadata
sharing with other enterprise tools.
Within your repository, Data Integrator populates a special set of reporting
tables with metadata describing the objects in your repository. When you
query these tables, you can perform analyses on your Data Integrator
applications.

Repository reporting tables and views 2
Data Integrator metadata reporting tables and views are listed in the following
table and described in Chapter 8, Metadata in Repository Tables and Views,
in the Data Integrator Reference Guide. (Note that this is not the complete list
because some repository tables and views are for internal use.)
Name Contains
AL_ATTR Attribute information about native objects
AL_AUDIT Audit information about each data flow
execution
AL_AUDIT_INFO Information about audit statistics
AL_CMS_BV Components of a Business View
AL_CMS_BV_FIELDS Business Fields within Business Elements in a
Business View
AL_CMS_REPORTS Information that uniquely identifies Crystal
Reports, Desktop Intelligence document, or
Web Intelligence documents
AL_CMS_REPORTUSAGE Tables, columns, Business Views, or Universes
that a Crystal Report, Desktop Intelligence
Document, or Web Intelligence Document uses
AL_CMS_FOLDER Folder names in which a Crystal Report,
Desktop Intelligence Document, or Web
Intelligence Document resides
AL_CMS_UNV Information that uniquely identifies Universes
AL_CMS_UNV_OBJ Universe classes and the child objects, with the
source column and table
AL_HISTORY Execution statistics about jobs and data flows
AL_INDEX Index information about imported tables
AL_LANG Information about native (.atl) Data Integrator
objects
AL_LANGXMLTEXT Information about objects represented in XML
format
AL_PCOLUMN Column information about imported table
partitions
AL_PKEY Primary key information about imported tables
AL_QD_VRULE Stores the validation rule names
AL_QD_VRULE_OFLOW Stores the rule name if it cannot fit it into
AL_QD_VRULE (if there is an overflow)
AL_QD_STATS Runtime validation rule statistics

Repository reporting tables and views
Name Contains
AL_QD_ROW_DATA Sample row data for which the validation rules
have failed
AL_QD_COLINFO All the column information for the failed
validation rules
AL_USAGE All ancestor-descendant relationships between
Data Integrator objects
ALVW_COLUMNATTR Attribute information about imported columns.
ALVW_COLUMNINFO Information about imported column.
ALVW_FKREL Primary-foreign key relationships among
imported tables.
ALVW_FLOW_STAT Execution statistics about individual transforms
within data flows.
ALVW_FUNCINFO Information about both native functions and
functions imported from external systems.
ALVW_MAPPING Mapping and lineage information for target
tables.
ALVW_PARENT_CHILD Direct parent-child relationships between Data
Integrator objects.
AL_SETOPTIONS Option settings for all objects
ALVW_TABLEATTR Attribute information about imported (external)
tables.
ALVW_TABLEINFO Information about imported tables
Data Integrator automatically creates reporting tables for each new or
upgraded repository. Except for AL_USAGE, Data Integrator automatically
updates all reporting tables.
The Metadata Integrator collects metadata for Crystal Reports, Business
Views, Universes, Desktop Intelligence document, and Web Intelligence
documents from the Central Management Server (CMS) and stores the
metadata in the Data Integrator reporting tables that start with AL_CMS. For
more information about installing, configuring, and running the Metadata
Integrator, see “Adding Metadata Integrator” on page 15.

Requirements 2
Requirements
Use the Data Integrator Administrator to configure repositories for Metadata
Reports to access. See “Connecting repositories to the Administrator” on
page 24 of the Data Integrator Administrator Guide for detailed information.
To make metadata reports available for Data Integrator objects, the Metadata
Reports application requires:
• The Web Server service (which uses the Tomcat servlet engine)
• JDBC drivers to connect to a repository
• Configured Data Integrator repositories
• Installation and configuration of Metadata Integrator for impact and
lineage analysis on objects such as Universes and Crystal Reports. See
“Adding Metadata Integrator” on page 15.
Adding Metadata Integrator

You must install, configure, and run the Metadata Integrator to view impact
and lineage analysis reports for the following objects:
• Business Views
• Crystal Reports
• Universes
• Desktop Intelligence documents
• Web Intelligence documents
Metadata Integrator scans definitions on your Central Management Server
(CMS) to find the tables and columns used by the reports, views, and
documents. Metadata Integrator stores the collected metadata in your Data
Integrator repository for use by the impact and lineage analysis module (see
Chapter 4: Impact and Lineage Analysis Reports).

Adding Metadata Integrator
Note: To run the Metadata Integrator, you must have Java Runtime
Environment or Java Development Kit installed on the computer where CMS
is installed. Also ensure that the JAVA_HOME environment variable is set to
the directory where Java is installed.
To run the Metadata Integrator
1. Ensure that the Metadata Integrator is installed and configured on the
computer where CMS is installed. For details, see “Installing Metadata
Integrator” on page 86 and “Configuring the Metadata Integrator” on
page 88 of the Data Integrator Getting Started Guide.
2. On the Central Management Console, find the program object for the
Metadata Integrator.

Adding Metadata Integrator 2
3. On the History tab, select the Metadata Integrator and click Run Now.
4. On the Schedule tab, you can select the option to run Metadata Integrator
periodically to obtain changes to the report, Business View, Universe,
Desktop Intelligence, or Web Intelligence document definitions.

Opening Metadata Reports
Opening Metadata Reports

You can open the Metadata Reports application in several ways:
• From a Windows computer, click Start > Programs > Business Objects
Data Integrator version > Metadata Reports.
Data Integrator launches the login page. Enter the same information you
use to log in to the Web Administrator (the default user name is admin
and the default password is admin). Only users with valid Administrator
login privileges can log in to the Metadata Reports application.
• Open a Web browser and enter the URL for the Metadata Reports
application:
http://computer_name:port/reports
The default port is the same as the Web server (28080).
Data Integrator launches the login page. Enter the same information you
use to log in to the Web Administrator (the default user name is admin
and the default password is admin). Only users with valid Administrator
login privileges can log in to the Metadata Reports application.
• From Data Integrator Designer, select Tools > Metadata Reports, or
click the Metadata Reports tool bar icon.
Data Integrator opens the Metadata Reports home page which contains a link
for each module:
• Impact and Lineage Analysis Reports
• Operational Dashboard Reports
• Data Quality Dashboard Reports
• Auto Documentation Reports
Navigation
The upper-right corner of each Metadata Reports module includes the
following navigation links:
• Home—Click to return to the Metadata Reports home page (for example
to select another module).
• Settings—Click to open the Settings control panel for the current
module.
• Logout—Click to exit Metadata Reports.

Impact and Lineage Analysis

Reports
chapter
3 Impact and Lineage Analysis Reports
Introduction
Introduction
The Impact and Lineage Analysis module of Metadata Reports provides a
simple, graphical, and intuitive way to view and navigate through various
dependencies between objects.
Impact and lineage analysis allows you to identify which objects will be
affected if you change or remove other connected objects.
For example for impact analysis, a typical question might be, “If I drop the
source column Region from this table, which targets will be affected?”
For lineage analysis, the question might be, “Where does the data come from
that populates the Customer_ID column in this target?”
In addition to the objects in your Data Integrator datastores, Metadata Reports
impact and lineage analysis allows you to view the connections to other
objects including Universes, classes and objects, Business Views, Business
Elements and Fields, and reports (Crystal Reports, Desktop Intelligence
documents, and Web Intelligence documents).
This chapter discusses:
• Navigation
• Analysis options
• Table-level and column-level analysis
• Impact and Lineage Analysis Settings control panel
Navigation
From the Metadata Reports home page, view impact and lineage information
by clicking the Impact and Lineage Analysis link.
The Impact and Lineage Analysis page contains two primary panes:
• The left pane contains a hierarchy (tree) of objects. The top of the tree is
the default repository. This pane also includes a search tool.
• The right pane displays object content and context based on how you
navigate in both panes.
In general, expand the tree in the left pane by clicking plus signs (+) next to
object nodes. Select an object in the tree to learn more about it. Details
associated with an object appear in the right pane on one or more tabs. Tabs
vary depending on the object you select.

Impact and Lineage Analysis Reports
Navigation 3
The top level of the navigation tree displays the current repository. (You can
change this repository in the Settings control panel; for details, see “Settings
tab” on page 27.)
Objects in a repository include:
• Datastores—Contain Data Integrator tables and columns
• CMS server(s)—After you configure the Metadata Integrator (see “Adding
Metadata Integrator” on page 15), this node contains folders as defined in
the Business Objects Central Management Console, Universes, and
Business Views.
The Universe node displays classes, and each class contains objects.
Business Views contain Business Elements, and each Business Element
has Business Fields. Any object can contain one or more reports.
To narrow the view of objects to display in the navigation tree or to quickly find
specific objects in the repository, use the Objects to analyze search feature.
You can do one or both of the following:
1. Select a category in the Select an object type drop-down list:
• Table and column
• Universe
• Class and object
• Business view
• Element and field
• Report
AND/OR
2. Search for a specific object by typing all or part of the object name the
search field. The search field is not case sensitive, spaces are allowed,
and you can use the percent symbol (%) as a wildcard.
3. Click the search icon (binoculars).
Metadata Reports highlights each object that meets your search criteria with a
red border.
Note: If you receive an error such as the following:
This image is scaled to 50% of the original image. You could
avoid scaling the image by allocating more memory to the
current java process.
it means the java process (JVM) does not have enough memory to process
the current task. Circumvent this error by allocating more heap memory to the
Java process associated with the Data Integrator Web server as described in
the following procedures.

Analysis options
To increase the java heap memory in Windows

1. In the Windows Services control panel, stop the Data Integrator Web
Server.
2. In the Data Integrator installation directory, navigate to
\ext\WebServer\conf.
3. Using a text editor, open the wrapper.properties file.
4. To allocate a minimum of 256 MB and a maximum of 512 MB to the java
process, add the following parameters to wrapper.cmd_ line:
-Xms256M -Xmx512M
The result will appear as follows:
wrapper.cmd_line=$(wrapper.javabin) -Xms256M -Xmx512M
-Djava.endorsed.dirs==$(ACTAHOME)\ext\webserver\commo
n\endorsed
...
5. Save and close the file.
To increase the java heap memory in UNIX
1. Stop the Data Integrator Web Server.
2. In the Data Integrator installation directory, navigate to /ext/WebServer/
bin.
3. Using a text editor, open the setclasspath.sh file.
4. To allocate a minimum of 256 MB and a maximum of 512 MB to the java
process, add the following lines to the end of the setclasspath.sh file:
JAVA_OPTS="-Xms256M -Xmx512M"
export JAVA_OPTS
5. Save and close the file.
Analysis options
The following table lists the types of objects that can appear in the navigation
tree and provides a summary of what information appears in the right pane
when you select that object type.
To view or hide a pane in the display such as an attributes pane, click the up/
down arrow in its header bar.
Moving the cursor over an object displays a pop-up window with more
information about that object; for example:
• Table—Data flow (if applicable), datastore, and owner

Analysis options 3
• Business Objects report—Depending on the report type, the pop-up
window displays the CMS server name, the Business View name, or the
Universe name, for example.
• Universe objects—CMS server, universe, and class
The following table lists the objects in the navigation tree, the corresponding
tabs, and the content of each.
Object Tab Associated content

Repository Overview Repository name
Repository type—The database type
Repository version—The repository version number
Datastore Overview Overview information varies depending on the datastore type.
The following entries apply to a datastore on Microsoft SQL
Server.
Application type—Database
Database type—Microsoft_SQL_Server
User—(Database user name)
Case sensitive—Whether or not the database is case
sensitive
Configuration—(The configuration selected in the datastore
editor)
SQL_Server version—Microsoft SQL Server 2000
Database name—(Database name)
Server name—(The host computer name)
Table Overview Table name—Table name
Datastore—Datastore to which this table belongs
Owner name—The table owner name in the database.
Business name—Business-use name of the table if defined
Table type—Table or template table
Last update date—When Data Integrator last updated the
table
Impact Graphically shows the end-to-end impact of the selected
source table and the targets it affects.
Clicking a table in the Impact diagram displays the object’s
attributes, which are the same as on the Overview tab.
See “Table-level and column-level analysis” on page 26.
Lineage The Lineage tab contains the same information as on the
Impact tab except it describes the flow from target to source.

Analysis options

Column Overview Column name—Column name
Table name—Parent table of the column
Data type—The data type for the column
Nullable—yes/no
Primary key—yes/no
Foreign key—yes/no
Impact Graphically shows the end-to-end impact of the selected
source column and the targets it affects.
Clicking a column in the Impact diagram displays the object’s
attributes, which are the same as on the Overview tab.
See “Table-level and column-level analysis” on page 26.
Lineage The Lineage tab contains the same information as on the
Impact tab except it describes the flow from target to source.
Universe Overview Universe name
Folder—The folder name on the CMS server to where the
Universe has been exported
CMS server—The name of the CMS server for this Universe
Description—The description created for the Universe in
BusinessObjects Designer
Business View Overview Business View name
Folder—The folder name on the CMS server to where the
Business View has been exported
Last update date—When the Business View was last
updated in the Business View Manger
CMS server—The name of the CMS server for this Business
View
Class Overview Class name
Universe—Universe to which this class belongs
CMS server—The name of the CMS server for this class
Object Overview Object name
Class—The class to which this object belongs
Universe—Universe to which this object belongs
CMS Server—The name of the CMS server for this object
Source column—The name of the source column for this
object followed by the owner.table name
Impact Shows all the reports that use the selected object.

Analysis options 3
Lineage Shows column-level lineage for the selected object.
Business Overview Business element name
Element Business view—The Business View to which this business
element belongs
CMS server—The name of the CMS server for this object
Business Field Overview Business field name
Business element—The Business Element to which this
Business Field belongs
Business view—The Business View to which this Business
Field belongs
CMS server—The name of the CMS server for this object
Impact Shows all the reports that use the field.
Lineage Shows column-level lineage for the selected Business Field.
Reports: Overview Report name
Crystal Folder—The folder on the CMS server where the report is
stored
and
CMS server—The name of the CMS server for this report
Web
Intelligence/ Last update date——When the report was last updated
Desktop
Intelligence
Lineage Shows the lineage to the Universe objects or Business View

fields on which the report is based (if any) and the column-
level lineage in the Data Integrator datastore.

Table-level and column-level analysis
Table-level and column-level analysis

Impact and lineage analysis at the table level shows datastores, tables, and
reports/documents as shown in the following graphic.

Impact and Lineage Analysis Settings control panel 3
Impact and lineage analysis at the column level shows datastores, objects,
fields, and reports/documents as shown in the following graphic.
Note: If a report includes conditions predefined in a Universe, the columns

used by those conditions will not appear on the Impact and Lineage Analysis
report because the metadata collected for Universes is limited to the tables
and columns referenced directly by Universe objects.
Impact and Lineage Analysis Settings control

panel
The Impact and Lineage Analysis Settings control panel allows you to change
the options for your reports. To open it, click Settings in the upper-right
corner of the Metadata Reports window.
Settings tab
The Settings tab allows you to change repositories. Select a repository from
the drop-down list box and click Apply.

Impact and Lineage Analysis Settings control panel
Refresh Usage Data tab

You can calculate column mappings from the Metadata Reports application
(or from the Designer) at any time.
The Calculate Column Mappings option populates the internal
ALVW_MAPPING view and the AL_COLMAP_NAMES table. The
ALVW_MAPPING view provides current data to Metadata Reports. If you
need to generate a report about a data flow that processes nested (NRDM)
data, query the AL_COLMAP_NAMES table using a custom report. For more
information, see “Storing nested column-mapping data” on page 602 of the
Data Integrator Reference Guide.
Data Integrator calculates column mappings automatically when you save
data flows in the Designer. (To change the default, clear the check box under
Tools > Options > Designer > General > Calculate column mapping while
saving data flow.)
Note: If you do not select Calculate column mappings when saving data
flows, you must select Calculate Column Mappings manually before
generating reports to ensure that Data Integrator returns accurate mapping
information. For example, assume you do not have Calculate column
mappings when saving data flows selected. You click the Calculate
Column Mappings button and you are able to view your column mappings.
So far, everything is fine. Now, you unintentionally move an object in a data
flow. When you try to execute the job, Data Integrator prompts you to save the
changes to the data flow. You comply. The next time you attempt to view
mapping information for the data flow, the information is gone because the
saved data flow is a new object in the repository. It does not have column
mapping information until you manually calculate it.
To calculate column mappings in the Metadata Reports application
1. In the Impact and Lineage Settings control panel, click the Refresh
Usage Data tab.
2. Select the Job Server that is associated with the repository you want to
use.
3. Click Calculate Column Mappings.
To calculate column mappings from the Designer
Right-click the object library and select Repository > Calculate column
mappings.

Impact and Lineage Analysis Settings control panel 3
Business Objects Connections tab
Use the Business Objects Connections tab to create a connection to a
BusinessObjects Enterprise 6.5 repository.
To add a connection to a BusinessObjects Enterprise 6.5 repository
1. Click Add. The Enter database connection information window
appears:
2. Enter the following information for the repository.
Option Description
Repository name Logical name for the repository.
Connection type Select a Business Objects or Auditor repository.
Database type The type of database storing your repository. Select one of the
following database types:
• DB2
• Informix
• Microsoft SQL Server
• ODBC
• Oracle
• Sybase ASE
Host name Host name where the repository resides.
Database port Port number of the repository or data source.
Service Name/SID, This field requires additional information based on the Database
Database name, Server Type you select.
name, or Data source
User name The user or owner name for the repository or data source.
Password The user’s account password for the repository or data source.
3. (Optional) To test the database information you have specified for the
repository, click Test. If there are no Business Objects repository tables in
the database, you will receive a notice that you can connect to the
database but that there are no repository tables.
4. Click Apply.
When you return to Metadata Reports, the navigation tree will display the
pertinent objects with respect to your selected repository.
To remove a connection, on the Business Objects Connections tab select the
check box for the connection and click Remove.

Impact and Lineage Analysis Settings control panel
About tab
This tab provides Data Integrator version information.

Operational Dashboard
Reports
chapter
4 Operational Dashboard Reports
Introduction
Introduction
Operational dashboard reports provide graphical depictions of Data Integrator
job execution statistics. This feedback allows you to view at a glance the
status and performance of your job executions for one or more repositories
over a given time period. You can then use this information to streamline and
monitor your job scheduling and management for maximizing overall
efficiency and performance.
For more information about how to use these reports to answer performance
questions, see Chapter 3, Measuring and Tuning Data Integrator
Performance,” in the Data Integrator Performance Optimization Guide.
This chapter describes:
• Dashboards home page
• Job execution statistics
• Job execution duration
• Operational dashboards Settings control panel
Dashboards home page

To view operational dashboards, on the metadata reports home page, click
Operational Dashboards.
The upper-right corner identifies the repository for the reports you are
viewing. You can change the repository to view in the dashboards settings
control panel (see “Operational dashboards Settings control panel” on
page 41).
You can drill into these dashboards for more details. The navigation path at
the top of the window indicates where you are in the operational dashboard
reports hierarchy. Click the hyperlinks to navigate to different levels. Click the
Operational tab to return to the dashboards home page.
There are two categories of dashboards: Job Execution Statistics and Job
Execution Duration. Each category contains a current (snapshot) report and a
historical (trend) report. Hence, the dashboards in the top row provide a
snapshot for the last 24 hours, and the dashboards on the bottom row display
trends over the last 7 days.
• Job execution statistics— Left side of dashboards home page. These
reports depict job execution statistics—how many jobs succeeded or had
errors:
• Current (snapshot) pie chart

Operational Dashboard Reports
Dashboards home page 4
• Historical (trend) bar chart
• Job execution duration—Right side of page. These reports depict how
long it took the jobs to run and whether those run times were within
acceptable limits:
• Current (snapshot) speedometer
• Historical (trend) line chart
Job statistics Job duration
Current
Historical
The following sections describe the contents of these reports and their
subreports.

Job execution statistics
Job execution statistics

Job execution statistics display in two formats on the left side of the page:
• Historical (trend) bar chart
The color codes on these two charts apply to the status of the job’s execution:
• Succeeded (green)
• One or more warnings (orange)
• One or more errors (red)
• Still running (blue)
Current (snapshot) pie chart

The pie chart displays status information for jobs that ran in the time period
displayed. You can change the start time and execution time window in the
dashboard Settings control panel (see “Operational dashboards Settings
control panel” on page 41).
The chart identifies the number and ratio of jobs that succeeded, had one or
more warnings, had one or more errors, or are still currently running.
Click on the pie “slices” to drill into the report, which displays a tabular list of
jobs within that group. From there you can click on the status tabs to view the
list of jobs in each group.

Job execution statistics 4
Each Job Execution Statistics table includes:

• Repository name—The repository associated to this job
• Job name—The name of the job in the Designer
• Start time and End time—The start and end timestamps in the format
hh:mm:ss.
• Execution time—The elapsed time to execute the job (how long it took to
run)
• System configuration—The name of the system configuration that applies
to that job. For details on system configurations, see “Creating and
managing multiple datastore configurations” on page 113 of the Data
Integrator Designer Guide .
Click the Operational tab or the link in the navigation path at the top of the
window to return to the dashboards home page.
Historical (trend) bar chart

The Job Execution Statistic History bar chart depicts how many jobs
succeeded, had warnings, failed, or are still currently running on each of the
last 7 days.

Job execution duration
As with the Job Execution Statistics pie chart, you can click on the individual
bars to drill into the report to display the Job Execution Statistics status tables
(succeeded, warning, error, etc.). See “Current (snapshot) pie chart” on
page 34 for details on the Job Execution Statistics tables.

Job execution duration reports display in two dashboards on the right side of
the dashboards home page:
• Historical (trend) line chart
The color codes on these two charts describe whether the set of jobs
executed within the allotted time frames that you set in the in the dashboard
Settings control panel (see “Operational dashboards Settings control panel”
on page 41).
• Normal (green)—All jobs executed within the job execution time window.
This window is the amount of time that you allot to run your jobs (so your
target data warehouse is available to applications and business users
during peak hours, for example). Specify this window with the Job
execution time window setting.
The size of the green zone changes based on the Job execution time
window setting.
• Warnings (orange)—At least one job finished executing during the
tolerance period. Tolerance is the amount of time that jobs can run
beyond your normal Job execution time window. Specify this tolerance
limit with the Job execution time window tolerance setting.
The size of the orange zone changes based on the Job execution time
window tolerance setting.

Job execution duration 4
• Critical (red)—At least one job finished executing beyond the normal or
warning (tolerance) limits.
The size of the red zone is fixed.
Current (snapshot) speedometer

The speedometer graphic displays the window of time allotted for your jobs to
complete their executions and whether the jobs as a whole finished within the
allocated time frame.
Note: This dashboard does not indicate whether a job succeeded or had
errors; it only displays execution duration. Drill into the speedometer
dashboard to see a Gantt chart that displays whether the job succeeded and
where it finished executing in the allotted time frame.
The actual elapsed time displays above the speedometer graphic. For
example,
8/23/05 2:00 AM - 8/23/05 1:38 PM
is the time elapsed from the start of the first job to end of last job.
You can move the pointer over this range to display the Job Execution
Duration (total elapsed time) in a pop-up window (in this case, Job Execution
Duration = 7h 40m 1s). The same value displays below the needle hub in
decimal form (in this case 7.667 hours). For example, say jobs J1, J2, and J3
are scheduled to run in parallel. J1 starts first and J3 finishes last. The
elapsed time displayed reflects the end time of J3 minus the start time of J1.
The left side of the speedometer (at the 0 end) indicates the start time as
defined in the Operational dashboards Settings control panel (for example
2:00 AM).
The colored zones are:

• Green—Normal. If the needle points in this range, all jobs executed in the
allotted time frame. The number displayed at the high end of the green
range is the Job execution time window setting in number of hours. For
example, if your start time is 2:00 AM and the number displays 7, your
preferred time window to execute all jobs is from 2:00 AM to 9:00 AM.
• Orange—Warning. If the needle points in this range, some jobs executed
in the (optional) Job execution time window tolerance setting. For
example, if the high end of the green zone is 7 and the orange zone
denotes 8, your tolerance for all jobs to execute is one additional hour.
• Red—Critical. If the needle points in this range, some jobs executed
beyond the normal or tolerance ranges. The high end of this zone is 24
hours.
Note that the needle hub also changes color to reflect in which range the
needle points.
Click on the speedometer to drill into the report and display a Gantt chart of
the Jobs Execution Duration for the jobs.
In the Job execution Gantt chart, each job shows its start time, end time, and
status (succeeded, warning, etc.). The orange line denotes the high end of
the Job execution time window setting, and the red line indicates the high

Job execution duration 4
end of the Job execution time window tolerance setting (see “Operational
dashboards Settings control panel” on page 41). You can move the pointer
over the Gantt bars to view a pop-up window with the Job Execution Duration
(total elapsed time).
From this window, you can drill into the job for data flow execution duration
times and audit details if applicable. Click on a Gantt bar to display the Data
Flow Execution Duration Gantt chart:
The Data Flow Execution Duration Gantt chart lists the data flows in the job
and the execution duration of each. It also shows the Job execution time
window tolerance (red) and Job execution time window (orange) limits.
You can move the pointer over the Gantt bars to view a pop-up window of the
execution duration (elapsed time), and if you enabled auditing for the job, the
audit status also displays:
• Not audited
• Success—All audit rules succeeded
• Collected—This status occurs when you define audit labels to collect
statistics but do not define audit rules
• Failed—Audit rule failed
If auditing has been enabled, click on the Gantt bar for the data flow to display
the Audit Details page:

In addition to job name, data flow name, and job start time, the report
includes:
• Audit rule information if applicable
• Audit failed information if applicable
• A table with the audit labels and values
For more information about auditing, see “Using Auditing” on page 348 of the
Data Integrator Designer Guide .
You can view Job Execution Duration and Data Flow Execution Duration
information in both graphical and tabular formats. Click the Graph or Table
tabs accordingly.
The Job Execution Duration table displays the repository name, the job name
(on which you can click to drill in to the Data Flow Execution Duration table),
the start and end time of the job execution, the execution time (elapsed), the
status, and whether the job is associated with a system configuration.
The Data Flow Execution Duration table shows the repository name, the data
flow name, the job name, the start and end time of the data flow execution,
the execution time (elapsed), the number of rows extracted and loaded, and
the audit status. You can view the Audit Details page from the Table tab by
clicking on a value in the Audit status column.
Historical (trend) line chart

The Job Execution Duration History line chart shows the trend of job
execution performance over the last 7 days. The vertical axis is in hours, the
horizontal axis shows the date, and the color panels illustrate the limits set for
the job execution period.

Operational dashboards Settings control panel 4
Each point denotes the Job Execution Duration (total elapsed time) of all the
jobs for that day. If you move the pointer over the point for Today for example,
it is the same value as when you move the pointer over the speedometer
graphic.
Click on the points to drill in to display the Job Execution Duration Gantt chart
as described in the previous section Current (snapshot) speedometer.
Also as with the speedometer dashboard, you can drill into the job for data
flow execution duration times and audit details by clicking on a Gantt bar to
display the Data Flow Execution Duration window. Additionally, if auditing has
been enabled, click on the Gantt bar to display the Audit Details page.
See “Current (snapshot) speedometer” on page 37 for details on the Job
Execution Duration Gantt chart, the Data Flow Execution Duration Gantt
chart, and the Audit Details pages.
Operational dashboards Settings control

panel
The dashboard settings window allows you to change the options for your
reports.
In the upper-right corner of the metadata reports window, click Settings.
The dashboard settings are:

Operational dashboards Settings control panel
• Select repository—Select all or a specific repository from the drop-down

list box.
• View data starting at—For Job Execution Duration and Job Execution
Duration History reports, enter the start of the job execution window in the
format HH:MM (from 00:00 to 23:59).
• Job execution time window—For Job Execution Duration and Job
Execution Duration History reports, enter the number of hours (numeric
value from 0 to 24) that you have available to run your ETL jobs.
• Job execution time window tolerance—For Job Execution Duration
and Job Execution Duration History reports, optionally enter a number of
hours to add to the Job execution time window, which will display as a
warning (orange) area (on the speedometer and line charts) or red line
limit (on Gantt charts).
This field accepts numeric values from 0 to 24. The total of the Job
execution time window parameter and the and Job execution time
window tolerance cannot exceed 24.

Data Quality Dashboard

Reports
chapter
5 Data Quality Dashboard Reports
Introduction
Introduction
Data Quality dashboard reports provide graphical depictions that let you
evaluate the reliability of your target data based on the validation rules you
created in your Data Integrator batch jobs. This feedback allows business
users to quickly review, assess, and identify potential inconsistencies or
errors in source data.
This chapter describes:
• Configuring Data Quality dashboards
• Functional area view
• Business rule view
• Validation rule view
• Sample data view
• Data Quality dashboards Settings control panel
Configuring Data Quality dashboards

To generate meaningful Data Quality dashboards, follow this process:
1. In your Data Integrator jobs in Designer, create data flows that contain
validation transforms with validation rules. You use validation transforms
to:
• Verify that your source data meets your business rules.
• Take the appropriate actions when the data does not meet your business
rules.
For more information on configuring and using the validation transform,
see the following sections:
• “Using the Validation transform” on page 343 of the Data Integrator
Designer Guide
• “Validation” on page 368 of the Data Integrator Reference Guide
2. In the Metadata Reports application in the Data Quality module, create
functional areas. A functional area is a virtual group of jobs that relate to
the same business function, for example Human Resources or
Customers. Functional areas can contain multiple Data Integrator jobs
and one or more data quality business rules. See “Creating functional
areas” on page 45.
3. In the Metadata Reports application in the Data Quality module, create
business rules. Business rules are typical categories of data, for example
Social Security Number or Address. See “Creating business rules” on

Data Quality Dashboard Reports
Configuring Data Quality dashboards 5
page 47. These business rules contain validation rules that you created
in your validation transforms in your data flows (see “Using the Validation
transform” on page 343 of the Data Integrator Designer Guide ).
Begin by opening the Metadata Reports application and clicking the Data
Quality link on the Home page.
Creating functional areas

After you create data flows with validation transforms and rules, next create
functional areas as follows.
Note: If you do not create any functional areas, the dashboard will display
statistics for all jobs for the selected repository.
To create functional areas
1. In the Data Quality module, click the Settings link.
The Repository tab displays.
2. Verify the desired repository displays.
To change the repository, select a different one from the drop-down list
and click Apply.
3. Click the Functional area tab.
The selected repository displays.
4. Type a name for the new functional area (such as Customer) and
optionally a description.
5. Click Save.
A list of batch jobs (and the associated system configuration for each, if
any) appears that lets you select the jobs you want to include in this
functional area.
For more information on system configurations, see “Creating and
managing multiple datastore configurations” on page 113 of the Data
Integrator Designer Guide .
You can change the sort order of the table by clicking the arrow in a
column heading.
6. From the list of Available batch jobs, select the check box for each job to
include in this functional area and click the arrow button to move it to the
Associated batch jobs window.
Note: In the Web administrator, deleting job information on the Batch
Job Status page (Batch Jobs History) also clears data quality statistics
from Data Quality Metadata Reports.

7. Click Apply to save the changes and keep the Functional area dialog box
open, for example to add more functional areas.
Clicking OK saves your changes and closes the Settings control panel.
Clicking Cancel closes the Settings control panel without saving
changes.
To add another functional area, on the Functional area tab click Add and
follow steps 4 through 7 in the previous procedure.
To display a different functional area for editing, select it from the drop-down
list.
Delete a functional area by clicking Delete next to the functional area
selected in the drop-down list.
Next, create business rules to associate the validation rules in your data flows
with your functional areas as described in the next section.

Creating business rules
After creating functional areas, associate business rules to each functional
area as follows.
Note: If you do not create business rules, each validation rule in the jobs that
you have associated with a functional area becomes its own business rule.
To create business rules
1. In the Settings control panel, click the Business rule tab.
On the Business rule tab, the default repository displays. (To change the
repository, click the Repository tab, select a different repository, and
click Apply.)
2. From the drop-down list, select the functional area to which this business
rule will belong.
3. In the business rule definition area, type a name for the business rule
such as Phone number.
4. Select a priority for how significant this group will be to your business end
users: High, Medium, or Low.
5. Type an optional description for the business rule such as Phone and
FAX. In this example, the validation rule checks to see if telephone and
fax numbers in the USA conform to the seven-digit standard.
6. Click Save.
A list of validation rules appears. Select the validation rules you want to
include in this business rule. See the table below for a description of the
columns in the lists of validation rules (scroll horizontally to view the other
columns).
7. From the list of Available validation rules, select the check box for all of
the rules to include in this business rule and click the arrow button to
move it to the Associated validation rules window.
Note: Validation rules are not reusable among business rules (you can
use a validation rule only once and only in one business rule).

8. Click Apply to save the changes and keep the business rules dialog box
open, for example to add more business rules.
Clicking OK saves your changes and closes the Settings control panel.
Clicking Cancel closes the Settings control panel without saving
changes.

The columns in the validation rule lists are as follows. Scroll horizontally to
view the other columns. Note that you can change the sort order of the tables
by clicking the arrow in a column heading.
Column Description
Validation rule name The validation rule name in Data Integrator. The
default is the column name unless you create a new
name in the validation transform Properties dialog
box. See “Using the Validation transform” on
page 343 of the Data Integrator Designer Guide and
“Validation” on page 368 of the Data Integrator
Reference Guide.
Description The description for the validation rule in Data
Integrator. See “Using the Validation transform” on
page 343 of the Data Integrator Designer Guide and
“Validation” on page 368 of the Data Integrator
Reference Guide.
Full path Describes the hierarchy in Data Integrator from the
job level to the data flow level to indicate where this
validation rule has been defined.
System configuration The name of the system configuration selected for
this job. For more information, see “Creating and
managing multiple datastore configurations” on
page 113 of the Data Integrator Designer Guide .
To add another business rule, on the Business rule tab click Add and follow
steps 3 through 8 in the previous procedure.
To display a different functional area so you can edit its business rules, select
it from the Functional area drop-down list.
To display a different business rule for editing, select it from the Business rule
drop-down list.
Delete a business rule by clicking Delete next to the business rule selected in
the drop-down list.
Enabling data quality statistics collection

To enable data quality statistics collection for your reports, you must verify two
options—one at the validation transform level and one at the job execution
level.

Viewing Data Quality dashboards
Validation transform level

In Designer, navigate to the validation transforms from which you want to
collect data quality statistics for your reports. For the columns that have been
enabled for validation, in the transform editor click the Validation transform
options tab and select the check box Collect data quality statistics.
Job execution level

When you execute a job, the Execution Properties window displays. On the
Parameters tab, clear the option Disable data quality statistics collection
(the default) before executing the job.
To run a job without collecting statistics, select the Disable data quality
statistics collection option to suppress statistics collection for all the
validation rules in that job.
Viewing Data Quality dashboards

To view Data Quality dashboards, on the metadata reports home page, click
Data Quality. The functional area view displays (see the next section,
Functional area view).
The upper-right corner identifies the repository for the reports you are
viewing. You can change the repository to view in the Settings control panel
(see “Repository tab” on page 56).
Some dashboards let you to drill in to some of the components for more
details. The navigation path at the top of the window indicates where you are
in the Data Quality dashboard reports hierarchy. Click the hyperlinks to
navigate to different levels.
Functional area view

The top-level Data Quality dashboard view is the functional area view. This
view includes two dashboards:
• Functional area pie chart—A current (snapshot) report.
• History line chart—A historical (trend) report that displays trends over the
last 7 days. To display this chart, click the link below the pie chart.
To change the functional area dashboards to view, select a different functional
area from the drop-down list at the top of the window. Select All to view data
for all batch jobs in that repository.

Functional area view 5
If there are no functional areas defined, the chart displays statistics for all jobs
for the selected repository.
Functional area pie chart

The pie chart displays status information for jobs that ran in the time period
displayed. The Data collection period begins at the time set on the Repository
tab in the Settings control panel (see “Repository tab” on page 56) and ends
with the time you open the report Web page.
The color codes on this chart apply to the volume of validation rules that
passed or failed:
• Green—The percentage of rules that passed for the selected functional
area.
• Red—The percentage of rules that failed for the selected functional area
with a High priority label.
Note: If you have All selected for Functional area, the failed portion
appears red and does not include priority information.
• Yellow—The percentage of rules that failed for the selected functional
area with a Medium priority label.
• Blue—The percentage of rules that failed for the selected functional area
with a Low priority label.

Business rule view
See “Creating business rules” on page 47 for how to set the priority labels.
Click on the failed pie “slices” to drill into the report:
• If there is at least one functional area and business rule defined, the
Business rule view displays. See “Business rule view” on page 52.
• If no functional areas or business rules are defined, the Validation rule
view displays. See “Validation rule view” on page 54.
History line chart

The History line chart displays the percentage of all validation rule failures
that occurred on each of the last 7 days. Data Integrator collects the number
of failures for the last run of all of the batch jobs that are associated with this
functional area on each day.
To display this chart, click the link below the pie chart.
Business rule view

The Business rule dashboard is a bar chart that depicts the percent of
validation failures for each defined business rule.
The Data collection period begins at the time set on the Repository tab in the
Settings control panel (see “Repository tab” on page 56) and ends with the
time you open the report Web page.

Business rule view 5
You can filter the view by selecting an option from the Priority drop-down list:
• All
• High priority
• Medium priority
• Low priority
The chart displays 10 bars per page; click the Next or Previous links to view
more.
To view the business rules associated with another functional area, select it
from the Functional area drop-down list.
To see the validation rules that apply to a particular business rule, click on that
bar in the chart. The Validation Rule View displays. See “Validation rule view”
on page 54.

Validation rule view
Validation rule view

The Validation Rule page includes two dashboards:
• Validation rule bar chart—A current (snapshot) report.
• History line chart—A historical (trend) report that displays trends over the
last 7 days. To display this chart, click the link below the Validation rules
bar chart.
The chart displays 10 bars per page; click the Next or Previous links to view
more.
To view the validation rules for a different business rule, select it from the
Business rule drop-down list.
Validation rule bar chart

The Validation rule bar chart displays the percentage of rows that failed for
each validation rule.
The Data collection period begins at the time set on the Repository tab in the
Settings control panel (see “Repository tab” on page 56) and ends with the
time you open the report Web page.
You can click on a bar to display the Sample data view. (See “Sample data
view” on page 55.)

Sample data view 5
History line chart
functional area.
To display this chart, click the link below the Validation rules bar chart.
Sample data view

If you have enabled the option to collect sample data in a validation transform
(see “Validation” on page 368 of the Data Integrator Reference Guide ), the
Sample data page includes two images:
• Sample data table
• History line chart
If you have not configured the validation transform to collect sample data,
only the History line chart displays.
To view sample data from another validation rule, select it from the drop-down
list.
Sample data table

If you have configured the validation transform to collect sample data (see
“Validation” on page 368 of the Data Integrator Reference Guide ), this page
displays up to 50 rows of sample data in tabular form.
The column that maps to the currently selected validation rule appears
highlighted.
History line chart

functional area.
To display this chart, click the link below the sample data table.

Data Quality dashboards Settings control panel
Data Quality dashboards Settings control

panel
The dashboard settings window allows you to change the options for your
reports.
In the upper-right corner of the metadata reports window, click Settings.
The three settings tabs are:
• Repository tab
• Functional area tab
• Business rule tab
For all of the Settings pages:
• Click Apply to save the changes and keep the Business rules dialog box
open, for example to add more business rules.
• Clicking OK saves your changes and closes the Settings control panel.
• Clicking Cancel closes the Settings control panel without saving
changes.
Repository tab
The settings on the Repository tab include:
• Repository—Select a repository to view from the drop-down list.
• View data starting at—Enter the time from where you want start viewing
data in the format HH:MM (from 00:00 to 23:59). On the Data Quality
dashboard charts, the end of the time window is the moment you open
one of the dashboard Web pages.
For example, entering 02:00 means your data quality reports will display
data from the repository starting at 2:00 a.m. through the time you open
the report page. Each dashboard page displays the time frame for which
the dashboard statistics apply.
Functional area tab

For details on how to use the Functional area tab settings, see “Creating
functional areas” on page 45.

Data Quality dashboards Settings control panel 5
Business rule tab
For details on how to use the business rule tab settings, see “Creating
business rules” on page 47.

Data Quality dashboards Settings control panel

Auto Documentation Reports
chapter
6 Auto Documentation Reports
Introduction
Introduction
Auto Documentation reports provide a convenient and comprehensive way to
create printed documentation for all of the objects you create in Data
Integrator. Auto Documentation reports capture critical information for
understanding your Data Integrator jobs so you can see at a glance the entire
ETL process.
After creating a Data Integrator project, you can use Auto Documentation
reports to quickly create a PDF or Microsoft Word file that captures a
selection of job, work flow, and/or data flow information including graphical
representations and key mapping details.
The types of information provided by Auto Documentation reports include:
• Object properties—Apply to work flows, data flows, and R/3 data flows
• Variables and parameters—Apply to jobs, work flows, data flows, and R/3
data flows
• Table usage—Shows all tables used in this object and its child objects.
For example for a the data flow, table usage information includes
datastores and the source and target tables for each.
• Thumbnails—An image that reflects the selected object with respect to all
other objects in the parent container. Applies to all objects except jobs.
• Mapping tree—Applies to data flows
The next section includes object descriptions that describe these components
in more detail as they apply to that object.
This chapter includes the following sections:
• Navigation
• Generating documentation for an object
• Auto Documentation Settings control panel
Navigation
Auto Documentation reports allow you to navigate to any project, job, work
flow, data flow, or R/3 data flow created in Designer and view information
about the object and its components.
To open Auto Documentation reports, from the Metadata Reports Home page,
click Auto Documentation.

Navigation 6
Auto Documentation navigation is similar to that of Impact and Lineage
reports (see Chapter 3: Impact and Lineage Analysis Reports). The Auto
Documentation page has two primary panes:
• The left pane shows a hierarchy (tree) of objects.
• The right pane shows object content and context.
Expand the tree to select an object to analyze. Select an object to display
pertinent information in the right pane. In the right pane, select tabs to display
desired information. Tabs vary depending on the object you are exploring.
Note that if the subcategory within a tab has an window icon on the far right
side of its header bar, you can collapse or expand that part of the display.
To search for a specific object

1. Type its name in the Objects to analyze search field. The search field is
not case sensitive, you may use the percent symbol (%) as a wildcard,
and spaces are allowed.

Navigation
2. Click the search icon (binoculars) or press Enter.

The top level of the navigation tree displays the current repository. You can
change this repository in the Settings control panel (see “Auto Documentation
Settings control panel” on page 65).
When you first open Auto Documentation, in the right pane the Project tab
displays with hyperlinks to the projects in the repository. You can click on
these links to drill into the project to display a list of jobs. You can also
continue to click the job name links to continue drilling into objects for more
information (thumbnails, object properties, etc.).
You can also navigate to this content by selecting objects in the navigation
tree. The hierarchy of the tree matches the hierarchy of objects created in
Designer:
• Repository
• Project
• Job
• Work flow
• Data flow
Repository
Clicking on a repository name in the navigation tree displays the Overview tab
in the right pane, which includes the following:
• Repository name—The name given to the repository in the Repository
Manager
• Repository type—The type of repository such as the database type
• Repository version—The Data Integrator repository version
Project
Clicking on a project name in the navigation tree displays the Project tab in
the right pane, which displays the list of jobs in the project. You can click on
these jobs to drill into the hierarchy.
Job
Clicking on a job name displays information on two tabs:
• Name of job—This tab includes:
• Description
• A graphical image of the next level of objects in the job (for example
one or more work flows or data flows)

Navigation 6
• Variables and parameters used in the job
• Table usage—This tab lists the datastores and associated tables
contained in the selected object if applicable.
Work flow
Clicking on a work flow name displays information on two tabs:
• Name of work flow—This tab includes:
• Thumbnail—This image reflects the selected object with respect to
all other objects in the parent container.
For example, if this work flow is the only one in the job, it appears
alone; but if there are two other work flows in the job, they will also
appear in the thumbnail image. You can click the other thumbnail
images to navigate to them, which replaces the content in the right
pane with that of the selected object.
• A graphical image of the object’s workspace window as it appears in
Designer.
You can click on objects to drill into them for more details. Objects
that have a workspace in Designer will display that workspace.
• Object properties—Displays properties such as Execute only once
or Recover as a unit if set.
• Variables and parameters used in the work flow
Data flow
Clicking on a data flow name displays information on three tabs:
• Name of data flow—This tab includes:
• Thumbnail—This image reflects the selected object with respect to
all other objects in the parent container.
• A graphical image of the object’s workspace window as it appears in
Designer.
You can click on an object in the data flow to drill into it for more
information:
A table displays the following information when selected:
• A thumbnail of the table with respect to the other objects in the
data flow

Generating documentation for an object
• Table properties including Optimizer hints (caching and join rank

settings) and Table basics (datastore and table name)
A transform displays the following information when selected:
• A thumbnail of the transform with respect to the other objects in
the data flow
• Mapping details including column names, mapping expressions,
descriptions, and data types.
To navigate back to the top level of the data flow object, click the data
flow name in the navigation tree, or click the Back button on your
browser.
• Object properties—Data flow properties such as Execute only once
and Degree of parallelism
• Variables and parameters used in the job
• Mapping tree—This tab displays a list of target tables. You can expand
or collapse each table display by clicking its header bar. Each target table
lists its target columns and the mapping expressions (sources) for each.
Generating documentation for an object

For most objects, you can quickly generate documentation in Adobe PDF or
Microsoft Word format by clicking the printer icon next to the object name in
the right pane.

Auto Documentation Settings control panel 6
To print Auto Documentation for an object

1. Select highest-level object you want to document in the left pane.
2. In the right pane, click the printer icon next to the object name.
3. In the Print dialog window, select or clear the check boxes for the items to
include in your printed report.
4. Select PDF or Microsoft Word format.
5. Click Print.
The Windows File download dialog box displays. Click Open to generate
and open the file now, or click Save to save the file to any location.
6. After saving or printing your report, click Close to close the Print window.
Auto Documentation Settings control panel

The Auto Documentation Settings control panel allows you to change the
options for your reports.
In the upper-right corner of the Metadata Reports window, click Settings.
The Auto Documentation settings tabs are:
• Repository—Select a repository from the drop-down list box and click
Apply.

Auto Documentation Settings control panel
• About—Provides Data Integrator version information.

Index
A Desktop Intelligence document 14
Administrator 15 Desktop Intelligence documents 15
Auto Documentation 60
F
B functional area
bar chart 35 creating 45
Business Element 25 definition 44
Business Field 25
business rule G
creating 47 Generating documentation 64
definition 44
priority 53
Business View 24 H
Business Views 14, 15 Home 18
BusinessObjects Enterprise 6.5 repository 29
I
C Impact and Lineage Analysis module 20
calculate column mappings 28 Impact and Lineage Analysis settings 27
Central Management Console 16
Central Management Server 14 J
Class 24 Java heap memory, increasing 22
CMS 16 JAVA_HOME 16
color codes, job execution duration 36 JDBC 15
color codes, job execution statistics 34, 51 Job execution duration 36
Column 24 Job Execution Statistic History 35
column level analysis 27 Job execution statistics 34
Crystal Reports 14, 15 Job Execution Statistics table 35
Crystal reports 25 Job execution time window 39
Job execution time window setting 36, 38, 38
D Job execution time window tolerance 38, 39
Dashboards home page 32 Job execution time window tolerance setting 39
data collection period 51, 52, 54
data quality statistics collection L
disabling 50 Logout 18
enabling 49
Datastore 23
Desktop Intelligence 25

Index
M ALVW_COLUMNINFO 14
Mapping tree 60 ALVW_FKREL 14
metadata ALVW_FLOW_STAT 14
reporting 12 ALVW_FUNCINFO 14
reporting tables and views 13 ALVW_MAPPING 14
Metadata Integrator 14, 15 ALVW_PARENT_CHILD 14
ALVW_TABLEATTR 14
ALVW_TABLEINFO 14
O Reports 25
Object 24 repositories, changing 27
Object properties 60 Repository 23
Objects to analyze 61 repository
Optimizer hints 64 tables 12
views 12
P repository information
pie chart 34 retrieving 13
priority, business rule 53 retrieving
repository information 13
R
R/3 data flow 60 S
reporting metadata 12 scaled images 21
reporting tables 12 Settings 18
AL_ATTR 13
AL_AUDIT 13 T
AL_AUDIT_INFO 13 Table 23
AL_CMS_BV 13 Table basics 64
AL_CMS_BV_FIELDS 13 table level analysis 26
AL_CMS_FOLDER 13 Table usage 60
AL_CMS_REPORTS 13 tables
AL_CMS_REPORTSUSAGE 13 reporting 12
AL_CMS_UNV 13 repository 12
AL_CMS_UNV_OBJ 13 Thumbnails 60
AL_HISTORY 13
AL_INDEX 13
AL_LANG 13 U
AL_LANGXMLTEXT 13 Universe 24
AL_PCOLUMN 13 Universes 14, 15
AL_PKEY 13
AL_SETOPTIONS 14 V
AL_USAGE 14 views, supporting metadata analysis 12
reporting tables and views
metadata 13
reporting views W
ALVW_COLUMNATTR 14 Web Administrator 18
Web Intelligence 14, 25

Index
Web Intelligence documents 15

Web Server service 15

Index

Dim Eta Data Reports

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Dim Eta Data Reports

Transféré par

Droits d'auteur :

Formats disponibles

Data Integrator Metadata Reports User’s

Data Integrator 11.5.1.5

for Windows and UNIX

Copyright Copyright © 2005 Business Objects. All rights reserved.

Date February 28, 2006

Chapter 2 Viewing Metadata Reports 11

Chapter 3 Impact and Lineage Analysis Reports 19

Chapter 4 Operational Dashboard Reports 31

Data Integrator Metadata Reports User’s Guide 3

Job execution statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 5 Data Quality Dashboard Reports 43

4 Data Integrator Metadata Reports User’s Guide

Chapter 6 Auto Documentation Reports 59

Data Integrator Metadata Reports User’s Guide 5

6 Data Integrator Metadata Reports User’s Guide

About this guide

Who should read this guide

Business Objects information resources

8 Data Integrator Metadata Reports User’s Guide

Data Integrator Metadata Reports User’s Guide 9

10 Data Integrator Metadata Reports User’s Guide

Viewing Metadata Reports

Repository reporting tables and views

12 Data Integrator Metadata Reports User’s Guide

Data Integrator Metadata Reports User’s Guide 13

14 Data Integrator Metadata Reports User’s Guide

Adding Metadata Integrator

Data Integrator Metadata Reports User’s Guide 15

16 Data Integrator Metadata Reports User’s Guide

Data Integrator Metadata Reports User’s Guide 17

Opening Metadata Reports

18 Data Integrator Metadata Reports User’s Guide

Impact and Lineage Analysis

20 Data Integrator Metadata Reports User’s Guide

Data Integrator Metadata Reports User’s Guide 21

To increase the java heap memory in Windows

22 Data Integrator Metadata Reports User’s Guide

Object Tab Associated content

Data Integrator Metadata Reports User’s Guide 23

Object Tab Associated content

24 Data Integrator Metadata Reports User’s Guide

Lineage Shows the lineage to the Universe objects or Business View

Data Integrator Metadata Reports User’s Guide 25

Table-level and column-level analysis

26 Data Integrator Metadata Reports User’s Guide

Note: If a report includes conditions predefined in a Universe, the columns

Impact and Lineage Analysis Settings control

Data Integrator Metadata Reports User’s Guide 27

Refresh Usage Data tab

28 Data Integrator Metadata Reports User’s Guide

Data Integrator Metadata Reports User’s Guide 29

30 Data Integrator Metadata Reports User’s Guide

Dashboards home page

32 Data Integrator Metadata Reports User’s Guide

Job statistics Job duration

Data Integrator Metadata Reports User’s Guide 33

Job execution statistics

Current (snapshot) pie chart

34 Data Integrator Metadata Reports User’s Guide

Each Job Execution Statistics table includes:

Historical (trend) bar chart

Data Integrator Metadata Reports User’s Guide 35

Job execution duration