Metadata Reports Guide

7/24/2019 Metadata Reports Guide

1/128

Data Services Management Console:

Metadata Reports Guide

BusinessObjects Data Services XI 3.0 (12.0.0)


2/128

2008 Business Objects. All rights reserved. Business Objectsowns the following

U.S. patents, which may cover products that are offered and licensed by Business

Copyright

Objects: 5,555,403; 5,857,205; 6,289,352; 6,247,008; 6,490,593; 6,578,027;

6,831,668; 6,768,986; 6,772,409; 6,882,998; 7,139,766; 7,299,419; 7,194,465;

7,222,130; 7,181,440 and 7,181,435. Business Objects and the Business Objects

logo, BusinessObjects, Business Objects Crystal Vision, Business Process OnDemand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions,

Crystal Enterprise, Crystal Insider, Crystal Reports, Desktop Intelligence, Inxight,

the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let

there be light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web

Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in

the United States and/or other countries of Business Objects and/or affiliated

companies. All other names mentioned herein may be trademarks of their respective

owners.

Business Objects products in this release may contain redistributions of software

licensed from third-party contributors. Some of these individual components may

Third-party

Contributorsalso 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

2008-03-12


3/128

ContentsIntroduction 7Chapter 1

Welcome to Data Services..........................................................................8

Welcome................................................................................................8

Documentation set for Data Services.....................................................8

Accessing documentation....................................................................11

Business Objects information resources..............................................12

Introduction to Metadata Reports..............................................................14

Getting Started 15Chapter 2

Requirements............................................................................................16

Adding Metadata Integrator.......................................................................16

Repository reporting tables and views.......................................................17

About the Management Console...............................................................20

Logging in.............................................................................................21

Management Console navigation.........................................................22

Impact and Lineage Analysis Reports 23Chapter 3

Navigation..................................................................................................24

To increase the java heap memory in Windows...................................26

To increase the java heap memory in UNIX.........................................26

Analysis options.........................................................................................27

Table-level and column-level analysis.......................................................33

Impact and Lineage Analysis Settings control panel.................................34Settings tab..........................................................................................34

Refresh Usage Data tab.......................................................................34

Business Objects Connections tab......................................................35

Data Services Management Console: Metadata Reports Guide 3


4/128

About tab..............................................................................................35

Operational Dashboard Reports 37Chapter 4

Dashboards home page............................................................................38

Job execution statistics..............................................................................39

Current (snapshot) pie chart.................................................................39

Historical (trend) bar chart....................................................................41

Job Execution Duration..............................................................................41

Configuring the Job Execution Duration dashboard.............................42

Current (snapshot) speedometer.........................................................43

Historical (trend) line chart...................................................................47

Data Validation Dashboard Reports 49Chapter 5

Configuring Data Validation dashboards...................................................50

Creating functional areas.....................................................................51

To create functional areas....................................................................51

Creating business rules........................................................................53

To create business rules.......................................................................53

Enabling data validation statistics collection........................................56Viewing Data Validation dashboards.........................................................56

Functional area view..................................................................................57

Functional area pie chart......................................................................57

History line chart...................................................................................59

Business rule view.....................................................................................59

Validation rule view....................................................................................61

Validation rule bar chart........................................................................61


Sample data view......................................................................................62

Sample data table................................................................................63


4 Data Services Management Console: Metadata Reports Guide

Contents


5/128

Data Validation dashboards Settings control panel...................................63

Repository tab......................................................................................64

Functional area tab...............................................................................64

Business rule tab..................................................................................64

Auto Documentation Reports 65Chapter 6

Navigation..................................................................................................66

To search for a specific object..............................................................67

Repository............................................................................................68

Project..................................................................................................68

Job........................................................................................................68Work flow..............................................................................................69

Data flow..............................................................................................69

To search for a specific object...................................................................71

To search for a specific object..............................................................71

Repository............................................................................................72

Project..................................................................................................72

Job........................................................................................................72

Work flow..............................................................................................73

Data flow..............................................................................................73

Generating documentation for an object...................................................75

To print Auto Documentation for an object................................................75

Auto Documentation Settings control panel..............................................76

Data Quality Reports 77Chapter 7

Lists of available reports............................................................................80

List of reports by job..................................................................................81

Data Quality Reports Settings control panel..............................................83

Report options...........................................................................................83

Descriptions of Reports.............................................................................84


Contents


6/128

USA CASS report: USPS Form 3553...................................................84

Canadian SERP report: Statement of Address Accuracy....................86

Australian AMAS report: Address Matching Processing Summary......88

Address Information Codes Sample report..........................................90

Address Information Code Summary report.........................................92

Address Validation Summary report.....................................................96

Address Type Summary report.............................................................98

Address Standardization Sample report............................................100

Address Quality Code Summary report.............................................102

Best Record Summary report.............................................................105

Match Contribution report...................................................................107Match Criteria Summary report..........................................................111

Match Source Statistics Summary report...........................................113

Match Duplicate Sample report..........................................................116

US Addressing Report........................................................................118

US Regulatory Locking Report...........................................................121

Index 125


Contents


7/128

Introduction

1


8/128

Welcome to Data Services

Welcome

Data Services XI Release 3 provides data integration and data quality

processes in one runtime environment, delivering enterprise performance

and scalability.

The data integration processes of Data Services allow organizations to easily

explore, extract, transform, and deliver any type of data anywhere across

the enterprise.

The data quality processes of Data Services allow organizations to easilystandardize,cleanse, andconsolidatedata anywhere, ensuring that end-users

are always working with information that's readily available, accurate, and

