boadminguide

SAP BusinessObjects Information Steward Administrator Guide■ SAP BusinessObjects Information Steward 4.0 (14.0.0)

2011-04-06

© 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAPBusiness ByDesign, and other SAP products and services mentioned herein as well as their respective

Copyright

logos are trademarks or registered trademarks of SAP AG in Germany and other countries. BusinessObjects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, WebIntelligence, Xcelsius, and other Business Objects products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of Business Objects S.A. in theUnited States and in other countries. Business Objects is an SAP company.All other product andservice names mentioned are the trademarks of their respective companies. Data contained in thisdocument serves informational purposes only. National product specifications may vary.These materialsare subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of anykind, and SAP Group shall not be liable for errors or omissions with respect to the materials. Theonly warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

2011-04-06

Contents

Getting Started........................................................................................................................9Chapter 1

Product overview.....................................................................................................................91.1Accessing Information Steward for administrative tasks...........................................................91.2

Architecture...........................................................................................................................11Chapter 2

Architecture overview............................................................................................................112.1Servers and services..............................................................................................................122.1.1Information Steward on Business Intelligence platform components.......................................192.2Information workflows............................................................................................................222.3Adding a table to a Data Insight project..................................................................................222.3.1Profiling data .........................................................................................................................232.3.2Scheduling and running a Metadata Management integrator source.......................................232.3.3Creating a custom cleansing package with Cleansing Package Builder...................................242.3.4

Securing SAP BusinessObjects Information Steward...........................................................27Chapter 3

Security Overview..................................................................................................................273.1Enterprise security.................................................................................................................273.2Securing user data for Information Steward...........................................................................283.2.1Storage of sensitive information.............................................................................................283.2.2Configuring the Remote Job Server for SSL..........................................................................293.2.3Reverse proxy servers...........................................................................................................323.2.4

Users and Groups Management...........................................................................................33Chapter 4

Users and Groups overview...................................................................................................334.1Information Steward pre-defined users and groups................................................................334.2Managing users in Information Steward..................................................................................354.3Creating users for Information Steward .................................................................................364.3.1Adding users and user groups to Information Steward groups................................................374.3.2Denying access......................................................................................................................384.3.3User rights in Data Insight......................................................................................................384.4Data Insight pre-defined user groups......................................................................................394.4.1Type-specific rights for Data Insight objects ..........................................................................404.4.2

2011-04-063

Customizing rights on Data Insight objects.............................................................................484.4.3User rights in Metadata Management....................................................................................534.5Metadata Management pre-defined user groups....................................................................544.5.1Type-specific rights for Metadata Management objects..........................................................544.5.2Assigning users to specific Metadata Management objects...................................................594.5.3User rights in Cleansing Package Builder...............................................................................614.6Group rights for cleansing packages......................................................................................614.6.1User rights for Information Steward administrative tasks .......................................................624.7Viewing and editing repository information.............................................................................634.7.1

Data Insight Administration...................................................................................................65Chapter 5

Administration overview for Data Insight................................................................................655.1Data Insight Connections.......................................................................................................665.2Defining a Data Insight connection to a database...................................................................665.2.1Defining a Data Insight connection to an application...............................................................795.2.2Defining a Data Insight connection to a file.............................................................................845.2.3Displaying and editing Data Insight connection parameters....................................................855.2.4Deleting a Data Insight connection.........................................................................................865.2.5Data Insight projects..............................................................................................................875.3Creating a project..................................................................................................................875.3.1Editing a project description...................................................................................................885.3.2Deleting a project...................................................................................................................885.3.3Data Insight tasks..................................................................................................................895.4Scheduling a task...................................................................................................................895.4.1Recurrence options................................................................................................................905.4.2Configuring for task completion notification ...........................................................................915.4.3Rule threshold notification .....................................................................................................945.4.4Monitoring a task...................................................................................................................955.4.5Pausing and resuming a schedule...........................................................................................965.4.6Common runtime parameters for Information Steward...........................................................975.4.7Configuration settings............................................................................................................985.5Profiling task settings and rule task settings...........................................................................995.5.1Configuring profiling tasks and rule tasks.............................................................................1035.5.2

Metadata Management Administration...............................................................................105Chapter 6

Administration overview for Metadata Management ............................................................1056.1Configuring sources for Metadata Integrators......................................................................1056.1.1Managing integrator sources and instances ........................................................................1196.1.2Running a Metadata Integrator ............................................................................................1236.1.3Changing run-time parameters for integrator sources...........................................................1256.1.4

2011-04-064

Contents

Viewing integrator run progress and history ........................................................................1316.1.5Troubleshooting ..................................................................................................................1326.1.6Grouping Metadata Integrator sources ................................................................................1356.1.7

Cleansing Package Builder Administsration.......................................................................139Chapter 7

Changing ownership of a cleansing package........................................................................1397.1Deleting a cleansing package...............................................................................................1397.2Changing the description of a cleansing package.................................................................1407.3Unlocking a cleansing package.............................................................................................1407.4Cleansing package states and statuses...............................................................................1417.5

Information Steward Utilities...............................................................................................145Chapter 8

Utilities overview..................................................................................................................1458.1Computing and storing lineage information for reporting.......................................................1468.1.1Recreating search indexes on Metadata Management.........................................................1478.1.2Scheduling a utility...............................................................................................................1488.2Rescheduling a utility............................................................................................................1498.3Running a utility on demand..................................................................................................1508.4Monitoring utility executions.................................................................................................1518.5Modifying utility configurations.............................................................................................1528.6Creating a utility configuration..............................................................................................1538.7

Server Management............................................................................................................155Chapter 9

Server management overview..............................................................................................1559.1Verifying Information Steward servers are running...............................................................1559.2Verifying Information Steward services ...............................................................................1569.3Configuring Metadata Browsing Service and View Data Service .........................................1579.4Metadata Browsing Service configuration parameters..........................................................1589.4.1View Data Service configuration parameters........................................................................1599.4.2Job server group..................................................................................................................1619.5Configuring a Data Services Job Server for Data Insight......................................................1619.5.1Adding Data Services Job Servers for Data Insight..............................................................1629.5.2Displaying job servers for Information Steward....................................................................1629.5.3Removing a job server..........................................................................................................1639.5.4

Performance and Scalability Considerations......................................................................165Chapter 10

Resource intensive functions...............................................................................................16510.1Architecture.........................................................................................................................16610.2Factors that influence performance and sizing......................................................................16710.3Data Insight..........................................................................................................................16710.3.1

2011-04-065

Contents

Metadata Management........................................................................................................16910.3.2Cleansing Package Builder...................................................................................................16910.3.3Scalability and performance considerations..........................................................................17010.4Scalability levels in deployment............................................................................................17110.4.1Distributed processing.........................................................................................................17210.4.2Scheduling tasks .................................................................................................................17410.4.3Queuing tasks......................................................................................................................17510.4.4Degree of parallelism...........................................................................................................17510.4.5Grid computing....................................................................................................................17810.4.6Using SAP applications as a source.....................................................................................18010.4.7Multi-threaded file read........................................................................................................18210.4.8Data Insight result set optimization.......................................................................................18210.4.9Performance settings for input data......................................................................................18310.4.10Settings to control repository size........................................................................................18410.4.11Settings for Metadata Management.....................................................................................18510.4.12Settings for Cleansing Package Builder................................................................................18610.4.13Best practices for performance and scalability.....................................................................18710.5General best practices.........................................................................................................18710.5.1Data Insight best practices...................................................................................................18810.5.2Metadata Management best practices.................................................................................19010.5.3Cleansing Package Builder best practices............................................................................19110.5.4

Backing Up and Restoring Metadata Management.............................................................193Chapter 11

Backing up and restoring overview.......................................................................................19311.1Exporting objects to XML.....................................................................................................19311.2To export objects to XML.....................................................................................................19311.2.1Backing up and restoring configurations...............................................................................19611.3Backing up configurations....................................................................................................19611.3.1Restoring configurations......................................................................................................19711.3.2

Life Cycle Management......................................................................................................199Chapter 12

Migration basics...................................................................................................................19912.1Development process phases..............................................................................................19912.1.1Migration mechanisms and tools..........................................................................................20012.2Moving objects using the lifecycle management console .....................................................20112.2.1Exporting and importing objects using Information Steward..................................................20112.2.2

Supportability......................................................................................................................203Chapter 13

Information Steward logs.....................................................................................................20313.1Log levels............................................................................................................................20313.1.1

2011-04-066

Contents

Changing log levels..............................................................................................................20413.1.2Viewing logs........................................................................................................................20513.1.3Viewing additional logs.........................................................................................................20713.1.4

Appendix.............................................................................................................................209Chapter 14

Glossary..............................................................................................................................20914.1

Index 215

2011-04-067

Contents

2011-04-068

Contents

Getting Started

1.1 Product overview

With operational systems frequently changing, data quality control becomes critical when you publishbusiness reports. SAP BusinessObjects Information Steward provides data profiling and validation rulefeatures that you can use to determine and improve the quality and structure of your source data.

Example:

1.2 Accessing Information Steward for administrative tasks

You perform administrative tasks for SAP BusinessObjects Information Steward on the CentralManagement Console (CMC) of SAP Business Intelligence Platform.1. Access the CMC in one of the following ways:

• Select SAP Business Intelligence Platform Central Management Console from the programgroup on the Windows Start menu.

Start > Programs > SAP BusinessObjects XI 4.0 > SAP BusinessObjects Enterprise > SAPBusinessObjects Enterprise Central Management Console.

• Type directly into your browser the name of the computer you are accessing.http://webserver:8080/BOE/CMC

Replace webserverwith the name of the web server machine. If you changed this default virtualdirectory on the web server, you need to type your URL accordingly. If necessary, change thedefault port number to the number you provided when you installed Business Intelligence Platform.

2. Login to the Central Management Console (CMC) with a user name that belongs to one or more ofthe following administration groups:• Data Insight Administrator• Metadata Management Administrator• Administrator

2011-04-069

Getting Started

For details, see "To log on to the CMC from your browser" in the BusinessObjects EnterpriseAdministrator's Guide.

3. On the CMC Home page, access Information Steward in one of the following ways:• Click the Information Steward link under the "Organize" area.• Click the Information Steward tab on the left of your screen.• Select the Information Steward option from the drop-down list at the top of the CMC Home

page.

2011-04-0610

Getting Started

Architecture

2.1 Architecture overview

Information Steward uses SAP BusinessObjects Business Intelligence platform for managing usersecurity, scheduling integrator sources as tasks and utilities, managing sources, and on demand services.

Information Steward uses Data Services for profiling, rule tasks, browsing metadata, and viewing data.

The following diagram shows the architectural components for SAP BusinessObjects BusinessIntelligence platform, SAP BusinessObjects Data Services, and SAP BusinessObjects InformationSteward.

Note:The diagram shows only the servers and services in the Business Intelligence platform and Data Servicesthat are relevant to Information Steward.

2011-04-0611

Architecture

Related Topics• Servers and services• Data Services Job Server• Web Application Server

2.1.1 Servers and services

SAP BusinessObjects Business Intelligence platform (BI platform) uses the terms server and serviceto refer to the two types of software running on an Information platform services machine.

The term “server” is used to describe an operating system level process (on some systems, this isreferred to as a daemon) hosting one or more services. For example, the Enterprise InformationManagement Adaptive Processing Server and Information Steward Job Server are servers. A serverruns under a specific operating system account and has its own PID.

A “service” is a server subsystem that performs a specific function. The service runs within the memoryspace of its server under the process id of the parent container (server). For example, the InformationStewardTask Scheduling Service is a subsystem that runs within the Information Steward Job Server.

2011-04-0612

Architecture

A “node” is a collection of BI platform servers running on the same host. One or more nodes can be ona single host.

Information platform services can be installed on a single machine, spread across different machineson an intranet, or separated over a wide area network (WAN).

2.1.1.1 Data Services Job Server

The Job Server component of SAP BusinessObjects Data Services is required for the following reasons:• The Data Services Job Server must already be installed on this computer because it provides the

following system management tools that are required during the first installation of InformationSteward:• Repository Manager

The Repository Manager creates the required Data Insight objects in the Information Stewardrepository. The Information Steward installer invokes the Repository Manager automatically whencreating the repository the first time the installer is run.

• Server Manager

The Server Manager creates the Information Steward job server group and job servers andassociates them to the Information Steward repository.

To add job servers to the Information Steward job server group, you must manually invoke theServer Manager. For details, see “Adding a job server for Data Insight” in the Installation Guide.

• The Data Services Job Server provides the engine processes that perform the Data Insight profilingand rule tasks. The engine processes use parallel execution and in-memory processing to deliverhigh data throughput and scalability.

Note:When you installed Data Services, ensure that you selected Job Server under the Server componentin the "Select Feature" window of the Data Services installer.

In addition, you need to choose MDS and VDS during the Data Services installation. These two optionsare not checked by default.

2.1.1.2 Web Application Server

SAP BusinessObjects Information Steward is deployed on:• The Central Management Console (CMC) through which you perform administrative tasks for

Information Steward

• A web application server through which you access the Information Steward modules:

2011-04-0613

Architecture

• Data Insight• Metadata Management• Metapedia• Cleansing Package Builder

Note:The Information Steward web application must be installed on the same web application server as thatof the SAP BusinessObjects Business Intelligence platform.

For specific version compatibility, refer to the Product Availability Matrix available at http://service.sap.com/PAM.

2.1.1.2.1 Administration

You use the Central Management Console (CMC) to perform SAP BusinessObjects Information Stewardadministrative tasks such as the following:• Define Data Insight connections and projects• Configure and run metadata integrators• Define source groups to subset the metadata when viewing relationships such as Same As, Impact,

and Lineage• Administer user security for the modules of Information Steward: Data Insight , Metadata Management,

and Cleansing Package Builder• Configure application settings that affect the behavior and performance of Data Insight profile and

rule tasks• Schedule Data Insight profile and rule tasks• Run or schedule Information Steward utilities

For more information, see the SAP BusinessObjects Information Steward Administrator Guide.

2.1.1.2.2 SAP BusinessObjects Information Steward web application

The SAP BusinessObjects Information Steward is a web-based interface through which users of eachmodule can perform tasks to analyze data and its metadata.• Data Insight users can perform tasks such as:

• Profile data in tables or files and analyze the resulting profile attributes• Define rules and set up data quality scorecards• View data quality score trend and view sample data that failed each rule• View data quality impact on dependent data sources

• Metadata Management users can perform tasks such as:• View metadata from different sources and search for objects without the need to know the source

or application in which it exists• Add annotations to an object and define custom attributes and values for an object• Run pre-defined reports that answer typical business questions such as "Which Universe objects

are not used in my reports?" or "Which reports are using my tables?"• View impact and lineage of objects within the same source or within different sources.

2011-04-0614

Architecture

http://service.sap.com/PAM


• Impact analysis - Allows you to identify which objects will be affected if you change or removeother connected objects.

• Lineage analysis - Allows you to trace back from a target object to the source object.

• Metapedia can perform tasks such as:• Define Metapedia terms related to your business data and organize the terms into categories.

• Cleansing Package Builder can perform tasks such as:• Define cleansing packages to parse and standardize data• Publish a cleansing package and export it to SAP BusinessObjects Data Services where users

can import it to generate a base Data Cleanse transform that can be included in jobs to cleanseyour data

For more information, see the SAP BusinessObjects Information Steward User Guide.

2.1.1.3 Metadata integrators

Metadata integrators are programs that do the following:• Collect metadata from source systems and store the collected metadata into the SAP BusinessObjects

Information Steward repository.• Can be scheduled to run at regular intervals.• Update the existing metadata.• Can run on one job server or multiple job servers for load balancing and high availability.• Each run as a separate process.

SAP BusinessObjects Information Steward provides the following metadata integrators:

Metadata collectedMetadata integrator name

Collects metadata about objects such as univers-es, Crystal Reports, Web Intelligence documents,and Desktop Intelligence documents.

SAP BusinessObjects Enterprise Metadata Inte-grator

Collects metadata about objects such as Queries,InfoProviders, InfoObjects, Transformations, andDataSources from an SAP NetWeaver BusinessWarehouse system.

SAP NetWeaver Business Warehouse MetadataIntegrator

Collects metadata about objects such as catalogs,schemas, and tables from the CWM RelationalPackage.

Common Warehouse Model (CWM) MetadataIntegrator

Collects metadata about objects such as projects,catalogs, datasources, and mapping rules froma Data Federator repository.

SAP BusinessObjects Data Federator MetadataIntegrator

2011-04-0615

Architecture

Metadata collectedMetadata integrator name

Collects metadata about objects such as sourcetables, target tables, and column mappings froma Data Services repository.

SAP BusinessObjects Data Services MetadataIntegrator

Collects metadata from other third-party sourcessuch as the following:• Data Modeling metadata such as Sybase

Power Designer, Embarcadero ER/Studio, andOracle Designer

• Extract, Transform, and Load (ETL) metadatasuch as Oracle Warehouse Builder and Mi-crosoft SQL Server Integration Services (SSIS)

• OLAP and BI metadata such as IBM DB2Cube Views, Oracle OLAP, and Cognos BIReporting

Meta Integration Metadata Bridge (MIMB) Meta-data Integrator (also known as MITI Integrator)

Collects metadata from relational database man-agement systems (RDBMS) which can be DB2,MySQL, Oracle, SQL Server, Java DatabaseConnectivity (JDBC), or a BusinessObjects Uni-verse connection. Collected metadata includesthe definition of objects such as tables, view,synonyms, and aliases.

Relational databases Metadata Integrator

You can also obtain third-party metadata integrators for other data sources. For more information aboutthird-party metadata integrators, see http://www.metaintegration.net/Products/MIMB/SupportedTools.html.

Related Topics• User Guide: section "BusinessObjects Enterprise objects"• User Guide: "SAP NetWeaver Business Warehouse metadata"• User Guide: section "Data Modeling metadata"• User Guide: section "BusinessObjects Data Federator objects"• User Guide: section "BusinessObjects Data Services objects"• http://www.metaintegration.net/Products/MIMB/SupportedTools.html• http://www.metaintegration.net/Products/MIMB/Documentation/• User Guide: section "Relational Database metadata"

2.1.1.4 Services

2011-04-0616

Architecture

http://www.metaintegration.net/Products/MIMB/SupportedTools.html

http://www.metaintegration.net/Products/MIMB/SupportedTools.html

http://www.metaintegration.net/Products/MIMB/Documentation/

The following table describes each of the services that are pertinent to SAP BusinessObjects InformationSteward.

Table 2-2: Services pertinent to Information Steward

Deployment commentsService descriptionPart of serverthat serviceruns on

Service

An Adaptive Processing Server ofSAP BusinessObjects Business Intel-ligence platform must already be in-stalled on this computer.

Performs the data analysis when youcreate a custom cleansing package inCleansing Package Builder. The dataanalysis uses the information the userprovides in the custom cleansing pack-age wizard, along with statistical analy-sis, to create an abstract version of therecords. The abstracted records arethen grouped, and each group is pro-cessed with data inference algorithmsto create the suggestions that the usersees in Design mode of CleansingPackage Builder.

Enterprise Infor-mation Manage-ment AdaptiveProcessingServer

CleansingPackageBuilderAuto-anal-ysis Ser-vice


Performs all the main functionality ofCleansing Package Builder, such ascreating and opening cleansing pack-ages, Design mode, and AdvancedMode.


CleansingPackageBuilderCore Ser-vice


Converts a published cleansing pack-age to the reference data format usedby Data Services. This process can takea significant period of time for largecleansing packages.


CleansingPackageBuilderPublishingService


Performs tasks on Data Services suchas test rule, delete objects (connection,datastore, workflow) from Data Ser-vices, export rules to Data Services.


Informa-tion Stew-ard Admin-istratorTask Ser-vice

2011-04-0617

Architecture


Service

The Data Services Metadata Brows-ing Service is a component of SAPBusinessObjects Data Serviceswhich must already be installed onthis computer.


Provides Data Insight users the capabil-ity to browse and import metadata fromdifferent data sources. Data sourcesinclude relational database systems(such as Oracle and Microsoft SQLServer) , and Applications (such as,SAP ECC and Oracle Applications).


Data Ser-vice Meta-dataBrowsingService

The Data Services View Data Serviceis a component of SAP BusinessOb-jects Data Services which must al-ready be installed on this computer.


Provides the capability to view the exter-nal data in Data Insight connections inInformation Steward.


Data Ser-vices ViewData Ser-vice

It is recommended that you install theMetadata Relationship Service on adifferent computer than the web ap-plication server. An Adaptive Process-ing Server of SAP Business Intelli-gence Platform must already be in-stalled on that computer.

You can deploy multiple MetadataRelationship Services for load balanc-ing and availability.

Computes metadata object relationships(such as data lineage and change im-pact analysis). The Metadata Manage-ment module of Information Stewarduses the results of these computed re-lationships to display metadata relation-ship diagrams.


Informa-tion Stew-ard Meta-data Rela-tionshipService

2011-04-0618

Architecture


Service

You can deploy multiple search ser-vices for load balancing and availabil-ity.If the Metadata Search Service is notavailable during the construction andupdate processes, the search mightreturn incorrect results. For thesesituations, Information Steward pro-vides a utility to reconstruct thesearch index. For details, see“Recreating search indexes onMetadata Management” in the Admin-istrator Guide.

Allows you to find an object that existsin any integrator source while viewingmetadata on the Metadata Managementmodule of Information Steward. It usesthe Lucene Search Engine.

The Metadata Search Service con-structs the search index during the exe-cution of the Metadata Integrators, andthe File Repository Server stores thecompressed search index. The Metada-ta Search Service also updates thesearch index for changes to Metapediaterms and categories, custom attributes,and annotations.


Informa-tion Stew-ard Meta-dataSearchService

An Adaptive Job Server of SAPBusinessObjects Business Intelli-gence platform must already be in-stalled on this computer.

Processes scheduled Data Insight pro-file and rule tasks in the Central Man-agement Console (CMC).

InformationSteward JobServer

Informa-tion Stew-ard TaskSchedul-ing Ser-vice

An Adaptive Job Server of SAPBusinessObjects Business Intelli-gence platform must already be in-stalled on this computer.

Processes scheduled Metadata Man-agement integrator sources in theCentral Management Console (CMC).

InformationSteward JobServer

Informa-tion Stew-ard Inte-gratorSchedul-ing Ser-vice

It is installed with the integrators.Helper service that is used for testingconnections to integrator sources.


Informa-tion Stew-ard Inte-grator Ser-vice

2.2 Information Steward on Business Intelligence platform components

2011-04-0619

Architecture

The following table describes how SAP BusinessObjects Information Steward uses each pertinent SAPBusinessObjects Business Intelligence platform (BI platform) component.

How SAP BusinessObjects Information Steward uses componentBI platformcomponent

Deploys Information Steward on:• The Central Management Console (CMC) through which administrative tasks

for Information Steward are performed• A web application server through which you access the Information Steward

modules:• Data Insight• Metadata Management• Metapedia• Cleansing Package Builder

Web Applica-tion Server

Manages the following for SAP BusinessObjects Information Steward• Enterprise Information Management Adaptive Processing Server (EIMAdaptive-

ProcessingServer) and services• Information Steward Job Server (ISJobServer) and services• Manage Metadata Management module:

• Integrator source configurations• Source group configurations

• Manage Data Insight module:• Connections• Projects• Profile and rule tasks

• Manage Cleansing Package Builder module:• Cleansing package owner

• Information Steward utilities• User security (authentication and authorization)• Manage repository and application settings

Central Man-agement Con-sole (CMC)

2011-04-0620

Architecture


Maintains a database of information about your BI platform system. The data storedby the CMS includes information about users and groups, security levels, scheduleinformation, BI platform content, and servers. For more information about the CMS,see SAP BusinessObjects Business Intelligence Platform Administrator's Guide.

The following objects in the Metadata Management module of Information Stewardare stored in the CMS.• Integrator Source configurations• Source groups• Utilities configurations• Data Insight connections• Projects• Tasks

Note:Because integrator source configurations and source group definitions are storedin the CMS, you can use the Upgrade management tool to move them from oneversion of the CMS to another. The schedules and rights information are considereddependencies of these configurations. For details, see the Upgrade Guide and the“Lifecycle Management” section in the Administrator Guide.

Central Man-agement Serv-er (CMS)

Information Steward Job Server uses the Adaptive Job Server for executing profilingtasks and integrator tasks.

The server may host the following services for Information Steward:• Information Steward Task Scheduling Service• Information Steward Integrator Scheduling Service

Adaptive JobServer

Required during Information Steward installation to create the Enterprise Informa-tion Management Adaptive Processing Server.

The EIM Adaptive Processing Server uses BIP adaptive processing server to hostthe following services:• Metadata Relationship Service• Metadata Search Service• Metadata Integrator Service• Data Services Metadata Browsing Service• Data Services View Data Service• Information Steward Administrator Task Service• Cleansing Package Builder Core Service• Cleansing Package Builder Auto-analysis Service• Cleansing Package Builder Publishing Service

Adaptive Pro-cessing Server

2011-04-0621

Architecture


Stores files associated with:• A published cleansing package. The stored information can be accessed by

Data Services• History logs for Data Insight task and metadata integrator execution• Search index for metadata integrator objects

File RepositoryServer

2.3 Information workflows

When tasks are performed in SAP BusinessObjects Information Steward, such as adding a table to aData Insight project, running a Metadata Management integrator source, or creating a cleansing package,information flows through SAP BusinessObjects intelligence platform services, SAP BusinessObjectsData Services, and SAP BusinessObjects Information Steward. The servers and services within eachof these software products communicate with each other to accomplish a task. For an overview of theservers and services, see Architecture overview.

The following section describes some of the process flows as they would happen in SAP BusinessObjectsintelligence platform services, SAP BusinessObjects Data Services, and SAP BusinessObjectsInformation Steward.

2.3.1 Adding a table to a Data Insight project

This workflow describes the process of adding a table to a Data Insight project.1. The user selects the Add > Tables on "Workspace Home" in the Data Insight tab to access the

"Browse Metadata" window.2. The web application server passes the request to the Central Management Server (CMS) and returns

a list of connections that the user can view assuming the user has appropriate permissions to viewthe connections.

3. If the user has the appropriate rights to view the selected connection, the CMS sends the requestto the Data Services Metadata Browsing Service.

4. The Data Services Metadata Browsing Service obtains the metadata from the connection and sendsthe metadata to the web application server.

5. The web application server displays the metadata in the Data Insight "Browse Metadata" window.6. When the user selects a table and clicks Add to Project, the web application stores the metadata

in the Information Steward repository.

2011-04-0622

Architecture

2.3.2 Profiling data

This workflow describes the process of running a profile task in Data Insight. Running validation rulesare similar to the steps here.1. The user selects the name of a table or file on "Workspace Home" in the Data Insight tab and clicks

Profile.2. Choose the tables in the "Workspace home" of the Data Insight tab.3. Save the task and schedule to run it.4. The web application server passes the request to the Central Management Server (CMS).5. The Information Steward web application determines from the CMS system if the user has the right

to run profile tasks on the connection that contains the table or file.6. The administrator determines if the user has the right to create a profile task for the connection, and

has the right to schedule the task. If so, the task is scheduled in the CMS system.7. When the scheduled time arrives, the CMS sends the task information to the Information Steward

Task Scheduling Service.8. The Information Steward Task Scheduling Service sends the profile task to the Data Services Job

Server.9. The Data Services Job Server partitions the profile task based on the performance application

settings.10. The Data Services Job Server executes the profile task and stores the results in the Information

Steward repository.11. The web application server displays the profile results in the Data Insight "Workspace Home" window.

2.3.3 Scheduling and running a Metadata Management integrator source

This workflow describes the process of scheduling and running a Metadata Management integratorsource to collect metadata.1. The user schedules an integrator source on the Central Management Console (CMC) and the request

is sent to the CMS system.2. The CMS determines if the user has the appropriate rights to schedule the integrator source.3. If the user has the appropriate rights to schedule the object, the CMS commits the scheduled

integrator request to the CMS system.4. When the scheduled time arrives, the CMS finds a suitable Information Steward Job Server based

on the Job Server group associated with the integrator and passes the job.If the process has a SAP BusinessObjects Enterprise 3.x source system, the process contacts theregistered remote job server and passes along the integrator process information.

2011-04-0623

Architecture

5. The integrator process collects metadata and stores the metadata in the Information Stewardrepository.

6. The integrator process also generates the Metadata Management search index files and loads themto the Input File Repository Server.

7. After uploading the search index files, the integrator source notifies the Metadata Managementsearch service.

8. The Metadata Management search service downloads the generated index files and consolidatesthem into a master index file.

9. The Information Steward Integrator Scheduling Service updates the CMS with the job status.

2.3.4 Creating a custom cleansing package with Cleansing Package Builder

This workflow describes the process of creating and publishing a custom cleansing package in CleansingPackage Builder.1. In Information Steward, the user clicks the Cleansing Package Builder tab.2. The Cleansing Package Builder (CPB) application sends the user's login information to the CPB

Web Service.3. The CPB Web Service sends the information to the Enterprise Information Management (EIM)

Adaptive Processing server.The EIM Adaptive Processing Server runs on the Business Intelligence platform.

4. The EIM Adaptive Processing Server determines which rights the user has in CPB.5. The information is sent back through the CPB Web Service to the CPB application.

The user sees the cleansing packges they have the rights to view.

6. In the "Cleansing Packages Tasks" screen, the user selects New Cleansing Package > CustomCleansing Package to start creating a cleansing package.The user provides the necessary information and sample data to create the cleansing package.

7. The CPB application sends the information through the CPB Web Service to the CPB Core Service,using the BusinessObjects Enterprise SDK mechanism.The CPB Core Service handles the main functions of CPB. The CPB Core Service runs on the EIMAdaptive Processing Server.

8. The CPB Core Service sends the response back through the CPB Web Service to the CPBapplication.The new cleansing package is created in CPB.

9. The application communicates with the CPB Auto-Analysis Service through the CPB Web Service.The CPB Auto-Analysis Service analyzes the data to create suggestions of standard forms andvariations. The CPB Auto-Analysis Service runs on the EIM Adaptive Processing Server.

10. When the user has finished refining the cleansing package, the user clicks Publish on the "CleansingPackages Tasks" screen.

11. The CPB application communicates with the CPB Publishing Service through the CPB Web Service.

2011-04-0624

Architecture

The CPB Publishing Service assists in the cleansing package's conversion to the reference dataformat used by Data Services. The CPB Publishing Service runs on the Enterprise ManagementAdaptive Processing Server.

12. The published cleansing package information is sent to the Input File Repository, where it is storedand can be accessed by Data Services.The Input File Repository runs on the Business Intelligence platform.

13. Data Services communicates directly with the Business Intelligence platform to sync with the publishedcleansing packages.

2011-04-0625

Architecture

2011-04-0626

Architecture

Securing SAP BusinessObjects Information Steward

3.1 Security Overview

SAP BusinessObjects Information Steward uses the security framework that SAP BusinessObjectsBusiness Intelligence plaform (BI platform) provides.

The BI platform architecture addresses the many security concerns that affect today's businesses andorganizations. The current release supports features such as distributed security, single sign-on, resourceaccess security, granular object rights, and third-party authentication in order to protect againstunauthorized access.

For details about how BI platform addresses enterprise security concerns, see the “Securing Informationplatform services” section of the SAP BusinessObjects Business Intelligence Platform Administrator'sGuide.

For details about user groups and granular object rights, see Information Steward pre-defined usersand groups

The following topics detail how Information Steward uses the enterprise security features provided byBI platform.

Related Topics• Securing user data for Information Steward• Storage of sensitive information• Configuring the Remote Job Server for SSL• Reverse proxy servers

3.2 Enterprise security

SAP BusinessObjects Information Steward is a web-based application that uses enterprise securityprovided by SAP BusinessObjects Business Intelligence platform. This section details the ways in whichInformation Steward takes advantage of the followingSAP BusinessObjects Enterprise security features:• Secure access to user data• Storage of sensitive information

2011-04-0627


• Secure connections• Reverse proxy servres

Related Topics• Securing user data for Information Steward• Storage of sensitive information• Configuring the Remote Job Server for SSL• Reverse proxy servers

3.2.1 Securing user data for Information Steward

SAP BusinessObjects Information Steward has access to the following data which might contain sensitiveinformation:• Source data in Data Insight connections on which users run profile and rule tasks• Sample data from profiling results that Data Insight stores in the Information Steward repository• Sample data that failed validation rules that Data Insight stores in the Information Steward repository• All data that failed validation rules that a user chooses to store in a database accessed through a

Data Insight connection.

The Database Administrator (DBA) secures the data in these databases by managing user permissionson them:• Data Insight connections for profiling• Information Steward repository• Data Insight connections for all data that failed validation rules

In addition, the Data Insight Administrator or Administrator control access to the data by using theCentral Management System (CMS) to manage the following rights on the Data Insight connections:• View Data• Profile/Rule permission• View Sample Data• Export DataFor more information, see User rights in Data Insight.

3.2.2 Storage of sensitive information

Information Steward uses the SAP BusinessObjects Enterprise cryptography which is designed toprotect sensitive data stored in the CMS repository. Sensitive data includes user credentials, data

2011-04-0628


source connectivity data, and any other info objects that store passwords. This data is encrypted toensure privacy, keep it free from corruption, and maintain access control. For more information, seethe "Overview of SAP BusinessObjects Enterprise data security" section of the SAP BusinessObjectsEnterprise Administrator's Guide.

Encryption of sensitive information, such as passwords, is done in the following Information Stewardareas:• Information Steward repositories• Metadata Integrator sources• Data Insight connections

3.2.3 Configuring the Remote Job Server for SSL

The SAP BusinessObjects Enterprise Metadata Integrator in SAP BusinessObjects Information Steward4.0 can collect metadata from an SAP BusinessObjects Enterprise XI 3.x system by using the RemoteJob Server. When you install Information Steward, you install the Remote Job Server component onthe computer where the Enterprise XI 3.x system resides. Then you use the Information Steward ServiceConfiguration to configure the Remote Job Server. For information about installing the Remote JobServer on the SAP BusinessObjects Enterprise XI 3.x system, see “Remote Job Server Installation” inthe Installation Guide.

If you are using the Secure Sockets Layer (SSL) protocol for all network communication between clientsand servers in your SAP BusinessObjects EnterpriseXI 3.x and SAP BusinessObjects Businessintelligence platform 4.0 deployments, you can use SSL for the network communication between theRemote Job Server and the Metadata Integrator on Information Steward. In this enviironment:• The server is the Remote Job server on the SAP BusinessObjects EnterpriseXI 3.x. To enable SSL,