trusted.

Documentation set for Data Services

You should become familiar with all the pieces of documentation that relate

to your Data Services product.

What this document providesDocument

Information about available Data Services books,

languages, and locationsDocumentation Map

Highlights of key features in this Data Services re-

leaseRelease Summary

Important information you need before installing and

deploying this version of Data ServicesRelease Notes

An introduction to Data ServicesGetting Started Guide

Information about and procedures for installing Data

ServicesInstallation Guide


Introduction

1 Welcome to Data Services


9/128


Guidelines and options for migrating applications in-

cluding information on multi-user functionality and

the use of the central repository for version control

Advanced Development Guide

Information about how to use Data ServicesDesignerDesigner Guide

Information for third-party developers to access Data

Services functionalityIntegrator's Guide

Information about how to use Data Services Adminis-

trator

Management Console: Administrator

Guide

Informationabout how to use Data Services Metadata

Reports

Management Console: Metadata Re-

ports Guide

Release-specific product behavior changes from

earlier versions of Data Services to the latest releaseMigration Considerations

Information about how to migrate from Data Quality

to Data ServicesMigration Guide

Information about how to improve the performance

of Data ServicesPerformance Optimization Guide

Detailed reference material for Data Services Design-er

Reference Guide


1Introduction



10/128


A compiled master PDF of core Data Services books

containing a searchable master table of contents and

index: Installation Guide

Getting Started Guide

Designer Guide

Reference Guide

Management Console: Metadata Reports Guide

Management Console: Administrator Guide

Performance Optimization Guide

Advanced Development Guide

Supplement for J.D. Edwards

Supplement for Oracle Applications

Supplement for PeopleSoft

Supplement for Siebel

Supplement for SAP

Technical Manuals

A step-by-step introduction to using Data ServicesTutorial

In addition, you may need to refer to several Adapter Guides and

Supplemental Guides.


Information about how to install, configure, and use the Data

Services Adapter for JMSJMS Adapter Interface

Information about how to install, configure, and use the Data

Services Salesforce.com Adapter Interface

Salesforce.com Adapter

Interface

Information about license-controlled interfaces between Data

Services and J.D. Edwards World and J.D. Edwards OneWorld

Supplement for J.D. Ed-

wards

Information about the license-controlled interface between Data

Services and Oracle Applications

Supplement for Oracle Ap-

plications


Introduction



11/128



Services and PeopleSoftSupplement for PeopleSoft


Services, SAP ERP and R/3, and SAP BI/BWSupplement for SAP

Information about the license-controlled interface between Data

Services and SiebelSupplement for Siebel

Accessing documentation

You can access the complete documentation set for Data Services in several

places.

Note: For the latest tips and tricks on Data Services, access our Knowledge

Base on the Customer Support site at http://technicalsupport.businessob

jects.com. We have posted valuable tips for getting the most out of your Data

Services product.

Accessing documentation on Windows

After you install Data Services, you can access the documentation from the

Start menu.

1. ChooseStart >Programs >BusinessObjects XI 3.0 >BusinessObjects Data Services >Data Services Documentation.

Note: Only a subset of the documentation is available from the Start

menu. The documentation set for this release is available inLINK_DIR\Doc\Books\en.

2. Click the appropriate shortcut for the document that you want to view.


1Introduction

http://localhost/var/www/apps/conversion/tmp/scratch_7/http://localhost/var/www/apps/conversion/tmp/scratch_7/http://localhost/var/www/apps/conversion/tmp/scratch_7/http://localhost/var/www/apps/conversion/tmp/scratch_7/


12/128

Accessing documentation on UNIX

After you install Data Services, you can access the online documentation bygoing to the directory where the printable PDF files were installed.

1. Go toLINK_DIR/doc/book/en/.

2. Using Adobe Reader, open the PDF file of the document that you want

to view.

Accessing documentation from the Web

You can access the complete documentation set for Data Services from the

Business Objects Customer Support site.1. Go towww.businessobjects.com

2. From the "Support" pull-down menu, chooseDocumentation.

3. On the "Documentation" screen, chooseProduct Guidesand navigate

to the document that you want to view.

You can view the PDFs online or save them to your computer.

Business Objects information resources

Customer support, consulting, and training

A global network of Business technology experts provides customer support,

education, and consulting to ensure maximum business intelligence benefit

to your business.

Useful addresses at a glance

ContentAddress

Information about the full range ofBusiness Objects products.

Product information

http://www.businessobjects.com


Introduction

http://localhost/var/www/apps/conversion/tmp/scratch_7/http://www.businessobjects.com/http://www.businessobjects.com/http://localhost/var/www/apps/conversion/tmp/scratch_7/


13/128

ContentAddress

Business Objects product documenta-

tion, including the Business Objects

Documentation Roadmap.

Product documentation

http://www.businessobjects.com/support

Send us feedback or questions about

your Business Objects documentation.

Documentation mailbox

documentation@businessob-

jects.com

Information on Customer Support pro-

grams, as well as links to technical arti-

cles, downloads, and online forums.

Online Customer Support

http://www.businessobjects.com/sup

port

An online resource for sharing and

learning about Data Services with your

developer colleagues.

Online Developer Community

http://diamond.businessobjects.com/

Information about how Business Ob-

jects can help maximize your business

intelligence investment.

Consulting services

http://www.businessobjects.com/ser

vices/consulting/

Information on Business Objects train-

ing options and modules.

Education services

http://www.businessobjects.com/services/training

Online Customer Support

The Business Objects Customer Support web site contains information about

Customer Support programs and services. It also has links to a wide range

of technical information including Knowledge Base articles, downloads, and

support forums.http://www.businessobjects.com/support

Looking for training options?

From traditional classroom learning to targeted e-learning seminars, Business

Objects can offer a training package to suit your learning needs and preferred

learning style. Find more information on the Business Objects Education

web site:http://www.businessobjects.com/services/training


1Introduction

http://www.businessobjects.com/supporthttp://www.businessobjects.com/supporthttp://www.businessobjects.com/supporthttp://www.businessobjects.com/supporthttp://diamond.businessobjects.com/http://www.businessobjects.com/services/consulting/http://www.businessobjects.com/services/consulting/http://www.businessobjects.com/services/traininghttp://www.businessobjects.com/services/traininghttp://www.businessobjects.com/supporthttp://www.businessobjects.com/services/traininghttp://www.businessobjects.com/services/traininghttp://www.businessobjects.com/supporthttp://www.businessobjects.com/services/traininghttp://www.businessobjects.com/services/traininghttp://www.businessobjects.com/services/consulting/http://www.businessobjects.com/services/consulting/http://diamond.businessobjects.com/http://www.businessobjects.com/supporthttp://www.businessobjects.com/supporthttp://www.businessobjects.com/supporthttp://www.businessobjects.com/support


14/128

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is

there something that you particularly like or have found useful? Drop us a

line, and we will do our best to ensure that your suggestion is considered forthe next release of our documentation: [email protected].

Note: If your issue concerns a Business Objects product and not the

documentation, please contact our Customer Support experts.

Introduction to Metadata Reports

This guide describes how to use the Data Services Web-based metadata

reporting tools. You can easily browse, analyze, and produce reports on the

metadata in your repositories.

Metadata Reports provides five applications for exploring your metadata.

Impact and Lineage Analysis ReportsAllows you to easily browse,

analyze, and produce reports on the metadata for your Data Services

jobs as well as for other Business Objects applications associated with

Data Services

Operational Dashboard ReportsProvides several standard graphical

dashboards that allow you to evaluate your job execution performance

at a glance

Data Validation Dashboard ReportsProvide feedback that allowsbusiness users to quickly review, assess, and identify potential

inconsistencies or errors in source data.

Auto Documentation ReportsOffers a convenient way to create printed

documentation for the objects you create in Data Services by capturing

critical information so you can see an overview of the entire ETL process.

Data Quality ReportsAllows you to view and export Crystal reports for

batch and real-time jobs that include statistics-generating transforms.

Report types include job summaries, transform-specific reports, and

transform group reports.


Introduction

1 Introduction to Metadata Reports


15/128

Getting Started

2


16/128

This section describes the overall requirements for enabling and viewing

metadata reports including software and configuration requirements,

configuring the Metadata Integrator, and logging in to the Management

Console.

Requirements

Use the Data Services Administrator to configure repositories for metadata

reporting applications to access.

To make metadata reports available for Data Services objects, the metadata

reporting applications require:

The Web Server service (which uses the Tomcat servlet engine)

JDBC drivers to connect to a repository

Configured Data Services repositories

Installation and configuration of Metadata Integrator for impact and lineage

analysis on BusinessObjects Enterprise objects such as Universes and

Crystal Reports

Related Topics

Management ConsoleAdministrator Guide: Administrator Management,

Connecting repositories to the Administrator Adding Metadata Integratoron page 16

Adding Metadata Integrator

To view impact and lineage analysis and auto documentation reports for the

following objects, you must install, configure, and run the Metadata Integrator:

Business Views

Crystal Reports

Universes Desktop Intelligence documents

Web Intelligence documents

Metadata Integrator scans definitions on your Business Objects Central

Management Server (CMS) to find the tables and columns used by the

reports, views, and documents. Metadata Integrator stores the collected


Getting Started

2 Requirements


17/128

metadata in your Data Services repository for use by the impact and lineage

analysis and auto documentaiton applications.

Related Topics

Impact and Lineage Analysis Reportson page 23

Repository reporting tables and views

The Data Services repository is a database that stores your application

components and the built-in Data Services design components and their

properties. Theopen architectureof the repository allows formetadata sharing

with other enterprise tools.

Within your repository, Data Services 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 Services

applications.

Data Services metadata reporting tables and views are listed in the following

table:


2Getting Started



18/128

ContainsName

Attribute information about native objectsAL_ATTR

Audit information about each data flow executionAL_AUDIT

Information about audit statisticsAL_AUDIT_INFO

Components of a Business ViewAL_CMS_BV

Business Fields within Business Elements in a Business

ViewAL_CMS_BV_FIELDS

Information that uniquely identifies Crystal Reports,

Desktop Intelligence document, or Web Intelligence

documents

AL_CMS_REPORTS

Tables, columns, Business Views, or Universes that a

Crystal Report, Desktop Intelligence Document, or Web

Intelligence Document uses

AL_CMS_REPORT

SUSAGE

Folder names in which a Crystal Report, Desktop Intel-

ligence Document, or Web Intelligence Document re-

sides

AL_CMS_FOLDER

Information that uniquely identifies UniversesAL_CMS_UNV

Universe classes and the child objects, with the source

column and tableAL_CMS_UNV_OBJ

Execution statistics about jobs and data flowsAL_HISTORY

Index information about imported tablesAL_INDEX

Information about native (.atl) Data Services objectsAL_LANG

Information about objects represented in XML formatAL_LANGXMLTEXT

Column information about imported table partitionsAL_PCOLUMN

Primary key information about imported tablesAL_PKEY

Validation rule namesAL_QD_VRULE