the server must have both keystore and truststore files defined.• The client is the Metadata Integrator on Information Steward 4.0. To enable SSL, the client must

use the same truststore and password as the server.

To set up SSL between the the Remote Job Server and the Metadata Integrator, you need to performthe following tasks:• Create keystore and truststore files for the Remote Job Server and copy the truststore file to the

SAP BusinessObjects Business intelligence platform 4.0 system.• Configure the location of SAP BusinessObjects XI 3.x SSL certificates and key file names (from

Server Intelligence Agent (SIA)).

Related Topics• Creating the keystore and truststore files for the Remote Job Server• Configuring the SSL protocol for the Remote Job Server

2011-04-0629


3.2.3.1 Creating the keystore and truststore files for the Remote Job Server

To set up SSL protocol for communication to the Remote Job Server, use the keytool command to:• Create a certificate and store it in a keystore file on the computer where SAP BusinessObjects

Enterprise XI 3.x resides• Create a trust certificate and store it in a truststore file on the computer where SAP BusinessObjects

Enterprise XI 3.x resides• Copy the trust certificate into a truststore file on the computer where SAP BusinessObjects Business

Intelligence Platform 4.0. resides

1. On the computer where you installed SAP BusinessObjects Enterprise XI 3.x, generate a keystorefile and export it:a. Open a cmd window and go to the directory where Metadata Management configuration files are

stored for Information Steward.For example, type the following command:cd C:\Program Files (x86)\SAP BusinessObjects\InformationSteward\MM\config

b. Generate the keystore file using the keytool command.For example, type the following command to generate a keystore file with the name is.keystoreand password mypwstore:%JAVA_HOME%\bin\keytool -genkey -keystore is.keystore

-keyalg RSA -dname "CN=localhost,OU=ICC,O=ICC,L=PA,ST=CA,C=US"-keypass mypwkey -storepass mypwstore

The value for keypass protects the generated key.This command creates the key and certificate in the keystore file in the C:\Program Files(x86)\SAP BusinessObjects\InformationSteward\MM\config directory.

c. Export the certificate from the keystore file using the keytool command.For example, type the following command to export to the file isClient.cer:%JAVA_HOME%\bin\keytool -export -keystore is.keystore-file isClient.cer -keypass mypwkey -storepass mypwstore

d. Import the certificate from the export file to create the truststore file.For example, type the following command to import the certificate into a truststore file namedis.truststore.keystore:%JAVA_HOME%\bin\keytool -import -v -trustcacerts-file isClient.cer -keystore is.truststore.keystore-keypass mypwkey -storepass mypwstore

This command stores the certificate in the truststore file in the InformationSteward\MM\Configdirectory.

2. Copy the truststore file to the computer where SAP BusinessObjects Business Intelligence Platform4.0. resides.

2011-04-0630


a. Ensure that the is.truststore.keystore file is in a directory that is accessible to both thecomputer where SAP BusinessObjects Enterprise XI 3.x is installed and the computer whereSAP BusinessObjects Business Intelligence Platform 4.0. is installed.

b. Copy the is.truststore.keystore file to the directory where Metadata Managementconfiguration files are stored for Information Steward.For example:C:\Program Files (x86)\SAP BusinessObjects\InformationSteward\MM\config

3.2.3.2 Configuring the SSL protocol for the Remote Job Server

After you create a key and certificate on the Remote Job Server computer and store them in a securelocation, you need to provide the Information Steward Service Configuration on SAP BusinessObjectsXI 3.x with the secure location.

To configure the SSL protocol in the CCM:1. Obtain the SSL certificate and key file names from the Server Intelligence Agent.properties.

a. Access the Central Configuration Manager (CCM) from the Windows Start > Programs menuunder your version of SAP BusinessObjects XI 3.x:SAP BusinessObjects Information Steward 4.0 > Central Configuration Manager

b. In the CCM, right-click Server Intelligence Agent and choose Properties.c. Obtain the values for the following options:

• SSL Certificates Folder• Server SSL Certificate File• SSL Trusted Certificate File• SSL Private Key File• SSL Private Key File Passphrase FileFor more information about these options, see “Configuring servers for SSL” in the SAPBusinessObjects Business Intelligence Platform Administrator's Guide.

d. Click Cancel to close the "Server Intelligence Agent Properties" window.

2. Access the Information Steward Service Configuration tool from the Windows Start > Programsmenu under your version of SAP BusinessObjects XI 3.x:SAP BusinessObjects Information Steward 4.0 > Information Steward Service Configuration.

3. In the "SAP BusinessObjects Information Steward Service Configuration" window, click the "Protocol"tab.

4. Make sure Enable SSL is selected.5. For the following options, enter the values for the SIA that you obtained from the CCM in step 1c

above.• SSL Certificates Folder• Server SSL Certificate File

2011-04-0631


• SSL Trusted Certificate File• SSL Private Key File• SSL Private Key File Passphrase File

6. For Keystore File and Keystore Password, enter the values that you specified in the keystoreand storepass options of the keytool -genkey command in step 1b in Creating the keystoreand truststore files for the Remote Job Server.

7. For Truststore File and Truststore Password, enter the values that you specified in the keystoreand storepass options of the keytool -import command in step 1d in Creating the keystoreand truststore files for the Remote Job Server.

8. Click Apply.9. Restart the Remote Job Server.

a. Click the "General" tab in "SAP BusinessObjects Information Steward Service Configuration"window.

b. Click Stop.c. Click Start.

Note:To run an integrator source with SSL enabled on the Remote Job Server, set the following run-timeJVM parameter. For more details, see Metadata collection using the Remote Job Server with SSL .-Dbusinessobjects.migration=on

3.2.4 Reverse proxy servers

SAP BusinessObjects Information Steward can be deployed in an environment with one or more reverseproxy servers. A reverse proxy server is typically deployed in front of the web application servers inorder to hide them behind a single IP address. This configuration routes all Internet traffic that isaddressed to private web application servers through the reverse proxy server, hiding private IPaddresses.

Because the reverse proxy server translates the public URLs to internal URLs, it must be configuredwith the URLs of the Information Steward web applications that are deployed on the internal network.

For information about supported reverse proxy servers and how to configure them, see “Informationplatform services and reverse proxy servers” and “Configuring reverse proxy servers for Informationplatform” in the SAP information platform services Administrator's Guide.

2011-04-0632


Users and Groups Management

4.1 Users and Groups overview

The Central Management System (CMS) manages security information, such as user accounts, groupmemberships, and object rights that define user and group privileges. When a user attempts an actionon an Information Steward object, the CMS authorizes the action only after it verifies that the user'saccount or group membership has sufficient privileges.

Use BusinessObjects Business Intelligence platform (formely known as BusinessObjects Enterprise)security to create users and authorize user access to the objects and actions within the InformationSteward modules:• Data Insight• Metadata Management• Metapedia (under Metadata Management in the Central Management Console)• Cleansing Package Builder

Information Steward provides pre-defined user groups that have specific rights on objects unique toeach module. These user groups enable you to grant rights to multiple users by adding the users to agroup instead of modifying the rights for each user account individually. You also have the ability tocreate your own user groups.

Related Topics• Information Steward pre-defined users and groups• Managing users in Information Steward• User rights in Data Insight• User rights in Metadata Management• User rights in Cleansing Package Builder

4.2 Information Steward pre-defined users and groups

SAP BusinessObjects Information Steward provides pre-defined user groups for each module (DataInsight, Metadata Management, Cleansing Package Builder) to facilitate managing security on theobjects within each module.

2011-04-0633


The following diagram provides an overview of the pre-defined Information Steward user groups andtheir relation to the Administrator group in SAP BusinessObjects Business Intelligence platform.• The Administrator group in Business Intelligence platform is for users that:

• Create users and custom groups for all Information Steward modules• Have rights to perform all tasks within all Information Steward modules.• Grant users access to cleansing packages

• The Data Insight Administrator is for users that grant users and groups access to connections andprojects (by default, all pre-defined Data Insight groups are granted access to all connections andprojects). A Data Insight Administrator also has access to all Data Insight actions.

• The Metadata Management Administrator grants users access to integrator sources. The MetadataManagement Administrator also has access to all Metadata Management actions.

• Within each Information Steward module, additional user groups have specific rights for the objectswithin that module. For example, the Data Insight Analyst group can create profile tasks and rules,but only the Data Insight Rule Approver can approve rules.

Subsequent topics describe these pre-defined groups and the rights they have on the specific objects.

2011-04-0634


Related Topics• Data Insight pre-defined user groups• Type-specific rights for Data Insight objects• Metadata Management pre-defined user groups• Type-specific rights for Metadata Management objects

4.3 Managing users in Information Steward

2011-04-0635


This section contains the steps to create users and add them to Information Steward groups.

4.3.1 Creating users for Information Steward

Create user accounts and assign them to groups or assign rights to control their access to objects inSAP BusinessObjects Information Steward.

To create users:1. Log on to the Central Management Console (CMC) with a user name that belongs to the Administrator

group.2. At the CMC home page, click Users and Groups.3. Click Manage > New > New User.4. To create a user:

a. Select your authentication type from the Authentication Type list.Information Steward can use the following user authentication:• Enterprise (default)• LDAP• Windows Active Directory (AD)• SAP ERP and Business Warehouse (BW)

b. Type the account name, full name, email, and description information.

Tip:Use the description area to include extra information about the user or account.

c. Specify the password information and settings.

5. To create a user that will logon using a different authentication type, select the appropriate optionfrom the Authentication Type list, and type the account name.

6. Specify how to designate the user account according to options stipulated by your SAPBusinessObjects Business Intelligence platform license agreement.If your license agreement is based on user roles, select one of the following options:• BI Viewer: access to Business Intelligence platform applications for all accounts under the BI

Viewer role is defined in the license agreement. Users are restricted to access applicationworkflows that are defined for the BI Viewer role. Access rights are generally limited to viewingbusiness intelligence documents. This role is typically suitable for users who consume contentthrough Business Intelligence platform applications.

• BI Analyst: access to SAP BusinessObjects Enterprise applications for all accounts under theBI Analyst role is defined in the license agreement. Users can access all applications workflowsthat are defined for the BI Analyst role. Access rights include viewing and modifying businessintelligence documents. This role is typically suitable for users who create and modify contentfor Business Intelligence platform applications

If your license agreement is not based on user roles, specify a connection type for the user account.

2011-04-0636


• Choose Concurrent User if this user belongs to a license agreement that states the number ofusers allowed to be connected at one time.

• Choose Named User if this user belongs to a license agreement that associates a specific userwith a license. Named user licenses are useful for people who require access to BusinessObjectsEnterprise regardless of the number of other people who are currently connected.

7. Click Create & Close.

The user is added to the system and is automatically added to the Everyone group. An inbox isautomatically created for the user, as is an Enterprise alias. You can now add the user to a group orspecify rights for the user.

Related Topics• Adding users and user groups to Information Steward groups• BusinessObjects Enterprise Administrator's Guide: Managing users and groups

4.3.2 Adding users and user groups to Information Steward groups

Groups are collections of users who share the same rights to different objects. SAP BusinessObjectsInformation Steward provides groups for Data Insight and Metadata Management, such as Data InsightAnalyst group and Metadata Management User group.

To add a user to a group:1. Log on to the Central Management Console (CMC) with a user name that belongs to the Administrator

group.2. At the CMC home page, click Users and Groups.3. Select the User List or Group List node in the navigation tree.4. Select the name of the user or user group in the right panel.5. Click Actions > Join Group.6. On the "Join Group" dialog box, select the Group List node in the navigation tree.7. Select one or more names from the "Available Groups" list, and click > to place them in the

"Destination Group(s)" list.8. Click OK.

Related Topics• Data Insight pre-defined user groups• Group rights for connections• Group rights for projects• Group rights for tasks• Metadata Management pre-defined user groups

2011-04-0637


4.3.3 Denying access

To deny access to Information Steward for an individual user or group:1. Log on to the Central Management Console (CMC) with a user name that is a member of either the

Administrator group or the Data Insight Administrator group.2. At the CMC home page, click Information Steward.3. Click Manage > Security > User Security.4. On the "User Security" page, click Add Principals.5. In the list of "Available users/groups", select the name of each user or group that you want to deny

access, and click the > button to move the names to the "Selected users/groups" list.6. Click Add and Assign Security.7. Click the Advanced tab.8. Click the Add/Remove Rights link.9. On the General rights list, deny the "View objects"right.10. Click Apply or OK.

4.4 User rights in Data Insight

The Data Insight module of SAP BusinessObjects Information Steward contains the following objectsthat have specific rights that allow various actions on them.• Connections through which users view data sources and import tables and files to profile the data.

In addition to rights to the connection, a user must also be granted permission on the source data:

For database connections, the Database Administrator must grant privileges on the tables to theuser.

For file connections, the users that run the following services must have permissions on the directorywhere the file resides:• Information Steward Web Application Server (for example, Tomcat)• Data Services service• Server Intelligence Agent that runs EIMAdaptiveProcessingServer and ISJobServer

• Views that can join tables and files from multiple connections.• Projects that contain profile tasks, rule tasks, and scorecards in specific business areas, such as

HR or Sales.• Profile tasks that collect profile attributes to help you determine the quality and structure of the data.• Rule tasks that validate the data according to your business and quality rules.

2011-04-0638


The following diagram shows a pictorial view of users and groups who are granted rights to accessConnections, Projects, and Tasks.

Related Topics• Data Insight pre-defined user groups• Type-specific rights for Data Insight objects• Customizing rights on Data Insight objects• Managing users in Information Steward

4.4.1 Data Insight pre-defined user groups

SAP BusinessObjects Information Steward provides the following pre-defined Data Insight user groupsto facilitate the assignment of rights on connections, projects, and tasks. These groups enable you tochange the rights for multiple users in one place (a group) instead of modifying the rights for each useraccount individually.

The following table describes the pre-defined user groups in ascending order of rights.

2011-04-0639


Table 4-1: Data Insight User Groups

DescriptionUser group

Users that can only view the connections, projects, source data, profile re-sults, sample profile data, rules, sample data that failed rules, and scorecardresults.

Data Insight User

Users that have all the rights of a Data Insight User, plus the following rights:• Add tables and files to a project• Remove tables and files from a project• Create, edit, and delete profile tasks and rule tasks• Create, edit, and delete rules, bind rules• Schedule profile tasks and rule tasks

Data Insight Analyst

Users that have all the rights of a Data Insight Analyst, plus the right toapprove and reject rules.

Data Insight Rule Ap-prover

Users that have all the rights of a Data Insight Analyst, plus the right tocreate and edit scorecards that consist of rules for specific business areascalled Key Data Domains.

Data Insight ScorecardManager

Users that have all the above rights on Data Insight objects, plus the follow-ing rights:• Configure, edit, delete, run, schedule, view history of Information Steward

utilities• Create, edit, and delete Data Insight connections and projects• Configure Information Steward application settings• Change Information Steward repository user and password

Data Insight Administra-tor

Related Topics• Group rights for Data Insight folders and objects in the CMC• Group rights for connections• User rights for views• Group rights for projects• Group rights for tasks

4.4.2 Type-specific rights for Data Insight objects

Rights are the base units for controlling user access to the objects, users, applications, servers, andother features in SAP BusinessObjects Enterprise.

2011-04-0640


“Type-specific rights” are rights that affect specific object types only, such as Data Insight connections,Data Insight projects, profile tasks, or rule tasks.

Rights are set on objects, such as a Data Insight connection or project, rather than on the "principals"(the users and groups) who access them. By default, the pre-defined Data Insight user groups aregranted access to newly created connections and projects. If you want some users to access onlycertain connections and projects, then do not add them to a pre-defined group, but add their user namesto the list of principals for each individual connection and project and assign the appropriate type -specificrights. For example, to give a user access to a particular connection, you add the user to the list ofprincipals who have access to the connection.

Type-specific rights consist of the following:• General rights for the object type

These rights are identical to general global rights (for example, the right to add, delete, or edit anobject), but you set them on specific object types to override the general global rights settings.

• Specific rights for the object type

These rights are available for specific object types only. For example, the right to view data appearsfor Data Insight connections but not for Data Insight projects.

For more information, see "How rights work in BusinessObjects Enterprise" in the BusinessObjectsEnterprise Administrator's Guide.

Related Topics• Group rights for connections• Group rights for projects• Group rights for tasks

4.4.2.1 Group rights for Data Insight folders and objects in the CMC

Each pre-defined Data Insight user group provides specific rights on the folders and objects in the CMC,as the following tables shows.

2011-04-0641


Table 4-2: Rights for Data Insight folders in the CMC

Pre-defined User Groups

DescriptionRightName

CMC Folder orObject

Data In-sightUser

Data In-sightAnalyst

Data In-sightRule Ap-prover

Data InsightScorecardManager

Data InsightAdministra-tor

YesYesYesYesYesView Data Insightfolder on the CMC

Viewobjects

Data Insightfolder

NoNoNoNoYesModify the rightsusers have to DataInsight

ModifyRights

YesYesYesYesYesView connections inConnections folder

Viewobjects

Connectionsfolder

NoNoNoNoYesCreate connection

AddObjectsto Fold-er

NoNoNoNoYesModify the rightsusers have to con-nections

ModifyRights

NoYesYesYesYesView connectionproperties

Viewobjects

Data InsightConnection

NoNoNoNoYesEdit connectionproperties

Edit ob-jects

NoNoNoNoYesDelete connectionDeleteobjects

NoNoNoNoYesModify the rightsusers have to DataInsight connections

ModifyRights

YesYesYesYesYesView Projects folderViewobjects

Projects folder NoNoNoNoYesCreate projectAdd ob-jects

NoNoNoNoYesModify the rightsusers have toprojects

ModifyRights

2011-04-0642




CMC Folder orObject

Data In-sightUser





NoYesYesYesYesView project proper-ties

Viewobjects

Projects

NoNoNoNoYesEdit project proper-ties

Edit ob-jects

NoNoNoNoYesDelete projectDeleteobjects

NoNoNoNoYesModify the rightsusers have toprojects

ModifyRights

YesYesYesYesYesView task propertiesViewobjects

Profile task orRule task

NoYesYesYesYesView task historyand logs

View in-stance

NoYesYesYesYesSchedule taskSchedule

NoNoNoNoYesChange the sched-ule of task

Reschedule

NoYesYesYesYesDelete taskDeleteobjects

NoNoNoNoYesModify the rightsusers have to tasks.

ModifyRights

Related Topics• User rights for Information Steward administrative tasks

4.4.2.2 Group rights for connections

SAP BusinessObjects Information Steward provides pre-defined Data Insight user groups that havespecific rights on connections, as the following table shows. You can add users to these groups tocontrol their rights on connections.

2011-04-0643


On the "Data Insight" tab of Information Steward:• A connection is visible in the "Browse Metadata" window if a user has the right to view a connection.• Tables and Views are visible if the user has the View right on the connection.

Table 4-3: Rights for Data Insight Connections on Information Steward


DescriptionRight Data In-sight Us-er





YesYesYesYesYesView connections and ta-bles, browse metadata inthe connection

View ob-jects

YesYesYesYesYesView external data in theconnection

ViewData

YesYesYesYesYesView profile sample dataand sample data that failedrules

ViewSampleData

YesYesYesYesYesExport viewed data, profilesample data, and sampledata that failed rules

ExportData

NoYesYesYesYesCreate profile tasks and ruletasks

Pro-file/Rulepermis-sion

Note:

• Rights to a Data Insight connection are granted to users or groups when the Data Insight Admnistratoradds them to the "Principals" list for the connection. For more information, see Adding users anduser groups to Information Steward groups.

• The Administrator and the Data Insight Administrator can create, edit, and delete connections in theCMC. See Group rights for Data Insight folders and objects in the CMC.

• For a database connection, the Database Administrator must grant the Data Insight user access tothe tables.

• For a file connection, the users that run the following services must have permissions on the directorywhere the file resides:• Information Steward Web Application Server (for example, Tomcat)• Data Services service• Server Intelligence Agent that runs EIMAdaptiveProcessingServer and ISJobServer

2011-04-0644


Related Topics• User rights in Data Insight• Data Insight pre-defined user groups• Assigning users to specific Data Insight objects

4.4.2.3 Group rights for projects

Each pre-defined Data Insight user group provides specific rights on projects on Information Steward,as the following table shows.

Table 4-4: Rights for Data Insight Projects on Information Steward


DescriptionRight Data In-sight User

Data In-sight An-alyst

Data In-sight RuleApprover

Data InsightScorecard Man-ager

Data Insight Ad-ministrator

YesYesYesYesYes

• View project• View profile results• View rule results• View rules• View scorecard re-

sult

View ob-jects

NoYesYesYesYes

• Add and remove ta-bles and files inproject

• Add, edit, and re-move views

Edit ob-jects

NoYesYesYesYes• Create profile tasks• Create rule tasks• Copy views

Add ob-jects

NoYesYesYesYes• Create, edit, and re-

move rules• Bind rules

Managerule

NoYesYesYesYes• Import rules• Import viewsImport

2011-04-0645








NoNoNoYesYesAdd, edit, and removeKey Data Domains

Managescore-card

NoNoYesNoYesApprove or reject ruleson Information Steward

Approverule

On the "Data Insight" tab of Information Steward:• A project is visible if a user has the right to view a project.• The Add Tables and Remove buttons are enabled in the Workspace if a user has the right to edit

a project.• The Bind and Unbind buttons are enabled on the "Rule" tab if a user has the right to manage rules.• The Profile and Calculate Score buttons are enabled in the Workspace if a user has the right to

add objects to the project.

Note:Only the Administrator and Data Insight Administrator can create, edit, and delete projects in the CMC.See Group rights for Data Insight folders and objects in the CMC.

4.4.2.4 User rights for views

The rights each user has on a view is inherited from the rights the user has on the connections thatcomprise the view.

For example, suppose View1 is comprised of the following connections and tables:• ConnectionA, Table1• ConnectionB, Table2

Suppose User1 has the Edit right on ConnectionA but not on ConnectionB. Therefore, User1 cannotedit View1 because the denied Edit right is inherited from ConnectionB.

Similarly, if User2 has the Edit right on ConnectionA and ConnectionB, then User2 can edit View1.

This inheritance applies to all of the rights on views, as the following table shows.

2011-04-0646


Table 4-5: Rights for Data Insight Views on Information Steward

Required inherited rightDescriptionRight

View objects right on all source connec-tions

The view name and columns are visiblein Workspace Home window.

View ob-jects

View Data right on all source connectionsLook at the source data in each table orfile that comprise a viewView Data

View Sample Data right on all sourceconnectionss

View profile sample data and sample datathat failed rules

View Sam-ple Data

Profile/Rule right on all source connectionsCreate profile tasks and rule tasksProfile/Rulepermission

Export Data right on all source connec-tions

Export viewed data, profile sample data,and sample data that failed rulesExport Data

Note:The following actions require rights on the project:• To add, edit, or remove views, a user must have the Edit objects right on the project.• To copy a view, a user must have the Add objects right on the project.

4.4.2.5 Group rights for tasks

Each pre-defined Data Insight user group provides specific rights on profile tasks and rule tasks inInformation Steward, as the following table shows.

Table 4-6: Rights for Data Insight Tasks on Information Steward







YesYesYesYesYesView the task in the"Task" tab of theWorkspace

View ob-jects

NoYesYesYesYes• Edit profile task• Edit rule task or

score calculator taskEdit ob-jects

2011-04-0647








NoYesYesYesYesDelete profile or ruletask

Deleteobjects

NoYesYesYesYes• Run profile task• Run rule task

Schedule

Related Topics• Group rights for Data Insight folders and objects in the CMC

4.4.3 Customizing rights on Data Insight objects

To facilitate user managment, assign users to a pre-defined Information Steward user group. By default,Information Steward assigns all pre-defined user groups to all Data Insight connections and projects.However, you might want to limit a user's access such as the following:• Only view and profile data in a subset of connections• Only create rules on a subset of projects• Only create scorecard and approve rules on a subset of projects• Restrict project access• Restrict access to Data Insight

To limit access, take one of the following actions:• Add the user or group to only a subset of connections. In addition, create projects for specific business

areas, such as HR or Sales, and assign only certain users to access these projects to create profiletasks and rule tasks.

• Deny a right from an existing user group for a specific connection and specific project.

Related Topics• Assigning users to specific Data Insight objects• Denying user rights to specific Data Insight objects• Data Insight pre-defined user groups

2011-04-0648


4.4.3.1 Denying user rights to specific Data Insight objects

By default, the pre-defined Data Insight user groups are added to the access list of connections andprojects when you create them. However, you might want to deny one or a small subset of users accessto a specific Data Insight connection and project.

To allow a user or group to access all but one specific Data Insight connection and project:1. Log on to the Central Management Console (CMC) with a user name that is a member of either the

Administrator group or the Data Insight Administrator group.2. Add the user name to a pre-defined Data Insight group because the user would still have access to

most connections and projects. For details, see Adding users and user groups to Information Stewardgroups

3. At the CMC home page, click Information Steward.4. Select the object type.

• To deny rights to a connection:• Select the Connections node in the Tree panel.• Select the connection name in the right panel.

• To deny rights to a project::• Expand the Data Insight node, and expand the Projects node in the Tree panel.• Select the project name in the Tree panel.

• To deny rights to a profile or rule task:• Expand the Data Insight node, and expand the Projects node in the Tree panel.• Select the project name in the Tree panel.• Select the task name in the right panel.

5. Click Manage > Security > User Security.6. On the "User Security" page, click Add Principals.7. In the list of "Available users/groups", select the name of each user or group that you want to deny

rights to this connection or project, and click the > button to move the names to the "Selectedusers/groups" list.

Note:To select multiple names, hold down the Ctrl key when you click each name.

8. Click Add and Assign Security.9. Click the "Advanced" tab.10. Click the Add/Remove Rights link.11. To deny rights to this connection:

a. Expand the "Application" node and select "Data Insight Connection".b. Click the Denied column for each right that you want to deny this user or group.

2011-04-0649


For example, to deny the right to view and profile the data in this connection, click the Deny columnfor the following "Specific Rights for Data Insight Connection":• Profile/Rule permsiion• View Data• View Sample Data

12. To deny project rights:a. Expand the "Application" node and select "Data Insight Project".b. Click the Denied column for each right that you want to deny this user or group.For example, to deny the right to create scorecard and approve rules in this project, click the Deniedcolumn for the following "Specific Rights for Data Insight Connection":• Approve Rule• Manage Rule

13. To deny profile or rule task rights:a. Expand the "Application" node and select "Information Steward Profiler Task".b. Click the Override General Global column and the Denied column for each right that you want

to deny this user or group.For example, to deny the right to schedule a profile task or rule task, click the Override GeneralGlobal column and the Denied column for the following "General Rights for Data Insight ProfilerTask":• Rechedule instances that the user owns• Schedule document to run• View document instances

14. Click OK and verify that the list under "Right Name" does not display the rights you denied.15. Click name of the principal you just added, click View Security and verify that the list of rights that

you denied has the red icon in the "Status" column.16. Click OK and close the "User Security" window.

Related Topics• Data Insight pre-defined user groups

4.4.3.2 Assigning users to specific Data Insight objects

You might want to limit a user's or group's access to only specific Data Insight connections, projects,and tasks. In this case, you would add the user or group to the list of principals for each specific DataInsight object (instead of adding to a pre-defined Data Insight user group).

Note:You must assign the user to both the connection and the project to be able to add tables or files, createprofile tasks, and create rules.

2011-04-0650


To add a user or group to a specific Data Insight connection and project:1. Log on to the Central Management Console (CMC) with a user name that is a member of either the

Administrator group or the Data Insight Administrator group.2. At the CMC home page, click Information Steward.3. Select the object type.

• For a connection:a. Select the Connections node in the Tree panel .b. Select the connection name in the right panel.

• For a project:a. Expand the Data Insight node, and expand the Projects node in the Tree panel.b. Select the project name in the Tree panel.

• For a profile task or rule task:a. Expand the Data Insight node, and expand Projects node in the Tree panel.b. Select the task name in the right panel.

4. Click Manage > Security > User Security.5. On the "User Security" page, click Add Principals.6. In the list of "Available users/groups":

a. Select the name of each user or group that you want to authorize to this connection or projector task.


b. Click the > button to move the names to the "Selected users/groups" list.

7. Click Add and Assign Security.8. Click the "Advanced" tab.9. Click the Add/Remove Rights link.10. To assign connection rights:

a. Expand the "Application" node and select "Data Insight Connection".b. Click the Granted column for each right that you want this user or group to have.For example, to grant the right to view and profile the data in this connection, click the Grantedcolumn for the following "Specific Rights for Data Insight Connection":• Profile/Rule permission• View Data• View Sample Data

11. To assign project rights:a. Expand the "Application" node and select "Data Insight Project".b. Click the Granted column for each right that you want this user or group to have.For example, to grant the right to create scorecard and approve rules in this project, click theGrantedcolumn for the following "Specific Rights for Data Insight Connection":• Approve Rule• Manage Rule

2011-04-0651


12. To assign profile or rule task rights:a. Expand the "Application" node and select "Data Insight Profiler Task".b. Click the Override General Global column and the Granted (green check mark icon) column

for each right that you want this user or group to have.For example, to grant the right to schedule a profile task or rule task, click the Override GeneralGlobal column and the Granted column for the following "General Rights for Data Insight ProfilerTask":• Reschedule instances that the user owns• Schedule document to run• View document instances

13. Click OK and verify that the list under "Right Name" displays the rights you just added.14. Click OK and verify that the list of principals includes the name or names you just added.15. Close the "User Security" window.

Related Topics• Data Insight pre-defined user groups

4.4.3.3 Restricting rights of a user group to one project

Whenever a project is created, all pre-defined Data Insight user groups are automatically added to itsprincipal list. This feature facilitates user rights management when you want the same user or samegroup of users to have rights on all projects.

You might want to limit rights of a subset of users to only one project. For example, you might want tolimit the Manage Scorecards right on the Human Resources project to only User A, and you want onlyUser B to have the Manage Scorecards right on the Finance project.

To restrict the Manage Scorecards right to a specific user for each project:1. Create User A and User B. For details, see Creating users for Information Steward .2. Add User A and User B to the Data Insight Analyst user group. For details, see Adding users and

user groups to Information Steward groups.This Data Insight Analyst user group has all of the rights of the Data Insight Scorecard Manageruser group except the Manage Scorecard right, which you will grant to specific users within a projectin subsequent steps.

3. Create the Human Resources project and the Finance project. For details, see Creating a project.4. To grant User A the Manage Scorecard right on the Human Resources project:

a. Log on to the Central Management Console (CMC) with a user name that is a member of eitherthe Administrator group or the Data Insight Administrator group.

b. At the CMC home page, click Information Steward, expand the Data Insight node, and expandthe Projects node in the Tree panel.

c. Select the Human Resources project and click Manage > Security > User Security.

2011-04-0652


d. On the "User Security" page, click Add Principals.e. In the list of "Available users/groups", select User A and click the > button to move the names to

the "Selected users/groups" list.f. Click Add and Assign Security.g. Click the Advanced tab.h. Click the Add/Remove Rights link.i. Expand the "Application" node and click "Information Steward Project".j. Click the Granted column for the "Manage Scorecards" right under "Specific Rights for Data

Insight Connection".k. Click OK and verify that the list under "Right Name" displays the "Manage Scorecards" right.l. Click OK and close the "User Security" window.

5. Repeat steps 3a through 3j in the Finance project for User B.

Related Topics• Creating users for Information Steward• Adding users and user groups to Information Steward groups• Denying user rights to specific Data Insight objects

4.5 User rights in Metadata Management

The Metadata Mangement module of SAP BusinessObjects Information Steward contains the followingobjects that have object-specific rights that allow various actions on them.• Metadata Management application through which users can view relationships (such as Same As,

Impact, and Lineage) between integrator sources.• Integrator Sources through which users collect metadata.• Integrator Source Groups to subset the metadata when viewing relationships.• Metapedia through which users define terms related to their business data and organize the terms

into categories.

The CMS manages security information, such as user accounts, group memberships, and object rightsthat define user and group privileges. When a user attempts an action on a Metadata Managementobject, the CMS authorizes the action only after it verifies that the user's account or group membershiphas sufficient privileges.

Related Topics• Metadata Management pre-defined user groups• Group rights for Metadata Management objects in Information Steward• Group rights for Metadata Management folders and objects• Assigning users to specific Metadata Management objects• Managing users in Information Steward

2011-04-0653


4.5.1 Metadata Management pre-defined user groups

SAP BusinessObjects Information Steward provides the following Metadata Management user groupsto enable you to change the rights for multiple users in one place (a group) instead of modifying therights for each user account individually.

Table 4-7: Metadata Management pre-defined user groups

DescriptionPre-defined UserGroup

Users that can only view metadata in the Metadata Management tab of InformationSteward.

Metadata ManagementUser

Users that have all the rights of a Metadata Management User, plus the followingrights:• Create and edit annotations• Create custom attributes and edit values of custom attributes• Define Metapedia categories and terms

Metadata ManagementData Steward

Users that have all the rights of a Metadata Management Data Steward, plus thefollowing rights:• Create, edit, and delete Metadata Management integrator sources and source

groups• Run and schedule Metadata Integrators.• Configure, edit, delete, schedule, view history of Information Steward utilities

Metadata ManagementAdministrator

Related Topics• Information Steward pre-defined users and groups

4.5.2 Type-specific rights for Metadata Management objects

Type-specific rights affect only specific object types, such as integrator sources or Metapedia objects.The following topics describe type-specific rights for each Information Steward object in the CMC andSAP BusinessObjects Information Steward.

Related Topics• Group rights for Metadata Management folders and objects

2011-04-0654


• Group rights for Metadata Management objects in Information Steward

4.5.2.1 Group rights for Metadata Management folders and objects

Each pre-defined Metadata Management user group provides specific rights on the folders and objectsin the Central Management Console (CMC), as the following table shows.

Table 4-8: Rights for Metadata Management folders in the CMC



CMC Folder or Ob-ject

MetadataManage-ment Us-er

Metadata Man-agement DataSteward

Metadata Man-agement Admin-istrator

YesYesYesView Metadata Manage-ment folder

View ob-jects

Metadata Manage-ment folder NoNoYesChange limits for integra-

tor source runsEdit ob-jects

NoNoYesManage user security forMetadata Management

ModifyRights

YesYesYesView integrator sources,their run history, theirlogs, and so on.

View ob-jects

Integrator Sourcefolder NoNoYesConfigure new integrator

sources

Add ob-jects tothe folder

NoNoYesModify the rights usershave to integratorsources

ModifyRights