Getting Started

2 Repository reporting tables and views


19/128

ContainsName

Rule name if it cannot fit it into AL_QD_VRULE (if there

is an overflow)AL_QD_VRULE_OFLOW

Runtime validation rule statisticsAL_QD_STATS

Sample row data for which the validation rules have

failedAL_QD_ROW_DATA

All the column information for the failed validation rulesAL_QD_COLINFO

All ancestor-descendant relationships between Data

Services objectsAL_USAGE

Attribute information about imported columnsALVW_COLUMNATTR

Information about imported columnALVW_COLUMNIN

FO

Primary-foreign key relationships among imported tablesALVW_FKREL

Execution statistics about individual transforms within

data flowsALVW_FLOW_STAT

Information about both native functions and functionsimported from external systems

ALVW_FUNCINFO

Mapping and lineage information for target tablesALVW_MAPPING

Direct parent-child relationships between Data Services

objects

ALVW_PAR

ENT_CHILD

Option settings for all objectsAL_SETOPTIONS

Attribute information about imported (external) tablesALVW_TABLEATTR

Information about imported tablesALVW_TABLEINFO

Note:This is not the complete list because some repository tables and views

are for internal use.


2Getting Started



20/128

Data Services automatically creates reporting tables for each new or

upgraded repository. Except for AL_USAGE, Data Services automatically

updates all reporting tables.

The Metadata Integrator collects metadata for Crystal Reports, BusinessViews, Universes, Desktop Intelligence document, and Web Intelligence

documents from the Central Management Server (CMS) and stores the

metadata in the Data Services reporting tables that start with AL_CMS.

Related Topics

Adding Metadata Integratoron page 16

About the Management Console

The Management Console is a collection of Web-based applications for

administering Data Services jobs and services, viewing object relationships,

evaluating job execution performance and data validity, and generating data

quality reports.

AdministratorUse to manage your production environment including

batch job execution, real-time services, Web services, adapter instances,

server groups, central and profiler repositories, and more. This applicaiton

is documented in the Data Services Management ConsoleAdministrator

Guide.

The remaining Management Console applications are documented in theData Services Management ConsoleMetadata Reports Guide.

Impact and Lineage AnalysisUse to analyze the end-to-end impact

and lineage for Data Services tables and columns and BusinessObjects

Enterprise objects such as universes, business views, and reports.

Operational DashboardsUse to view dashboards of Data Services

job execution statistics to see at a glance the status and performance of

your job executions for one or more repositories over a given time period.

Data Validation DashboardsUse to evaluate the reliability of your

target data based on the validation rules you created in your Data Servicesbatch jobs to quickly review, assess, and identify potential inconsistencies

or errors in source data.

Auto DocumentationUse to view, analyze, and print graphical

representations of all objects as depicted in Data Services Designer

including their relationships, properties, and more.


Getting Started

2 About the Management Console


21/128

Data Quality ReportsUse to view and export reports for batch and

real-time jobs such as job summaries and data quality transform-specific

reports.

Logging in

To access the metadata reporting applications, first log in to the Data Services

Management Console. The first time you log in to the Management Console,

use the default user name and password (admin/admin). Business Objects

recommends that you change the defaults thereafter by updating user roles

in the Data Services Administrator.

1. The first step depends on your operating system.

On Windows, click theStartmenu and selectPrograms>Business

Objects>BusinessObjects Data Services>Data Services

Management Console.

If you encounter an error, check to see whether the Data Services

Web Server service is installed and running. If the Web Server service

is running but you cannot log in, see the Troubleshooting section of

theData Services Administrator Guide.

On UNIX or Windows, open a browser, enter the following

case-sensitive URL, then press Enter:

http://hostname:28080/DataServices/

2. Enter the default user name (admin) and password (admin) and click Log

in.

The Management Console home page opens.

3. To launch one of the metadata reporting applications, click its icon (or

name).

If you are logged in to the Designer, you can also access the Management

Console home page as follows:

From the Start page, clickData Services Management Console.

From theToolsmenu, clickData Services Management Console.

Click theData Services Management Consoletool bar icon.


2Getting Started

About the Management Console


22/128

Management Console navigation

After you log in to the Management Console and launch one of theapplications, the application name appears under the Management Console

banner.

The upper-right side of the main window includes the following links:

HomeClick to return to the Management Console home page (for

example to select another application).

SettingsUse the Settings control panel for changing a variety of options

depending on the application.

LogoutClick to exit the application and the Management Console andreturn to the login page.

Help iconClick to open theData Services Management Console:

Administrator Guide or the Data Services Management Console: Metadata

Reports Guide, depending on which application you have open.

As you navigate around the applications, notice the top of the right-hand

pane often displays a "bread crumb" path to indicate where you are in the

application. Depending on the page displayed, sometimes you can click on

the bread crumbs to navigate to a different part of the application.

The Administrator, Impact and Lineage Analysis, and Auto Documentationapplications also use a navigation tree in the left-hand pane.

Data Services Management Console sessions time out after 120 minutes (2

hours) of inactivity.


Getting Started

2 About the Management Console


23/128

Impact and LineageAnalysis Reports

3


24/128

The Impact and Lineage Analysis application 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 beaffected 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 Services datastores, impact and lineage

analysis allows you to view the connections to other objects including

Universes, classes and objects, Business Views, Business Elements andFields, and reports (Crystal Reports, Desktop Intelligence documents, and

Web Intelligence documents).

Navigation

From the Management Console home page, view impact and lineage

information by clicking theImpact and Lineage Analysislink.

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.

The top level of the navigation tree displays the current repository. (You canchange this repository in the Settings control panel; for details, see Settings

tabon page 34.)

Objects in a repository include:

DatastoresContain Data Services tables and columns


Impact and Lineage Analysis Reports

3 Navigation


25/128

CMS server(s)After you configure the Metadata Integrator (seeAdding

Metadata Integratoron page 16), 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 analyzesearch

feature. You can do one or both of the following:

1. Select a category in theSelect an object typedrop-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 in thesearch 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 with a red border each object that meets your

search criteria.

To repopulate the CMS navigation tree with any objects that might have

been changed (added, deleted, renamed, and so on) in the CMS repository

after you display an impact and lineage report, log out and log back in to

the Management Console to display the changes.

If you receive an error such as the following:

This image is scaled to 50% of the original image. You couldavoid scaling the image by allocating more memory to the

current java process.


3Impact and Lineage Analysis Reports

Navigation


26/128

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 Services Web server.

To increase the java heap memory in Windows

1. In the Windows Services control panel, stop the Data Services Web

Server.

2. In the Data Services installationdirectory, 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\common\endorsed

...

5. Save and close the file.

To increase the java heap memory in UNIX1. Stop the Data Services Web Server.

2. In the Data Services 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.



3 Navigation


27/128

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:

TableData flow (if applicable), datastore, and owner

Business Objects reportDepending on the report type, the pop-up

window displays the CMS server name, the Business View name, or theUniverse name, for example.

Universe objectsCMS server, universe, and class

The following table lists the objects in the navigation tree, the corresponding

tabs, and the content of each.

Associated contentTabObject

Repository name

Repository typeThe database type

Repository versionThe repository version

number

OverviewRepository



Analysis options


28/128


Overview information varies depending on thedatastore type. The following entries apply to a

datastore on Microsoft SQL Server.

Application typeDatabase

Database typeMicrosoft_SQL_Server

UserDatabase user name

Case sensitiveWhether or not the database is

case sensitive

ConfigurationThe configuration selected in the

datastore editor

SQL_Server versionMicrosoft SQL Server

2000

Database nameDatabase name

Server nameThe host computer name

OverviewDatastore

Table nameTable name

DatastoreDatastore to which this table belongs

Owner nameThe table owner name in the

database.

Business nameBusiness-use name of the table

if defined

Table typeTable or template table

Last update dateWhen Data Services last up-dated the table

OverviewTable



3 Analysis options


29/128


Graphically shows the end-to-end impact of theselected 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.

Impact

Contains the same information as on the Impact

tab except it describes the flow from target to

source.

Lineage

Displays the overall mapping information for each

column in the table. Select betweenGroup by

data floworGroup by column.

Mapping

tree

Column nameColumn name

Table nameParent table of the column

Data typeThe data type for the column

Nullableyes/no

Primary keyyes/no

Foreign keyyes/no

OverviewColumn

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

Impact



Analysis options


30/128


Contains the same information as on the Impacttab except it describes the flow from target to

source.

It also displays any data flow objects associated

with the column. Move the cursor over a data flow

icon to display a pop-up window with the mapping

information.

Click on a data flow icon to open another pop-up

window that displays the Auto Documentation in-

formation including mapping. Notice that in theauto documentation window, any objects that are

not part of the lineage for this column are dimmed.

Lineage

Universename

FolderThe folder name on the CMS server to

where the Universe has been exported

CMS serverThe name of the CMS server for

this Universe

DescriptionThe description created for the

Universe in BusinessObjects Designer

OverviewUniverse

Business Viewname

FolderThe folder name on the CMS server to

where the Business View has been exported

Last update dateWhen the Business View was

last updated in the Business View Manager


this Business View

OverviewBusiness

View



3 Analysis options


31/128


Classname

UniverseUniverse to which this class belongs


this class

OverviewClass

Objectname

ClassThe class to which this object belongs

UniverseUniverse to which this object belongs

CMS ServerThe name of the CMS server for

this object

Source columnThe name of the source column

for this object followed by the owner.table name

OverviewObject

Shows all the reports that use the selected objectImpact

Showscolumn-level lineage for theselected objectLineage

Business elementname

Business viewThe Business View to which this

business element belongs


this object

OverviewBusiness

Element



Analysis options


32/128


Business fieldname

Business elementThe Business Element to

which this Business Field belongs

Business viewThe Business View to which this

Business Field belongs


this object

OverviewBusinessField

Shows all the reports that use the field.Impact

Shows column-level lineage for the selected

Business Field.

Lineage

Reportname

FolderThe folder on the CMS server where the

report is stored


this report

Last update dateWhen the report was last

updated

OverviewReports:

Crystal

and Web

Intelli-gence/

Desktop In-

telligence

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

Services datastore.

Lineage

Related Topics

Table-level and column-level analysison page 33

Auto Documentation Reportson page 65



3 Analysis options


33/128

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 at the column level shows datastores, objects,

fields, and reports/documents as shown in the following graphic.



Table-level and column-level analysis


34/128

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

used by those conditions do 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 Settingscontrol panel

The Impact and Lineage Analysis Settings control panel allows you to change

the options for your reports. To open it, clickSettingsin the upper-right

corner of the application window.

Settings tab

The Settings tab allows you to change repositories. Select a repository from

the drop-down list box and click Apply.

Refresh Usage Data tab

You can calculate column mappings from the Impact and Lineage Analysis

application (or from the Designer) at any time.

TheCalculate Column Mappingsoption 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.

Data Services calculates column mappings automatically when you save