2011-04-0655








NoNoYesView history of metadataintegrator runs

View In-stance

Integrator Sources

NoNoYesCreate integrator sourceconfigurations


NoNoYesEdit the properties of inte-grator sources

Edit ob-jects

NoNoYes

• Delete integratorsources

• Delete integratorsource instances

• Delete the integratorsource schedule

Deleteobjects

NoNoYesSchedule and set run-time parameters for inte-grator source

Schedule

NoNoYesChange the schedule orrun-time parameters forintegrator source

Reschedule

NoNoYesModify the rights usershave to integratorsources.

ModifyRights

NoNoYesView Source Groups andaccess properties

View ob-jects

Source Groups

NoNoYesCreate integrator sourcegroups


NoNoYesEdit integrator sourcegroups

Edit ob-jects

NoNoYesDelete integrator sourcegroups

Deleteobjects

NoNoYesModify the rights usershave to source groups

ModifyRights

2011-04-0656








NoYesYesView terms and cate-gories on InformationSteward

View ob-jectsMetapedia Folder

4.5.2.2 Group rights for Metadata Management objects in Information Steward

Each pre-defined Metadata Management user group provides specific rights on objects in InformationSteward, as the following table shows.

2011-04-0657


Table 4-9: Rights for Metadata Management objects in Information Steward



InformationSteward tab

MetadataManagementUser

MetadataManagementData Steward

MetadataManagementAdministrator

YesYesYes

• View all of the metadata ob-jects and their relationships

• View the custom attributesand values

• View the Preferences page• Search all metadata sources• View Metadata Management

lineage from View Lineageoption on the "Documents "tab of BI Launch Pad.

Viewobjects

MetadataManagementtab

NoYesYes

• Update Preferences page• Edit custom attributes and

display order• Edit custom attribute values• Edit annotations• Edit user-defined relation-

ships between objects

Edit ob-jects

NoYesYes

• Create new custom attribute• Associate custom attribute

to an object type• Update Preferences page• Create custom attributes and

display order• Create custom attribute val-

ues• Create annotations• Create user-defined relation-


Addob-jects

NoYesYes

• Delete custom attribute• Create annotations• Delete user-defined relation-


Deleteobjects

2011-04-0658




InformationSteward tab

MetadataManagementUser

MetadataManagementData Steward

MetadataManagementAdministrator

NoYesYes

• View "Metapedia" tab• View Categories• View terms• Export to Excel

View

Metapedia tab

NoYesYes

• Create Category• Create Term• Import to Excel• Edit Category• Edit Term (including Ap-

proval)• Add Terms to Categories• Relate Terms• Associate objects to a Term• Delete Related Terms• Delete Associated Objects• Delete associated Terms• Delete Category• Delete Term

Addob-jects tothefolder,

Edit ob-jects,

Deleteobjects

4.5.3 Assigning users to specific Metadata Management objects

By default, the pre-defined Metadata Management user groups are added to the access list of integratorsources and source groups when you create them. You might want to allow only certain users toconfigure integrator sources, define source groups, or define Metapedia categories and terms. In thesecases, you would add the user or group to the specific Metadata Management object's access list(instead of adding to a pre-defined Metadata Management user group).1. Log on to the Central Management Console (CMC) with a user name that is a member of either the

Administrator group or the Metadata Management Administrator group.2. At the CMC home page, click Information Steward.3. Expand the Metadata Management node in the Tree panel.4. Select the object type.

• For an integrator source:a. Select the Integrator Sources node in the Tree panel.

2011-04-0659


b. Select the integrator source name in the right panel.• For Metapedia categories and terms:

a. Select the Metapedia node in the Tree panel.• For a source group:

a. Expand the Source Groups node in the Tree panel.b. Select the source group name in the right panel.

5. Click Manage > Security > User Security.6. On the "User Security" page, click Add Principals.7. In the list of "Available users/groups":

a. Select the name of each user or group that you want to authorize to this inegrator source orMetapedia or source group.


b. Click the > button to move the names to the "Selected users/groups" list.

8. Click Add and Assign Security.9. Click the "Advanced" tab.10. Click the Add/Remove Rights link.11. To assign integrator source rights:

a. Expand the "Application" node and select "Metadata Management Integrator configuration".b. Click the Override General Global column and the Granted (green check mark icon) column

for each right that you want this user or group to have.For example, to grant the right to schedule and view integrator instances, click the Override GeneralGlobal column and theGranted column for the following "General Rights for Metadata ManagementIntegrator configuration ":• Pause and resume document instances• Schedule document to run• View document instances

12. To assign Metapedia rights:a. Expand the "Content" node and select "Folder".b. Click the Granted column for each right that you want this user or group to have.For example, to grant the right to create, edit, and delete Metapedia categories and terms, click theGranted column for the following "General Rights for Folder":• Add objects to folder• Delete objects• Edit objects• View objects

13. To assign source group rights:a. Expand the "Application" node and select "Metadata Management Source Group".b. Click the Override General Global column and the Granted (green check mark icon) column

for each right that you want this user or group to have.

2011-04-0660


For example, to grant the right to schedule and view integrator instances, click the Override GeneralGlobal column and theGranted column for the following "General Rights for Metadata ManagementIntegrator configuration ":• Pause and resume document instances• Schedule document to run• View document instances

14. Click OK and verify that the list under "Right Name" displays the rights you just added.15. Click OK and verify that the list of principals includes the name or names you just added.16. Close the "User Security" window.

4.6 User rights in Cleansing Package Builder

The Cleansing Package Builder module of SAP BusinessObjects Information Steward contains thefollowing objects to which you control access.• Private cleansing packages: Private cleansing packages are viewed or edited by the user who owns

them and are listed under My Cleansing Packages. Private cleansing packages include those createdby using the New Cleansing Package Wizard or by importing a published cleansing package.

• Published cleansing packages: Published cleansing packages are cleansing packages includedwith SAP BusinessObjects Information Steward or cleansing packages which a data steward createdand then published. Published cleansing packages are available to all users and can be used in anSAP BusinessObjects Data Services Data Cleanse transform or imported and used as the basis fora new cleansing package.

Related Topics• Group rights for cleansing packages• Managing users in Information Steward

4.6.1 Group rights for cleansing packages

The Administrator and the pre-defined Cleansing Package Builder User groups can perform specificactions on cleansing packages, as the following table shows.

2011-04-0661


Table 4-10: Rights for Cleansing Package Builder

Pre-defined User GroupsSoftware in whichthis action is per-formed

DescriptionRights CleansingPackageBuilder User

Administrator

YesYesCleansing PackageBuilderCreate cleansing package.Create

YesYesCleansing PackageBuilder

Change, delete, and re-name your own privatecleansing packages.

Edit


Publish cleansing pack-ages.Publish


Browse your own privatecleansing packages and allpublished cleansing pack-ages.

View

NoYesCentral ManagementConsoleLog in to the CMC.Access the

CMC

NoYesCentral ManagementConsole

Start and stop the Cleans-ing Package Builder Ser-vice.

Control Cleans-ing PackageBuilder server


Create users and addusers to groups.

Set up usersand groups


Reassign ownership of pri-vate cleansing packages.Reassign


Delete private and pub-lished cleansing packages.Delete


See all private and pub-lished cleansing packages.View all


Change description, owner,and state of cleansingpackages.

Edit

4.7 User rights for Information Steward administrative tasks

2011-04-0662


The following table describes the Information Steward actions in the "Applications" area of the CMC.To perform any of these Information Steward actions, a user must belong to one fo the following groups:• Administrator• Data Insight Administrator• Metadata Management Administrator

Table 4-11: Actions for Information Steward in the CMC "Applications" area

DescriptionActionItem

View list of job servers in the InformationSteward job server groupViewView Data Services Job Server

View history of utility runsView instance

Information Steward Utilities

Create utility instanceCreate

Edit run-time parameters for utilityEdit

Delete utility instanceDelete

Define schedule utilitySchedule

Change the schedule of utilityReschedule

Change configuration settings for Data In-sight Profiling, Rules, or PerformanceEditInformation Steward Settings

Update repository passwordEditInformation Steward repository

Related Topics• Job server group• Utilities overview• Configuration settings• Viewing and editing repository information• Group rights for Data Insight folders and objects in the CMC• Group rights for Metadata Management folders and objects

4.7.1 Viewing and editing repository information

You might want to view or edit the SAP BusinessObjects Information Steward repository connectioninformation for situations such as the following:• View connection information, such as database type and server name.

2011-04-0663


• Change the database user and password for the repository.• If the database type of the repository is an Oracle RAC database, change the connection string to

add another server or tune parameters for failover.

To view or edit the Information Steward repository:1. Log on to the Central Management Console (CMC) with a user name that is a member of either the

Administrator group.2. Select Applications from the navigation list at the top of the CMC Home page.3. In the "Applications Name" list, select Information Steward.4. Click Action > Configure Repository.

The connection information for the Information Steward repository was defined at installation time.a. For most of the database types, you can only view the connection information here.b. If the database type is Oracle RAC, you can modify the connection string here if you want to add

another server or tune parameters for failover.

5. You can change the user name and password for the Information Steward repository.

Caution:You must have the appropriate credentials to access the Information Steward database. After youchange the user name and password, you must restart the Web Application Server and CMS.

2011-04-0664


Data Insight Administration

5.1 Administration overview for Data Insight

Each deployment of SAP BusinessObjects Information Steward supports multiple users in one or moreData Insight projects to assess and monitor the quality of data from various sources.• A project is a collaborative workspace for data stewards and data analysts to assess and monitor

the data quality of a specific domain and for a specific purpose (such as customer quality assessment,sales system migration, and master data quality monitoring).

• A connection defines the parameters for Information Steward to access a data source. A data sourcecan be a relational database, application, or file.

Data Insight users in a project can perform tasks such as browse tables and files in connections, addtables of interest to the project, profile the data and execute rules to measure the data quality, createdata quality scorecards and monitor data quality. For more details, see the "Data Insight" section in theUser Guide.

Before Data Insight users can perform the above tasks, administrators must do the following tasks onthe Central Management Console (CMC) of SAP BusinessObjects Business Intelligence Platform:• Define connections to data sources• Create projects• Add user names to pre-defined Data Insight user groups to access connections and projects

Tip:Users of a project should be given access to the same set of connections so that they can collaborateon the same set data with a project.

• Optionally, define connections to save all data that failed rules for rule tasks. Each rule task can usea different failed data connection.

After a Data Insight user creates tasks, the Data Insight Administrator can do the following tasks:• Create schedules to run the profile task and rule task at regular intervals.• Modify the default schedule to run utilities if the frequency of the profile and rule tasks warrant it.• Modify application-level settings to change the default configuration for Data Insight.

Tip:It is recommended that the Data Insight Administrator be someone who is familiar with the CMC.

Related Topics• Data Insight Connections

2011-04-0665


• Data Insight projects• User rights in Data Insight• Scheduling a utility• Configuration settings

5.2 Data Insight Connections

Data Insight provides you the capability to define the following types of connections:• For data profiling

You can configure connections to the following types of data sources to collect profile attributes thatcan help you determine the data quality and structure:• Databases such as Microsoft SQL Server, IBM DB2, Oracle, MySQL, Informix IDS, Sybase ASE,

and ODBC• Applications such as SAP Business Suite and SAP NetWeaver Business Warehouse• Text files

• For failed data

You can configure connections to databases to store all data that fail your quality validation rules.Each rule task can use a different failed data connection. For more information, see “Viewing failedrule data” in the User Guide.

Note:For a complete list of supported databases, applications, and their versions, see the Platform AvailabilityMatrix available at http://service.sap.com/PAM.

Related Topics• Defining a Data Insight connection to a database• Defining a Data Insight connection to an application• Defining a Data Insight connection to a file• Displaying and editing Data Insight connection parameters

5.2.1 Defining a Data Insight connection to a database

You define a Data Insight connection to a database for any of the following purposes:• Contains data that you want to profile, run validation rules on, and calculate quality scorecords to

determine the quality and structure of the data.

2011-04-0666



• Store the data that failed quality validation rules.

To create a Data Insight connection to a database source:1. Ensure that you have the proper privileges on the source database.

• If you will profile and run validation rules on the data, you must have privileges to read themetadata and data from the source tables.

• If you will store failed data, you must have privileges to create, modify, and delete tables, and tocreate stored procedures.

2. Log on to the Central Management Console (CMC) with a user name that belongs to the Data InsightAdministrator group or that has the Create right on Connections in Information Steward.

3. At the CMC home page, click Information Steward.4. Select the Connections node in the Tree panel.5. Click Manage > New > Data Insight Connection.6. On the "Create Connection" page, enter the following information.

DescriptionOption

Name that you want to use for this Data Insight connection.• Maximum length is 64 characters• Can be multi-byte• Case insensitive• Can include underscores and spaces• Cannot include other special characters : ?!@#$%^&*()-

+={}[]:";'/\|.,`~You cannot change the name after you save the connection.

Connection Name

(Optional) Text to describe this profile source.Description

7. In the Connection Type drop-down list, select the Database connection value.8. In the Purpose of connection drop-down list, select one of the following options:

• For data profiling if you want to profile the data in this connection• For failed data if you want to use this connection to store all the data that fail specific quality

validation rules.

9. In the Database Type drop-down list, select the database that contains the data that you want toprofile or that will store the data that fail validation rules.

10. Enter the relevant connection information for the database type.11. If you want to verify that Information Steward can connect successfully before you save this profile

connection, click Test connection.12. Click Save.

Note:After you save the connection, you cannot change its name, connection type, purpose and connectionparameters which uniquely identify a database..

The newly configured connection appears in the list on the right of the "Information Steward" page.

2011-04-0667


After you create a connection, you must authorize users to it so that they can perform tasks such asview the data, run profile tasks and run validation rules on the data.

Related Topics• User rights in Data Insight• SAP In-Memory Database connection parameters• IBM DB2 connection parameters• Informix database connection parameters• Microsoft SQL Server connection parameters• MySQL database connection parameters• Netezza connection parameters• ODBC connection parameteres• Oracle database connection parameters• Sybase ASE connection parameters• Sybase IQ connection parameters• Teradata connection parameters

5.2.1.1 SAP In-Memory Database connection parameters

DescriptionPossible valuesSAP In-Memory Databaseoption

Select the version of your SAP In-MemoryDatabase client. This is the version of SAP In-Memory Database that this Data Insight connec-tion accesses.

SAP In-Memory Database<version number>

Database version

Select or type the Data Source Name defined inthe ODBC Administrator for connecting to yourdatabase.

Refer to the requirements ofyour database.Data Source

Enter the user name of the account through whichInformation Steward accesses the database.

The value is specific to thedatabase server and lan-guage.

User name

Enter the user's password.The value is specific to thedatabase server and lan-guage.

Password

Language of the data in the database.default

Select the correct languagefor your database server.

Language

2011-04-0668


DescriptionPossible valuesSAP In-Memory Databaseoption

Code page of the database client.

See "Supported locales andencodings" in the SAP Busi-nessObjects Data ServicesReference Guide.

Client Code page

Code page of the database server.


Server code page

5.2.1.2 HP Neoview connection parameters

DescriptionValuesODBC option

Select the version of your HP Neoview client. Thisis the version of HP Neoview that this profileconnection accesses.

HP Neoview <versionnumber>

Database version

Select or type the Data Source Name defined inthe ODBC Administrator for connecting to thedatabase you want to profile.

Refer to the requirements ofyour database.Data Source Name

Enter the user name of the account through whichthe software accesses the database.

Note:If you use the Neoview utility Nvtencrsrv for stor-ing the encrypted words in the security file whenusing Neoview Transporter, enter the encrypteduser name


User name

Enter the user's password.

Note:If you use the Neoview utility Nvtencrsrv for stor-ing the encrypted words in the security file whenusing Neoview Transporter, enter the encryptedpassword.


Password

2011-04-0669





Language


See "Supported locales andencodings" in the SAP Busi-nessObjects Data ServicesReference Guide

Client Code page



Server code page

5.2.1.3 IBM DB2 connection parameters

DescriptionPossible valuesDB2 option

Select the version of your DB2 client. This is theversion of DB2 that this Data Insight connectionaccesses.

DB2 UDB <versionnumber>

Database version

Type the data source name defined in DB2 forconnecting to your database.

Refer to the requirements ofyour databaseData Source Name

Enter the user name of the account through whichSAP Information Steward accesses the database.


User name


Password



Language



Client Code page

2011-04-0670


DescriptionPossible valuesDB2 option



Server code page

5.2.1.4 Informix database connection parameters

DescriptionPossible valuesInformix option

Select the version of your Informix client. Thisis the version of Informix that this profile connec-tion accesses.

Informix IDS <versionnumber>

Database version

Type the Data Source Name defined in theODBC.


Enter the user name of the account throughwhich SAP Information Steward accesses thedatabase.

The value is specific to thedatabase server and language.User name

Enter the user's password.The value is specific to thedatabase server and language.Password


Select the correct language foryour database server.

Language


See "Supported locales andencodings" in the SAP Busines-sObjects Data Services Refer-ence Guide

Client Code page



Server code page

2011-04-0671


5.2.1.5 Microsoft SQL Server connection parameters

To use Microsoft SQL Server as a profile source when SAP BusinessObjects Information Steward isrunning on a UNIX platform, you must use an ODBC driver, such as the DataDirect ODBC driver.

For more information about how to obtain the driver, see the Platforms Availability Report (PAR) availablein the SAP BusinessObjects Support > Documentation > Supported Platforms section of the SAPService Marketplace: http://service.sap.com/bosap-support.

DescriptionPossible valuesMicrosoft SQL Serveroption

Select the version of your SQL Server client. This isthe version of SQL Server that this profile source ac-cesses.

Microsoft SQL Server<version number>

Database version

Enter the name of machine where the SQL Server in-stance is located.

Computer name, fullyqualified domain name, orIP address

Server Name

Enter the name of the database to which the profilerconnects.

Refer to the requirementsof your database.Database Name

Enter the user name of the account through which In-formation Steward accesses the database.

Note:Information Steward supports both Windows authenti-cation and Microsoft SQL Server authentication.


User Name


Password

Language of the data in the database.

default

Select the correct lan-guage for your databaseserver.

Language


See "Supported localesand encodings" in the SAPBusinessObjects DataServices Reference Guide.

Client Code page

2011-04-0672


http://service.sap.com/bosap-support

DescriptionPossible valuesMicrosoft SQL Serveroption


See "Supported localesand encodings" in the SAPBusinessObjects DataServices Reference Guide.

Server code page

5.2.1.6 MySQL database connection parameters

DescriptionValuesMySQL option

Select the version of your MySQL client. This isthe version of MySQL that this profile connectionaccesses.

MySQL <version number>Database version





User name


Password



Language



Client Code page



Server code page

2011-04-0673


5.2.1.7 Netezza connection parameters

DescriptionValuesNetezza option

Select the version of your Netezza client. This isthe version of Netezza that this profile connectionaccesses.

Netezza NPS <versionnumber>

Database version





User name


Password



Language


ee "Supported locales andencodings" in the SAP Busi-nessObjects Data ServicesReference Guide

Client Code page


ee "Supported locales andencodings" in the SAP Busi-nessObjects Data ServicesReference Guide

Server code page

5.2.1.8 ODBC connection parameteres

2011-04-0674