data flows in the Designer. (To change the default, clear the check box underTools>Options>Designer>General>Calculate column mapping

while saving data flow.)

Note: If you do not selectCalculate column mappings when saving data

flow, you must selectCalculate Column Mappingsmanually before

generating reports to ensure that Data Services returns accurate mapping

information. For example, assume you do not have Calculate column

mappings when saving data flow selected. You click the Calculate Column



3 Impact and Lineage Analysis Settings control panel


35/128

Mappingsbutton 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 Services prompts you to save the

changes to the data flow. You comply. The next time you try to view mapping

information for the data flow, the information is gone because the saved dataflow is a new object in the repository. It does not have column mapping

information until you manually calculate it.

Business Objects Connections tab

Use the Business Objects Connections tab to create a connection to a

BusinessObjects Enterprise 6.5 repository.

About tab

This tab provides Data Services version information.



Impact and Lineage Analysis Settings control panel


36/128



3 Impact and Lineage Analysis Settings control panel


37/128

Operational DashboardReports

4


38/128

Operational dashboard reports provide graphical depictions of Data Services

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 streamlineand 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 theData Services Performance Optimization Guide.

Dashboards home page

To view operational dashboards, on the Management Console home page,

clickOperational Dashboards.

The upper-right corner identifies the repository for the reports you are viewing.

You can change the repository to view in the dashboards Settingscontrol

panel.

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

theOperationaltab 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 anda 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 statisticsLeft side of dashboards home page. These

reports depict job execution statisticsin general, how many jobs

succeeded or had errors.

Current (snapshot) pie chart

Historical (trend) bar chart

Job execution durationRight side of page. These reports depict howlong it took the jobs to run and whether those run times were within

acceptable limits.

Each report type includes a current (snapshot) speedometer and a

historical (trend) line chart.


Operational Dashboard Reports

4 Dashboards home page


39/128

The following sections describe the contents of these reports and their

subreports.

Job execution statisticsJob execution statistics display in two formats on the left side of the page:



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)


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

dashboardSettings control panel (see Configuring the Job Execution Duration

dashboardon page 42).

The chart identifies the number and ratio of jobs that succeeded, had oneor more warnings, had one or more errors, or are still currently running.


4Operational Dashboard Reports

Job execution statistics


40/128

Click on the pie "slices" to drill into the report, which displays a table that

shows the jobs in that status group. From there you can click on the status

tabs to view the list of jobs in each group.

Each Job Execution Statistics table includes:

Repository nameThe repository associated to this job

Job nameThe name of the job in the Designer

Start time and End timeThe start and end timestamps in the format

hh:mm:ss.

Execution timeThe elapsed time to execute the job

System configurationThe name of the system configuration that applies

to that job.



4 Job execution statistics


41/128


The Job Execution Statistics History bar chart depicts how many jobssucceeded, had warnings, failed, or are still currently running on each of the

last 7 days.

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, and so on) for a particular day. SeeCurrent

(snapshot) pie charton page 39 for details on the Job Execution Statistics

tables.

Job Execution Duration

Job Execution Duration reports display in two dashboards on the right side

of the dashboards home page:


Historical (trend) line chart

These two charts describe whether all jobs in the selected repositories

executed within the acceptable time frame that you established using the

dashboard Settings control panel. This window is the amount of time that





42/128

you allot to run your jobs so your target data warehouse is available to

applications and users during business hours, for example.

Configuring the Job Execution Duration dashboard

The recommended process for setting up the Job Execution Duration

dashboards is as follows.

1. In the Administrator, schedule your jobs for when you want them to run.

Example: Schedule all jobs to start executing at 1:00 AM.

2. In the Operational Dashboards application, clickSettingsto open the

control panel.

3. Select the repository to configure.4. For the View data starting at value, enter the beginning of the time frame

in which you want to view job execution as a whole on the speedometer

dashboard (in the format HH:MM, from 00:00 to 23:59).

For example, if all of your jobs begin to execute at 1:00 AM, it would be

logical to set the View data starting atvalue to 1:00.

5. Enter a value forJob execution time windowin number of hours (from

0 to 24) that you have available to run your ETL jobs.

For example, if you want all of your jobs to finish executing by 5 AM, enter

4 hours, which would be the time window between 1 AM and 5 AM.

6. Optionally, add a value for theJob execution time window tolerance

in increments of 1 hour.

Note: The total of theJob execution time windowvalue and the Job

execution time window tolerancevalue cannot exceed 24.

For example, suppose you determine that in some circumstances it is ok

if some jobs finish executing by 6 AM. In this case, set the Job execution

time window toleranceto 1 (extending the window from 5 AM to 6 AM).



4 Job Execution Duration


43/128

Current (snapshot) speedometer

The speedometer graphic displays the current window of time allotted foryour jobs to complete their executions and whether or not the jobs as a whole

finished within the selected job execution time window.

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 or not the job succeeded

and if and where it finished executing within the job execution time window.

Continuing with the example described in the preceding process, the following

morning, after running your jobs overnight, you want to verify they executed

within the time window of 1 AM to 5 AM. Open the Operational Dashboards

application and view the Job Execution Duration speedometer dashboard.

The speedometer needle points in the green zone, which represents the Job

execution time window setting in the Settings control panel. In the example,

that setting was 4 hours (from 1:00 AM to 5:00 AM). Therefore, all jobs in

the repository finished executing within the desired time frame.





44/128

The solid red bar indicates when the first job actually started, which in the

case of the example was 1:00 AM.

The time below the needle hub indicates when the last job finished executing

for the selected repository. If the start time of the first job execution and theView data starting atvalue are the same, as in the example, that value

equates to the total execution time for all the jobs (1:15 in the example).

If, however, you entered aView data starting atvalue other than when the

first job actually started, to calculate the overall job execution duration period,

subtract the time the first job started (indicated by the red bar and noted

below the dashboard) from the time below the needle hub.

The time period displayed above the speedometer graphic indicates the

viewing period. For example,

3/6/07 1:00 AM - 3/6/07 2:57 PM

indicates that you are viewing a dashboard that reflects all jobs that ran

between 1:00 AM and 2:57 PM. The time 1:00 AM is the same as the View

data starting at value. The time 2:57 PM is when you opened the Operational

Dashboards control panel, which acts as a time stamp for the end period of

the data you are actually viewing.

Therefore, the color zones on both Job Execution Duration dashboards (the

speedometer and the history line chart) represent:

Green (normal)All jobs executed within the job execution time window.Specify this window with theJob execution time windowsetting. The

green range of the speedometer represents this value.

Yellow (warning)At least one job finished executing during the tolerance

period. Tolerance is the amount of time that jobs can run beyond your

normalJob execution time window. Specify this tolerance limit with the

Job execution time window tolerance setting. This value is represented

in the yellow range of the speedometer and in line charts, and it defines

the red line limit on Gantt charts.

Red (exceeded)At least one job finished executing beyond the normal

or warning (tolerance) limits.





45/128

Viewing job execution duration details

Click on the speedometer dashboard to drill into the report and display aGantt chart of the Job Execution Duration for all jobs.

In the Job Execution Duration Gantt chart, each job shows its start time, end

time, and status (succeeded, warning, and so on). The orange line denotes

the high end of theJob execution time windowsetting, and the red line

indicates the high end of the Job execution time window tolerance setting.

You can move the cursor over the Gantt bars to view a pop-up window with

the Job Execution Duration (total elapsed time).

You can view Job Execution Duration (and Data Flow Execution Duration)

information in both graphical and tabular formats. Click the GraphorTable

tabs accordingly.

The Job Execution Duration table displays the repository name, the job name

(for successful jobs, you can click its name 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.

Viewing data flow execution duration details

From the Job Execution Duration detailsGraphwindow, you can drill into a

job for its data flow execution duration times and audit details if applicable.

Click on a job's Gantt bar to display the Data Flow Execution Duration Gantt

chart:





46/128

The Data Flow Execution Duration Gantt chart lists the data flows in the job

and the execution duration of each. It also shows theJob execution time

window(orange) andJob execution time window tolerance(red) 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

SuccessAll audit rules succeeded

CollectedThis status occurs when you define audit labels to collect

statistics but do not define audit rules

FailedAudit rule failed

You can view Data Flow Execution Duration (and Job Execution Duration)information in both graphical and tabular formats. Click the GraphorTable

tabs accordingly.

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.

Viewing audit details

If auditing has been enabled, on the Data Flow Execution Duration Gantt

chart (Graph), 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:





47/128

Audit rule information if applicable

Audit failed information if applicable

A table with the audit labels and values

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 colored dots indicate the overall results of job

execution duration based on the settings defined in the Settings control panel.

SeeConfiguring the Job Execution Duration dashboardon page 42.

Each point denotes the Job Execution Duration (total elapsed time) of all the

jobs for that day.

Click on the points to drill in to display the Job Execution Duration Gantt chart

as described in the section Current (snapshot) speedometeron page 43.

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.





48/128

SeeCurrent (snapshot) speedometeron page 43 for details on the Job

Execution Duration Gantt chart, the Data Flow Execution Duration Gantt

chart, and the Audit Details pages.

Click theView all historybutton to display two tables: Job Execution HistoryThis table lets you view execution history for

all jobs or individual jobs. You can also select over how many days you

want to view the history.

This table displays the same information as in the Job Execution Duration

table: repository name, job name, 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.

Data Flow Execution HistoryThis table includes three options for

customizing the display:

Data FlowEnter a data flow name for which to search and click

Search.

Job NameSelect all jobs or an individual job.

View history for x daysSelect over how many days you want to

view the history

This table displays almost the same information as in the Data Flow

Execution Duration table: repository name, data flow name, job name,

the start and end time of the data flow execution, the execution time(elapsed), and the number of rows extracted and loaded.





49/128

Data Validation DashboardReports

5


50/128

Data Validation 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 Services batch jobs. This feedback allows business

users to quickly review, assess, and identify potential inconsistencies orerrors in source data.

Configuring Data Validation dashboards

To generate meaningful Data Validation dashboards, follow this process:

1. In your Data Services 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.

2. In the Data Validation application, 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 Services jobs and one or more data validation

business rules.

3. In the Data Validation application, create business rules. Business rules

are typical categories of data, for example Social Security Number orAddress.

These business rules contain validation rules that you created in your

validation transforms in your data flows.

Begin by opening the Management Console and clicking the Data Validation

name or icon link on the Home page.

Related Topics

Creating functional areason page 51

Creating business ruleson page 53

Designer Guide: Data Assessment, Using the Validation transform


Data Validation Dashboard Reports

5 Configuring Data Validation dashboards


51/128

Creating functional areas

After you create data flows with validation transforms and rules in DataServices Designer, next create functional areas.

Note: If you do not create any functional areas, the dashboard displays

statistics for all jobs for the selected repository.

To create functional areas

1. In the Data Validation module, click theSettingslink.

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 theFunctional areatab.

The selected repository displays.

4. Type a name for the new functional area (such as Customer) and

optionally a description.5. ClickSave.

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.

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:

Jobs are not reusable among functional areas.


5Data Validation Dashboard Reports



52/128

In the Data Services Administrator, deleting job information on the

Batch Job Status page (Batch Jobs History) also clears data validation

statistics from Data Validation Metadata Reports.

7. ClickApplyto save the changes and keep the Functional area window

open, for example to add more functional areas.

ClickingOKsaves 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 Addand

follow steps 4 through 7 in the previous procedure.

To display a different functional area for editing, select it from the drop-downlist.

Delete a functional area by clicking Delete next to the functional area selected

in the drop-down list.





53/128

Next, create business rules to associate the validation rules in your data

flows with your functional areas as described in the next section.

Related Topics

Designer Guide: Datastores, Creating and managing multiple datastore

configurations

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

To create business rules

1. In the Settings control panel, click theBusiness ruletab.

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 asPhone 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 asPhone 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. ClickSave.

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





54/128

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

Note: Validation rules are not reusable among business rules (you canuse a validation rule only once and only in one business rule).

8. ClickApplyto save the changes and keep the Business rule window

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.





55/128

DescriptionColumn

The validation rule name in Data Services. The de-fault is the column name unless you create a new

name in the validation transform Properties dialog

box.

Validation rule name

The description for the validation rule in Data Ser-

vices.

Description

Describes the hierarchy in Data Services from the

job level to the data flow level to indicate where thisvalidation rule has been defined.

Full path

The name of the system configuration selected for

this job.

System configuration

To add another business rule, on the Business rule tab clickAddand 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 Deletenext to the business rule selected

in the drop-down list.

Related Topics

Designer Guide: Data Assessment, Using the Validation transform Designer Guide: Datastores, Creating and managing multiple datastore

configurations





56/128

Enabling data validation statistics collection

To enable data validation statistics collection for your reports, you must verifytwo optionsone at the validation transform level and one at the job execution

level.

Validation transform level

In Designer, navigate to the validation transforms from which you want to

collect data validation statistics for your reports. For the columns that have

been enabled for validation, in the transform editor click the Validation

transform optionstab and select the check boxCollect data validation

statistics.

Job execution level

When you execute a job, the Execution Properties window displays. On the

Parameters tab, clear the optionDisable data validation statistics

collection(the default) before executing the job.

To execute a job without collecting statistics, select the Disable data

validation statistics collection option, which suppresses statistics collectionfor all the validation rules in that job.

Viewing Data Validation dashboards

To view Data Validation dashboards, on the Management Console Home

page, clickData Validation. The functional area view displays.

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.

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 Validation dashboard reports hierarchy. Click the hyperlinks

to navigate to different levels.



5 Viewing Data Validation dashboards


57/128

Related Topics

Functional area viewon page 57

Repository tabon page 64

Functional area view

The top-level Data Validation dashboard view is the functional area view.

This view includes two dashboards:

Functional area pie charton page 57A current (snapshot) report.

History line charton page 59A 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. SelectAllto view data

for all batch jobs in that repository.

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 tabon page 64) and ends