Enter information for any additional parametersthat the data source supports (parameters thatthe data source's ODBC driver and databasesupport). Use the format:

<parameter1=value1; parameter2=value2>

Alphanumeric characters andunderscores, or blankAdditional information



User name


Password



Language



Client Code page



Server code page

Table 5-10: Connection


Enter information for any additional parameters that the datasource supports (parameters that the data source's ODBCdriver and database support). Use the format:

<parameter1=value1; parameter2=value2>

Alphanumeric charactersand underscores, or blank

Additional connec-tion information

2011-04-0675


5.2.1.9 Oracle database connection parameters

DescriptionPossible valuesOracle option

Select the version of your Oracle client. This is theversion of Oracle that this profile conncection ac-cesses.

Oracle <versionnumber>

Database version

Enter an existing Oracle connection through whichthe software accesses sources defined in this profileconncection.

Refer to the requirementsof your database

Database Connectionname



User Name


Password



Language


See "Supported locales andencodings" in the SAPBusinessObjects Data Ser-vices Reference Guide.

Client Code page


See "Supported locales andencodings" in the SAPBusinessObjects Data Ser-vices Reference Guide.

Server code page

5.2.1.10 Sybase ASE connection parameters

2011-04-0676


DescriptionPossible valuesSybase ASE option

Select the version of your Sybase ASE client. Thisis the version of Sybase that this profile connectionaccesses.

Sybase ASE <versionnumber>

Database version

Enter the name of the computer where the SybaseASE instance is located.Computer nameServer Name

Enter the name of the database to which the profilerconnects.

Refer to the requirementsof your databaseDatabase Name



User name


Password


Select the correct languagefor your database server..

Language


See "Supported locales andencodings" in the SAPBusinessObjects Data Ser-vices Reference Guide

Client Code page


See "Supported locales andencodings" in the SAPBusinessObjects Data Ser-vices Reference Guide

Server code page

5.2.1.11 Sybase IQ connection parameters

DescriptionPossible valuesSybase IQ option

Select the version of your Sybase IQ client. Thisis the version of Sybase IQ that this datastoreaccesses.

Currently supported versionsDatabase version

2011-04-0677


DescriptionPossible valuesSybase IQ option

Select or type the Data Source Name definedin the ODBC Administrator for connecting toyour database.


Enter the user name of the account throughwhich the software accesses the database.

The value is specific to thedatabase server and language.User Name



Select the correct language foryour database server..

Language



Client Code page



Server code page

5.2.1.12 Teradata connection parameters

DescriptionPossible valuesTeradata option

Select the version of your Teradataclient. This is the version of Terada-ta that this datastore accesses.

Teradata <version number>Database version

Type the Data Source Name de-fined in the ODBC Administrator forconnecting to your database.

Refer to the requirements of yourdatabaseData Source Name

Enter the user name of the accountthrough which the software access-es the database.

The value is specific to thedatabase server and language.User Name


2011-04-0678


DescriptionPossible valuesTeradata option

Language of the data in thedatabase.

default

Select the correct language for yourdatabase server.

Language

Code page of the database client.See "Supported locales and encod-ings" in the SAP BusinessObjectsData Services Reference Guide

Client Code page

Code page of the database server.See "Supported locales and encod-ings" in the SAP BusinessObjectsData Services Reference Guide

Server code page

5.2.2 Defining a Data Insight connection to an application

You must define a connection to any application that contains data that you want to profile to determinethe quality and structure of the data.

To create a connection to an application system:1. Log on to the Central Management Console (CMC) with a user name that has the following

authorizations:• Authorization to read data on the source application system. For authorizations to SAP

Applications, see “SAP user authorizations” in the SAP BusinessObjects Data ServicesSupplement for SAP.

• Either belongs to the Data Insight Administrator group or has the Create right on theConnectionsnode .

2. At the CMC home page, click Information Steward.3. Select the Connections node in the navigation tree on the left.4. Click Manage > New > Data Insight connection.5. On the "Create Connection" page, enter the following information.

2011-04-0679


DescriptionOption

Name that you want to use for this Data Insight source.• Maximum length is 64 characters• Can be multi-byte• Case insensitive• Can include underscores and spaces• Cannot include other special characters : ?!@#$%^&*()-

+={}[]:";'/\|.,`~You cannot change the name after you save the connec-tion.

Connection Name

(Optional) Text to describe this Data Insight source.Description

6. In the Connection Type drop-down list, select the Application connection value.7. In the Application Type drop-down list, select one of the following applications that contains the

data you want to profile:• SAP Netweaver Business Warehouse• SAP ApplicationsFor the specific components that Information Steward can profile the data, see the Product AvailabilityMatrix available at http://service.sap.com/PAM.

8. Enter the relevant connection information for the application type.9. If you want to verify that Information Steward can connect successfully before you save this profile

connection, click Test connection.10. Click Save.

The newly configured connection appears in the list of Profile Connections on the right of the"Information Steward" page.

After you create a connection, you must authorize users to it so that they can perform tasks such asview the data, run profile tasks and run validation rules on the data

Related Topics• User rights in Data Insight• SAP Applications connection parameters• SAP NetWeaver Business Warehouse connection parameters

5.2.2.1 SAP NetWeaver Business Warehouse connection parameters

The SAP NetWeaver Business Warehouse connection has the same options as the SAP Applicaitonsconnection type.

2011-04-0680



Related Topics• SAP Applications connection parameters

5.2.2.2 SAP Applications connection parameters

To connect to SAP Applications, the Data Insight module of Information Steward uses the sameconnections as Data Services. For more information, see the SAP BusinessObjects Data ServicesSupplement for SAP.

DescriptionPossible valuesSAP Applications option

Name of the remote SAP application computer(host) to which the software connects.

Computer name, fully qualifieddomain name, or IP addressServer Name

The three-digit SAP client number. Default is 800.000-999Client Number

The two-digit SAP system number. Default is 00.00-99System Number

Enter the name of the account through which thesoftware accesses the SAP application server.

Alphanumeric characters andunderscoresUser Name

Enter the user's password.Alphanumeric characters, un-derscores, and punctuationPassword

Select the login language from the drop-down list.You can enter a customized SAP language in thisoption. For example, you can type S for Spanishor I for Italian.

E - English

G - German

F - French

J - Japanese

Application Language

See the section "Supported locales and encod-ings" in the SAP BusinessObjects Data ServicesReference Guide.

Code Page

Information Steward does not take advantage ofthis feature in release 4.0.Not applicableABAP execution option

Information Steward does not take advantage ofthis feature in release 4.0.

Dialog processing or background processing isdefined by the user type of the SAP user config-ured for the communication between InformationSteward and the SAP server.

Not applicableExecute in background(batch)

2011-04-0681



A directory on the SAP application server wherethe software can write intermediate files. This di-rectory also stores the transport file used by theFTP and shared-directory data transfer methods.

By default, the value in this field uses the valuethat was typed into the Application server field.For example, if the value sap01 was typed intothe Application server field, the value of Workingdirectory on SAP server becomes \\sap01\.

Directory pathWorking directory onSAP server

Information Steward does not take advantage ofthis feature in release 4.0.Not applicableGenerated ABAP direc-

tory

Information Steward does not take advantage ofthis feature in release 4.0.Not applicableSecurity Profile

The number of times the software tries to establisha connection with the SAP application server.

Defaults to 3.Positive integerNumber of connection

retries

The time delay in seconds between connectionretries.

Defaults to 10.Positive integerInterval between retries

(sec)

2011-04-0682



Define how to retrieve data from the SAP applica-tion server to the SAP BusinessObjects DataServices server:

None: Synchronous data transfer. If the SAP userused for the connection is of user type Dialog, theamount of data that can be transferred is boundto dialog process restrictions. Users of type Sys-tem/Communication can also perform syn-chronous Remote Function Call (RFC) datatransfers using the background processes andresources available.

Shared directory: Asynchronous processing.Data is written into a file and saved in a shareddirectory to which the SAP server and InformationSteward both have access. If you select this datatransfer method, the Application Shared Direc-tory appears.

FTP: Asynchronous processing. InformationSteward (through Data Services) obtains the datafrom an FTP folder. If you select this data transfermethod, the FTP options appear (Local directory,FTP relative path, and so forth).

For performance information, see Using SAP ap-plications as a source.

None

Shared directory

FTP

Data transfer method

If you selected the Shared directory data transfermethod, specify the SAP application server direc-tory that stores data extracted by SAP Busines-sObjects Data Services , and to which both DataServices and SAP application server have directaccess. After the extraction is completed, Informa-tion Steward picks up the file for further process-ing.

Directory pathApplication Shared Di-rectory

These options are visible if you selected the FTP data transfer method.FTP

If you selected the FTP data transfer method,select a client-side directory to which data fromthe SAP application server downloads.

Directory pathLocal directory

Indicate the path from the FTP root directory tothe SAP server's working directory. When youselect FTP, this directory is required.

Directory pathFTP relative path

2011-04-0683



Must be defined to use FTP.Computer (host) name, fullyqualified domain name, or IPaddress

FTP host name

Must be defined to use FTP.Alphanumeric characters andunderscoresFTP login user name

Enter the FTP password.Alphanumeric characters andunderscores, or blankFTP login password

5.2.3 Defining a Data Insight connection to a file

You must define a connection to a text file that contains data that you want to profile to determine thequality and structure of the data.

To create a Data Insight connection to a file source:1. Ensure that your file meets the following requirements:

• The users running the following services must have permission on the shared directory wherethe file resides:• Web Application Server (for example, Tomcat)• Data Services• Service Intelligence Agent

• The file must be located on a shared location that is accessible to the Data Services Job Serverand the View Data Server which are components of SAP BusinessObjects Data Services.

2. Go to the Information Steward area of the CMC.3. Click Manage > New > Connection.4. On the "Create Connection" page, enter the following information.

DescriptionOption

Name that you want to use for this data source.• Maximum length is 64 characters• Can be multi-byte• Case insensitive• Can include underscores and spaces• Cannot include other special characters : ?!@#$%^&*()-

+={}[]:";'/\|.,`~You cannot change the name after you save the connection.

Connection Name

2011-04-0684


DescriptionOption

(Optional) Text to describe this data source.Description

5. In the Connection Type drop-down list, select the File connection option.6. Enter the path for the file in Directory Path.7. Click Save.

The name of the newly configured connection appears in the list on the right pane of the "InformationSteward" page.

After you create a connection, you must authorize users to it so that they can perform tasks such asview the data, run profile tasks and run validation rules on the data.

Related Topics• User rights in Data Insight

5.2.4 Displaying and editing Data Insight connection parameters

Situations when you might want to view or change Data Insight connection parameters include:• You need to view the connection parameters on a development or test system so that you can

recreate the Data Insight connection when you move to a production system.• You have several source systems and you want to ensure that you are connecting to the appropraite

source.

To edit connection parameters of your Data Insight project:1. Ensure that you have Edit rights on the connection or you are a member of the Data Insight

Administrator group.2. Go to the Information Control Center area of the CMC.3. Expand the Data Insight node in the Tree panel, and select Connections.4. In the list of connections on the right, select the name of your profiling connection, click "Action" in

the top menu tool bar, and select Properties.5. Type your changes in the following fields:

• Description• Database version• User Name• Password• Language• Client Code Page• Server Code Page

2011-04-0685


6. If you want to verify that Information Steward can connect successfully before you save this DataInsight connection, click Test connection.

7. Click Save.The edited description appears in the list of projects on the right pane of the "Information Steward"page.

5.2.5 Deleting a Data Insight connection

The following table shows the Data insight objects that you can delete from the Central ManagementConsole (CMC).

For information about dependencies when deleting connections and projects on the Central ManagementConsole (CMC), see “Deleting a connection” and “Deleting a project” in the Administrator Guide.

Note:You cannot delete a connection if a table or file is being used in a project. You must remove the tableor file from all projects on Information Steward before you can delete the connection or project in theCMC.

Table 5-18: Delete object dependents and dependencies

Dependent objects that will alsobe deleted

Object dependencies that pre-vent deletion because they areused in another project

Data insight object to deletefrom CMC

• Profile Task InstancenoneProfile Task

• Table metadata

• Referenced projectYou must delete each table fromthe Workspace of each projectin Data Insight.

Connection

• Referenced project• Rule• View

Warning message appears, butyou can click OK to go aheadand delete all dependent ob-jects.

Project

1. Log on to the Central Management Console (CMC) with a user name that belongs to the Data InsightAdministrator group or that has the Create right on Connections in Information Steward.

2. At the CMC home page, click Information Steward.3. Click the Connections node in the Tree panel.4. From the list in the right pane, select the name of the connection and click Manage > Delete.5. To confirm that you want to delete this connection, click OK in the warning pop-up window.

2011-04-0686


6. If the following message appears, you must must delete each table from the "Workspace" of eachData Insight project listed in the message.The connection cannot be deleted because it is referenced by the following:Project: projectname

5.3 Data Insight projects

A project is a collaborative workspace for data stewards and data analysts to assess and monitor thedata quality of a specific domain and for a specific purpose (such as customer quality assessment,sales system migration, and master data quality monitoring).

5.3.1 Creating a project

Create a Data Insight project in the Central Management Console (CMC) to allow your users to definethe project's tasks to profile and validate data in SAP BusinessObjects Information Steward.1. Log on to the CMC with a user name that belongs to the Data Insight Administrator group or that

has the Create right on Projects in Information Steward.2. At the CMC home page, click Information Steward.

The "Information Steward" page opens with the Information Steward node selected in the Treepanel.

3. Expand the Data Insight node in the Tree panel, and select Projects.4. Click Manage > New > Data Insight Project.5. On the "New Profiling Project" window, enter the following information.

DescriptionOption

Name that you want to use for this profile project.• Maximum length is 64 characters• Can be multi-byte• Case insensitive• Can include underscores and spaces• Cannot include other special characters : ?!@#$%^&*()-

+={}[]:";'/\|.,`~You cannot change the name after you save the project.

Name

(Optional) Text to describe this profile project.Description

6. Click Save.

2011-04-0687


Note:After you save the project, you cannot change its name.

The new project appears in the list of projects on the right pane of the "Information Steward" page.

After you create a project, you must grant users rights to perform actions such as create profile andrule tasks, run these tasks, or create score cards.

Related Topics• User rights in Data Insight

5.3.2 Editing a project description

To edit a Data Insight project, you must have Edit rights on the project or be a member of the DataInsight Administrator group.

To edit the Description field of your profile project:1. Log on to the Central Management Console (CMC) with a user name that belongs to the Data Insight

Administrator group or that has the Edit right on Projects in Information Steward.2. At the CMC home page, click Information Steward.3. Expand the Data Insight node in the Tree panel, and select Projects.4. In the list of projects on the right, select the name of your profiling project and click Action > Prop

erties.5. Type the changes you want in the "Description" field.6. Click Save to see the edited description in the list of projects on the right pane of the "Information

Steward" page.

5.3.3 Deleting a project

To delete a Data Insight project:

1. Log on to the Central Management Console (CMC) with a user name that belongs to the Data InsightAdministrator group or that has the Create right on Projects in Information Steward.

2. At the CMC home page, click Information Steward.3. Expand the Data Insight node in the Tree panel, and select Projects.4. From the list in the right pane, select the name of the project and click Manage > Delete.5. To confirm that you want to delete this project, click OK in the warning pop-up window.

2011-04-0688


Caution:When you delete a project, you delete all the contents of the project which include unapproved rules,tasks, scorecards, profile results, sample data, views, and so forth.

5.4 Data Insight tasks

The Data Insight module of SAP BusinessObjects Information Steward provides you the capability tocreate the following types of tasks that you can run immediately or schedule on the CMC to run lateror recurringly:• Profile tasks to generate profile attributes about data tables and files• Rule tasks to execute rules bound to table columns to measure the data quality.

5.4.1 Scheduling a task

The Data Insight Administrator can schedule a profile or rule task for a given project in the CentralManagement Console (CMC). A Data Insight user must have already created the profile task or ruletask on Information Steward (see “Creating a profile task” or “Creating a rule task and setting an alert”in the User Guide).

You would schedule a profile task or rule task for reasons including the following:• Set up a recurring time to run a profile task or rule task.• Specify a specific time to run the profile task or rule task.

To define or modify a schedule for a Data Insight task:1. Log on to the CMC with a user name that belongs to the Data Insight Administrator group or that



3. In the Tree panel, expand the Data Insight node expand the Projects node.4. Select the name of your project in the Tree panel.5. Select the name of the task from the list on the right panel.6. Click Action > Schedule in the top menu tool bar.

The "Instance Title" pane appears on the right in the "Schedule" window.

7. If you do not want the default value for Instance Title, change the title to a value you want.8. To define when and how often to run the task:

2011-04-0689


a. Click Recurrence in the navigation tree in the left pane of the "Schedule" window.b. Select the frequency in the Run object drop-down list.c. Select the additional relevant values for the recurrence option.

For a list of the recurrence options and the additional values, see Recurrence options.d. Optionally, set the Number of retries to a value other than the default 0 and change the Retry

interval in seconds from the default value 1800..

9. If you want to trigger the execution of this utility when an event occurs, expand Events, and fill inthe appropriate information. For more information about Events , see the SAP BusinessObjectsBusiness Intelligence Platform Administrator Guide.

10. If you want to change the default values for the run-time paraemeters for the task, click theParameters node on the left. For parameter descriptions, see Common runtime parameters forInformation Steward.

11. Click Schedule.

Related Topics• Pausing and resuming a schedule

5.4.2 Recurrence options

When you schedule an integrator source or an SAP BusinessObjects Information Steward utility, youcan choose the frequency to run it in the Recurrence option. The following table describes eachrecurrence option and shows the additional relevant values that you must select for each recurrenceoption.

DescriptionRecurrence Option

The utility will run when you click Schedule .Now

The utility will run once only. Select the values for• Start Date/Time• End Date/Time.

Once

The utility will run every N hours and X minutes. Select the valuesfor:• Hour(N)• Minute(X)• Start Date/Time• End Date/Time

Hourly

The utility will run once every N days. Select the value for Days(N).Daily

2011-04-0690


DescriptionRecurrence Option

The utility will run once every week on the selected days. Select thefollowing values:• Days of the week• Start Date/Time• End Date/Time

Weekly

The utility will run once every N months. Select the following values:• Month(N)• Start Date/Time• End Date/Time

Monthly

The utility will run on the Nth day of each month. Select the followingvalues:• Day(N)• Start Date/Time• End Date/Time

Nth Day of Month

The utility will run on the first Monday of each month. Select the fol-lowing values:• Start Date/Time• End Date/Time

1st Monday of Month

The utility will run on the last day of each month. Select the followingvalues:• Start Date/Time• End Date/Time

Last Day of Month

The utility will run on the X day of the Nth week of each month. Selectthe following values:• Week(N)• Day(X)• Start Date/Time• End Date/Time

X Day of Nth Week of theMonth

The utility will run on the days you specified as "run" days on a calen-dar you have created in the "Calendars" management area of theCMC.

Calendar

5.4.3 Configuring for task completion notification

2011-04-0691


The Data Insight Administrator or someone in the Administrator group can configure the server toprovide email notifications in the Central Management Console (CMC). A Data Insight user must havealready created the profile task or rule task on Information Steward (see “Creating a profile task” or“Creating a rule task and setting an alert” in the User Guide).

When a task is schedule to run via the Central Management Console (CMC), you can be notified whetherthe task completed successfully or with errors. A profiling task is considered to be in error when profilingany of the tables fails, either because of an infrastructure error, or due to invalid source informationsuch as an invalid connection, table, column and so on.

The calculate score task may only fail when a table in the task was unable to generate its score, eitherdue to an infrastructure error or due to invalid source information such as an invalid connection, table,column and so on.

To configure the notification server for completed processing:1. In the CMC Home window, click Information Steward.2. ChooseData Insight > Projects > <your project name> and then highlight the profiling or calculate

score task that you want to schedule and be notified of the completion.3. Choose Actions > Scheduleand set up the scheduling information.4. ChooseNotification and expand Email notification. Define whether you want to receive notification

when the job is completed successfully and/or failed. You can override the default configurations.

DescriptionOption

Select to use the settings already defined in the Job Server.Use Job Server defaults

The following options override those defined in the JobServer.Set values to be used here

Provide the return email address."From"

Specify the email address of the alert subscriber."To"

Specify which recipient(s) should receive carbon copies ofalerts sent through email."CC"

Specify the default subject heading used in emails containingsystem alerts."Subject"

Specify the default message to include in emails containingsystem alerts."Message"

5. In the CMC Home window, click Servers. Select the ISJobServer. If more than one is available,configure each one.

6. Choose Manage > Properties, and then click Destination in the navigation pane.7. Select Email from the Destination drop-down list and then click Add.8. To set up a notification server for completed processing, you must enter information into the Domain,

Host, and Port fields. All other fields are optional. The following table describes the fields on theDestination page:

2011-04-0692


DescriptionOption

Enter the fully qualified domain of the SMTP server.Domain (required)

Enter the name of the SMTP server.Host (required)

Enter the port that the SMTP server is listening on. (This standardSMTP port is 25.)Port (required)

Select Plain or Login if the job server must be authenticated using oneof these methods in order to send email.Authentication

Provide the Job Server with a user name that has permission to sendemail and attachments through the SMTP server.User Name

Provide the Job Server with the password for the SMTP server.Password

Provide the return email address. Users can override this default whenthey schedule an object.From

Specify the email address of the alert subscriber.

Note:It is recommended that you keep the %SI_EMAIL_ADDRESS%If youspecify a specific email address or recipient all system alerts are sentto that address by default.

To

Specify which recipient(s) should receive carbon copies of alerts sentthrough email.CC

Specify the default subject heading used in emails containing systemalerts.Subject

Specify the default message to include in emails containing systemalerts.Message

You can add placeholder variables to the message body using theAddplaceholder list. For example, you can add the report title, author, orthe URL for the viewer in which you want the email recipient to viewthe report.

Add placeholder

Not used in this scenario.Add Attachment

9. Click Save.

Related Topics• Rule threshold notification

2011-04-0693


5.4.4 Rule threshold notification

The Data Insight Administrator or someone in the Administrator group can configure the server toprovide email notifications in the Central Management Console (CMC). A Data Insight user must havealready created the profile task or rule task on Information Steward (see “Creating a profile task” or“Creating a rule task and setting an alert” in the User Guide).

When a calculate score task is created, you have the option to provide an email address for notificationwhen the rule score falls below the low threshold setting. You must configure the notification serverbefore processing the task so the server has the correct information to send in the alert. To configurethe notification server to receive processing information:

You'll receive an email when the task is complete.1. In the CMC Home window, click Servers.2. Select Server List and then highlight the AdaptiveProcessingServer. If you have more than one

available, you must configure all of them.3. Choose Manage > Properties and then select Destination in the navigation pane.4. Select Email from the Destination drop-down list and then click Add.5. To set up a notification server for rules, you must enter information into the Domain, Host, Port and

From fields. All other fields are optional. The following table describes the fields on the Destinationpage:

DescriptionOption

Enter the fully qualified domain of the SMTP server.Domain (required)

Enter the name of the SMTP server.Host (required)

Enter the port that the SMTP server is listening on. (This standardSMTP port is 25.)Port (required)

Select Plain or Login if the job server must be authenticated using oneof these methods in order to send email.Authentication

Provide the Job Server with a user name that has permission to sendemail and attachments through the SMTP server.User Name

Provide the Job Server with the password for the SMTP server.Password

Provide the return email address. Users can override this default whenthey schedule an object.From (required)

Not used in this scenario. The email address specified when creatingthe task is used.To

Not used in this scenario.CC

2011-04-0694


DescriptionOption

Not used in this scenario.Subject

Not used in this scenario.Message

You can add placeholder variables to the message body using theAddplaceholder list. For example, you can add the report title, author, orthe URL for the viewer in which you want the email recipient to viewthe report.

Add placeholder

Not used in this scenario.Add Attachment

6. Click Save.

Related Topics• Configuring for task completion notification

5.4.5 Monitoring a task

To look at the status of or the progress of a profile task or rule task:1. Login to the Central Management Console (CMC) with a user name that belongs to the Data Insight

Administrator group or Administrator group.2. At the CMC home page, click Information Steward.


3. In the Tree panel, expand the Data Insight node expand the Projects node.4. Select the name of your project in the Tree panel.

A list of tasks appears in the right panel with the date and time each was last run.

5. To update the "Last Run Status" and "Last Run" columns, click the Refresh icon.6. To view the history of a task, select its name and click Action > History in the top menu tool bar.

The "Data Insight Task history" pane idsplays each instance the task was executed with the status,start time end time, and duration. The "Schedule Status" column can contain the following values:

DescriptionSchedule Status

Task did not complete successfully.Failed

Task is scheduled to run one time. When it actually runs, the statuschanges to “Running."Pending

2011-04-0695



Task is scheduled to recur. When it actually runs, there will be anotherinstance with status “Running."Recurring

Task is currently executing.Running

Task completed successfully.Success

7. To see the progress of a task instance:a. Select the instance name and click the icon for View the database log in the top menu bar of

the "Data Insight Task History" page.The "Database Log" window shows the task messages.

Note:The "Database Log" shows a subset of the messages in the log file.

b. To find specific messages in the "Database Log" window, enter a string in the text box and clickFilter.For example, you might enter error to see if there are any errors.

c. To close the "Database Log" window, click the X in the upper right corner.

8. To save a copy of a task log:a. Scroll to the right of the "Data Insight Task History" page, and click the Download link in the "Log

File" column in the row of the utility instance you want.b. Click Save.c. On the "Save As" window, browse to the directory where you want to save the log and change

the default file name if you want.

Note:This downloaded log file contains more messages than the "Database Log" because its defaultlogging level is set lower.

9. To close the "Data Insight Task History" page, click the X in the upper right corner.

Related Topics• Scheduling a task• Information Steward logs• Log levels• Changing log levels

5.4.6 Pausing and resuming a schedule

2011-04-0696


You pause a recurring schedule for a task when you do not want to run it at its regularly scheduled timeuntil you resume the schedule.

To pause a schedule:1. Log on to the CMC with a user name that belongs to the Data Insight Administrator group or that



3. In the Tree panel, expand the Data Insight node expand the Projects node.4. Select the name of your project in the Tree panel.5. Select the name of the task from the list on the right panel.6. Click Action > History in the top menu tool bar.

A list of instances for the task appears in the right pane.

7. Select the task instance that has the value "Recurring" in the "Schedule Status " column and clickAction > Pause in the top menu tool bar.

8. When you are ready to resume the recurring schedule, select he task instance that has the value"Paused" in the "Schedule Status " column and click Action > Resume in the top menu tool bar.

5.4.7 Common runtime parameters for Information Steward

When you schedule a profile task, rule task, or integrator source, you can change the default values ofthe runtime parameters in the Parameters option when you schedule the instance. The following tabledescribes the runtime parameters that are applicable to all metadata integrators, profile tasks, and ruletasks. For information about runtime parameters that apply to only specific metadata integrators, seethe topics in Related Topics below.

DescriptionRuntime parameter

This log is in the SAP BusinessObjects Information Steward repository. Youcan view this log while a Data Insight task or Metadata Integrator is running.

The default logging level is Information. Usually you can keep the defaultlogging level. However, if you need to provide more detailed informationabout your integrator run, you can change the level to log tracing information.For a description of log levels, see "Log levels".

Database Log Level

2011-04-0697


DescriptionRuntime parameter

A Data Insight task or Metadata Integrator creates this log in in the BusinessObjects installation directory and copies it to the File Repository Server.You can download this log file after the Data Insight task or Metadata Inte-grator run completed.

The default logging level for this log is Configuration. Usually you cankeep the default logging level. However, if you need to debug your task orintegrator run, you can change the level to log tracing information. For in-structions to change log levels, see "Changing log levels".

File Log Level

The Information Steward Job Server creates a Java process to perform theprofile task, rule task or metadata collection. Use the JVM Arguments pa-rameter to configure runtime parameters for the Java process. For example,if there are many parsed values per row in the data being used by CleansingPackage Builder, you might want to provide more memory than the defaultvalue for the -Xmx argument.

JVM Arguments

Optional runtime parameters for the metadata integrator source or Data In-sight task. For more information, see "mm_admin_runtime_parm_boe_in-teg.dita#icc14.0.0_topic_45BF540E11CB43F78E2AB9FE71384A8E".

Additional Arguments

Related Topics• JVM runtime parameters

5.5 Configuration settings

The "Information Steward Settings" window in Central Management Console allows you to configuredata profiling and rule settings in Data Insight. These settings control the behavior and performance ofdata profiling tasks and rule tasks. Some settings provide default values for parameters that you canoverride when you define a profiling task or rule task on Data Insight.

Related Topics• Configuring profiling tasks and rule tasks• Profiling task settings and rule task settings

2011-04-0698


5.5.1 Profiling task settings and rule task settings

The following parameters in the "Information Steward Settings" window control the behavior of profilingtasks, rule tasks, and their performance.

Note:

• The parametersMax input size,Max sample data size, andOptimization period affect the amountof data to process. The more data to process, the more resources are required for efficient processing.For performance considerations, see Input data settings.

• The parametersMax sample data size,Number of distinct values,Number of patterns,Numberof words, and Results retention period affect the size of the Information Steward repository. Ifyou increase these values, the repository size also increases and you might need to free spacemore often. For more information, see Settings to control repository size.

2011-04-0699


DescriptionDefaultvalueParameterData Insight sub-

category

Maximum number of rows to profile.

The default value -1 processes allrecords.

If the tables you profile are very large andyou want to reduce memory consumption,specify a maximum number of rows toprofile.

-1Max input size

"Profiling"

Rate at which rows are read. Set 1 toread every row, set 2 to read every sec-ond row, and so on.

1Input sampling rate

Maximum number of records to save foreach profile attribute.25Max sample data size

Number of distinct values to store of datadistribution result.25Number of distinct values

Number of patterns to store of patterndistribution result.25Number of patterns

Number of words to store of word distribu-tion result.25Number of words

Duration in days before the profiling re-sults are deleted from the InformationSteward repository by the Purge utility.For more information about the Purgeutility, see Utilities overview.

The default of 90 days is approximately3 months.

90Results retention period

Number of hours before profiling resultswill be replaced for a table by a scheduledtask. Set to 0 to refresh results with everytask run.

24Optimization period

Directory location for the reference datafor address profiling.

Address Reference Datadirectory

2011-04-06100



category

Maximum number of rows to validate forrules.

The default value -1 processes allrecords.

If the tables you process are very largeand you want to reduce memory consump-tion, specify a maximum number of rowsto validate for rules.

For performance considerations, see In-put data settings.

-1Maximum input size

"Rules"

Number of rows to read before a row isvalidated for rules.

For performance considerations, see In-put data settings.

1Input sampling rate

Maximum number of failed records tosave for each rule.100Max sample data size

Number of days before the scores arepurged.

The default of 1095 days is approximately3 years.

1095Score retention period

Number of hours before a new score willbe calculated for a table by a scheduledtask. Set 0 to always refresh immediately.

For performance considerations, seeData Insight result set optimization.

1Optimization period

Default value for Low Threshold whenbinding a rule and defining a scorecard.

You can override this for an individual ruleor scorecard. The range is 0 to 10.

5Default low threshold

Default value for High Threshold whenbinding a rule and defining a scorecard.

You can override this for individual ruleor scorecard. The range is 0 to 10.

8Default high threshold

2011-04-06101



category

Number of parallel processing threads fora task.4Degree of parallelism

"Performance"

Average number of profile or rule tasksthat can execute in parallel in the DataServices Job Server Group for Informa-tion Steward.

Information Steward multiplies this valuetimes the number of Job Servers availablein the Job Server Group. . For example,if Average concurrent tasks is set to 5and the Job Server Group contains 2 jobservers, then 10 tables or sub-tables canbe processed in parallel.For more information, see Data Insightrelated services .

5Average concurrent tasks

Maximum number of threads for file pro-cessing.2File processing threads

Directory location to use for caching ifprofiling and rule tasks require morememory.

Ensure that you specify a pageable cachedirectory that: contains enough disk spacefor the amount of data you plan to profile.For more information, see Hard disk re-quirements .

Pageable cache directory

TableTask distribution level

2011-04-06102



category

Level to distribute the execution of a pro-file or rule task in a Data Services jobserver group. The term “table” in thiscontext means “table, file, or view”.

Table: The entire table executes on onejob server.

Sub-table: The table is partitioned to ex-ecute in parallel on multiple job servers.

Note:If you specify Sub-table, ensure that:• You set up a pageable cache directory

on a shared directory that is accessi-ble to all job servers in the job servergroup.

• The network is efficient between thejob servers in the group.

• The requirements for a Data Servicesjob server group are met.

For more information, see Distributionlevel sub-table .

Related Topics• Configuring profiling tasks and rule tasks

5.5.2 Configuring profiling tasks and rule tasks

1. Log on to the Central Management Console (CMC) with a user name that belongs to the Data InsightAdministrator group or Administrator group.

2. Select Applications from the navigation list at the top of the CMC Home page.3. In the Application Name list, select Information Steward application.4. Click Actions > Configure Application to display the "Information Steward Settings" window.5. Keep or change the parameters values listed in the "Information Steward Settings" window.6. Click Save to apply the changed settings. Changes that affect the user interface will only be visible

to users once they log out and log back in.To reset the settings to their default values, clickReset. To cancel the changes made to the "settings",click Cancel.

2011-04-06103


Related Topics• Profiling task settings and rule task settings

2011-04-06104


Metadata Management Administration

6.1 Administration overview for Metadata Management

The Metadata Management module of SAP BusinessObjects Information Steward collects metadataabout objects from different source systems and stores the metadata in a repository. Source systemsinclude Business Intelligence (SAP BusinessObjects Enterprise and SAP NetWeaver BusinessWarehouse), Data Modeling, Data Integration (SAP BusinessObjects Data Services and SAPBusinessObjects Data Federation), and Relational Database systems.

When you access Information Steward as a user that belongs to the Metadata Management Administratorgroup, you can perform the following tasks in the CMC:• Configure integrator sources from which to collect metadata (see Configuring sources for Metadata

Integrators)• Run Integrators to collect metadata (see Running a Metadata Integrator )• View the status of Metadata Integrator runs (see Viewing integrator run progress and history )• Organize Metadata Integrator Sources into groups for relationship analysis (see Grouping Metadata

Integrator sources )• Manage user security of Metadata Integrator sources, source groups, Metapedia (see Type-specific

rights for Metadata Management objects.• Compute and store end-to-end impact and lineage information for Reporting (see Computing and

storing lineage information for reporting)• Manage the Metadata Management search indexes (see Recreating search indexes on Metadata

Management)

6.1.1 Configuring sources for Metadata Integrators

SAP BusinessObjects Metadata Integrators collect metadata from repository sources that you configure,and they populate the SAP BusinessObjects Information Steward repository with the collected metadata.

When you install Information Steward, you can select the following Metadata Integrators:• SAP BusinessObjects Enterprise Metadata Integrator• SAP NetWeaver Business Warehouse Metadata Integrator• Common Warehouse Metamodel (CWM) Metadata Integrator• SAP BusinessObjects Data Federator Metadata Integrator

2011-04-06105


• SAP BusinessObjects Data Services Metadata Integrator• Relational Database Metadata Integrator• Meta Integration Metadata Bridge (MIMB) Metadata Integrator - also known as MITI Integrator

6.1.1.1 Configuring sources for SAP BusinessObjects Enterprise MetadataIntegrator

This section describes how to configure the SAP BusinessObjects Enterprise Metadata Integrator forthe SAP BusinessObjects Enterprise repository which is managed by SAP BusinessObjects CentralManagement Server (CMS). This Integrator collects metadata for Universes, Crystal Reports, WebIntelligence documents, and Desktop Intelligence documents.

Note:Ensure that you selected the BusinessObjects Enterprise Metadata Integrator when you installed SAPBusinessObjects Information Steward .

To configure the BusinessObjects Enterprise Integrator, you must belong to the Metadata ManagementAdministrator group or add Objects right on the Integrator Sources folder.1. Log on to the Central Management Console (CMC) and access the Information Steward area.2. Click Manage > New > Integrator Source in the top menu tool bar.3. In the Integrator Type drop-down list, select BusinessObjects Enterprise.4. On the "New Integrator Source" page, enter the following information.

DescriptionOption

Name that you want to use for this metadata integrator source. Themaximum length of an integrator source name is 128 characters.Name

(Optional) Text to describe this metadata integrator source.Description

Host name of the CMS (Central Management Server). This value isrequired.

The CMS is responsible for maintaining a database of informationabout your BusinessObjects Enterprise system. The data stored bythe CMS includes information about users and groups, security levels,BusinessObjects Enterprise content, and servers. For more informa-tion about the CMS, see SAP BusinessObjects Business IntelligencePlatform Administrator'Guide.

Note:The version of BusinessObjects Enterprise installed on the MetadataManagement host must match the version of BusinessObjects Enter-prise that this CMS manages.

CMS Server Name

2011-04-06106


DescriptionOption

The CMS user name to connect to the CMS server.

The default value is Administrator. If you want a user other thanAdministrator to run the Metadata Integrator, change the valueto the appropriate name.

User Name

The password to connect to the CMS server to register and run theMetadata Integrator.Password

The process that CMS uses to verify the identity of a user who at-tempts to access the system. The default value is Enterprise. Seethe Business Intelligence Platform Administrator's Guide for availablemodes.

Authentication Method

The name of the "BI Launchpad" (formerly known as InfoView) userto invoke the Information Steward lineage diagrams when View Lin-eage is selected for each document in the "Documents List" of "BILaunchpad".

The default value is Administrator.

InfoView Integration Us-er

The password of the InfoView user to connect to Information Stewardto display the lineage diagram for a document in InfoView.Password

5. If you want to verify that Information Steward can connect successfully before you save this source,click Test connection.

6. Click Save.The newly configured source appears in the list of Integrator Sources on the right of the InformationSteward page.

Related Topics• Running a Metadata Integrator immediately• Defining a schedule to run a Metadata Integrator• Viewing integrator run progress and history

6.1.1.1.1 Checkpointing

SAP BusinessObjects Information Steward can run the SAP BusinessObjects Enterprise MetadataIntegrator for extended periods of time to collect large quantities of objects. If unexpected problemsoccur during object collection, Information Steward automatically records warning, error, and failureincidents in your log file for you to analyze later.

As additional failure management, Information Steward uses an automatic checkpointing mechanismwith preset "safe start" points to ensure that processing restarts from the nearest "safe start" point(instead of from the beginning of the job). Regardless of reason for the failure (power outage, accidental

2011-04-06107


shutdown, or some other incident), the next time you run the BusinessObjects Enterprise MetadataIntegrator, it restarts from the safe start point to finish object collection in the least amount of time.

6.1.1.2 Configuring sources for SAP NetWeaver Business Warehouse MetadataIntegrator

This section describes how to configure the Metadata Integrator for SAP NetWeaver BusinessWarehouse.

Note:Ensure that you selected the SAP NetWeaver Business Warehouse Metadata Integrator when youinstalled SAP BusinessObjects Information Steward.

To configure an SAP NetWeaver Business Warehouse integrator source, you must have the Createor Add permission on the integrator source.1. Log on to the Central Management Console (CMC) and access the Information Steward area.2. Click the down arrow next to Manage in the top menu tool bar and select New > Integrator Source.3. In the Integrator Type drop-down list, select SAP NetWeaver Business Warehouse.4. On the "New Integrator Source" page, enter the following information.

DescriptionOption

Name that you want to use for this integratorsource. The maximum length of an integratorsource name is 128 characters.

Name

(Optional) Text to describe this source.Description

One of the following connection types for thissource:• Custom Application Server• Group/Server Selection

Connection Type

SAP Application Server host name when Con-nection Type is Custom Application Server.

Application Server

SAP NetWeaver BW Message Server host namewhen Connection Type is Group/Server Selec-tion.

Message Server

SAP group name when Connection Type isGroup/Server Selection.

Group/Server

ID number for the SAP NetWeaver BW client.Client

Number for the SAP NetWeaver BW system.System Number

2011-04-06108


DescriptionOption

(Optional) String that contains the informationrequired by SAProuter to set up a connectionbetween the Metadata Integrator and the SAPNetWeaver BW system. The string contains thehost name, the service port, and the password,if one was given.

SAProuter String

Name of the user that will connect to the SAPNetWeaver BW system.

SAP User

Password for the user that will connect to theSAP NetWeaver BW system.

SAP Password

Language to use for the descriptions of SAPNetWeaver BW objects. Specify the 2-characterISO code for the language (for example, en forEnglish).

Language

5. To verify that Information Steward can connect successfully before you save this source, click Testconnection.

6. Click Save.

The newly configured source appears in the list of Integrator Sources on the right of the page.

Related Topics• SAP router string information: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4f/992df1446d11d189700000e8322d00/content.htm• Running a Metadata Integrator immediately• Accessing Information Steward for administrative tasks• Defining a schedule to run a Metadata Integrator• Viewing integrator run progress and history

6.1.1.3 Configuring sources for Common Warehouse Metamodel (CWM) MetadataIntegrator

This section describes how to configure the Metadata Integrator for Common Warehouse Metamodel(CWM).

Note:Ensure that you selected the CWM Metadata Integrator when you installed SAP BusinessObjectsInformation Steward.

2011-04-06109


http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4f/992df1446d11d189700000e8322d00/content.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4f/992df1446d11d189700000e8322d00/content.htm

To configure the CWM Integrator, you must have the right to add objects in the Integrator Sourcesfolder.1. Log on to the Central Management Console (CMC) and access the Information Steward area. For

details, see Accessing Information Steward for administrative tasks.2. Click the down arrow next to "Manage" in the top menu tool bar and selectNew > Integrator Source.3. In the Integrator Type drop-down list, select Common Warehouse Modeling .4. On the "CWM Integrator Configuration" page, enter the following information.

DescriptionOption

Name that you want to use for this source. The maximum length of an integratorsource name is 128 characters.Source Name


Name of the file with the CWM content. For example: C:\data\cwm_export.xml

This value is required. The file should be accessible from the computer wherethe Metadata Management web browser is running.

Click the Browse button to find the file.

Note:Metadata Management copies this file to the Input File Repository Server onSAP BusinessObjects Business Intelligence Platform. Therefore, if the originalfile is subsequently updated, you must take the following steps to obtain theupdates before you run the Integrator again:• Update the configuration to recopy the CWM file.

a. From the Integrator Sources list, select the CWM integrator source nameand click Action > Properties.

The file name displays in the comments under the File Name text box,and the file name has "frs:" prefacing it.

b. Browse to the original file again.c. Click Save.

• Create a new schedule for the CWM integrator because the old schedulehas a copy of the previous file.a. With the CWM integrator source name still selected in the Integrator list,

click Action > Schedules.b. Select the Recurrence and Parameter options that you want.c. Click Schedule.

File Name

5. Click Save.The newly configured source appears in the list of Integrator Sources on the right of the page.

2011-04-06110



6.1.1.4 Configuring sources for SAP BusinessObjects Data Federator MetadataIntegrator

This section describes how to configure the Metadata Integrator for SAP BusinessObjects Data Federator.

Note:Ensure that you selected the SAP BusinessObjects Data FederatorMetadata Integrator when youinstalled SAP BusinessObjects Information Steward.

To configure an SAP BusinessObjects Data Federator integrator source, you must have the Create orAdd right on the integrator source.1. Log on to the Central Management Console (CMC) and access the Information Steward area. For

details, see Accessing Information Steward for administrative tasks.2. Click the down arrow next to Manage in the top menu tool bar and select New > Integrator Source.3. In the Integrator Type drop-down list, select Data Federator.4. On the "New Integrator Source" page, enter the following information.

DescriptionOption

Name that you want to use for this source. The maximum length of an integrator source name is 128 characters.

Name


Name or IP address of the computer where the Data Federator Designerresides. For example, if you installed the Data Federator Designer on thesame computer as the Data Federator Integrator, type localhost.

DF Designer ServerAddress

Port number for the Data Federator Designer. The default value is 3081.DF Designer ServerPort

Name of the user that will connect to the Data Federator Designer.User name

Password for the user that will connect to the Data Federator Designer.Password

5. If you want to verify that Metadata Management can connect successfully before you save thissource, click Test connection.


2011-04-06111



6.1.1.5 Configuring sources for SAP BusinessObjects Data Services MetadataIntegrator

This section describes how to configure the Metadata Integrator for SAP BusinessObjects Data Services.

Note:Ensure that you selected the SAP BusinessObjects Data Services Metadata Integrator when youinstalled SAP BusinessObjects Information Steward.

To configure the Data Services Integrator, you must have the Create or Add right on the integratorsource.1. Log on to the Central Management Console (CMC) and access the Information Steward area. For

details, see Accessing Information Steward for administrative tasks.2. Click the down arrow next to Manage in the top menu tool bar and select New > Integrator Source.3. In the Integrator Type drop-down list, select Data Services.4. On the "New Integrator Source" page, in the Integrator Type drop-down list, select BusinessObjects

Data Services information.5. Enter the following Data Services information.

DescriptionOption

Name that you want to use for this source. The maximum length of anintegrator source name is 128 characters.Name


The database type of the Data Services repository. The availabledatabase types are:• DB2• Microsoft SQL Server• MySQL• Oracle• Sybase

Database Type

Name of the computer where the Data Services repository resides.Computer Name

Port number of the database.Database Port Num-ber

2011-04-06112


DescriptionOption

The name of the database, data source, or service name. Specify thefollowing name for the database type of the Data Services repository:• DB2 - Data source name

• Microsoft_SQL_Server - Database name

• Oracle - SID/Service name

• Sybase - Database name

Datasource,Database Name, orService name

Name of the user that will connect to the Data Services repository.Database User

The password for the user that will connect to the Data Services reposi-tory.Database Password

6. If you want to verify that Metadata Management can connect successfully before you save thissource click Test Connection.

7. Click Save.The newly configured source appears in the list of Integrator Sources on the right of the window.


6.1.1.6 Configuring sources for Meta Integration Metadata Bridge MetadataIntegrator

This section describes how to configure the Metadata Integrator for Meta Integration® Metadata Bridge(MIMB). For a description of the objects collected by the MIMB Integrator, see the MIMB documentationat http://www.metaintegration.net/Products/MIMB/Documentation/.

Note:Ensure that you selected the Meta Integration Metadata Bridge (MIMB) Metadata Integrator when youinstalled SAP BusinessObjects Information Steward.

To configure the MIMB Integrator, you must have the Create or Add right on the integrator source.1. Log on to the Central Management Console (CMC) and access the Information Steward area. For

details, see Accessing Information Steward for administrative tasks.2. Click the down arrow next to Manage in the top menu tool bar and select New > Integrator Source.3. In the Integrator Type drop-down list, select Meta Integration Metadata Bridge.

2011-04-06113



4. On the "New Integrator Source" page, enter values forName andDescription. The maximum lengthof an integrator source name is 128 characters.

5. In the Bridge drop-down list, select the type of integrator source from which you want to collectmetadata and follow the instructions on the user interface to configure the connection information.


Related Topics•• Running a Metadata Integrator immediately• Defining a schedule to run a Metadata Integrator• Viewing integrator run progress and history

6.1.1.7 Configuring sources for Relational Database Metadata Integrator

This section describes how to configure and run the Metadata Integrator for a DB2, JDBC, MicrosoftSQL Server, MySQL, or Oracle relational database.

Note:Ensure that you selected the Relational Database System Metadata Integrator when you installed SAPBusinessObjects Information Steward.

To configure the Relational Database Integrator, you must add objects in the Integrator Sources folder.1. Log on to the Central Management Console (CMC) and access the Information Steward area. For

details, see Accessing Information Steward for administrative tasks.2. To access the "New Integrator Source" page, take one of the following actions:

• Click the left-most icon, "Create an Integrator source", in top menu bar.• On the Manage menu, point to New and click Integrator Source.The "New Integrator Source" page displays.

3. In the Integrator Type drop-down list, select Relational Database.4. Specify the pertinent connection information for the relational database that you specify inConnection

Type.

DescriptionOption

Name that you want to use for this source. Themaximum length of an integrator source nameis 128 characters.

Name


2011-04-06114



DescriptionOption

The type of database for which you want tocollect metadata. Select one of the followingdatabase types:• Universe Connection for secure connections

defined in CMS. For options specific to auniverse connection source, see Configuringsources for universe connections .

• DB2• Microsoft SQL Server• MySQL• Oracle For information to download and in-

stall a JDBC driver for an Oracle database,see “Extra requirements for Oracle” in theInstallation Guide.

• JDBC (Java Database Connectivity) fordatabases such as Teradata. For optionsspecific to a JDBC source, see Configuringsources for JDBC connections .

Connection Type

The name of the Central Management System(CMS) connection.

You must select a value forConnectionswhenConnection Type is set to Universe Connec-tion. The drop-down list displays the secureconnections defined in the CMS.

Connections

Host name on which the database server isrunning.Computer name

Port number of the database.Database port number

The name of your DB2 database, Microsoft SQLServer database, MySQL database, or Oracledatabase service (SID).

Database Name, or Service name

The name of the user or owner of the databaseor data source.Database User

The password of the user for the database ordata source.Database Password

2011-04-06115


DescriptionOption

(Optional) Specify the name of the schema thatyou want to import from this source database.If you do not specify a schema name:• Metadata Management imports all available

schemas for SQL Server or DB2.• Metadata Management uses the user name

to import the schema for Oracle.

Table Schema applies to the following connec-tion types:• DB2• Microsoft SQL Server• Oracle

Table Schema



6.1.1.7.1 Configuring sources for JDBC connections

If you plan to use a JDBC source (such as Teradata) for the Relational Database Metadata Integrator,do the following steps:1. Obtain the JDBC driver from your database server web site or utilities CD.2. Unzip the JDBC driver into a folder such as the following:

c:\temp\teradata

3. Log on to the Central Management Console (CMC) and access the Information Steward area. Fordetails, see Accessing Information Steward for administrative tasks.

4. Take one of the following actions to access the "New Integrator Source" page.• Click the left-most icon, "Create an Integrator source", in top menu bar.• On the Manage menu, point to New and click Integrator Source.The "New Integrator Source" page displays.

5. In the Integrator Type drop-down list, select Relational Database.6. Specify the following JDBC connection parameters:

2011-04-06116


DescriptionJDBC parameter

Name that you want to use for this source.Name


Select JDBC from the drop-down list.Connection Type

Name of the JDBC driver class that you ob-tained in step 1 above.Driver

URL address that specifies the JDBC connec-tion to the database.URL

(Optional) The name of the catalog in the Tera-data database.Catalog

Name of the user or owner of the database.Database User

Password for the user of the database.Database Password

(Optional) Specify the name of the schema thatyou want to import from this source database.Table Schema

The jar files, separated by semicolons. For example: c:\temp\teradata\tdgssjava.jar;c:\temp\teradata\terajdbc4.jar;c:\temp\teradata\tdgssconfig.jar

Note:In a distributed deployment, you must set Library Files to the classpath on the computerwhere the integrator runs.

Library files

7. Click Test connection if you want to verify that Metadata Management can connect successfullybefore you save this source.

8. Click Save.The newly configured source appears in the list of Integrator Sources on the right of page.

Related Topics• Configuring sources for Relational Database Metadata Integrator• Running a Metadata Integrator immediately• Defining a schedule to run a Metadata Integrator• Viewing integrator run progress and history

2011-04-06117


6.1.1.7.2 Configuring sources for universe connections

The Relational Database Integrator can collect metadata from secured universe connections that useJDBC and ODBC. For the most current list of supported universe connection types, refer to the ReleaseNotes.

To configure a universe connection source that uses a JDBC or ODBC connection:1. If you want to configure a universe connection source that uses a JDBC connection, perform the

following steps:a. Obtain the JDBC driver from your database server web site or utilities CD.b. Unzip the JDBC driver into a folder such as the following:

c:\temp\teradata

2. If you want to configure a universe connection source that uses an ODBC connection, ensure thatthe ODBC Datasource exists in the computer where the integrator will run.

3. Log on to the Central Management Console (CMC) and access the Information Steward area. Fordetails, see Accessing Information Steward for administrative tasks.The "Information Steward" page opens with the Integrator Sources node selected in the tree onthe left.

4. Take one of the following actions to access the "New Integrator Source" page.• Click the left-most icon, "Create an Integrator source", in top menu bar.• On the Manage menu, point to New and click Integrator Source.The "New Integrator Source" page displays.

5. In the Integrator Type drop-down list, select Relational Database.6. Specify the following universe connection parameters:

2011-04-06118


DescriptionOption

Name that you want to use for this source.Name


Select Universe Connection from the drop-down list.Connection Type

The name of the Central Management System (CMS) connection. The drop-down list displays the secure connections defined in the CMS.

Connections

(Optional) Specify the name of the schema that you want to import from thissource database. If you do not specify a schema name:• Metadata Management imports all available schemas for SQL Server or

DB2.• Metadata Management uses the user name to import the schema for Oracle.

Table Schema

The full paths to the Java library files (separated by semicolons)required bythe Universe Connection. For example:

Note:In a distributed deployment, you must set Library Files to the classpath onthe computer where the integrator runs.

Library Files

7. Click Test connection if you want to verify that Metadata Management can connect successfullybefore you save this source.


Related Topics• Configuring sources for Relational Database Metadata Integrator• Running a Metadata Integrator immediately• Defining a schedule to run a Metadata Integrator• Viewing integrator run progress and history

6.1.2 Managing integrator sources and instances

You manage integrator sources and instances in the SAP BusinessObjects Information Steward areaof the CMC.

From the list of configured integrator sources, you can select an integrator source and perform a taskfrom Manage or Actions in the top menu tool bar.

You can perform the following tasks from the Manage menu.

2011-04-06119


DescriptionManage task

Create a new Integrator Source or Source Group.New

Manage user security for Integrator Sources, Source Groups, or Metapedia objects.Security

Obtain the latest Integrator Sources information.Refresh

Delete this source configuration (see Deleting an integrator source ) and its asso-ciated schedules, source runs, and logs.

Delete

Remove all integrator source runs. This option keeps the source configuration,file logs, and schedules.

Purge

You can perform the following tasks from the Actions menu.

DescriptionAction task

View the current and previous executions of this Metadata Integrator source(see Viewing integrator run progress and history ).History

View and edit the configuration information for this Metadata Integratorsource.Properties

Run the Metadata Integrator at regular intervals (see Defining a scheduleto run a Metadata Integrator ).Schedule

Run the Metadata Integrator immediately (see Running a Metadata Integra-tor immediately ).Run now

Related Topics• Viewing and editing an integrator source• Deleting an integrator source• Changing log levels• Changing limits

6.1.2.1 Viewing and editing an integrator source

You can view and modify the definition of an integrator source in its "Properties" dialog box to changeits description, connection information, and other pertinent information for the integrator source.• To view the definition, you must have the right to View the integrator source.• To modify the definition, you must have the right to Edit the integrator source.

1. From the Central Management Console (CMC) click Information Steward.

2011-04-06120



2. Expand the "Metadata Management" node in the Tree panel and select Integrator Sources.3. From the list in the right pane, select the name of the integrator source that you want.

Note:If you click the integrator source type, you display the version and customer support information forthe integrator.

4. Access the "Properties" dialog box in one of the following ways:• Double-click the row for the integrator source.• Click Actions > Properties in the top menu tool bar.

5. You can change any property for the integrator source, except its type and name.6. To verify the database connection information on this "Integrator Source Properties" dialog box,

click Test connection.7. Click Save to save your changes to the configuration.8. To change parameters such as Log Level orUpdate Option (BusinessObjects Enterprise Integrator

only), expand the Schedule node in the tree on the left and click Parameters.

Related Topics• Defining a schedule to run a Metadata Integrator

6.1.2.2 Deleting an integrator source

You might want to delete an integrator source in situations such as the following:• You want to rename your integrator source

Note:If you rename your integrator source, you lose all the previously collected metadata.

• You no longer need your integrator source

To delete an integrator source, you must belong to the Metadata Management Administrator user groupor have the right to Delete the integrator source.1. From the Central Management Console (CMC) click Information Steward.


2. Expand the Metadata Management node.3. Select the Integrator Sources node.

A list of configured integrator sources appears in the right panel with the date and time each waslast run.

2011-04-06121


4. Select the integrator source and click Manage > Delete in the top menu tool bar.

Note:If you delete an integrator source, you also delete the metadata from that source that was stored inthe Metadata Management repository.

5. Reply to the confirmation prompt.

6.1.2.3 Changing limits

Each time you run a metadata integrator or SAP BusinessObjects Information Steward utility, SAPBusinessObjects Information Steward creates a new instance and log files for it. By default, the maximumnumber of instances to keep is 100. When this maximum number is exceeded, SAP BusinessObjectsEnterprise deletes the oldest instance and its associated log file.

Note:The Purge utility deletes the database log in the Metadata Management repository for each instancethat was deleted.

To change the limits to delete integrator source instances, you must have Full Control access levelon the Metadata Management folder.1. Log on to the CMC with a user name that belongs to the Metadata Management Administrator or

Administrator user group.2. From the Central Management Console (CMC) click Information Steward.


3. Expand the Metadata Management node.4. Click Actions > Limits in the top menu bar.

The "Limits: Metadata Management" window appears.

5. If you want to change the default value of 100 maximum number of instances to keep:a. Select the check box for the option Delete excess instances when there are more than N

instances.b. Enter a new number in the box under this option.c. Click Update to save your changes.

6. If you want to specify a maximum number of instances to keep for a specific user or group:a. Click the Add button next to Delete excess instances for the following users/groups.b. Select the user or group name from the "Available users/groups" pane and click >.c. Click OK.d. If you want to change the default value of 100 maximum number of instances to keep, type a

new number under Maximum instance count per object per user.e. Click Update to save your changes.

7. If you want to specify a maximum number of days to keep instances for a specific user or group:

2011-04-06122


a. Click the Add button next to Delete instances after N days for the following users or groups.

b. Select the user or group name from the "Available users/groups" pane and click >.c. Click OK.d. If you want to change the maximum number of instances to keep (default value 100), type a new

number under Maximum instance count per object per user.e. Click Update to save your changes.

8. To close the "Limits: Metadata Management" window, click the X in the upper right corner.

6.1.3 Running a Metadata Integrator

Run the Metadata Integrator to collect the metadata for each source that you configured. When youselect Integrator Sources under the "Metadata Management " node in the tree panel on the left of theSAP BusinessObjects SAP BusinessObjects Information Steward page in the CMC, all configuredintegrator sources appear. When you select an integrator source from the list in the right pane, you cancan run it immediately or define a schedule to run it.

Related Topics• Running a Metadata Integrator immediately• Defining a schedule to run a Metadata Integrator

6.1.3.1 Running a Metadata Integrator immediately

To run a Metadata Integrator immediately:1. Log on to the CMC with a user name that belongs to the Metadata Management Administrator or

Administrator user group.2. From the Central Management Console (CMC) click Information Steward.


3. Expand the Metadata Management node and click Integrator Sources.4. From the list of configured sources that appears on the right, select the integrator source that you

want by clicking anywhere on the row except its type.

Note:If you click the integrator source type, you display the version and customer support information forthe integrator. If you double-click the row, you open the "Properties" dialog box for the integratorsource.

2011-04-06123


5. Click Actions > Run Now in the top menu tool bar and select .

Tip:You can also click the icon "Run selected object(s) now" in the icon bar under Manage and Actions.

6. To view the progress of the integrator run, select the integrator source, and click Action > History.

Tip:If you select Now in the Run object option under Action > Schedule > Recurrence and clickSchedule, the "Integrator History" page automatically displays.

7. Click the Refresh icon to update the status.

For more details about the "Integrator History" page, see Viewing integrator run progress and history.

8. If you use impact and lineage reports on the Reports option in the Open drop-down menu in the"Metadata Management" tab of Information Steward, you must recompute the contents of the lineagestaging table to incorporate changes from the Integrator runs. For more information, see Computingand storing lineage information for reporting.

6.1.3.2 Defining a schedule to run a Metadata Integrator

To run a Metadata Integrator at regular intervals, define a schedule for it.

To define a schedule for an integrator source, you must have the right to Schedule the integrator source.1. From the Central Management Console (CMC) click Information Steward.


2. Expand the Metadata Management node.3. Select the Integrator Sources node.

A list of configured integrator sources appears in the right panel with the date and time each waslast run.

4. From the list of configured sources that appears on the right, select the source from which you wantto collect metadata by clicking anywhere on the row except its type.

Note:If you click the source type, you display the version and customer support information for the metadataintegrator.

5. Click Actions > Schedule.The "Instance Title" pane of the "Schedule" page appears with the name of the configured source.

6. If you do not want the default value for Instance Title, change it to a unique name that describesthis schedule.

7. Select the Recurrence node on the left to choose the frequency in the Run object drop-down list.

2011-04-06124


8. Choose the additional relevant values for the selected recurrence option. For details, see Recurrenceoptions.

9. If you want to send notification when the integrator has run, select the Notification node on the left.For more information about Notification, see the SAP BusinessObjects Business IntelligencePlatform Administrator Guide.

10. If you want to trigger the execution of a Metadata Integrator when an event occurs, select the Eventsnode on the left. For more information about Events, see the SAP BusinessObjects BusinessIntelligence Platform Administrator Guide.

11. Select the Parameters node on the left to change the default values for run-time parameters for themetadata integrator. For details, see Common run-time parameters for metadata integrators.

12. Click Schedule.13. If you use impact and lineage reports on the Open > Reports option on Metadata Management tab

in Information Steward, you must recompute the contents of the lineage staging table to incorporatechanges from the Integrator runs. Similar to setting up a regular schedule to run an Integrator, youcan set up a schedule to compute the lineage staging table at regular intervals. For more information,see Computing and storing lineage information for reporting.

6.1.4 Changing run-time parameters for integrator sources

When you schedule an integrator source, you can change the default values of the run-time parameterson the "Parameters" page in the Central Management Console (CMC). The following sections describethe runtime parameters that you can set for different integrator sources.

To change the run-time parameters for an integrator source:1. From the Central Management Console (CMC) click Information Steward.2. Expand the "Metadata Management" node.3. Select the Integrator Sources node, and select your integrator source4. Click Actions > Schedule.5. On the "Schedule" window, click Parameters in the navigation tree.6. In the text box for JVM Arguments or Additional Arguments, enter the parameter and value you

want to change.7. Click Recurrence in the navigation tree to schedule this integrator source. For more information,

see "recurrence_options.dita#icc14.0.0_reference_285CCB668AEE45E890D59C6C149B2D23".8. Click Schedule.

6.1.4.1 Common run-time parameters for metadata integrators

2011-04-06125


The following table describes the run-time parameters that are applicable to all metadata integrators.For information about run-time parameters that apply to only specific metadata integrators, see thetopics in Related Topics below.

DescriptionRun-time parameter

This log is in the SAP BusinessObjects Metadata Management Repository.You can view this log while the Metadata Integrator is running.

The default logging level is Information. Usually you can keep the defaultlogging level. However, if you need to provide more detailed informationabout your integrator run, you can change the level to log tracing information.For a description of log levels, see Log levels.

Database Log Level

The Metadata Integrator creates this log in in the Business Objects installa-tion directory and copies it to the File Repository Server. You can downloadthis log file after the Metadata Integrator run completed.

The default logging level for this log is Configuration. Usually you cankeep the default logging level. However, if you need to debug your integratorrun, you can change the level to log tracing information. For a descriptionof log levels, see Log levels.

File Log Level

The Metadata Management Job Server creates a Java process to performthe metadata collection. Use the JVM Arguments parameter to configurerun-time parameters for the Java process. For example, if the metadatasource is very large, you might want to provide more memory than the de-fault.

JVM Arguments

Optional run-time parameters for the metadata integrator source. For moreinformation, see User collection parameters.Additional Arguments

Related Topics• Metadata collection using the Remote Job Server with SSL

6.1.4.2 Run-time parameters for SAP BusinessObjects Enterprise integratorsource

6.1.4.2.1 User collection parameters

The SAP BusinessObjects Enterprise metadata integrator provides the following run-time parameterto adjust memory usage when collecting user permissions.

2011-04-06126


Default val-ueDescriptionRun-time parame-

ter

false

Enable or disable user permissions collection

Specify true to enable user permissions collection.

Note:If you specify true, increase the memory with the -Xmx parame-ter in the JVM Arguments. If the amount of memory is available,you can set this value as high as -Xmx1500m, where "m" indi-cates megabytes.

Set this parameter in Additional Arguments on the "Parame-ters" page.

collectUserPermissions

6.1.4.2.2 Selective CMS object collection

Selective collection of CMS metadata through the SAP BusinessObjects Enterprise Metadata Integratorreduces processing time. To view a complete picture of the information in your BusinessObjectsEnterprise system, run the integrator multiple times, specifying a different component for each run.Also, you might want to incrementally collect CMS metadata for a large SAP BusinessObjects Enterprisedeployment by using selective collection.

To add metadata to the previous metadata collections, select the Update existing objects and addnewly selected objects option. For example, if you have collected Web Intelligence documents on thefirst run, then you collect Crystal Reports on the second run, then you will see the Web Intelligencedocuments and Crystal Reports metadata together in the SAP BusinessObjects Metadata ManagementExplorer. The first time you schedule and run a metadata collection for a specific object type, all metadatafor that object is collected. Subsequent runs will only collect changes since the last run.

To delete metadata from previous metadata collections, select the Delete existing objects beforestarting object collection option. For example, if you have collected Web Intelligence documents ona previous run, and then choose to collect Crystal Reports on the next run, you will see only CrystalReports metadata in the Metadata Management Explorer.

You can collect metadata from Universe, Public, or Personal folders. Anyone using the SAPBusinessObjects Metadata Management Explorer can see the contents of these folders. However, youmust have the proper permissions to be able to run collections on the objects in these folders. In yourPersonal folder, only you or an administrator can run a collection on those objects.

Note:SAP BusinessObjects Enterprise Metadata Integrator does not collect metadata from Inboxes orCategories.

2011-04-06127


DescriptionOption

Specifies the names of the folders that you wantin the collection using a Java Regular Expression.For example,• an asterisk (*) means that all folders are col-

lected.• folderName collects metadata within a specific

folder. It will also collect metadata in any asso-ciated subfolders.

• folderName* an asterisk at the end of a stringvalue includes all folders with that string.

• folderName|folderName a pipe (also calledvertical bar separator) between folder namesincludes one or the other folder. For example,Sales|Finance means either the Sales or theFinance folder.

• ^(?!folderName$) excludes the folder withthis specific folder name.

• ^(?!folderName) excludes any folders thatstart with this specific folder name.

• (?!folderName) excludes any folders that hasthis specific folder name within the name.

Folder Name Expression

Collect the SAP BusinessObjects Enterprise uni-verse metadata in the folders specified in theFolder Name Expression option.

Note:If you uncheck this option, and choose to collectany report that uses a universe, the integratorcollects the universe metadata as well.

Collect Universes

Collects Web Intelligence documents and sourceuniverses from Public and/or Personal folders.

Collect Web Intelligence Documents and sourceUniverses

Collects Desktop Intelligence documents andsource universes from Public and/or Personalfolders.

Collect Desktop Intelligence Documents andsource Universes

Collects Crystal Reports and associated universesfrom Public and/or Personal folders.Collect Crystal Reports and associated Universes

2011-04-06128


DescriptionOption

This option only appears for an SAP BusinessOb-jects Enterprise Metadata Integrator.• Delete existing objects before starting ob-

ject collection

This choice is the default and collects allmetadata the integrator source.

• Update existing objects and add newly se-lected objects

This choice only collects metadata about ob-jects that are new or have changed since thelast time the integrator source was run.

Note:It is recommended that you specify Delete exist-ing objects before starting object collectionthe first time you run the integrator source, butspecifyUpdate existing objects and add newlyselected objects for subsequent runs.

Update Option:

Delete existing objects before starting objectcollection

Update existing objects and add newly select-ed objects

6.1.4.2.3 Metadata collection using the Remote Job Server with SSL

You can configure an integrator source on SAP BusinessObjects Information Steward 4.0 to collectmetadata from an SAP BusinessObjects Enterprise XI 3.x system. The Information Steward installationprogram installs a Remote Job Server component on the Enterprise XI 3.x to enable this collection. IfSSL is enabled between the Information Steward 4.0 and the Remote Job Server systems, you mustset the businessobjects.migration run-time parameter when you schedule the integrator source.

When you schedule an integrator source to collect metadata from an SAP BusinessObjects EnterpriseXI 3.x system that has SSL enabled, you must set the businessobjects.migration run-timeparameter

Note:You cannot run remote integrators if Federal Information Processing Standards (FIPS) mode is enabledon Enterprise XI 3.x.

To set the run-time parameter for the SAP BusinessObjects Enterprise XI 3.x integrator source whenSSL is enabled:1. From the Central Management Console (CMC) click Information Steward.


2. Expand the Metadata Management node and click Integrator Sources.

2011-04-06129


3. From the list of configured sources that appears on the right, select the source by clicking anywhereon the row except its type.

Note:If you click the source type, you display the version and customer support information for the metadataintegrator.

4. Click Actions > Schedule.5. On the "Schedule" window, click Parameters in the navigation tree.6. In the text box for JVM Arguments, enter the following parameter:

-Dbusinessobjects.migration=on

7. Click Recurrence in the navigation tree to schedule this integrator source. For more information,see Recurrence options.

8. Click Schedule.

6.1.4.3 Run-time parameters for an SAP NetWeaver BW integrator source

The SAP NetWeaver Business Warehouse metadata integrator provides run-time parameters to adjustthe number of threads to use when collecting metadata from the SAP system and to filter the queriesor workbooks to collect.


Specifies the number of threads to use whencollecting metadata from the SAP system. Youmight want to increase the number of threads ifyour SAP NetWeaver BW system has a largenumber of objects and it has available work pro-cesses.

The default value is 5. In a multiprocessor envi-ronment, you can increase this value. The numberof threads is limited by the number of processorsconfigured on the SAP NetWeaver BW server. Ifthe number of threads is greater than the availableprocessors, the thread is put on a queue and willbe processed when a processor becomes avail-able.

Number of Threads

2011-04-06130



Specifies the names of the queries that you wantin the collection using a Java Regular Expression.For example:• * an asterisk (*) means that all queries are

collected.• queryName* an asterisk at the end of a string

value includes all queries with that string.• queryName|queryName a pipe (also called

vertical bar separator) between query namesincludes one or the other query. For example,Sales|Finance means either the Sales or theFinance query.

• ^(?!queryName$) excludes the query with thisspecific query name.

• ^(?!queryName) excludes any queries thatstart with this specific query name.

• (?!queryName) excludes any queries that hasthis specific query name within the name.

Query Name Expression

Specifies the names of the workbooks that youwant the integrator source to collect using a JavaRegular Expression.

Examples are similar to those for Query NameExpression

Workbook Name Expression

6.1.5 Viewing integrator run progress and history

When you select the Integrator Sources in the Tree panel on the left on the SAP BusinessObjectsInformation Steward page in the CMC, all configured integrator sources display. Next to each sourcename is the date and time when the Integrator was last run for that source.

To view all runs for a metadata integrator source, you must have the right to Viewintegrator sources:1. From the list of all configured integrator sources, select the name of the source that you want to see

the history of runs.2. Click the down arrow next to "Actions" in the top menu tool bar and selectHistory from the drop-down

list.3. The "Integrator History" page displays the following information:

• All "Schedule Names" for the integrator source.

2011-04-06131


• Status of each schedule. The possible values are, Success, Failed, Running, Paused, Resumed,and Stopped.

• "Start Time", "End time", and "Duration" of each integrator run.• "Log File" for that integrator run.

4. Click the "View the database log" icon (fifth from the left) in the menu bar or clickActions >DatabaseLog to view the progress messages of the integrator run. For details on logs, see Information Stewardlogs

By default, Metadata Management writes high-level messages (such as number of universe processedand number of reports processed) to the log. You can change the message level on the configurationpage for the integrator source. For details, see Changing log levels.

5. In the top menu bar of the "Integrator History" page, use either the Actions drop-down list or theicons to perform any of the following options:

DescriptionOption

Run this integrator immediatelyRun Now

Stop the execution of this integrator instance if it is currently running.Stop

Pause the execution of this integrator instance if it has a status of Pending orRecurring.

Pause

Resume the execution of this integrator instance if it is currently paused.Resume

Define a new schedule to execute this integrator.Reschedule

View messages that indicate which metadata objects have been collected fromthe integrator source.

Database log

Refresh the status of this integrator instance.Refresh

Delete this integrator instance from the history list.Delete

6.1.6 Troubleshooting

The following sections tell you how to interpret the warning and error messages that you might see inthe database log and file log for each Metadata Integrator run.

6.1.6.1 Crystal Report message

Crystal Report [reportname]. Unable to find class for universe object[objectname]. Universe class cannot be uniquely identified for object

2011-04-06132


[objectname]. Data association cannot be established directly through theobject. Reference will be established directly to the column.

Cause: The BusinessObjects Enterprise Metadata Integrator cannot uniquely identify a universe objectthat is used to create a Crystal Report when the object has the same name as another object in adifferent universe class. Therefore, the Integrator cannot establish the correct relationship between theuniverse object and the report. However, the Integrator can establish a relationship between the sourcetable or column and the report because the SQL parser can find the source column used by the universeobject.

Action: Name the objects uniquely across the classes in a universe.

6.1.6.2 DeskI document error

DeskI document [reportname]. Universe [ ] not found.

Cause: Data providers in the Desktop Intelligence document refer to an invalid or non-existent universe.

Action: Open the Desktop Intelligence document and edit the data provider to specify a valid universe.

6.1.6.3 Out of memory error

Error occurred during initialization of VMCould not reserve enough space for object heap

Cause: The SAP BusinessObjects Enterprise Metadata Integrator does not have enough memory torun.

Action: Decrease the value of the MaxPermSize run-time parameter in the JVM Arguments on the"Parameters" page when you schedule the integrator source. For example, enter-XX:MaxPermSize=256m and rerun the metadata integrator.

6.1.6.4 Parsing failure

Parsing failure. Unable to find columns for SQL with select *.

Cause: The BusinessObjects Enterprise Metadata Integrator cannot collect the metadata for a universederived table if the SQL used in the derived table is of the form SELECT * FROM TABLE.

2011-04-06133


Action: Always use the fully-qualified column names in the projection list of the SELECT clause.

6.1.6.5 Parsing failure for derived table

Parsing failure for derived Table <table_name>. Unable to find tableassociated with column <column_name>

Cause: The SQL parser in the BusinessObjects Enterprise Metadata Integrator requires column namesin a derived table to be qualified by the table name: table_name.column_name. If you do not qualifythe column name, the Metadata Integrator cannot associate the column to the correct table.

Action: Fully qualify the column reference or add the tables used by the derived tables to the universe.The Metadata Integrator treats the universe tables as a system catalog to find the table and columnreferences.

6.1.6.6 Unable to parse SQL

Unable to parse SQL ... <error message>

Cause: The SQL parser in Metadata Management has limited parsing capabilities to extract columnnames and table names to build the relationships. For example, if a Metadata Integrator fails to parsethe SQL for a view, it cannot build the source-target relationship between the view and the table ortables upon which the view is based.

However, the Metadata Integrators collect the SQL statement and the Metadata Management Explorerdisplays it.

Action: Analyze the SQL statement in the Metadata Management Explorer and establish a user-definedrelationship for these tables and columns.

6.1.6.7 Unable to retrieve SQL to parse

Unable to retrieve SQL to parse. <error message>

The cause of this warning message can be one of the following:

Cause: You do not have sufficient privilege to extract metadata about Web Intelligence documents.

Action: Take one of the following actions:

2011-04-06134


• Have your administrator change your security profile to give you permission to refresh Web Intelligencedocuments.

• Run the Metadata Integrator with a different user id that has permission to refresh Web Intelligencedocuments.

Cause: If a database connection is not configured for Trusted Authentication in SAP BusinessObjectsBusiness Intelligence Platform, you must supply the user id and password at runtime. If you try to collectmetadata for a report that uses a non-Trusted connection to the database, the report collection fails.

Action: Configure both your SAP BusinessObjects Business Intelligence Platform server and client toenable Trusted Authentication. For details, see the SAP BusinessObjects Business Intelligence PlatformAdministrator Guide.

Cause: The extract for Web Intelligence documents fails if you create your Web Intelligence documentswith the Refresh on Open option and the computer on which you run the BusinessObjects EnterpriseMetadata Integrator does not have connection to the source database on which the reports are defined.

Action: Take one of the following actions:• Run the BusinessObjects Enterprise Information Steward on the computer where BusinessObjects

Enterprise is installed• Define the database connection on the computer where you run the BusinessObjects Enterprise

Metadata Management.

6.1.6.8 Connection with Data Federator Designer

If the Data Federator Integrator connects successfully to the Data Federator Designer, but Data Federatorreturns an error:1. Login to the Data Federator Designer.2. Within Data Federator Designer, you can obtain a more detailed error message.

6.1.7 Grouping Metadata Integrator sources

SAP BusinessObjects Information Steward provides the capability to group Metadata Sources intogroups such as Development System, Test System, and Production System. After the groups aredefined, you can view impact and lineage diagrams for a specific Source Group.

Related Topics• Creating source groups• Modifying source groups

2011-04-06135


6.1.7.1 Creating source groups

You must have the Add Objects right on the SAP BusinessObjects Information Steward Source groupfolder to create a Metadata Integrator source group.1. Log on to the Central Management Console (CMC) and access the Information Steward area.2. Select Source Groups node in the tree on the left on the page.3. Access the "Source Group" window in one of the following ways:

• Click the second icon "Create a Source Group" in the menu bar on top.• In the menu bar on top, click Manage > New > Source Group.

4. Define the configuration on the Source Group page.a. Enter the Name and Description.b. Select integrator sources to add to this source group by clicking the check box to the left of each

integrator source name.c. Click Save.

The new source group name appears on the right side of the page.

6.1.7.2 Modifying source groups

You must have the Edit right on the Metadata Integrator source group.1. Log on to the Central Management Console (CMC) and access the Information Steward area.2. Select Source Groups node in the tree on the left on the page.3. Select the source group that you want to modify.4. In the menu bar on top, click Actions > Properties.5. You can change any of the following properties of the source group:

• Name• Description• Integrator sources that you want to remove or add to the source group.

6. Click on User Security to do any of the following tasks:• Add principals to this source group.• View security for a selected principal.• Assign security for a selected principal.

7. Click Save.

2011-04-06136


6.1.7.3 Deleting source groups

You must have the Delete right on the Metadata Integrator source group.

1. Log on to the Central Management Console (CMC) and access the Information Steward area.2. Select Source Groups node in the tree on the left on the page.3. Select the source group that you want to delete.4. In the menu bar on top, click Manage > Delete.5. Click OK to confirm the deletion.

2011-04-06137


2011-04-06138


Cleansing Package Builder Administsration

7.1 Changing ownership of a cleansing package

Ownership can be reassigned only by an Information Steward administrator. You can change ownershiponly for private cleansing packages. Published cleansing packages are either unowned or linked toprivate cleansing packages and therefore when you change the ownership of a private cleansingpackage, the new owner automatically can republish to the linked cleansing package.

To reassign ownership of a cleansing package:1. Log in to the Central Management Console (CMC) as an administrator.2. At the CMC home page, click Information Steward.3. In the left pane, expand the Cleansing Packages node and then click Private.4. In the right pane, right-click the cleansing package whose owner you want to reassign. In the pop-up

menu, choose Properties to open the Properties window.Other ways of accessing the Properties window:• Choose Actions > Properties.• Click the link in the "Name" or "Kind" column for the desired cleansing package.

5. In the Properties window, choose a different owner in the "Owner" drop-down list, and click Save.

The new owner is now assigned to this cleansing package.

7.2 Deleting a cleansing package

To delete a private or published cleansing package:1. Log in to the Central Management Console (CMC) as an administrator.2. At the CMC home page, click Information Steward.3. In the left pane, expand the Cleansing Packages node and then click either Private or Published.4. In the right pane, right-click the cleansing package that you want to delete. In the pop-up menu,

choose Manage > Delete.5. In the confirmation window that opens, click OK.

The selected cleansing package is deleted.

2011-04-06139


7.3 Changing the description of a cleansing package

You can edit the description of published or private cleansing packages.

To edit the description:1. Log in to the Central Management Console (CMC) as an administrator.2. At the CMC home page, click Information Steward.3. In the left pane, click Cleansing Packages and then click Private or Published.4. In the right pane, right-click the cleansing package whose description you want to edit and select

Properties.Other ways of accessing the Properties window:• Choose Actions > Properties.• Click the link in the "Name" or "Kind" column for the desired cleansing package.

5. In the Properties window, edit the description, and click Save.

7.4 Unlocking a cleansing package

The status of a cleansing package is displayed in the status bar of the "Cleansing Package Tasks"screen and is also indicated by the cleansing package icon.

It may take some time for a cleansing package with a BUSY status to complete the operation andchange to a READY state. The state of a cleansing package with a BUSY status cannot be changedby an Information Steward administrator. You can either wait for the operation to complete or deletethe cleansing package.

When a cleansing package is opened for editing, it enters a locked state so that no other user may editit. To close a cleansing package, you must either return to the "Cleansing Package Tasks" screen,switch to another cleansing package, or log off from Cleansing Package Builder. If the browser windowis closed or the computer is shut down without logging off, the cleansing package may become locked.

A cleansing package may become locked when it is in any of the following states:• OPEN_FOR_READWRITE• CANCEL_AUTO_ANALYSIS• CANCEL_PUBLISHING• AUTO_ANALYSIS• PUBLISHED

To unlock a cleansing package:

2011-04-06140


1. (Data steward ) When you encounter a locked cleansing package ( , , or ) in the "CleansingPackage Tasks" screen, ask your Information Steward administrator to unlock it.

2. (Information Steward administrator) Change the cleansing package state from LOCKED to ERROR.a. Log in to the Central Management Console (CMC).b. Select Information Steward.c. Expand the "Cleansing Package" node and select Private or Published.d. Right-click the desired cleansing package, and choose Properties.e. Change the state to ERROR and click Save.f. Notify the data steward that the cleansing package state is updated to ERROR. .

The data steward must verify the condition of the cleansing package prior to further use

3. (Data steward) When notified that the cleansing package is unlocked and moved to the ERRORstate ( , , or ), do the following:a. From the "Cleansing Package Tasks" screen, open the cleansing package.b. Verify the condition of the cleansing package and that it displays information as expected.c. Close the cleansing package.

If the cleansing package is returned to a READY state and its condition was as you expected,you may use it.

If the cleansing package returns to the ERROR state or the condition was not as expected, thecleansing package is corrupt and should be deleted.

Related Topics• Cleansing package states and statuses

7.5 Cleansing package states and statuses

You can view cleansing package properties, including the state, in the following locations:• In the "Cleansing Package Tasks" screen.

In Cleansing Package Builder, in the "Cleansing Package Tasks" screen, hover over the desiredcleansing package to display the properties sheet.

• In the Information Steward area of the Central Management Console (must have Information Stewardadministrator privileges).

Log in to the Central Management Console (CMC). Select Information Steward. Expand the"Cleansing Package" node and select Private or Published. Right-click the desired cleansingpackage and choose Properties.

The table below describes the possible states for a cleansing package:

2011-04-06141


DescriptionState

Cleansing package is in good condition and available for editingor viewing.READY

Cleansing package is being created.CREATE

Cleansing package is being browsed and is in view-only mode.OPEN_FOR_READ

Cleansing package is open for editing.OPEN_FOR_READWRITE

Cleansing package is in the process of being published. Wait forpublishing to complete.PUBLISHING

Auto-analysis process is performed after a custom cleansingpackage is initially created.AUTO_ANALYSIS

The ERROR state occurs in two situations: Either 1) The cleansingpackage is possibly corrupt, or 2) The cleansing package waspreviously locked. An Information Steward administrator changedthe state to ERROR in an attempt to make the cleansing packageusable again. In either situation, a data steward must open thecleansing package, check the condition and close the cleansingpackage. If the cleansing package is returned to a READY state,it may be used. If the cleansing package is still in an ERRORstate, it is corrupt and should be deleted

ERROR

Data steward canceled the auto-analysis process. It may takesome time for the cleansing package to move to the READY state.CANCEL_AUTO_ANALYSIS

Data steward canceled the publishing process. It may take sometime for the cleansing package to move to the READY state.CANCEL_PUBLISHING

A cleansing package may have of the following statuses: READY, BUSY, LOCKED, ERROR. Thestatus of a cleansing package is displayed in the status bar of the "Cleansing Package Tasks" screenand is also indicated by the cleansing package icon. The following table shows the state, associatedicon and possible user action:

Possible user actionIconStatus

Open and edit or view the cleansing package., , orREADY

Wait for the process (auto-analysis or publishing) to complete or cancelthe process.

, , orBUSY

2011-04-06142


Possible user actionIconStatus

When a cleansing package is opened for editing, its status changes toLOCKED so that no other user may edit it.

Ensure that you do not have the cleansing package open in a differentbrowser window.

Wait at least 20 minutes for Cleansing Package Builder to automaticallyclose the cleansing package and restore it to a READY state.

Contact your Information Steward administrator to unlock the cleansingpackage from the Central Management Console (CMC). Unlocking acleansing package changes the cleansing package to an ERROR stateand status. For more information, see Unlocking a cleansing package

, , orLOCKED

Open the cleansing package and assess its condition. For more information,see Unlocking a cleansing package.

, , orERROR

The state of a cleansing package with a BUSY status cannot be changed by an Information Stewardadministrator. You can either wait for the operation to complete or delete the cleansing package.

A cleansing package with a LOCKED status can be unlocked by an Information Steward administrator.Unlocking a cleansing package changes its status to ERROR. Before further use, the condition of thecleansing package must be verified by a data steward.

Related Topics• Unlocking a cleansing package

2011-04-06143


2011-04-06144



8.1 Utilities overview

SAP BusinessObjects Information Steward provides the following utilities that you manage on the CMC.

DefaultSchedule

ConfigurablePropertiesDescriptionUtility

Daily

(You canchange thisdefaultschedule.)

None

Calculates scores of key data domains regularly for dataquality scorecards.

Note:You can also recalculate scorecards immediately fromthe Data Insight tab in Information Steward when youselect Now for the Show score as of option.

CalculateScore-card

None

(You eithercreate aschedule fora configuredutility or run itimmediately.)

Mode

(See Modify-ing utilityconfigura-tions)

Computes and stores end-to-end impact and lineage in-formation across all integrator sources for the Reportsoption in the Open drop-down list in the Metadata Man-agement module.

Information Steward provides a configured ComputeLineage Report utility that computes impact and lineagefor only the integrator sources that contain changes sincethe last time the computation was run. You can alsocreate another configuration to compute impact and lin-eage across all integrator sources.

ComputeLineageReport

2011-04-06145


DefaultSchedule

ConfigurablePropertiesDescriptionUtility

Daily

(You canchange thisdefaultschedule.)

None

Increases disk space in the repository in the followingways:1. Deletes database logs after integrator sources have

been deleted2. Deletes profile results, scores, and sample data that

have exceeded the configured retention period3. Purges logically deleted information that includes

sample data for profiling and rule tasks.

Note:If you want to delete profile results, scores, and sampledata for an individual table or file before the retentionperiod has been reached, see "Deleting profile resultsfrom the repository" in the User Guide.

Purge

None

(You eithercreate aschedule fora configuredutility or run itimmediately.)

Integratorsource

(See Modify-ing utilityconfigura-tions)

Recreates Metadata Management search indexes.

Information Steward provides a configured Search Indexutility that rebuilds the search indexes across all integratorsources. You can create additional configurations torecreate search indexes for specific integrator sources.

UpdateSearchIndex

Related Topics• Computing and storing lineage information for reporting• Recreating search indexes on Metadata Management• Scheduling a utility• Running a utility on demand• Monitoring utility executions• Modifying utility configurations• Creating a utility configuration

8.1.1 Computing and storing lineage information for reporting

The SAP BusinessObjects Information Steward Repository provides a lineage staging table,MMT_Alternate_Relationship, that consolidates end-to-end impact and lineage information across allintegrator sources. The Metadata Management module provides pre-defined Crystal Reports from this

2011-04-06146


table. You can also create your own reports from this table. To view the reports on the Reports optionin the Open drop-down list in the Metadata Management tab, they must be Crystal Reports (see"Defining custom reports" in the Users Guide).

Before generating reports that rely on this lineage staging table, you should update the lineage informationin the lineage staging table. You can either schedule or run the Compute Lineage Report utility ondemand to ensure those reports contain the latest lineage information.

The following activities can change the lineage information, and it is recommended that you run thelineage computation after any of these activities occur:• Run an Integrator to collect metadata from a source system (see "Running a Metadata Integrator"

in the Metadata Management Administration section).• Change preferences for relationships between objects (see "Changing preferences for relationships"

in the Users Guide). The data in the lineage staging table uses the values in Impact and LineagePreferences and Object Equivalency Rules to determine impact and lineage relationships acrossdifferent integrator sources.

• Establish or modify a user-defined relationship of type Impact or Same As (see "Establishinguser-defined relationships between objects" in the Users Guide).

Related Topics• Scheduling a utility• Running a utility on demand• Monitoring utility executions• Modifying utility configurations• Creating a utility configuration

8.1.2 Recreating search indexes on Metadata Management

The search feature of the Metadata Management module of SAP BusinessObjects Information Stewardallows you to search for an object that might exist in any metadata integrator source. When you run ametadata integrator source, Metadata Management updates the search index with any changedmetadata.

You might need to recreate the search indexes in situations such as the following:• The Search Server was disabled and could not create the index while running a metadata integrator

source.• The search index is corrupted.

Related Topics• Scheduling a utility• Running a utility on demand• Monitoring utility executions• Modifying utility configurations

2011-04-06147


8.2 Scheduling a utility

You would schedule a utility for reasons including the following:• To change the default frequency that the Calculate Scorecard utility is run to generate rule results

for the data quality trend graphs in Data Insight.• To change the default frequency that the Purge utility is run to increase space in the Information

Steward repository,• To schedule the Compute Lineage Report utility for Reports on Metadata Management.• To schedule the Update Search Index utility in Metadata Management.

To define or modify a schedule for a utility:1. Log in to the Central Management Console (CMC) with a user name that belongs to the Metadata

Management Administrator group or the Administrator group.2. At the top of the CMC Home screen, select Applications from the navigation list.3. Select Information Steward Application in the "Applications Name" list.4. Click Action > Manage Utilities in the top menu tool bar.5. From the list of "Utility Configurations", select the name of the utility configuration that you want to

schedule.6. In the top menu tool bar, click Actions > Schedule.7. If you do not want the default value for Instance Title:

a. Click Instance Title in the navigation tree in the left pane of the "Schedule" window.b. Change the title to a value you want.

8. To define the frequency to execute this utility:a. Click Recurrence in the navigation tree in the left pane of the "Schedule" window.b. Select the frequency in the Run object drop-down list.c. Select the additional relevant values for the recurrence option.

For a list of the recurrence options and the additional values, see Recurrence options.

9. Optionally, set the Number of retries to a value other than the default 0 and change the Retryinterval in seconds from the default value 1800.

10. If you want to be notified when this utility runs successfully or when it fails, expand Notification,and fill in the appropriate information. For more information about Notification, see the SAPBusinessObjects Business Intelligence Platform Administrator Guide.

11. If you want to trigger the execution of this utility when an event occurs, expand Events, and fill inthe appropriate information. For more information about Events, see the SAP BusinessObjectsBusiness Intelligence Platform Administrator Guide.

12. Click Schedule.13. If you want this newly created schedule to override the default recurring schedule for the Purge or

Calculate Scorecard utility, delete the old recurring instance.

2011-04-06148


a. From the list of "Utility Configurations", select the name of the utility whose schedule you wantto delete.

b. Click Actions > History.c. Select the recurring schedule that you want to delete and click the delete icon in the menu bar.

Note:To change the recurring schedule directly (instead of creating a new and deleting the old one), seeRescheduling a utility.

Related Topics• Computing and storing lineage information for reporting• Recreating search indexes on Metadata Management• Running a utility on demand• Monitoring utility executions• Modifying utility configurations• Creating a utility configuration

8.3 Rescheduling a utility

You would reschedule a utility for reasons including the following:• Change the default frequency that the Calculate Scorecard utility is run to generate rule results for

the data quality trend graphs in Data Insight.• Change the default frequency that the Purge utility is run to Increase space in the Information Steward

repository.• If you setup a recurring schedule for the Compute Lineage Report utility and you want to change

the schedule to compute the lineage information for Reports on Metadata Management.• If you setup a recurring schedule for the Update Search Index utility and you want to change the

schedule to rebuild the search indexes in Metadata Management.

To reschedule a utility:1. Login to the Central Management Console (CMC) with a user name that belongs to the Metadata

Management Administrator group or the Administrator group.2. At the top of the CMC Home screen, select Applications from the navigation list.3. Select Information Steward Application in the "Applications Name" list.4. Click Action > Manage Utilities in the top menu tool bar.5. From the list of "Utility Configurations", select the name of the utility configuration that you want to

reschedule.6. In the top menu tool bar, click Actions > History.7. On the "Utility History" screen, select the schedule name with that has a schedule status of "Recurring"

and click Reschedule in the top menu bar.a. Click Recurrence in the navigation tree in the left pane of the "Reschedule" window.

2011-04-06149


b. Select the frequency in the Run object drop-down list.c. Select the additional relevant values for the recurrence option.

For a list of the recurrence options and the additional values, see Recurrence options.d. If you want to provide a different name for this schedule, click Instance Title in the navigation

tree and enter the name.

8. Click Schedule.The newly created "Recurring" schedule appears on the "Utility History" screen.

9. Delete the original "Recurring" schedule:a. From the list on the "Utility History" window, select the original "Recurring" schedule.b. Click the Delete icon.

8.4 Running a utility on demand

To run an Information Steward utility on demand:1. Login to the Central Management Console (CMC) with a user name that belongs to one or more of

the following administration groups:• Data Insight Administrator• Metadata Management Administrator• Administrator

2. At the top of the CMC Home screen, select Applications from the navigation list.3. Select Information Steward Application in the "Applications Name" list.4. Click Action > Manage Utilities in the top menu tool bar.

The list of configured utilities displays with the date and time each was last run.

5. From the "Utility Configurations" list, select the name of the utility you want to run.6. In the top menu tool bar, click Action > Run Now.

Caution:If an instance of the lineage report utility is still running, do not start another lineage report utility run.Starting another utility run might cause deadlocks or delays. The same behavior might occur if youstop the utility and start another instance right away because the process might still be running inthe repository.

7. On the "Utility Configurations" screen, click the Refresh icon to update the "Last Run" column forthe utility configuration.

Related Topics• Computing and storing lineage information for reporting• Recreating search indexes on Metadata Management• Scheduling a utility• Monitoring utility executions

2011-04-06150


• Modifying utility configurations• Creating a utility configuration

8.5 Monitoring utility executions

To look at the status of or the progress of a utility run:1. Login to the Central Management Console (CMC) with a user name that belongs to one or more of

the following administration groups:• Data Insight Administrator• Metadata Management Administrator• Administrator

2. At the top of the CMC Home screen, select Applications from the navigation list.3. Select Information Steward Application in the "Applications Name" list.4. Click Action > Manage Utilities in the top menu tool bar.

The list of configured utilities displays with the date and time each was last run.

5. Click the Refresh icon to update the "Last Run" column on the "Utility Configurations" screen.6. To view the status of the utility run, select the utility configuration name and click Action > History.

The "Schedule Status" column can contain the following values:


The utility did not complete successfully.Failed

The utility is scheduled to run one time. When it actually runs, there willbe another instance with status “Running."Pending

The utility is scheduled to recur. When it actually runs, there will be anotherinstance with status “Running."Recurring

The utility is currently executing.Running

The utility completed successfully.Success

7. To see the progress of a utility instance:a. Select the instance name and click the icon for View the database log in the top menu bar of

the "Utility History" screen.The "Database Log" window shows the utility messages.

b. To find specific messages in the "Database Log" window, enter a string in the text box and clickFilter.For example, you might enter error to see if there are any errors.

2011-04-06151


c. To close the "Database Log" window, click the X in the upper right corner.

8. To save a copy of a utility log:a. Scroll to the right of the "Utility History" screen, and click the Download link in the "Log File"

column in the row of the utility instance you want.b. Click Save.c. On the "Save As" window, browse to the directory where you want to save the log and optionally

change the default file name.

9. To close the "Utility History" screen, click the X in the upper right corner.

Related Topics• Computing and storing lineage information for reporting• Recreating search indexes on Metadata Management• Scheduling a utility• Running a utility on demand• Modifying utility configurations• Creating a utility configuration

8.6 Modifying utility configurations

SAP BusinessObjects Information Steward provides a default configuration for each of the utilities. Youcan modify the configuration settings for the following utilities:• Compute Lineage Report utility

The default configuration for the Compute Lineage Report utility has Mode set to Optimized whichrecalculates lineage information in the lineage staging table for only integrator sources that havechanged since the utility was last run. You might want to set Mode to Full to recalculate lineageinformation across all integrator sources.

• Update Search Index utility

The default configuration for the Update Search Index utility has Integrator Source set to AllSources, which rebuilds the search indexes in Metadata Management for all integrator sources.You might want to set Integrator Source to a specific integrator source to rebuild search indexesfor the metadata collected for only that integrator source.

Note:The Calculate Scorecard and Purge utilities do not have configuration parameters.

To change the configuration of a utility:1. Login to the Central Management Console (CMC) with a user name that belongs to the Metadata

Management Administrator group or the Administrator group.2. Select Applications from the navigation list at the top of the CMC Home screen.3. Select Information Steward in the "Applications Name" list.

2011-04-06152


4. Click Action > Manage Utilities in the top menu tool bar.5. Select the utility whose configuration you want to change.6. Click Actions > Properties in the top menu tool bar.

The "Utilities Configurations" screen appears.

7. For a Compute Lineage Report utility, you can change the following parameters:• Description• Mode

Mode can be set to one of the following values:• Full mode recalculates all impact and lineage information and repopulates the entire lineage

staging table.

Note:If you select Full mode, the computation can take a long time to run because it recalculatesimpact and lineage information across all integrator sources.

• Optimized mode (the default) recalculates recalculates impact and lineage information foronly the integrator sources that contain changes since the last time the computation was run.For example, if only one Integrator was run, the computation only recalculates impact andlineage information corresponding to that integrator source and updates the lineage stagingtable.

8. For an Update Search Index utility, you can change the following parameters:• Description• Integrator Source

• All Sources recreates the search index for all integrator sources that you have configured.• The specific name of an integrator source that appears in the drop-down list.

9. Click Save.

Related Topics• Computing and storing lineage information for reporting• Recreating search indexes on Metadata Management• Scheduling a utility• Running a utility on demand• Monitoring utility executions• Creating a utility configuration

8.7 Creating a utility configuration

SAP BusinessObjects Information Steward provides a default configuration for each of the utilities. Youcan define another configuration with different settings and still keep the default configuration for thefollowing utilities:

2011-04-06153


• Compute Lineage Report utility

The default configuration for the Compute Lineage Report utility has Mode set to Optimized whichrecalculates lineage information in the lineage staging table for only integrator sources that havechanged since the utility was last run. You might want to configure another Compute Lineage Reportutility with Mode set to Full to recalculate lineage information across all integrator sources.

• Update Search Index utility

The default configuration for the Update Search Index utility has Integrator Source set to AllSourceswhich rebuilds the search indexes in Metadata Management for all integrator sources. Youmight want to configure another Update Search Index utility with Integrator Source set to only oneof the integrator sources to rebuild indexes for the metadata collected for only that integrator source.

Note:You cannot define another configuration for the Calculate Scorecard and Purge utilities.

To define a new configuration for a utility:1. Login to the Central Management Console (CMC) with a user name that belongs to any of the

following groups:• Metadata Management Administrator• Administrator

2. Select Applications from the navigation list at the top of the CMC Home screen.3. Select Information Steward in the "Applications Name" list.4. Click Action > Manage Utilities in the top menu tool bar.5. On the "Utilities Configurations" screen, click Manage > New Utility Configuration... in the top

menu tool bar.6. In the Utility Type drop-down list, select the utility you want to create a new configuration for.7. Type a Name and Description for the utility.8. If you want to recalculate the entire impact and lineage information across all integrator sources,

change the Mode default value from Optimized to Full.9. If you want to to rebuild indexes for the metadata collected for only one integrator source, select its

name from the Integrator Source drop-down list.10. Click Save.

The new name appears on the new Utility Configurations screen.

Related Topics• Computing and storing lineage information for reporting• Recreating search indexes on Metadata Management• Scheduling a utility• Running a utility on demand• Monitoring utility executions• Modifying utility configurations

2011-04-06154


Server Management

9.1 Server management overview

SAP BusinessObjects Information Steward uses the following types of servers:• SAP BusinessObjects Business Intelligence platform servers that are collections of services running

under a Server Intelligence Agent (SIA) on a host. Information Steward uses the following serversand services:

Enterprise Information Management Adaptive Processing Server which has the following services:• Cleansing Package Builder Auto-analysis Service• Cleansing Package Builder Core Service• Cleansing Package Builder Publishing Service• Information Steward Administrative Task Service• Metadata Relationship Service• Metadata Search Service• Data Services Metadata Browsing Service• Data Services View Data Service

Information Steward Job Server which has the following services:• Information Steward Task Scheduling Service• Information Steward Integrator Scheduling Service

• SAP BusinessObjects Data Services Job Server which executes the Data Insight profiling tasks.You can create multiple Job Servers, each on a different computer, to use parallel execution for theprofiling tasks.

For a description of these servers and services, see Servers and services.

This section describes how to manage the above servers for Information Steward.

9.2 Verifying Information Steward servers are running

To verify that the SAP BusinessObjects Information Steward servers are running and enabled:1. From the CMC Home page, go to the "Servers" management area.2. Expand the Service Categories node and select Enterprise Information Management Servers.

2011-04-06155

Server Management

The list of servers in the right pane includes a State column that provides the status for each serverin the list.

3. Verify that the following Enterprise Information Management Servers servers are “Running” and“Enabled”.• "EIMAdaptiveProcessingServer"• "ISJobServer"

4. If a Enterprise Information Management Servers server is not running or enabled, do the following:a. Select the server name from the list.b. Open the Actions drop-down menu and select Start Server or Enable Server.

For information about the services that run under Enterprise Information Management Servers , seethe “Architecture” section.

Related Topics• Services

9.3 Verifying Information Steward services

To verify that the SAP BusinessObjects Information Steward services were added:1. From the CMC Home page, go to the "Servers" management area.2. Expand the Service Categories node and select Enterprise Information Management Services.

The right pane lists the following servers:• "EIMAdaptiveProcessingServer"• "ISJobServer"

3. Ensure that the relevant services appear for "EIMAdaptiveProcessingServer".a. Right-click "EIMAdaptiveProcessingServer" and click Stop Server.b. Right-click "EIMAdaptiveProcessingServer" and click Select Services.c. Verify that for each Information Steward feature that you installed, the list of services for

EIMAdaptiveProcessingServer includes the following services:

Services

Information Steward Job Server(ISJobServer)EIM Adaptive Processing ServerFeature Installed

• Information Steward TaskScheduling Service

• Information Steward IntegratorScheduling Service

Information Steward Admin TaskServiceInformation Steward Task Server

2011-04-06156

Server Management

Services

Information Steward Job Server(ISJobServer)EIM Adaptive Processing ServerFeature Installed

NoneInformation Steward Metadata Re-lationship ServiceMetadata Relationship Service

NoneSearch ServiceMetadata Search Service

None

• Cleansing Package BuilderCore service

• Cleansing Package Builder Au-to-analysis service

• Cleansing Package BuilderPublishing service

Cleansing Package Builder Ser-vice

• Information Steward IntegratorScheduling Service

• Information Steward IntegratorService

NoneAll Metadata Integrators

d. If any of the EIMAdaptiveProcessingServer services are not in the list on the right, select theservice name from the "Available services" list on the left, click > to add it, and click OK.

e. Right-click "EIMAdaptiveProcessingServer" and click Start Server.

4. Ensure that the relevant services appear for "ISJobServer".a. Right-click "ISJobServer" and click Stop Server.b. Right-click "ISJobServer" and click Select Services.c. Verify that for each Information Steward feature that you installed, the list of services for

"ISJobServer" includes the services listed in the table in step 3c.d. If any of the "ISJobServer" services are not in the list on the right, select the service name from

the "Available services" list on the left, click > to add it, and click OK.e. Right-click "ISJobServer" and click Start Server.

9.4 Configuring Metadata Browsing Service and View Data Service

The installation process of SAP BusinessObjects Data Services configures the following services (underthe server EIMAdaptiveProcessingServer) with default settings.• Metadata Browsing Service• View Data ServiceThese services are used by SAP BusinessObjects Information Steward to connect and view data inprofiling sources. You might want to change the configuration settings to more effectively integrateInformation Steward with your hardware, software, and network configurations.

2011-04-06157

Server Management

1. Go to the "Servers" management area of the CMC.2. Expand "Service Categories" in the tree panel and select "Enterprise Information Management

Services".3. Double-click computername."EIMAdaptiveProcessingServer " in the list in the right pane.4. On the "Properties " window, scroll down until you find the service whose settings you want to change.5. Make the changes you want, then click Save or Save & Close.

Note:Not all changes occur immediately. If a setting cannot change immediately, the "Properties " windowdisplays both the current setting (in red text) and the updated setting. When you return to the Serversmanagement area, the server will be marked as Stale. When you restart the server, it will use theupdated settings from the Properties dialog box and the Stale flag is removed from the server.

Related Topics• Metadata Browsing Service configuration parameters• View Data Service configuration parameters

9.4.1 Metadata Browsing Service configuration parameters

You can change the following properties of the Metadata Browsing Service.

Possible ValuesDescriptionServer Configuration Pa-rameter

Alphanumeric string with amaximum length of 64. TheService Name cannot containany spaces.

Default value: MetadataBrows-ingService

Name of the service configuration.Service Name

integer.

Default value: 200

Maximum number of data source connectionsthat can be opened at any time under a serviceinstance.

Maximum Data SourceConnections

Default value: 1Maximum number of attempts to launch a newservice provider when there is contention to ac-cess a shared service provider.

Retry attempts to launchService Provider

Default value: 1200Maximum duration which a stateful connection isopen. Stateful connections include SAP Applica-tions and SAP BW Source.

Stateful ConnectionTimeout (seconds)

2011-04-06158

Server Management


Default value: 1200Maximum duration which a stateless connectionis open. Stateless connections include all relation-al database sources.

Stateless ConnectionTimeout (seconds)

Default value: 50000

Maximum number of requests that will be pro-cessed by a service before the Data Servicesbackend engine is recycled to free memory thatwas allocated for metadata browsing.

Recycle Threshold

Default is enabled.Enable or disable logging of trace messages tothe log file.Enable Trace

Default is enabled.Enable or disable the collection of statistic infor-mation for each open connection.

Collect ConnectionStatistics

Four-digit port number that isnot currently in use.

Default value: 4010

Port number used to communicate with the DataServices backend engine.

If you change the port number, you must restartthe EIMAdaptiveProcessingServer for the changeto take effect.

Listener Port

Four-digit port number that isnot currently in use.

Default value: 4011

Port number used for the JMX Connector.


JMX Connector Port

9.4.2 View Data Service configuration parameters

You can change the following properties of the View Data Service.


Alphanumeric string with amaximum length of 64. TheService Name cannot containany spaces.

Default value: ViewData

Name of the service configuration.Service Name

2011-04-06159

Server Management


Four-digit integer.

Default value: 4012

Port number used to communicate with the DataServices backend engine.


Listener Port

Four-digit integer.

Default value: 4013

Port number used for the JMX Connector.


JMX Connector Port

Minimum value: 1000

Maximum value: 50000

Default value: 1000

Size of the data to be stored in a view data re-sponse.Batch Size (kilobytes)

Default value: 1Minimum number of shared Data Services back-end engines that need to be launched at thestartup time of the service.

Minimum Shared ServiceProviders

Default value: 5Maximum number of shared Data Servicesbackend engines that can be launched during thetime to service the view data requests.

Maximum Shared ServiceProviders

Default value: 10Maximum number of dedicated Data Servicesbackend engines that can be launched at any in-stant of time.

Maximum Dedicated Ser-vice Providers

Any integer.

Default value: 200

Maximum number of requests that will be pro-cessed by a service before the Data Servicesbackend engine is recycled to free memory thatwas allocated for viewing data.

Recycle Threshold

Default value: 1Number of attempts to be made to try launchingthe Data Services backend engine instance.

Number of attempts tolaunch service provider

Default value: 120

Maximum number of minutes that a Data Servicesbackend engine can remain without processingany requests. After this time is exceeded, theData Services backend engine is shut down.

Maximum idle time forshared service provider(minutes)

Default is enabled.Specifies whether to enable or disable logging oftrace messages to the log file.Enable Trace

2011-04-06160

Server Management

9.5 Job server group

The SAP BusinessObjects Data ServicesJob Server performs the profile and rule tasks on data in DataInsight connections. The Information Steward Task Server sends Data Insight profile tasks to the DataServicesJob Server which partitions the data and uses parallel processing to deliver high data throughputand scalability.

This section contains the tasks to manage Data ServicesJob Servers for Information Steward.

Related Topics• Configuring a Data Services Job Server for Data Insight• Adding Data Services Job Servers for Data Insight• Displaying job servers for Information Steward• Removing a job server

9.5.1 Configuring a Data Services Job Server for Data Insight

If you will run Data Insight profile and rule tasks, you must access the Data Services Server Managerto create a job server and associate it with the Information Steward repository. This association addsthe job server to a pre-defined Information Steward job server group that Data Insight will use to runtasks. For details about how job server groups improve performance, see the “Performance and SizingConsiderations” section in the Administrator Guide.

To configure a job server and associate it with the Information Steward repository:1. Access the Data Services Server Manager from the Windows Start menu:

Start > Programs > SAPBusinessObjects Data Services XI 4.0 >Data Services Server Manager

2. On the "Job Server" tab, click Configuration Editor.3. On the "Job Server Configuration Editor" window, click Add.4. In the "Job Server Properties" window, enter a name for Job Server name.5. In the "Associated Repositories" section, click Add and fill in the "Repository Information" of the

Information Steward repository that you want to associate with this Job Server.• Database type• Database Server name• Database name• Username• Password

6. Click Apply and OK.

2011-04-06161

Server Management

The "Job Server Configuration Editor" window now displays the job server you just added.

7. Click Close and Restart to restart the job server with the updated configurations.

For more information about using the Data ServicesServer Manager, see “Server management” in theSAP BusinessObjects Data Services Administrator's Guide.

9.5.2 Adding Data Services Job Servers for Data Insight

If you installed additional Data Services Job Servers on multiple computers, you can use them to runData Insight profile and rule tasks even though Information Steward is not installed on those computers.

On each computer where a Data Services Job Servers is installed, you must add a job server to thepre-defined Information Steward job server group. For details, see Configuring a Data Services JobServer for Data Insight.

For more information about job server groups, see “Performance and Sizing Considerations” in theAdministrator Guide.

Related Topics• Displaying job servers for Information Steward• Removing a job server

9.5.3 Displaying job servers for Information Steward

To display the job servers that are associated with your SAP BusinessObjects Information Stewardrepository:1. Log in to the Central Management Console (CMC) with a user name that belongs to the Metadata

Management Administrator group or the Administrator group.2. At the top of the CMC Home screen, select Applications from the navigation list.3. Select Information Steward Application in the "Applications Name" list.4. Click Action > View Data Services Job Server in the top menu tool bar.

The "Job Server List" screen displays:• The name of each Data Server Job Server associated with the Information Steward repository.• The computer name and port number for each Data Server Job Server.

Related Topics• Configuring a Data Services Job Server for Data Insight

2011-04-06162

Server Management

9.5.4 Removing a job server

To remove a job server from the Information Steward job server group on Data Services:1. On each computer where you installed additional Data Service Job Servers, access the Data Services

Server Manager from the Windows Start menu:Start > Programs > SAPBusinessObjects Data Services XI 4.0 >Data Services Server Manager

2. On the "Job Server" tab, click Configuration Editor.3. On the "Job Server Configuration Editor" window, select the name of the job server you want to

delete and click Delete.4. In the "Job Server Properties" window, in the "Associated Repositories" section, ensure the name

of your Information Steward repository is selected and click Delete.5. In the " Repository Information" section, enter the password of your Information Steward repository

and click Apply.

6. Click Yes on the prompt that asks if you want to remove persistent cache tables.7. Click OK to return to the "Job Server Manager" window.8. Click Close and Restart and then click OK to restart the Data Services job server with the updated

configuration.

Related Topics• Configuring a Data Services Job Server for Data Insight• Adding Data Services Job Servers for Data Insight• Displaying job servers for Information Steward

2011-04-06163

Server Management

2011-04-06164

Server Management

Performance and Scalability Considerations

10.1 Resource intensive functions

The main Information Steward functions that influence performance and sizing are as follows.

Data profilingInformation Steward can perform basic and advanced data profiling operations to collect informationabout data attributes like minimum, maximum values, pattern distribution, data dependency, uniqueness,address profiling, and so on. These operations require intense, complex computations and are affectedby the amount data that is processed.

Validation rule processingInformation Steward validates source data against business rules to monitor data quality and generatescores. This also is a computation heavy process and affects performance based on the number ofrecords and the number of rules.

Complexity of rules also affects performance. For example, if you have lookup functions in ruleprocessing, it takes more time and disk space. Typically, lookup tables are small, but if they are big, itcan adversely affect performance.

Cleansing Package BuilderThe Auto-analysis service for Cleansing Package Builder is the process that is performed after a customcleansing package is initially created. Auto-analysis service analyzes the sample data that was providedduring the steps in the wizard to create a custom cleansing package. Some of the analyzing that isperformed is grouping similar records, and generates parsing rules based on analysis of combinationsof parsed values found in the data. With a large number of records and parsed values, this becomesvery computation and memory intensive.

Metadata integratorsMetadata integrators collect metadata about different objects in the source systems and store it in theInformation Steward repository. If a large amount of metadata is being collected, it can affect performanceand the size of the repository.

Lineage and impact analysisAfter the metadata is collected, Information Steward can do end-to-end lineage and impact calculations.Typically, these are periodically run as utilities to capture the latest information. If the amount of metadatais large, this calculation can affect performance.

2011-04-06165


Metadata browsing and view dataYou can browse metadata for tables and columns and also view source data. If table has a large numberof columns, the View Data operation is affected because a lot of data must be accessed, transferred,and displayed in the user interface.

Related Topics• Factors that influence performance and sizing• Scalability and performance considerations• Best practices for performance and scalability

10.2 Architecture

The following diagram shows the architectural components for SAP BusinessObjects BusinessIntelligence platform, SAP BusinessObjects Data Services, and SAP BusinessObjects InformationSteward. The resource-intensive servers and services are indicated with a red asterisk:• Data Services Job Server processes data profiling and rule validation tasks in Data Insight.• Cleansing Package Builder Auto-analysis Service analyzes sample data and generates parsing

rules for Cleansing Package Builder.• Information Steward Integrator Scheduling Service processes Metadata Integrators.• Metadata Relationship Service performs lineage and impact analysis.• Data Services Metadata Browsing Service obtains metadata from Data Insight connections.• Data Services Viewdata Service obtains the source data from Data Insight connections.• Web Applicaiton Server handles requests from users on the web applications for Information Steward.For more details about these servers and services, see Servers and services.

2011-04-06166


10.3 Factors that influence performance and sizing

Use Information Steward to work on large amounts of data and metadata. The following factors affectthe performance and sizing. These factors affect the required processing power (CPUs), RAM, andhard disk space (for temporary files during processing) and the size of the Information Steward repository.

Related Topics• Data characteristics and profiling type• Number of concurrent users

10.3.1 Data Insight

2011-04-06167


10.3.1.1 Amount of data

The amount of the data is calculated using the number of records and the number of columns. In general,the more data that is processed, the more time and resources it requires. This is true for profiling andrules validation operations. The data may come from one or more sources, multiple tables within asource, views, or files.

This factor affects the required CPU, RAM, and hard disk space and the Information Steward repositorysize. The larger the record size, the more resources are required for efficient processing.

If the data being processed has many columns, it requires more time and resources. If you are doingcolumn profiling on many columns or if the columns being processed have long textual data, it affectsperformance. In short, if the record length is more, more resources are required.

Related Topics• Factors that influence performance and sizing

10.3.1.2 Data characteristics and profiling type

For distribution profiling such as Value, Pattern, or Word distribution, if the data has many distinct values,patterns, or words, it requires more resources and time to process.

This factor affects the required CPUs, RAM, and Information Steward repository size. The more distinctthe data, the more resources required.


10.3.1.3 Number of concurrent users

Information Steward is a multi-user web-based application. As the number of concurrent users increases,it affects practically all aspects of the application. More users may mean more profiling tasks, morescorecard views and rule execution, and so on. The key word is concurrent.

2011-04-06168


If all users run tasks concurrently, it affects the required CPUs, RAM, and hard disk and the InformationSteward repository size. If most of the users are just viewing the scorecard, then the performancedepends more on the web application server where the Information Steward repository is created.


10.3.2 Metadata Management

10.3.2.1 Number of metadata sources

Metadata integrators collect metadata from various sources. As the number of metadata sourcesincreases, it takes more resources and time. This factor affects the required CPUs, RAM, and InformationSteward repository size.



If multiple users view impact and lineage information concurrently, it affects the response time.


10.3.3 Cleansing Package Builder

2011-04-06169


10.3.3.1 Amount of sample data

For Cleansing Package Builder, the amount of sample data used to create the cleansing package affectsthe performance of the Auto-analysis service. This in turn can affect response time for the user interface.


10.3.3.2 Data characteristics

When you create custom cleansing packages, if there are many parsed values per row, it requires moreresources and time to analyze and create parsing rules. For Cleansing Package Builder, the larger thedata set, the more CPU processing power is required. The more parsed values per row, the more RAMis required.



If there many users create custom cleansing packages concurrently, it requires more CPUs and RAM.


10.4 Scalability and performance considerations

2011-04-06170


Information Steward uses SAP BusinessObjects Business Intelligence platform and Data Servicesplatform for most of the heavy computational work. It inherits the service-oriented architecture providedby these platforms to support a reliable, flexible, highly available, and high performance environment.

Here are some features and recommendations for using the platforms for performance. These are notmutually exclusive, nor are they sufficient by themselves in all cases. You should employ a combinationof the following ways to improve throughput, reliability, and availability of the deployment.

Related Topics• Resource intensive functions• Factors that influence performance and sizing• Best practices for performance and scalability• Information Steward web application• Scheduling tasks• Queuing tasks• Degree of parallelism• Grid computing• Multi-threaded file read• Data Insight result set optimization• Performance settings for input data• Settings to control repository size• Settings for Metadata Management• Settings for Cleansing Package Builder

10.4.1 Scalability levels in deployment

A typical Information Steward environment can be scaled at the following levels:1. Web tier level: Deploy multiple instances of Information Steward web application for high availability

and large numbers of concurrent users.2. Business Intelligence platform and Information Steward services level: Deploy multiple Business

Intelligence platform services and/or Information Steward services in a distributed environment forload balancing and scalability. For example, you can deploy multiple metadata integrators on differentservers for load balancing. You can also have multiple Information Steward task servers on differentservers for high availability.

3. Data Services Job Server level: A Data Services Job Server group used for a given InformationSteward deployment can have one or more Data Services Job Servers added to it. As the need forData Services processing increases (for Data Insight operations), you can scale by adding moreData Services Job Servers to the Job Server group.

Related Topics• Scalability and performance considerations• Information Steward web application

2011-04-06171


10.4.2 Distributed processing

Business Intelligence platform provides a distributed scalable architecture. This means that servicesthat are needed for a specific functionality can be distributed across machines in the given landscape.As long as the services are in the same Business Intelligence platform environment, it doesn't matterwhich machine they are on; they just need to be in the same CMS cluster. The Information Stewardweb application and the Information Steward repositories can be on different machines.

Information Steward uses some Business Intelligence platform services, and also has its own servicesthat can be distributed across machines for better throughput. The general principle is that if one of theservices needs many resources, then it should be on a different machine. Similarly, if you add capacityto existing hardware, it can be used for more than one service.

The Data insight module of Information Steward uses the Data Services Job Server, which supportsdistributed processing.

This section offers some recommendations on different combinations of Information Steward servicesthat can be combined or decoupled.

Related Topics• Scalability and performance considerations• Data Insight related services• Metadata Management related services• Cleansing Package Builder related services• Information Steward repository• Information Steward web application• Grid computing

10.4.2.1 Data Insight related services

The most important part of the processing for Data insight is done by the Data Services Job Server.You can install Data Services Job Servers on multiple machines and make them part of the single jobserver group that is used for Information Steward. The profiling and rules tasks are distributed by theInformation Steward Job Server to the Data Services Job Server group. The actual tasks are executedby a specific Data Services Job Server based on the resource availability on that server. So, if oneserver is busy, the task can be processed by another server. This way, multiple profiling and rule taskscan be executed simultaneously.

Related Topics• Scalability and performance considerations

2011-04-06172


• Information Steward web application

10.4.2.2 Metadata Management related services

For Metadata Management, two important services from a performance perspective are the metadatarelationship service and metadata integrators.

Generally, these two services should be on separate servers (or should run at different times, if theyare on the same server). If there are many metadata integrators and they collect a lot of metadata fromdifferent sources, each one of them could be on a separate server.

Schedule intensive processing integrators to run at non-commercial hours.


10.4.2.3 Cleansing Package Builder related services

The Auto-analysis service is a resource intensive service in Cleansing Package Builder. The CPU andRAM requirements depend on the number of parsed values found in the data. Also, if multiple concurrentusers create large cleansing packages, it is recommended that you dedicate one server to theAuto-analysis service and allocate enough memory to the Java process.

Related Topics• Scalability and performance considerations• Information Steward web application• Common runtime parameters for Information Steward

10.4.2.4 Information Steward repository

The Information Steward repository stores all of the metadata collected, profiling and rule results, andsample data. The repository should be on a separate database server. To avoid resource contention,

2011-04-06173


the database server should not be the same database server that contains the source data. This mayor may not be on the same database server that hosts the Business Intelligence platform repository.

The Information Steward repository should be on the same subnetwork as the Data Services Job Serverthat processes large amounts of data and the metadata integrator that processes the largest amountof metadata.


10.4.2.5 Information Steward web application

Typically all web applications are installed on a separate server with other web applications. No otherservices or repositories are typically installed with the web application, so that response time forInformation Steward user interface users is not affected by services that process data.


10.4.3 Scheduling tasks

Information Steward runs many tasks that are resource intensive. Business Intelligence platform providesthe ability to schedule them. This ability can be used to distribute the tasks so that the same resourcescan be utilized for multiple purposes. The following can be scheduled:• Profiling tasks• Rule tasks• Metadata integrators• Calculate Scorecard utility• Compute Lineage report utility• Purge utility• Update search index utility

If you schedule these tasks so that they run at different times and when few users access the system,you can achieve good performance with limited resources. This time slicing is highly recommended forprofiling, rules tasks, and metadata integrators. For example, if you have users that process profiling

2011-04-06174


tasks on demand during business hours, then the metadata integrators and rules task should bescheduled during non-business hours.

If there are large profiling jobs, they should be scheduled during non-business hours and ideally on adedicated powerful server.

Related Topics• Scalability and performance considerations• Scheduling a task• Scheduling a utility

10.4.4 Queuing tasks

Information Steward can queue when there are many Data Insight tasks that are requested to run atthe same time. This depends on the user configuration for the Average Concurrent Tasks option.Based on this setting and the number of Data Services Job Servers in the group, Information Stewardcalculates the total number of tasks allowed to run simultaneously in a given landscape. Only that manytasks are sent to the Data Services Job Server group for processing. The remaining tasks are queued.As soon as one of the running tasks finishes, the next task in the queue is processed.

Using this setting, you can control how many Data Insight-related processes are running so that theresources can be utilized and scheduled for other processes running on the system.

Related Topics• Scalability and performance considerations• Configuration settings

10.4.5 Degree of parallelism

For Data Insight functionality, Information Steward uses the Data Services engine. The Data Servicesengine supports parallel processing in multiple ways, one of which is Degree of Parallelism (DOP). Thebasic idea is to split a single Data Services job into multiple processing units and utilize availableprocessing power (CPUs) on a server to work on those processing units in parallel. The distribution ofwork is different for profiling vs. rule processing.

Note:

• DOP is only used for Data Insight functionality for column profiling and rule processing. MetadataManagement and Cleansing Package Builder do not use DOP.

2011-04-06175


• In general, do not set the DOP more than the number of available CPUs. To fine tune the performance,set the DOP value based on the number of concurrent tasks and available hard disk and RAMresources. Gradually increase the value of DOP to reach an optimal setting. For more information,see the SAP BusinessObjects Data Services Performance Optimization Guide.

Related Topics• Scalability and performance considerations• Column profiling• Rule processing• Hard disk requirements• When to use degree of parallelism

10.4.5.1 Column profiling

For column profiling, the task is distributed proportionately for different number of columns. The formulais: Number of execution units = Number of Columns / DOP.

For example, if there is a column profiling task for 100 million rows with 20 columns, with DOP = 4, thetask will be broken down in execution units that work on 5 columns each for all 100 million rows. Thedata is "partitioned" for 5 columns each for each execution unit to work on.

Using multiple CPUs simultaneously causes the throughput to increase proportionately.

Related Topics• Scalability and performance considerations• Degree of parallelism

10.4.5.2 Advanced profiling

Advanced profiling tasks (dependency, redundancy, and uniqueness) require complex sorting operations,so it is important to optimize the degree of parallelism settings. The degree of parallelism setting is usedto execute sorting operations in parallel sorting operations to increase throughput.


2011-04-06176


10.4.5.3 Rule processing

For rule processing, the number of execution units is proportional to the number of rules (as opposedof number of columns for profiling). The formula is: Number of execution units = Number of rules / DOP.

For example, if there is a rule execution task for 100 million rows with 20 rules, with DOP = 4, the taskwill be broken down in execution units that processes 5 rules each for all 100 million rows.


10.4.5.4 Hard disk requirements

Adding CPUs and increasing DOP does not guarantee improved throughput. When many processesrun in parallel, they also share other hardware resources such RAM and hard disk.

When the Data Services engine processes data, it creates temporary work files in the Pageable CacheDirectory. Naturally, if many processes are running simultaneously, all of them create temporary filesin the same location. Because this directory is accessed by all of the processes simultaneously, thereis a potential for disk contention. In most environments, depending on the hard disk capacity and speed,you will hit a ceiling after which an increase in DOP will not improve performance proportionately.

Therefore, it is important to enhance all aspects of the hardware at the same time: the number of CPUs,hard disk capacity, speed, and RAM. You should have a very efficient disk access to go along with theincreased number of DOP. Make sure the pageable cache directory is set accordingly.

Related Topics• Scalability and performance considerations• Degree of parallelism• Grid computing

10.4.5.5 When to use degree of parallelism

Higher DOP should be employed in the following conditions:

2011-04-06177


• When you have only a few very powerful machines with a lot of processing power, RAM, and fastdisk access.

• When you have a large amount of data for profiling or rule tasks.

Note:

• If you run many profile tasks simultaneously with DOP > 1, each of them could be split in multipleexecution units. For example, 4 tasks and DOP 4 could result in 16 execution units. Now there are16 processes competing for resources (CPU, RAM, and hard disk) on the same machine. So italways a good idea to schedule jobs efficiently or to use multiple Data Services Job servers.

• DOP is a global setting and affects the entire landscape.

Related Topics• Scalability and performance considerations• Degree of parallelism• Grid computing

10.4.6 Grid computing

You can perform grid computing using the Data Services Job Server group. This group is a logicalgroup of multiple Data Services Job Servers. When you install Information Steward, you can assign asingle Data Services Job Server group for that Information Steward instance. There are two ways youcan utilize the Job Server group with Distribution level setting: distribution level table and distributionlevel sub-table.

A single profiling or rule task can work on one or more “tables”. The term “table” is used in a generalsense of the number of records with rows and columns. In reality, this can come from an RDBMS table,a flat file, an SAP application, and so on.

Note:DOP and distribution level are global settings and affect the entire landscape.

Related Topics• Scalability and performance considerations• Distribution level table• Distribution level sub-table• When to use grid computing

2011-04-06178


10.4.6.1 Distribution level table

When you set the distribution level to Distribution level table, each table of the task is executed onseparate Data Services Job Server in the group. If you have set DOP, it is effective on the independentmachines and one task on that particular server could be further distributed.

For example, if you have 8 tables in a task and it is submitted to a Data Services Job Server group with8 Data Services Job Server, then each Data Services Job Server processes one table. If the DOP isset to 4, then each Data Services Job Server tries to parallelize the task into 4 execution units, one foreach particular table. There is no interdependency between the different job servers; they share noresources.

When a Data Services Job Server group receives a task that involves multiple tables and the distributionlevel is set to Table, it uses an intelligent algorithm that chooses the Data Services servers based onthe available resource. If a particular server is busy, then the task is submitted to a relatively less busyData Services server. These calculations are based on the number of CPUs, RAM, and so on. If youhave two Data Services servers, one with many resources and another with low resources, it is quitepossible that the bigger server gets a proportionally higher number of tasks to execute.

You can also choose servers based purely in a "round robin" fashion, in which case the task is submittedto the next available Data Services server. For more information, see theSAP BusinessObjects DataServices Administrator Guide.

Related Topics• Scalability and performance considerations• Grid computing

10.4.6.2 Distribution level sub-table

Note:This setting is only effective for column profiling. Use this setting with caution, as it may have a negativeimpact on performance of other types of profiling, such as advanced profiling.

When you set the distribution level to Distribution level sub-table, based on the DOP setting DataServices distributes a single table task across multiple machines in the network. The basic idea is tosplit a single task into multiple independent execution units and send them to different Data ServicesJob Servers for execution. You can think of this as DOP but across multiple machines rather thanmultiple CPUs of a single machine.

For example, you have a column profiling task for 100 million rows 40 columns, the distribution level isset to Sub-Table, the DOP is 8, and there are 8 Data Services Job Servers in the group. The task is

2011-04-06179


split into 8 execution units for 5 columns each and sent to the 5 Data Services Job Servers, which thencan execute it in parallel. There is no sharing of CPU or RAM. But all of the Data Services Job Serversshare the same pageable cache directory. You must ensure this directory location is shared andaccessible to all Data Services Job Servers . This location should have a very efficient disk and thenetwork on which this setup is done should be very fast so that it does not become bottleneck; otherwise,the gains of parallel processing will be negated.


10.4.6.3 When to use grid computing

The principles are similar to DOP, but with the additional aspects of distribution level.• Distribution level table: Use when you have many concurrent profiling and rules tasks that work on

large amount of data. Set the distribution level to Table, so that individual tasks are sent to differentservers.

• Distribution level sub-table: Use when you have a very few column profiling tasks on very largeamount of data. In this case, use distribution level "Sub-table". It is important that these machinesshare an efficient hard disk and that they are connected by a fast network.


10.4.7 Using SAP applications as a source

SAP BusinessObjects Information Steward allows direct integration with the SAP Business Warehouseand the SAP ERP Central Component (ECC) system. One of the main benefits is the ability to connectdirectly to the production SAP systems to perform data profiling and data quality analysis based on theactual, most timely data, instead of connecting to a data warehouse, which is loaded infrequently. Tofully utilize this advantage without risking the performance and user experience on the production ECCsystem, consider these requirements.

To use utilize the back-end resources in the most efficient and sustainable way, the connection userdefined for the interaction between Information Steward and the SAP back-end system should be linkedto background processing. This is the recommended setup for the connection user.

2011-04-06180


The option to use a dialog user for the connection between Information Steward and the SAP back-endsystem should be considered carefully and should only be considered for smaller datasets not exceeding50,000 records from a medium width table. In this case, the synchronous processing will block a dialogprocess for the processing time and its resources. Using this approach on larger data sets would requirechanging the heap size for the maximum private memory for a dialog process and therefore has impacton the overall memory required by the ECC system. In addition, the extraction of larger sets of data willmost likely exceed the recommended maximum work process runtime for dialog process on the ABAPWeb Application server significantly. Depending on the amount of records and number of columns ofthe table the data is retrieved from, the extraction process runtime will vary. Due to the significantresource required and the extended runtime and allocation of a dialog process the usage of dialog userfor the communication is not recommended.

You can connect to the SAP ECC system and retrieve data for profiling and data quality analysis usingone of the following methods.• Transfer the data directly via the RFC connection established.

In this case the data is stored in an internal table first and then transferred via the synchronous RFCconnection.

• Asynchronous processing scenario 1.

The extracted data is written into a file to a shared directory for both the ABAP Web Application andthe Information Steward. After the extraction is completed, Information Steward picks up the file forfurther processing.

For this first asynchronous processing scenario, specify the SAP Applications connection parametersWorking directory on SAP server and Application Shared Directory, and set Data transfermethod to Shared directory.

• Asynchronous processing scenario 2.

In this case the data is written to directory on the back-end server, which is made available toInformation Steward via an FTP server connection. Similar to the second scenario, the data filesare then picked up by Information Steward from the directory specified, in this case via the FTPconnection path.

For this second asynchronous processing scenario, specify the Working directory on SAP serverand the FTP parameters when you define the SAP Applications connection, and set Data transfermethod to FTP.

The data transfer via option two and three have slightly longer turnaround times, but consumes fewerresources on the back-end system.

It is recommended that you perform optimized requests for data extraction from the SAP system whenyou define Information Steward profiling tasks. This optimization should be considered in all scenarios.Therefore, specify only a subset of the columns in your profile task and use filters to focus on a specificdata set. The more optimized the request, the faster the extraction and overall process execution. Inthis case, Information Steward only requests the data for extraction as defined by the filter. The filtercriteria is passed to the SAP system.


2011-04-06181


• SAP application connection best practices• General best practices• Profiling and rules• Organizing projects

10.4.8 Multi-threaded file read

When reading flat files, the Data Services engine can parallelize the tasks in multiple threads to achievehigher throughput. With multi-threaded file processing, the Data Services engine reads large chunksof data and processes them simultaneously. This way, the CPUs are not waiting for the file input/outputoperations to finish.

You can set the number of file processing threads to the number of CPUs available. Use this settingwhen you have a large file to run profile or rule task on.


10.4.9 Data Insight result set optimization

This optimization is applicable to all of the scheduled profile and rule tasks. Information Steward providesthe ability to optimize redundant tasks for Data Insight. If the profile or rule result set for a particulartable is already available, then it is not processed. This is controlled by the Optimization Period setting.Data in certain tables do not change very often or to refresh the result set is at a specified frequency.It is not required to execute that again within that time period. If the data is not going to change in aprofiling task, there is no need to process the task again. Similarly, if the scorecards are calculated onlyon a nightly basis, there is no need to recalculate the score.

Suppose the Optimization Period is set to 24 hours. A rule task was executed for Table1 and theresult set is already stored. If that same task is tried again within 24 hours, it is not processed again.Imagine another case where a single rule task involves Table1 and Table2. In this case, rules are notexecuted on Table1, but they are processed for Table2 because this table does not have a result setavailable.

If you want to always get the latest results due to the changing nature of the data, set the OptimizationPeriod to the expected period of change in data.

Note:Any profiling or rule tasks that are run on demand do not use this optimization and all of the data isprocessed.

2011-04-06182



10.4.10 Performance settings for input data

For Data Insight functionality, Information Steward provides the following settings to improve performance.

Related Topics• Scalability and performance considerations• Input data settings

10.4.10.1 Input data settings

These settings are available for both profile and rule tasks when you create a task. Defaults are set in"Configure Applications".

Max Input Size and Input Sampling RateWhen you create a rule or profiling task, specify the maximum rows and the rate at which you want toprocess them. Because processing time and resource requirements are proportional to the number ofrecords being processed, these settings are very important. Set these numbers only to what is requiredfor the task. For example, if you know that there are 100 million rows in a table and you want to get asense of your data profile quickly, set the Max Input Size to 1 million rows and the Sampling Rate to100. Every 100th record will be processed up to maximum of 1 million records.

Filter conditionYou can also control exactly which data gets processed using the filter condition. Because the numberof records affects performance, set the filter condition and process only the amount of data required.

Suppose you have 10 million records for all countries and there are 1 million records for the U.S. If youare interested in profiling data for the U.S. only, you should set the filter for country = US. This way,only 1 million records are processed.

You can combine this with Max Input Size and Sampling Rate to further improve performance, ifapplicable.

Related Topics• Scalability and performance considerations• Performance settings for input data• Configuration settings

2011-04-06183


10.4.11 Settings to control repository size

For Data Insight functionality, Information Steward provides the following settings to control the size ofthe Information Steward repository. This depends on the number of records as well, because the moredata, the bigger the potential result set. However, the repository size can be controlled for even verylarge amounts of data.

Related Topics• Scalability and performance considerations• Profiling• Rule processing• Metadata Management

10.4.11.1 Profiling

The following settings affect the size of the Information Steward repository. Choose these numberscarefully based on what your data domain experts require to understand data. The lower the number,the smaller the repository.

You can set a high number, but the repository size increases. Also, response time for viewing sampledata is affected because more rows need to be read from the database, transported over the network,and rendered in the browser.• Max sample data size: The sample size for each profile attribute.• Number of distinct values: The number of distinct values to store for the value distribution result.• Number of patterns: The number of patterns to store for the pattern distribution result.• Number of words: The number of words to store for the word distribution result.• Results retention period: Controls the number of days before the profiling results are deleted. The

longer you keep the results, the bigger the repository. For more information, see the Purge utility.

Related Topics• Scalability and performance considerations• Settings to control repository size• Profiling task settings and rule task settings

2011-04-06184


10.4.11.2 Rule processing

Max sample data size: This setting controls the number of failed records to save for each rule. Thehigher the number, the more records that are available to view as sample data. This results in a largerrepository size, and the response time for viewing sample failed data is affected.

Score retention period: This setting controls the number of days before the scores are deleted. Thelonger you keep the score data, the larger the repository size. For more information, see the Purgeutility.

Related Topics• Scalability and performance considerations• Settings to control repository size• Profiling task settings and rule task settings

10.4.11.3 Metadata Management

The size of the Information Steward repository is also controlled by the amount of metadata that iscollected and retained. Optimize the amount by selectively choosing the components that you areinterested in for different metadata integrators.

Related Topics• Scalability and performance considerations• Settings to control repository size

10.4.12 Settings for Metadata Management

10.4.12.1 Runtime parameter for metadata integrators

Here is a list of parameters that affect performance:

2011-04-06185


1. JVM arguments for metadata integrators that collect a large amount of metadata should be adjustedfor higher memory allocation. It is recommended that you update the JVM parameters on the integratorparameters page to -Xms1024m -Xmx4096m.

2. Run-time parameters for the maximum number of concurrent processes to collect metadata shouldbe set to the number of CPUs that can be dedicated for metadata collection. Typically metadataintegrators are installed on independent servers, so you can set it to the number of CPUs on theserver. These parameters for parallel processing may be different for different metadata integrators.

3. Each metadata integrator provides some method of performance improvement specifically for thetype of metadata that it collects. For example, with SAP BusinessObjects Enterprise MetadataIntegrator, you can reduce processing time by selectively choosing different components.

4. For the first time the integrator is run, the run-time parameterUpdate Option for metadata integratorsshould be set to Delete existing objects before collection. For subsequent runs, change it toUpdate existing objects and add newly selected objects. For example, for SAP BusinessObjectsEnterprise Metadata Integrator, you can first collect metadata only for Web Intelligence documents(by selecting only that component as specified in step 3). For the first run, set the option to Deleteexisting. In the next run, you may collect all of the Crystal Reports metadata. For the second run,set the option to Update existing

Related Topics• Scalability and performance considerations• Common runtime parameters for Information Steward

10.4.12.2 Utility configurations

The Metadata Management utilities Compute Lineage Report and Update Search index have someconfiguration parameters. RunCompute Lineage inOptimizedmode so that it is updated incrementally.


10.4.13 Settings for Cleansing Package Builder

10.4.13.1 JVM runtime parameters

2011-04-06186


If there are many parsed values (more than 20) per row in the data being used for Cleansing PackageBuilder, then the Auto-Analysis service requires adjustment to the JVM runtime parameter that controlsmemory allocation for EIMAPS. If the memory cap for Java is left at 1GB, even though the system has16GB, the service will run out of memory. The best practice is to allocate 2-3GB of memory to the Javaservices via the -Xmx setting.


10.4.13.2 Publishing cleansing packages

Schedule cleansing package processing during non-business hours. Depending on the size of thecleansing package, publishing can be a time consuming task. SAP-supplied cleansing packages forName-Title-Firm are typically very large. If they are updated and published, schedule the processingduring non-business hours. It may be a good idea to have a dedicated server for publishing, if this is afrequent occurrence.


10.5 Best practices for performance and scalability

10.5.1 General best practices

• When using a distributed environment, enable and run only the servers that are necessary. For moreinformation, see the Business Intelligence Platform Administrator Guide.

• Use dedicated servers for resource intensive servers like the Data Services Job Server, MetadataIntegrators, and the Cleansing Package Builder Auto-Analysis service.

• Install the Information Steward Web Application on a separate server. The Business Intelligenceplatform Web Tier must be installed on the same computer as the Information Steward WebApplication. If you do not have Tomcat or Bobcat, you need to manually deploy the InformationSteward Web Application.

2011-04-06187


• If you have many concurrent users, you can use multiple Information Steward web applications withLoad Balancer.

• To obtain a higher throughput, the Information Steward repository should be on a separate computerbut in the same sub-network as the Information Steward Web applications, Enterprise InformationManagement Adaptive Processing Server, Information Steward Job Server, and Data Services JobServer.

• Make sure that the database server for the Information Steward repository is tuned and has enoughresources.

• Allocate enough memory and hard disk space to individual servers as needed.• Follow good scheduling practices to make sure that resource intensive tasks do not overlap each

other. Schedule them to run during non-business hours so that on-demand request performance isnot affected.

Related Topics• Installation Guide: Deploying web applications with WDeploy• SAP BusinessObjects Business Intelligence platform Web Application Deployment Guide: Failoverand load balancing• Data Insight best practices• Metadata Management best practices• Cleansing Package Builder best practices

10.5.2 Data Insight best practices

10.5.2.1 Profiling and rules

1. If you expect your Data Insight profiling and rule tasks to consume a large amount of processing,deploy the Data Services Job Server on a separate computer.

2. To improve the execution of Data Insight profiling tasks, the Data Services Job Server can be onmultiple computers that are separate from the web application server to take advantage of DataServices job server groups and parallel execution. You must access the Data Services ServerManager on each computer to do the following tasks:• Add a Data Services Job Server and associate it with the Information Steward repository. For

more information, see “Adding Data Services Job Servers for Data Insight” in the AdministratorGuide.

• Specify the path of the pageable cache that will be shared by all job servers in the Pageablecache directory option.

2011-04-06188


3. For a predictable distribution of tasks when using multiple Data Services Job Servers, try to ensurethat the hardware and software configurations are homogeneous. This means that they should allhave similar CPU and RAM capacity.

4. Irrespective of using DOP and/or multiple Data Services Job Servers, set the pageable cachedirectory on high speed and high capacity disk.

5. If you are processing flat files, store them on a high speed disk so that read performance is good.6. Process only data that must be processed. Use settings such as Max Input Size, Sampling rate,

and Filter conditions appropriately.7. When using Information Steward views, use correct join and filter conditions so that you are pulling

in only required rows.8. Choose only columns that you are interested in profiling or the rules that you are interested in

calculating for the score. Selecting all columns may lead to redundant processing.9. Word distribution profiling is done only on a few columns. Do not choose this for all columns.

Otherwise, performance and the size of the Information Steward repository is affected.10. If you have lookup functions in rule processing, it takes more time and disk space. Typically, lookup

tables are small, but if they are big, lookup tables can adversely affect performance. Ensure thatthe tables on which lookup is performed are small. As an alternative to lookup, you can use the SQLfunction.

11. Choose the DOP setting and the distribution level carefully. Remember that these are global settingsand affect the entire landscape.

12. When doing column profiling on large amounts of data with many small capacity Data Services JobServers, only use the distribution level Sub-Table. This setting can have an adverse effect on othertypes of tasks. You may want to change it back to Table level after that column profiling task is done.

13. Store the reference data required for address profiling on a high speed and high capacity disk.14. Make sure that the database server that contains source data is tuned and has enough resources.15. Schedule the Purge utility to run during non-business hours. If column profiling and rules are executed

many times a day, try to schedule the Purge utility to run more than once, so that it can increasefree disk space in the repository.

Related Topics• General best practices• Using SAP applications as a source• Organizing projects• User Guide: Creating a rule

10.5.2.2 SAP application connection best practices

1. Choose the data retrieval method (synchronous or asynchronous) based on the data set size andperformance requirements of your SAP system.

2. For smaller data sets, use the synchronous method.

2011-04-06189


3. For larger data sets, use the asynchronous method, where the data from SAP systems is writteninto a file that Information Steward uses.

It is recommended to use background processing on the SAP back-end, which can be controlled bythe user type of the connection the user defined.

Dialog processing should be considered carefully. In this case, adjust the run-time parameter such asheap size for th maximum private memory and maximum work process runtime.


10.5.2.3 Organizing projects

How scorecards and projects are organized depends on how business users want to view the scorecards.But this organization can affect the response time for the users. If a project contains many scorecards,details of all the scorecards must be retrieved for viewing. So it is good idea to create multiple projectsaccording to the area of interest and have a limited number of scorecards in those projects.

For example, you could create projects for different geographical locations. Within each project, youcould have different scorecards, such as Customer, Vendor, and so on. Or you could create projectsbased on Customer, Vendor, and so on, and then have scorecards based on geography.

The organization also helps you decide what data sources you want to use and the filter conditionsinvolved for profiling and rule execution.

Another benefit of proper organization is that you can control the user security per project and restrictaccess to only specific users.

To avoid future problems, different Data Insight user groups should work together in the beginning ofthe project to decide these aspects.

Related Topics• General best practices• Profiling and rules• Using SAP applications as a source

10.5.3 Metadata Management best practices

2011-04-06190


1. Metadata integrators for BusinessObjects Enterprise, Data Services, and SAP Business Warehouseshould be installed on their own dedicated servers if they require large processing time or they runin overlapping time periods with other metadata integrators or Data Insight tasks.

2. The Metadata Relationship Service and Metadata Search Service can be combined.3. Additional guidelines to consider for Metadata Relationship Service:

• Should be on a separate computer than the web application server to obtain higher throughput.• Can be on its own computer, or it can be combined with any Metadata Integrator. The rationale

for this combination is that Metadata Integrators usually run at night or other non-business hours,and the Metadata Relationship Service runs during normal business hours when users are viewingrelationships (such as impact and lineage) on the Information Steward web application.

4. Another guideline to consider for Metadata Search Service:• Can be on its own computer, or it can be combined with any Metadata Integrator. The rationale

for this combination is that Metadata Integrators usually run at night or other non-business hours,and the Search Server runs during normal business hours when users are searching on theMetadata Management tab of Information Steward.

5. The File Repository Servers should be installed on a server with a high speed and high capacitydisk.

6. Adjust runtime parameters correctly.

Related Topics• General best practices

10.5.4 Cleansing Package Builder best practices

1. Cleansing Package Builder Auto-Analysis service should be on a dedicated server obtain higherthroughput.

2. Use sample data that represents various patterns in your whole data set. Large amounts of sampledata with too many repeating patterns leads to redundant processing overhead.

3. Run-time parameters should be set correctly for Auto-Analysis service. Specifically, memoryrequirements are very important. If enough memory is not made available to the process, it will runout of memory. If the memory cap for Java is left at 1GB, even though the system has 16GB, theservice will run out of memory. The best practice is to allocate 2-3GB of memory to the Java servicesvia the -Xmx setting.

Related Topics• Common runtime parameters for Information Steward• General best practices

2011-04-06191


2011-04-06192


Backing Up and Restoring Metadata Management

11.1 Backing up and restoring overview

This section describes suggested procedures for performing backups and restorations of various objectsassociated with this product.

Related Topics• Migration mechanisms and tools

11.2 Exporting objects to XML

This application provides an XML export utility, MMObjectExporter.bat, which allows you to exportrepository objects to an XML file. The utility is installed on the machine on which you installed thisproduct. You specify its output by using required and optional command line arguments.

11.2.1 To export objects to XML

1. From a command prompt, navigate to the installation directory's subdirectory location.2. Invoke the XML export utility by typing and running the command MMObjectExporter with the

appropriate arguments from the following table.

2011-04-06193


DescriptionOption

(Required) Represents the id number of the integrator source configurationto be exported. You can find the configuration id number at the end of theURL displayed in the status bar of the SAP BusinessObjects MetadataManagement Explorer when you move the pointer over the integratorsource name. Include only the configuration id number for this argument.Do not include the word configuration.

configuration

(Required) Represents the name of the XML file you want this product tocreate, including the full path. If this argument contains blank spaces, youmust enclose the argument in quotation marks. Include only the full pathand file name for this argument. Do not include the word filename.

filename

(Optional) Represents the name of the computer that contains the CMSserver. The default value is localhost. Include both the argument nameand the value, separated by a space.

boeServer

(Optional) Represents the logon authentication method. The default valueis secEnterprise. Include both the argument name and the value, separatedby a space.

boeAuthentication

(Optional) Represents the CMS user name to connect to the CMS server.The default value is Administrator. Include both the argument name andthe value, separated by a space.

boeUser

(Optional) Represents the password to connect to the CMS server. Thedefault is no password (the empty string ""). Include both the argumentname and the value, separated by a space.

boePassword

(Optional) Represents the object type to be exported. The default value ishierarchy. Include both the argument name and the value, separated bya space. If you do not specify this argument, then the utility finds the toplevel object types from the integrator's <object-hierarchy> element.

By default, all other objects related to the object or objects specified bythis argument are also included in the XML output. However, this argumenthas an optional name list to limit the object selection to a specific set ofobjects. The object type is limited to those shown in the object type XMLspecification's <object-type> element type attribute in the file ObjectTypes.xml, and must be spelled and cased the same. The type attributeis also used to specify the logical name of the table containing objects ofthat type.

If there are no objects found in the repository that meet the mainObjectrequirements, then the utility exits with an error message. If some but notall of the objects are found, the utility generates the XML file but writes awarning message about the objects that were not found to the log.

mainObject

(Optional) Represents a boolean value to indicate whether to includeproperties with null values. The default value is TRUE. Include both theargument name and the value, separated by a space.

includeNulls

2011-04-06194


DescriptionOption

(Optional) Represents a boolean value to indicate whether to include par-ents of objects. The default value is TRUE. Include both the argumentname and the value, separated by a space.

includeParents

(Optional) Represents a boolean value to indicate whether to include chil-dren of objects. The default value is TRUE. Include both the argumentname and the value, separated by a space.

includeChildren

(Optional) Represents a boolean value to indicate whether to include objectrelationships. The default value is TRUE. Include both the argument nameand the value, separated by a space.

includeRelationships

(Optional) Represents a boolean value to indicate whether to validate theexported XML file. The default value is TRUE. Include both the argumentname and the value, separated by a space.

validate

(Optional) Represents location of the file ObjectExportSchema.xsd.The location of the file is added to the exported XML file as the attributeschemaLocation. Other programs can validate and interpret the exportedXML file by reading the value of that attribute. Use this argument to overridethe default name or the default location in order to specify a network-ac-cessible location for the XSD file.

xsdUrl

After the utility runs, this product creates an XML file according to the specified arguments.

Example:

In this example, at a command prompt positioned in the installation directory's subdirectory, the userenters the following command and arguments:

mmobjectexporter 82 "c:\temp\first exported.xml"boeUser Jane boePassword My1PasswordmainObject Universe

The entries represent the following:

2011-04-06195


DescriptionEntry

Invokes the utility.mmobjectexporter

Uses the configuration argument and represents in this example the IDnumber of the configuration for export to XML.

82

Uses the filename argument and represents the path and name of thecreated XML file. Here the argument is in quotation marks because thefile name contains a space.

"c:\temp\first exported.xml"

Uses the boeUser argument to specify the name of the CMS user.boeUser Jane

Uses the boePassword argument to specify the password for the CMSuser.

boePassword My1Pass-word

Uses the mainObject argument to select all Universes in the configuration.Alternatively, the argument could be more specific. For example, usingthe syntax mainObject "Universe=MyUniverse" selects only the Universenamed MyUniverse. Using the syntax mainObject "Universe=MyUni-verse,YourUniverse" selects the two Universes named MyUniverse andYourUniverse. The parents and children of these objects would also beincluded, because the arguments for includeParents and includeChildrenare not invoked, and so they default to TRUE.

mainObject Universe

11.3 Backing up and restoring configurations

Use these procedures when you want to backup and restore this application's configurations from onesystem to another.

Note:Use the backup utility in your Relational Database Management System to back up the repository thatcontains all MMT_* tables. Use the Lifecyle management console for SAP BusinessObjects BI platformto back up and restore configurations of this product.

11.3.1 Backing up configurations

You must have the current version of this product on both the source and target machines.

To back up your configurations, use the Lifecyle management console for SAP BusinessObjects BIplatform to create an output BIAR file for Metadata Management configuration information on the sourceSAP BusinessObjects BI platform system:

2011-04-06196


1. On the "Destination environment" screen, specify a BIAR file that is accessible to both the sourceand target SAP BusinessObjects BI platform machines.

2. On the "Select objects to import" screen, select only the Import application folders and objectsoption.

3. On the "Select application folders and objects" screen, select Metadata Management.4. On the "Select objects to import" screen, select the users and groups that have permissions to the

Metadata Management integrator source configurations.5. On the next screen, select the users and groups that have permissions to the Metadata Management

integrator source configurations.

The following configuration information is backed up as a result of this procedure:• Metadata Integrator source configuration• Metadata Management utilities configurations• Metatdata source groups• Security information (users, groups, and their permissions)

11.3.2 Restoring configurations

You must have this version of the application on both the source and target machines.

To restore the configurations on the target system:1. Use the Lifecyle management console for SAP BusinessObjects BI platform to import the generated

BIAR file.2. Do the following steps for each imported integrator source.

a. In Information Steward, go to the "Metadata Management" area and select the "Integrator Sources"node.The list of integrator source configurations displays by default.

b. Double-click the name of each integrator source configuration to open the Properties page andenter the password for the source system.For security purposes, the password is not stored in the backup information.

c. Save the Properties page.

3. Restart the system and Web application.

2011-04-06197


2011-04-06198


Life Cycle Management

12.1 Migration basics

About this sectionMigration as it relates to SAP BusinessObjects Information Steward is the process of moving applicationconfigurations from a test phase into production. The software supports simple and complex applicationmigration through all development phases.

12.1.1 Development process phases

The application development process typically involves two phases:• Test phase• Production phase

You can use SAP BusinessObjects Information Steward in both phases. Because each phase mightrequire a different repository to control environment differences, the software provides controlledmechanisms for moving objects from phase to phase.

Each phase could involve a different computer in a different environment with different security settings.For example, the initial test may require only limited sample data and low security, while final testingmay require a full emulation of the production environment including strict security.

12.1.1.1 Test phase

In this phase, you define and test the following objects for each module of SAP BusinessObjectsInformation Steward:• Data Insight—Define profile tasks, rules, and scorecards that instruct Information Steward in your

data quality requirements. The software stores the rule definitions so that you can reuse them ormodify them as your system evolves.

2011-04-06199


• Metadata Management—Define integrator sources, integrator source groups, and integrator sourceinstances that collect metadata to determine the relationships of data in one source to data in anothersource.

After you define the objects, use SAP BusinessObjects Information Steward to test the execution ofyour application. At this point, you can test for errors and trace the flow of execution without exposingproduction data to any risk. If you discover errors during this phase, you can correct them and retestthe application.

The software provides feedback through trace, error, and monitor logs during this phase.

The testing repository should emulate your production environment as closely as possible, includingscheduling Data Insight tasks and Metadata Integrator runs rather than manually starting them.

12.1.1.2 Production phase

In this phase, you set up a schedule in the Central Management Console (CMC) to run your Data Insighttasks and Metadata Integrator runs as jobs. Evaluate results from production runs and when necessary,return to the test phase to optimize performance and refine your target requirements.

After you move the software into production, monitor it in the CMC for performance and results. Duringproduction:• Monitor your Data Insight tasks and Metadata Integrator runs and the time it takes for them to

complete.

The trace and monitoring logs provide information about each task and run.

You can customize the log details. However, the more information you request in the logs, the longerthe task or integrator runs. Balance run time against the information necessary to analyzeperformance.

• Check the accuracy of your data.

To enhance or correct your jobs:1. Make changes in your test environment.

2. Repeat the object testing.

3. Move changed objects back into production.

12.2 Migration mechanisms and tools

SAP BusinessObjects Information Steward provides the following migration mechanisms:

2011-04-06200


• Lifecycle management console for SAP BusinessObjects BI platform• Information Steward export and import

12.2.1 Moving objects using the lifecycle management console

Lifecycle management console for SAP BusinessObjects BI platform is a web-based tool that enablesyou to move BI resources from one system to another system, without affecting the dependencies ofthese resources. It also enables you to manage different versions of BI resources, manage dependenciesof BI resources, and roll back a promoted resource to restore the destination system to its previousstate.

You can use the lifecycle management console for SAP BusinessObjects BI platform to move objectsin the Central Management System (CMS) between the same versions. For example, when you moveobjects from the test system to the production system, you can accomplish the task through the lifecyclemanagement console.

You can use the lifecycle management console to move the following Information Steward objects:• Integrator source configurations• Metadata Management utilities• Source groups• Security information (including users, groups, and their permissions) for Metadata Management,

Metapedia, Data Insight, and Cleansing Package Builder. Most Information Steward securityinformation is stored at the folder level, so to move all of the security settings from one system toanother, promote each folder. The lifecycle management console has an option that lets you choosewhether to promote a job with its associated security and whether to include application rights.

12.2.2 Exporting and importing objects using Information Steward

Using Information Steward import and export functionality, you can move the following objects:

2011-04-06201


For more informationObject

For more information about importing and exporting file formats, see the“Data Insight ” section of the SAP BusinessObjects Information StewardUser Guide.

Data Insight file formats

For more information about managing rules, see the “Data Insight ” sectionof the SAP BusinessObjects Information Steward User Guide.

Data Insight rules

For more information about importing and exporting views, see the “Views”section of the SAP BusinessObjects Information Steward User Guide.

Data Insight views

For more information about importing and exporting terms and categorieswith Excel, see the “Metapedia” section of the SAP BusinessObjects Infor-mation Steward User Guide.

Metapedia terms and cat-egories

2011-04-06202


Supportability

13.1 Information Steward logs

For each profiling and rule task and Metadata Integrator run, SAP BusinessObjects Information Stewardwrites information in the following logs:• Database Log - Use the database log as an audit trail. This log is in the Information Steward

Repository. You can view this log while the Metadata Integrator or Data Insight profile or rule taskis running.

The default logging level for the database log is Informationwhich writes informational messages,such as number of reports processed, as well as any warning and error messages. It is recommendedthat you keep the logging level for the database log at a high level so that it does not occupy a largeamount of disk space.

• File Log - Use the file log to provide more information about a Metadata Integrator or Data Insightprofile or rule task run. The Metadata Integrator creates this log in in the Business Objects installationdirectory and copies it to the File Repository Server. You can download this log file after the MetadataIntegrator run completed.

The default logging level for the file log is Configuration which writes static configurationmessages, as well as informational, warning, and error messages. You can change the logging levelfor the file log if you want more detailed information. If your logs are occupying a large amount ofspace, you can change the maximum number of instances or days to keep logs.

13.1.1 Log levels

Each logging level logs all messages at that level or higher. Therefore, the default logging levelInformation logs informational, warning, and error messages. If you change the logging level to Warning,SAP BusinessObjects Information Steward logs warning and error messages. Similarly, if you changethe logging level to Integrator trace, Information Steward logs trace, configuration, informational, warning,and error messages

DescriptionLog level

Turn off logging any messagesOff

2011-04-06203

Supportability

DescriptionLog level

Log messages that indicate a serious failureError

Log messages that indicate a potential problemWarning

Log informational messagesInformation

Log static configuration messagesConfiguration

Log integrator tracing informationIntegrator trace

Log SQL tracing informationSQL trace

Log highly detailed tracing informationSystem trace

Log all messagesAll

13.1.2 Changing log levels

You can change the log levels for Metadata Management and Data Insight logs.

13.1.2.1 Changing Metadata Management log levels

To change the Metedata Managent log levels, you must have the Schedule right on the integratorsource.1. On the Information Steward page in the Central Management Console (CMC) , expand theMetadata

Management node, and expand the Integrator Sources node to display all configured integratorsources.

2. Select the integrator source for which you want to change the logging level by clicking anywhere onthe row except its type.

Note:If you click the integrator type, you display the version and customer support information for the integrator.

3. Select Action > Schedule in the top menu tool bar.4. Click the Parameters node in the tree on the left.5. From the drop-down list, select the logging level that you want for Database Log Level or File Log

Level.

2011-04-06204

Supportability

6. Click Schedule.

Future runs of the recurring schedule for this integrator source will use the logging level you specified..

13.1.2.2 Changing Data Insight log levels

To change the Data Insight log levels, do the following:1. On the Information Steward page in the Central Management Console (CMC) , expand the Data

Insight node, and expand the Projects node.2. Select the project source, and select the project for which you want to change the log level by clicking

anywhere on the row except its type.3. Select Action > Schedule in the top menu tool bar.4. Click the Parameters node in the tree on the left.5. From the drop-down list, select the log level that you want for Database Log Level or File Log

Level.6. Click Schedule.

Future runs of the recurring schedule for this Data Insight profile or rule task will use the logging levelyou specified.

13.1.3 Viewing logs

You can view Metadata Management and Data Insight logs.

13.1.3.1 Viewing integrator source logs

To view Metadata Management integrator source logs:1. From the Central Management Console (CMC) click Information Steward.


2. Expand the Metadata Management node and select the Integrator Sources node.A list of configured integrator sources appears in the right panel with the date and time each waslast run.

3. Select the integrator source and click Action > History in the top menu tool bar.

2011-04-06205

Supportability

The "Integrator History" pane displays each schedule in the right panel.

4. Select the schedule name and click the icon for View the database log.The "Database log" shows the task messages which are a subset of the message in the log file.

5. To find specific messages in the "Database log" window, enter a string in the text box and clickFilter.For example, you might enter error to see if there are any errors.

Note:

• For information about troubleshooting Cleansing Package Builder, see “Troubleshooting” in theUser Guide.

• For information about troubleshooting integrator sources, see Troubleshooting

6. To close the "Database log" window, click the X in the upper right corner.

13.1.3.2 Viewing Data Insight task logs

To view Data Insight task logs:1. From the Central Management Console (CMC) click Information Steward.


2. In the Tree panel, expand the Data Insight node.3. Expand the Projects node.4. Select the name of your project in the Tree panel.

A list of tasks appears in the right panel with the date and time each was last run.

5. Select the task and click Action> History in the top menu tool bar.

The "Data Insight Task history" pane displays each instance the task was executed.

6. Select the instance name and click the icon for View the database log.The "Database log" shows the task messages which are a subset of the message in the log file.

7. To find specific messages in the "Database log" window, enter a string in the text box and clickFilter.For example, you might enter error to see if there are any errors.

Note:For information about troubleshooting Cleansing Package Builder, see “Troubleshooting” in the UserGuide.

8. To close the "Database log" window, click the X in the upper right corner.

2011-04-06206

Supportability

13.1.4 Viewing additional logs

You can also view log information for SAP BusinessObjects Data Services and SAP BusinessObjectsEnterprise XI 4.0.

Data Services log filesThe log files are located in the Data Services log directory, for example: C:\Program Files(x86)\SAP BusinessObjects\Data Services\log.

You can also find log files in the following locations:

C:\Program Files (x86)\SAP BusinessObjects\Data Services\log\MetadataService

C:\Program Files (x86)\SAP BusinessObjects\Data Services\log\ViewdataService

Look for log files associated with job execution, for example errorlog.txt and tracelog.txt

Business Object Enterprise Cleansing Package Builder log filesThe log files are in the platform Log directory where CMS is installed. For example, C:\ProgramFiles (x86)\SAP BusinessObjects \SAP BusinessObjects Enterprise XI 4.0\logging

Look for the following log files:• InformationSteward.RelationshipService.log• InformationSteward.SearchService.log• InformationSteward.IntegratorService.log• InformationSteward.SchedulingService.log• InformationSteward.Administrator.log• InformationSteward.Explorer.log

On machines with only Web Applications, the log files (InformationSteward.Administrator.logand InformationSteward.Explorer.log) are stored in the Web Application temp directory. Forexample, C:\Program Files (x86)\SAP BusinessObjects\Tomcat6\temp\ICC

Cleansing Package Builder log filesAll Cleansing Package Builder Services log details can be found in EIM Adaptive Processing Servertrace log under <BOE Install>\SAP BusinessObjects Enterprise XI 4.0\logging

For example: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjectsEnterprise XI 4.0\logging\ pjs_<BOE NodeName>EIMAdaptiveProcessingServer_trace.00000X.glf

2011-04-06207

Supportability

2011-04-06208

Supportability

Appendix

14.1 Glossary

accuracyThe extent to which data objects correctly represent the real-world values for which theywere designed.

address profilingA process that componentizes and measures address data with dictionary data.

alternateA substitute spelling or nickname; Mr. is an alternate for Mister.

annotationUser notes added to an object in Metadata Management and Data Insight.

associationA relationship between terms contained in a Metapedia business glossary and metadataobjects.

catalogA relational object type that, in a relational database management system (RDBMS),corresponds to a database. Each deployment contains two such object types, one for thedatasources and one for the target tables.

categoryThe organization system for grouping terms to denote a common functionality. Categoriescan contain sub-categories, and you can associate terms to more than one category.

cleansing packageThe parsing rules and other information that define how to parse and standardize the dataof a specific data domain.

Cleansing Package BuilderA module of Information Steward that allows a data steward to create and modify cleansingpackages for any data domain. A cleansing package is then used to process the data inaccordance with package guidelines through SAP BusinessObjects Data Services.

cleansing package categoryThe organization system for grouping terms to denote a common functionality. Cleansingpackage categories can contain sub-categories, and you can associate terms to more thanone category.

2011-04-06209

Appendix

completenessThe extent to which data is not missing.

conformityThe extent to which data conforms to a specified format.

consistencyThe extent to which distinct data instances provide non-conflicting information about thesame underlying data object.

context definitionA method that allows users to specify context when data contains a pattern or containsparsed values that have a special meaning when used together, such as a range ofacceptable values.

custom attributeProperties you add to existing metadata objects that, once defined, can be searched forand viewed.

custom cleansing packageThe parsing rules and other information that you have defined in order to parse andmanipulate all types of data including operational and product data.

data insight projectA collaborative space for data stewards and data analysts to assess and monitor the dataquality of a specific domain and for a specific purpose (such as customer qualityassessment, sales system migration, and master data quality monitoring).

data stewardA person who manages data as an asset, is an expert in his data domain and is responsiblefor the quality of the data.

databaseOne or more large structured sets of persistent data, usually associated with software, toupdate and query the data. A relational database organizes the data, and relationshipsbetween them, into tables.

datasource schemaThe definition of a table’s columns and primary keys.

dependency profilingA process that determines whether the data in one column or table is based on the resultsof another column or table.

dimensionA logical grouping of characteristics within an InfoCube.

directory structureA hierarchy within Information Steward that is organized into folders that contain fourcategories, namely Data Integration, Business Intelligence, Data Modeling, and RelationalDatabases.

extract

2011-04-06210

Appendix

A process by which Information Steward copies information from source systems and loadsit into the repository.

file formatFlat file definition which includes the column name, data type, delimiter or character width.This is equivalent to the schema for a relational database table.

impact diagramA graphical representation of the object(s) that will be affected if you change or removeother connected objects.

InfoCubeA type of InfoProvider that describes a self-contained dataset, for example, from a businessoriented area.

integrator sourceA named set of parameters that describes how a metadata integrator can access a datasource.

integrityThe extent to which data is not missing important relationship linkages.

key data domainsA set of related data objects or key data entities.

lineage diagramA diagram that shows where the data comes from and what sources provide the data forthis object.

metadata integratorAn application that collects information about objects in a source system and integrates itin one or more related source systems.

metadata objectA unit of information that the software creates from an object in a source system.

MetapediaA custom glossary within Information Steward that you use to define and organize termsand categories related to your business data.

Metapedia categoryThe organization system for grouping Metapedia terms to denote a common functionality.Categories can contain sub-categories, and you can associate Metapedia terms to morethan one category.

Metapedia termA word or phrase that defines a business concept in your organization.

MultiProviderAn SAP NetWeaver Business Warehouse object that combines data from severalInfoProviders and makes it available for reporting.

object equivalency ruleA naming rule that indicates that an object in one source system is the same physicalobject in another source system.

2011-04-06211

Appendix

object trayA temporary holding space for objects that you want to export or define a relationship forin Metadata Management.

Open Hub DestinationAn SAP NetWeaver Business Warehouse object within the open hub service that containsall information about a target system for data in an InfoProvider. The target system can beexternal.

parent-childA hierarchical relationship where one object is subordinate to another. In this hierarchy,the parent is one level above the child; a parent can have several children, but a child canhave only one parent. For example, a table can have multiple columns, but a column canbelong to only one table.

parsed valueA data string that results from parsing.

parsing ruleA rule that determines how data is classified based on a pattern within the data and howthe data is mapped to specific attributes.

person and firm cleansing packageA cleansing package that parses party or name and firm information such as given name,family name, prename, title, phone number, and firm or company name.

private cleansing packageA cleansing package that can be viewed or edited only by the user who owns it.

profileA process that generates attributes about the data such as minimum and maximum values,pattern distribution and data dependency to help data analysts discover and understanddata anomalies.

profileTo generate attributes about the data.

profile taskA task to profile one or more tables, views and/or flat files. This task can be scheduled orexecuted on demand.

properties fileA collection of information that appears on the Report tab of each report; it includes suchinformation as the name and description of the report, and the source(s) of the informationcontained in the report.

published cleansing packageA cleansing package that is either SAP-supplied or created and then is published by adata steward, is available to all users, and can be used in a Data Services transform.

quality dimensionsA category for rules such as accuracy and completeness. This helps to organize your rulesand provides a score that contributes to the scorecard value.

2011-04-06212

Appendix

queryAn SAP NetWeaver Business Warehouse object consisting of a combination ofcharacteristics and key figures (InfoObjects) that allow you to analyze the data in anInfoProvider.

query viewsAn SAP NetWeaver Business Warehouse object consisting of a modified view of the datain a query or an external InfoProvider.

redundancy profilingA process that measures the amount of repeated data.

rule taskA task to run rules bound by one or more tables, views and/or flat flies. This task can bescheduled or executed on demand.

same as relationshipThe association between two objects indicating that they are identical physical objects.Only objects of the same object type can have this kind of association.

schemaA definition of a table in a relational database.

scoreA numerical result calculated by counting the records that pass a rule divided by the totalnumber of records.

scorecardA high level data quality view of a key data domain based on business data qualityobjectives.

scripting languageExpression language used to write validation rules.

server instanceA database, data source, or service in a relational database management system.

sourceAn object that provides data that is copied or transformed to become part of the targetobject.

source groupA set of related integrator sources.

source systemA software application from which SAP BusinessObjects Information Steward extracts andorganizes metadata into directory structures, enabling you to navigate and analyze themetadata.

standard formThe standardized or normalized form of a variation, which is displayed after cleansing.

sub-category

2011-04-06213

Appendix

Within a category, the organization system for grouping terms to denote a commonfunctionality.

synonymAnother name for an object in the same system. For example, a synonym for a relationaltable exists in the same database as the table.

target schemaA set of tables. A project can only contain one target schema, and its name is always targetschema.

timelinessThe extent to which data is sufficiently up-to-date for the task at hand.

transfer rulesAn SAP NetWeaver Business Warehouse object that determines how the data for aDataSource is to be moved to the InfoSource. The uploaded data is transformed usingtransfer rules.

transformationAn SAP NetWeaver Business Warehouse object that consists of functions for unloading,loading, and formatting data between different data sources and data targets that use datastreams.

transformation nameThe identity of the universe object, if the target is a measure, or the data flow name, if thesource data was taken from an Extract, Transform, and Load (ETL) system.

uniquenessThe extent to which the data for a set of columns is not repeated.

uniqueness profilingA process that determines whether the exact piece of data is repeated within the samecolumn or differing columns.

usage scenarioAn example that is typical of the kinds of tasks you’d like to perform with the software.

validation rulesA method that assesses the quality of data in the source system. These rules are boundto one or more columns to derive a score.

variationA value that has been assigned to an attribute.

web templateAn SAP NetWeaver Business Warehouse object consisting of an HTML document thatdetermines the structure of a Web application.

workbookAn SAP NetWeaver Business Warehouse object consisting of a Microsoft Excel spreadsheetwith one or more embedded NetWeaver Business Warehouse queries.

2011-04-06214

Appendix

IndexA

accessing Information Steward 9accuracy 209adaptive job server 19adaptive processing server 19add collected metadata 127address profiling 209administration

tasks for Metadata Management105

advanced profiling 176alias 209alternate 209annotation 209assigning rights

Metadata Management tasks 59association 209asynchronous processing

SAP as a source 180Average Concurrent Tasks 175

B

backing upintegrator configurations 196

best practicesCleansing Package Builder 191Data Insight 188general 187Metadata Management 190profiling 188projects 190rules 188SAP as a source 180

BI platform componentsthat Information Steward uses 11

Business Intelligence platformcomponentshow Information Steward uses 19

BusinessObjects Enterprise Integratorconfiguring 106

C

calculate scorecard utilitydescription 145monitoring 151rescheduling 149run now 150scheduling 148

catalog 209categories and terms

importing and exporting 201category 209Central Management Console

See CMC 19Central Management Server

See CMS 19chunk of data 209cleansing package 209Cleansing Package Builder 209

best practices 191distributed processing 173performance 186performance factors 170related services 173resource intense 165scalability 186security rights 61

cleansing package category 209cleansing packages

deleting 139editing descriptions 140group rights 61owners 139publishing 187states and statuses 141unlocking 140

CMC 19CMS 19collect

Crystal Reports 127universes 127Web Intelligence documents 127

column profilingdegree of parallelism 176

Common Warehouse MetamodelMetadata Integratorconfiguring 109

completeness 209components

Business Intelligence platform 19compute lineage report utility 146

configuring 153description 145modifying configuration 152monitoring 151rescheduling 149run now 150scheduling 148

computing Relationship Table 146

concurrent tasks 175concurrent users

performance 168performance factors 170response time 169

configurations, backing up 196configurations, backing up³ 196configurations, restoring 197configure

utility 186configuring

Common Warehouse MetamodelMetadata Integrator 109

Metadata Integrator,BusinessObjects Enterprise106

Data Federator Metadata Integrator111

Data Services Metadata Integrator112

Meta Integration Metadata Bridge(MIMB) Metadata Integrator113

Metadata Browsing Service 157, 158

NetWeaver Business WarehouseMetadata Integrator 108

View Data Service 157, 159configuring Metadata Integrator

JDBC connections 116Relational Database 114universe connections 118

conformity 209connection parameters

displaying and editing 85HP Neoview 69IBM DB2 70Informix IDS 71Microsoft SQL Server 72MySQL 73Netezza 74ODBC 74Oracle database 76SAP Applications 81SAP In-Memory Database 68SAP NetWeaver Business

Warehouse 80connections

for Data Insight 66to application 79to database 66

2011-04-06215

connections (continued)to file 84

connections, Data Insightsecurity rights 43

consistency 209context definition 209creating source groups 136custom attribute 209custom cleansing package 209

D

datacharacteristics 170performance factors 168

data characteristicsperformance 168performance factors 170sizing 168

Data Federator Metadata Integratorconfiguring 111

Data Insightadministrator tasks 65best practices 180, 188, 190distributed processing 172monitoring tasks 95optimize result set 182organizing projects 190pausing and resuming tasks 96performance factors 168related services 172SAP as a source 180scheduling tasks 89tasks 89test phase 199

Data Insight connectionconfiguring for file source 84

Data Insight connection parametersdisplaying and editing 85

Data Insight connectionsassigning security 50denying rights 49

data insight project 209Data Insight projects

assigning security 50creating 87deleting 86, 88denying rights 49editing 88purpose 87

Data Insight rulesimporting and exporting 201

Data Insight viewsimporting and exporting 201

data profilingresource intense 165

Data Services job serveradding job server for Information

Steward 162configuring for Information Steward

161Data Services Job Server

description 13Data Services job server group

deleting a job server for InformationSteward 163

displaying for Information Steward162

Data Services Job Server Groupfor Information Steward 161

Data Services Metadata Integratorconfiguring 112

data steward 209database 209datasource schema 209DB2 connection parameters 70defining objects 199degree of parallelism 175

column profiling 176disk requirements 177rule processing 177using 177

deletingcleansing packages 139

deleting source groups 137dependency 176dependency profiling 209deployment

scalability 171developing applications

production phase 200testing phase 199

development process phases 199dimension 209directory structure 209distribution level sub-table 180distribution level table 180DOP

advanced profiling 176

E

editing descriptionscleansing packages 140

EIMAPS 187email notification

configuring notification server 91, 94

processing alert 91, 94encryption

of sensitive data 28exporting and importing 201

extract 209

F

file format 209file repository server 19folders, Data Insight

security rights 41folders, Metadata Management

security rights 55

G

grid computing 178, 180group rights

cleansing packages 61groups

assigning rights 48, 50denying rights 49

H

history of Metadata Integrator runs 131HP Neoview connection parameters

69

I

IBM DB2 connection parameters 70impact

response time 169impact analysis

resource intense 165impact diagram 209importing and exporting 201InfoCube 209Information Steward

accessing 9architecture 11log levels 204, 205logs 203, 205, 206, 207product overview 9services 16user groups 35

Information Steward applicationsecurity rights 63

Information Steward architectureperformance intensive components

166Information Steward components

run on BI platform servers 11Information Steward groups 37Information Steward job server

displaying on CMC 162

2011-04-06216

Index

Information Steward job server groupdescription 161

Information Steward repositoryediting user and password 63

Information Steward users 36information workflose 22Informix IDS connection parameters

71input data

performance 183scalability 183settings 183

installing metadata integrators 105integrator configurations

backing up 196restoring 197

integrator source 209Integrator source configurations

moving 201integrator sources

changing limits for 122configuring 105managing tasks 119run-time parameters 125types of 105viewing and editing 120

integrity 209

J

JDBC connection sourcesconfiguring 116

job serverconfiguring on Data Services 161

job server groupadding job server 162deleting a job server 163

Job Server Groupfor Information Steward 161

JVMruntime parameters 187

K

key data domains 209keystore and truststore

SSL setup for Remote Job Server30

L

lifecycle management console 201lineage

response time 169

lineage (continued)viewing from InfoView for Web

Intelligence documents 106lineage analysis

resource intense 165lineage diagram 209lineage staging table

recalculate lineage information 153logs, viewing 131

M

match standard 209Meta Integration Metadata Bridge

(MIMB) Metadata Integratorconfiguring 113

metadata browsingresource intense 165

Metadata Browsing Servicechanging properties 158

metadata integrator 209runtime parameters 185scheduling 124

Metadata Integrator historyviewing 131

Metadata Integrator logsviewing 131

Metadata Integrator, CommonWarehouse Modelconfiguring 109

metadata integratorsoptions to schedule 90resource intense 165runtime parameters 97when you install Information

Steward 105Metadata Integrators

definition 15running 123running immediately 123tasks 119

Metadata Managementadministration tasks 105best practices 190distributed processing 173lineage staging table 146performance 185performance factors 169pre-defined user groups 54related services 173repository 185scalability 185test phase 199updating search indexes 147

Metadata Management search indexesrescheduling update of 149

Metadata Management search indexes(continued)scheduling update of 148

Metadata Management utilitiesmoving 201

metadata object 209metadata sources

performance factors 169Metapedia 209metapedia category 209metapedia term 209Metapedia terms and categories

importing and exporting 201Microsoft SQL Server connection

parameters 72migrating

application configurations 199Information Steward objects using

lifecyle management console201

migration tools 200MMT_Alternate_Relationship table

description 146scheduling computation of 148

modifying source groups 136moving

Information Steward objects usinglifecyle management console201

multi-threaded filesperformance 182scalability 182

multiple usersperformance 168

MultiProvider 209MySQL connection parameters 73

N

Netezza connection parameters 74NetWeaver Business Warehouse

Metadata Integratorconfiguring 108

NetWeaver BW integrator sourcerun-time parameters 130

notification serveralerts 91, 94configuring for processing 91configuring for rules 94email notification 91, 94

O

object collectionselective 127

object equivalency rule 209

2011-04-06217

Index

object tray 209ODBC connection parameters 74Open Hub Destination 209optimize result set

Data Insight 182performance 182scalability 182

Oracle databaseconnection parameters 76

out of memory erroraction to resolve 133

ownerscleansing packages 139

P

parallelism 175parameters to run integrator sources

125parameters to run metadata integrators

97parent-child 209parsed value 209parsing failure

action to resolve 133parsing rule 209pausing a utility 151performance

considerations 170input data 183

performance considerationsCleansing Package Builder 186degree of parallelism 175deployment 171distributed processing 172grid computing 178input data 183Metadata Management 185multi-threaded files 182optimize result set 182queuing tasks 175repository size 184scheduling tasks 174

performance factors 167concurrent users 168, 169, 170data 168data characteristic 168data characteristics 170Data Insight 168metadata sources 169multiple users 168profiling type 168sample data 170

person and firm cleansing package209

pre-defined user groups 33Metadata Management 54

private cleansing package 209processing

Cleansing Package Builderrelated services 173

Data Insightrelated services 172

degree of parallelism 177distributed 172, 173, 174Metadata Management

related services 173repository 173web application 174

production phase 199, 200profile 209profile connection

configuring for a database source66

configuring for application 79profile connections

assigning security 48profile projects

assigning security 48profile task 209profile tasks 89

monitoring 95pausing and resuming 96runtime parameters 97scheduling 89

profilingadvanced 176best practices 188column

degree of parallelism 176repository 184

profiling task settings 98, 99profiling tasks

configuring 103profiling type

performance 168sizing 168

projectsbest practices 190organizing 190

projects, Data Insightsecurity rights 45

promotingInformation Steward objects using

lifecyle management console201

properties file 209published cleansing package 209publishing

cleansing packages 187

purge utilitydescription 145monitoring 151rescheduling 149run now 150scheduling 148

Q

quality dimensions 209query 209query views 209queuing

tasks 175

R

rebuilding search indexesMetadata Management 147

recurrence options 90redundancy 176redundancy profiling 209Relational Database Metadata

Integratorconfiguring 114

Remote Job ServerSSL 129

Reports optionMetadata Management lineage

staging table 146repository

distributed processing 173Metadata Management 185profiling 184rule processing 185

repository sizeperformance 184scalability 184

requirementsdegree of parallelism 177

resource intenseCleansing Package Builder 165data profiling 165impact analysis 165lineage analysis 165metadata browsing 165metadata integrators 165validation rule 165viewing data 165

response time 167concurrent users 169

restoringintegrator configurations 197

reverse proxy serversdescription 32

2011-04-06218

Index

rightsfor Metadata Management objects

54, 57rule

profilingdegree of parallelism 177

rule processingrepository 185

rule task 209rule task settings 98, 99rule tasks 89

configuring 103monitoring 95pausing and resuming 96runtime parameters 97scheduling 89

rulesbest practices 188importing and exporting 201

run-time parametersBusinessObjects Enterprise user

collection 126SAP NetWeaver BW integrator

source 130running integrator sources 125running metadata integrators 97

options to schedule 90running utilities

options to schedule 90runtime

metadata integrator 185parameters 185

runtime parametersJVM 187

S

same as relationship 209sample data

performance factors 170SAP Applications connection

parameters 81SAP as a source

best practices 180SAP In-Memory Database connection

parameters 68SAP NetWeaver BW connection

parameters 80scalability

considerations 170deployment 171

scalability considerationsCleansing Package Builder 186degree of parallelism 175distributed processing 172grid computing 178

scalability considerations (continued)input data 183Metadata Management 185multi-threaded files 182optimize result set 182queuing tasks 175repository size 184scalability levels 171scheduling tasks 174

schedulingmetadata integrator 124tasks 174

schema 209score 209scorecard 209scripting language 209Secure Socket Layer (SSL) 29Secure Sockets Layer (SSL) 31security

adding users to InformationSteward groups 37

creating users 36Data Insight connections 49, 50Data Insight objects 38Data Insight projects 49, 50Metadata Management objects 53profile connections 48profile projects 48SSL 29user data 28within SAP BusinessObjects

Enterprise 27security information

moving 201security rights

Cleansing Package Builder 61Data Insight connections 43Data Insight folders 41Data Insight projects 45Data Insight tasks 47Data Insight views 46Information Steward application 63Metadata Management folders 55

serveradaptive job server 19adaptive processing server 19file repository server 19

server instance 209servers 12

verify running 155services 12

pertinent to Information Steward16

verify running 156settings

input data 183

sizing factors 167source 209source group 209source groups

creating 136deleting 137metadata sources 135modifying 136moving 201

source system 209SSL 31

configuring remote job server 29, 31

SSL setup for Remote Job Serverkeystore and truststore 30

standard form 209states

cleansing packages 141statuses

cleansing packages 141sub-category 209synchronous RFC connection

SAP as a source 180synonym 209

T

target schema 209tasks

queuing 175scheduling 174

tasks, Data Insightsecurity rights 47

tasks, Metadata Managementsecurity rights 59

terms and categoriesimporting and exporting 201

Test indextermin cell of a table 106

test phase 199testing applications 199time out

Information Steward sessions 9timeliness 209token 209transfer rules 209transformation 209transformation name 209type-specific rights

Metadata Management objects 54, 57

U

uniqueness 176, 209uniqueness profiling 209

2011-04-06219

Index

universe connection sourcesconfiguring 118

unlockingcleansing packages 140

update search index utility 147configuring 153description 145modifying configuration 152monitoring 151run now 150

usage scenario 209user data

securing 28user groups

Data Insight 39Information Steward 35

user rightsData Insight objects 38

usersadding to Information Steward

groups 37assigning rights 48, 50concurrent 168denying rights 49

users (continued)multiple 168

utilitiesdescriptions 145options to schedule 90

utilityconfiguring 186

utiltieschanging limits for 122

V

validation ruleresource intense 165

validation rules 209value 209variation 209View Data Service

changing properties 159viewing data

resource intense 165viewing impact and lineage

response time 169

viewing log for utility 151views

importing and exporting 201views , Data Insight

security rights 46

W

web applicationdistributed processing 174

web application server 19Web application server 13, 14

administration 14Web Intelligence documents

viewing lineage from InfoView 106web template 209workbook 209workflow

adding table to project 22scheduling and running a profile

task 23scheduling and running an

integrator source 23

2011-04-06220

Index