with the time you open the report Web page.



Functional area view


58/128

The color codes on this chart apply to the volume of validation rules that

passed or failed:

GreenThe percentage of rules that passed for the selected functional

area.

RedThe percentage of rules that failed for the selected functional areawith a High priority label.

Note: If you have All selected for Functional area, the failed portion

appears red and does not include priority information.

OrangeThe percentage of rules that failed for the selected functional

area with a Medium priority label.

BlueThe percentage of rules that failed for the selected functional area

with a Low priority label.

SeeCreating business ruleson page 53 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. SeeBusiness rule viewon page 59.



5 Functional area view


59/128

If no functional areas or business rules are defined, the Validation rule

view displays. SeeValidation rule viewon page 61.

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 Services 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 the History line chart, click the link below the pie chart.

Business rule viewThe Business rule dashboard is a bar chart that shows the percentage of

validation failures for each defined business rule. You access this chart by

clicking on one of the failed slices of the functional area pie chart.

Note: If no functional areas or business rules have been defined, drilling

down on the functional area pie chart displays the Validation rule view.

Therefore, the business rules are the same as the validation rules.

The data collection period begins at the time set on the Repository tab in the

Settings control panel (seeRepository tabon page 64) and ends with thetime you open the report Web page.



Business rule view


60/128

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 orPrevious 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. SeeValidation rule

viewon page 61.



5 Business rule view


61/128

Validation rule view

When you view the Functional area pie chart (the Data Validation Home

page) and click on one of the failed pie slices to drill into the report, if no

functional areas or business rules have been defined, the Validation rule

view displays.

Note: If no Functional areas or Business Rules have been defined, drilling

down on the functional area pie chart displays the Validation rule view.

Therefore, the business rules are the same as the validation rules.

The Validation Rule page includes two dashboards:

Validation rule bar charton page 61A current (snapshot) report.

History line charton page 62A historical (trend) report that displaystrends 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 orPrevious 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 (seeRepository tabon page 64) and ends with

the time you open the report Web page.



Validation rule view


62/128

You can click on a bar to display the Sample data view. (SeeSample data

viewon page 62.)

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 Services collects the number

of failures for the last run of all of the batch jobs that are associated with this

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,

the Sample data page includes two images:

Sample data tableon page 63

History line charton page 63



5 Sample data view


63/128

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 , 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

The History line chart displays the percentage of

Date post:	23-Feb-2018
Category:	Documents
Upload:	pinina-jacinta-villa-rufatt
View:	240 times
Download:	1 times

Metadata Reports Guide

Documents