SAP BusinessObjects Metadata Management User's · PDF fileSAP®BusinessObjects™MetadataManagement. ... repository (BOMMRepository ... object. •

SAP BusinessObjects MetadataManagement User's Guide

SAP® BusinessObjects™ Metadata Management XI 3.1 (12.1.0)

© 2009 SAP® BusinessObjects™. All rights reserved. SAP BusinessObjects andits logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid Mart™,

Copyright

SAP BusinessObjects Data Insight™, SAP BusinessObjects Desktop Intelligence™,SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist Security™,SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks orregistered trademarks of Business Objects, an SAP company and/or affiliatedcompanies in the United States and/or other countries. SAP® is a registeredtrademark of SAP AG in Germany and/or other countries. All other namesmentioned herein may be trademarks of their respective owners.

2009-07-28

ContentsIntroduction 13Chapter 1

About this guide.........................................................................................14SAP BusinessObjects Metadata Management overview..........................14Product benefits.........................................................................................16Product documentation..............................................................................17SAP BusinessObjects information resources............................................17

Architecture 19Chapter 2

Architecture overview................................................................................20Central Management System repository objects for MetadataManagement........................................................................................22Web Application Server........................................................................23Metadata integrators............................................................................25Relationship Server..............................................................................27Search Server......................................................................................27

Metadata Management on BusinessObjects Enterprise components.......28

Deployment 31Chapter 3

Deployment................................................................................................32Planning your Metadata Management deployment..............................32Deployment guidelines.........................................................................33Prerequisites for each component.......................................................34Deployment scenarios..........................................................................36

Installation for Windows 43Chapter 4

Preparing to install Metadata Management...............................................44

SAP BusinessObjects Metadata Management User's Guide 3

Pre-installation overview......................................................................44Repository database requirements and preparation............................51Installation scenarios............................................................................53License keys.........................................................................................53

Standard installation of Metadata Management........................................54To begin running the installation program............................................54To accept the license agreement.........................................................55To enter user information and a product key code...............................55To specify the CMS log on information.................................................56To select components to install............................................................57To configure your Metadata Management repository...........................59To configure your existing Web application server...............................60To start the installation..........................................................................61To manually deploy web application server components.....................62

Silent installation........................................................................................63To create a response file......................................................................64To start the silent installation................................................................65Silent install parameters.......................................................................66

Migration....................................................................................................68Migrating from 11.7 to 12.x...................................................................68Migrating from 12.x to 12.x...................................................................69Migrating a Metadata Management repository.....................................70Migrating Metadata Management objects to a different CMS..............72

Copying integrator configurations..............................................................73Backing up and restoring Metadata Management configurations.............74

Backing up configurations....................................................................75Restoring configurations.......................................................................75

Remote Job Server Installation.................................................................76Installing a Remote Job Server............................................................77Renaming File Repository Servers......................................................78Modifying the configuration of a Remote Job Service..........................79

4 SAP BusinessObjects Metadata Management User's Guide

Contents

After installing Metadata Management......................................................82Verifying Metadata Management servers are running.........................82Metadata Integrator server groups.......................................................83Updating the license key......................................................................83

Uninstalling Metadata Management..........................................................84

Installation for UNIX 87Chapter 5

Preparing to install Metadata Management...............................................88Pre-installation overview......................................................................88Repository database requirements and preparation............................95Installation scenarios............................................................................97License keys.........................................................................................97

Standard installation of Metadata Management on UNIX.........................98To begin running the installation program............................................98To accept the license agreement.........................................................99To specify the installation directory.......................................................99To enter product key code..................................................................100To specify the CMS log on information...............................................100To select components to install..........................................................102To configure your Metadata Management repository.........................103To configure your existing Web application server.............................104To start the installation........................................................................104To manually deploy Web Application Server components on UNIX....105

Metadata Integrator server groups..........................................................106Silent installation......................................................................................107

To create a response file....................................................................107Silent install parameters.....................................................................109To start the silent installation..............................................................110

Migration..................................................................................................111Objects that migrate...........................................................................111Migrating a repository.........................................................................112


Contents

Updating the license key..........................................................................115Uninstalling Metadata Management on UNIX.........................................116

Administration 117Chapter 6

Metadata Management administration overview.....................................118Accessing Metadata Management for administrative tasks...............119Managing Metadata Management servers.........................................120Managing security in Metadata Management....................................122Configuring sources for Metadata Integrators....................................133Managing integrator sources and instances......................................153Running a Metadata Integrator..........................................................158Common run-time parameters for metadata integrators....................166Viewing integrator run progress and history ......................................175View the collection results..................................................................176Grouping Metadata Integrator sources..............................................177Managing Metadata Management utilities.........................................179Viewing and editing repository information.........................................189Exporting objects to XML...................................................................190

SAP BusinessObjects Metadata Management Explorer 195Chapter 7

Metadata Management Explorer.............................................................196Accessing Metadata Management Explorer......................................197Metadata Management Explorer user interface.................................198

Viewing objects in the Metadata Management Explorer.........................199Directory home page..........................................................................199Navigating metadata .........................................................................201

Searching for objects...............................................................................202Search scope.....................................................................................203Search string parameters ..................................................................203Advanced search................................................................................204


Contents

Search results ...................................................................................206Viewing custom reports...........................................................................207Defining custom reports...........................................................................208

Metadata Management Views to query for your Crystal Reports.......208Typical usage scenarios.....................................................................210Enabling your reports in Metadata Management Explorer ................211

Viewing relationships between objects....................................................212Viewing impact and lineage of objects...............................................215Options to view relationships..............................................................215

Adding annotations for user notes...........................................................221Adding annotations ............................................................................221Editing annotations ............................................................................222

Custom attributes.....................................................................................223Creating custom attributes.................................................................224Entering values for custom attributes.................................................228

Metadata Management Metapedia..........................................................231Understanding terms and categories.................................................233Data steward and security..................................................................234Working with Metapedia terms and categories..................................234Custom attributes in Metapedia..........................................................242Metapedia search...............................................................................242Object association and quick search..................................................244

Exporting relational objects......................................................................245Selecting objects to export ................................................................248Exporting objects to a general-purpose CWM XML file ....................249Exporting objects to create a universe...............................................253

User-defined relationships between objects............................................259Establishing user-defined relationships between objects...................260Removing a user-defined relationship................................................264

Changing preferences for relationships...................................................264Recognizing the same object in multiple source systems .................265


Contents

Setting impact and lineage preferences.............................................266Setting object equivalency rules for Same As relationships ..............267

SAP BusinessObjects Enterprise Metadata 271Chapter 8

Exploring SAP BusinessObjects Enterprise metadata............................272SAP BusinessObjects Enterprise metadata objects................................273

SAP BusinessObjects Enterprise object relationships.......................275SAP NetWeaver BW objects as sources............................................277

Navigating SAP BusinessObjects Enterprise metadata..........................278Exploring the universe metadata object.............................................279Exploring an instance of a universe ..................................................280Exploring the report metadata object.................................................281Exploring Users..................................................................................284Exploring Groups ...............................................................................284Exploring personal folders..................................................................285

Viewing relationships for universe objects and reports...........................286Viewing relationships for universe objects and reports......................289Impact analysis for a universe object.................................................291Lineage analysis for universe object..................................................291Lineage analysis for a report..............................................................294

Viewing relationships with SAP NetWeaver BW sources........................297SAP NetWeaver BW objects used by a Crystal Report.....................297Universe lineage from InfoCube.........................................................300Crystal Report lineage from DataStore Object...................................301

Viewing relationships of users and groups..............................................302Finding user privileges to reports and universes................................303Finding group privileges to reports and universes.............................305Impact analysis for users and groups ...............................................306Privileges and object rights for users and groups..............................308


Contents

SAP NetWeaver Business Warehouse Metadata 311Chapter 9

Exploring SAP NetWeaver Business Warehouse metadata....................312SAP NetWeaver Business Warehouse metadata objects.......................314

SAP NetWeaver BW object relationships...........................................319SAP NetWeaver BW object attributes collected.................................320

Navigating SAP NetWeaver Business Warehouse metadata..................323Exploring the InfoCube metadata object............................................324Exploring an InfoCube instance.........................................................325

Viewing relationships of SAP NetWeaver BW objects ............................327Impact analysis of a BW source system............................................327Impact of BW source on Web Intelligence Documents......................329Impact of BW Open Hub table on Crystal Report..............................330Lineage of web templates..................................................................331Lineage of a BW Crystal Report.........................................................333

Data Modeling Metadata 335Chapter 10

Exploring Data Modeling metadata ........................................................336Navigating data modeling metadata .......................................................337

Exploring CWM objects .....................................................................338Exploring an instance of a modeling object .......................................340

Viewing relationships of CWM objects.....................................................340Same As relationships........................................................................341Impact analysis for a table..................................................................341Lineage analysis ................................................................................342

SAP BusinessObjects Data Services Metadata 345Chapter 11

Exploring Data Services Metadata..........................................................346Navigating Data Services metadata........................................................347

BusinessObjects Data Services objects.............................................348


Contents

Exploring Data Services sources metadata.......................................351Exploring Data Services objects .......................................................353Exploring data flow metadata.............................................................353Exploring an instance of a data flow..................................................354Exploring datastore metadata............................................................356Exploring a table instance..................................................................357Exploring a column instance..............................................................358

Viewing Data Services object relationships.............................................358Viewing Same As relationships..........................................................361Viewing impact and lineage of tables.................................................361Viewing impact and lineage of Open Hub tables...............................365Viewing column mappings for tables..................................................366Viewing impact and lineage of columns.............................................367

SAP BusinessObjects Data Federator Metadata 369Chapter 12

Data Federator Metadata Integrator overview.........................................370Exploring Data Federator Metadata........................................................370Data Federator objects............................................................................371

Data Federator object relationships...................................................373Navigating Data Federator Metadata......................................................374

Exploring Data Federator sources metadata.....................................375Exploring deployed versions metadata..............................................377Exploring catalog metadata................................................................377Exploring datasource tables...............................................................378Exploring target tables metadata ......................................................378Exploring a target table instance........................................................379Exploring a column instance..............................................................382

Viewing Data Federator object relationships...........................................382Relationship tabs on Metdata Management Explorer........................383Setting object equivalency rules for Data Federator .........................385Viewing Same As relationships..........................................................385


Contents

Viewing impact and lineage of tables.................................................386Viewing impact and lineage of columns.............................................388

Relational Database Metadata 393Chapter 13

Exploring Relational Database metadata ...............................................394Navigating relational database metadata ...............................................395

Relational Database objects ..............................................................395Exploring a table.................................................................................399Exploring an instance of a column.....................................................399Exploring an instance of a view..........................................................400

Viewing relationships in a database source............................................401Viewing synonyms and alias relationships.........................................402Viewing primary key and foreign key relationships............................404Viewing impact and lineage ...............................................................405

Index 409


Contents


Contents

Introduction

1

About this guideThis guide describes the purpose, installation, configuration, and usage ofSAP® BusinessObjects™ Metadata Management.

The expected audience for this technical information include:

• Administrators who install and configure SAP BusinessObjects MetadataManagement and its components.

• Application developers, business report designers, consultants, anddatabase administrators who perform any of the following tasks:

• Browse and search metadata to determine relationships and analyzethe impact of changes to source data.

• Define and maintain Business Intelligence reports.

• Extract data, build and maintain data warehouses, or integrate datafrom multiple sources.

• Define, organize, and maintain business terms.

SAP BusinessObjects MetadataManagement overview

SAP BusinessObjects Metadata Management is a Web-based applicationthat provides an integrated view of metadata and their relationships acrossall of the products used in a Business Intelligence project.

Metadata is definitional data that provides information about data managedwithin an application or system. Metadata includes the following information:

• Attributes such as name, size, data type

• Structures such as length, fields, columns

• Properties such as where it is located, how it is associated, ownership

• Descriptive information about the context, quality and condition, orcharacteristics of the data

As the following diagram illustrates, the software collects and unifies metadatafrom data sources such as:


Introduction1 About this guide

• Business Intelligence (BI) systems• Databases• Data Integration technologies, such as SAP BusinessObjects Data

Services and SAP BusinessObjects Data Federator• Modeling utilities

You can enrich the collected metadata with the following information, whichyou can use to search for objects and perform analysis on the resultingobjects.• Annotations–You can add user notes to any object.• Custom attributes–You can define custom attributes to do tasks such as

assign a data steward to objects and tag objects as containing sensitiveinformation.

• Metapedia terms and categories–You can implement a business glossaryof terms related to your business data and organize the termshierarchically.

You can export relational objects from the SAP BusinessObjects MetadataManagement repository to a Common Warehouse Modeling (CWM) XMLfile. You can then import the CWM XML file into SAP BusinessObjectsEnterprise to create a universe.


1IntroductionSAP BusinessObjects Metadata Management overview

Product benefitsWith SAP BusinessObjects Metadata Management, you can do the following:

• View all metadata associated with your Business Intelligence systems,database sources, data integration systems, and modeling utilities.

• Analyze lineage to understand where the data came from and whatsources provide data for your Business Intelligence reports.

• Analyze the impact of changing a source table, column, or report field onyour Business Intelligence reports.

• Detect and analyze relationships (such as Is Same As, Is Related To)across metadata sources.

• Define standard business terms in a business glossary, relate businessterms to objects, and search for metadata objects using familiar businessterms.

• Analyze the metadata to determine usage of objects by other objects,such as how many reports are based on this universe or what tables arein this universe.

These capabilities provide the following benefits:

• Lower your total cost of ownership (TCO) because you can do thefollowing:• Track usage of data and reports

For example, you can determine which data in your data warehouseis never used in your Business Intelligence reports or which reportsare never viewed by users.

• Manage change

For example, you can determine which Business Intelligence reportswould be affected if you modified your source tables and you canidentify the users of the affected reports.

• Determine the source of the data in your documents and reports.

For example, you can determine the source of any number in any report.

• Determine what Business Intelligence information a user can access.

For example, you can determine what privileges a user or user group hasfor accessing reports or data universes.


Introduction1 Product benefits

• Enable the discovery, common understanding, and consistentimplementation of business concepts through Metapedia, bridging thegap of understanding between an organization's business users and ITstaff.

• Understand your entire Business Intelligence project because you canview the relationships (such as impact and lineage) of all metadata objectsfrom your data integration system to your relational databases to yourBusiness Intelligence reports.

Product documentationYour product CD provides the SAP BusinessObjects Metadata Managementdocumentation in PDF format. You can read PDF files using the latest versionof Adobe Acrobat Reader (download instructions at the Adobe websitehttp://www.adobe.com/products/acrobat/readstep2.html).

To view these documents after you install the software, go to theStartmenu,select Programs >BusinessObjects XI 3.1 >BusinessObjects MetadataManagement, and choose:

• Release Notes–Opens the Release Notes PDF document, which includessupported configurations and known problems in the associated softwarerelease.

• User's Guide–Opens this document, which describes the purpose,installation, configuration, and usage of the software.

Obtain other relevant documents by visiting the Technical CustomerAssurance documentation page at http://service.sap.com/.

SAP BusinessObjects informationresources

A global network of SAP BusinessObjects technology experts providescustomer support, education, and consulting to ensure maximum businessintelligence benefit to your business.

Useful addresses at a glance:

ContentAddress


1IntroductionProduct documentation

http://www.adobe.com/products/acrobat/readstep2.html

http://service.sap.com/

ContentAddress

Information about Technical Customer Assuranceprograms, as well as links to technical articles,downloads, and online forums. Consulting servicescan provide you with information about how SAPBusinessObjects can help maximize your businessintelligence investment. Education services canprovide information about training options andmodules. From traditional classroom learning totargeted e-learning seminars, SAP BusinessOb-jects can offer a training package to suit yourlearning needs and preferred learning style.

Customer Support, Consulting, and Educa-tion services

http://service.sap.com/

Get online and timely information about SAP Busi-nessObjects Data Services, including tips andtricks, additional downloads, samples, and muchmore. All content is to and from the community, sofeel free to join in and contact us if you have asubmission.

SAP BusinessObjects Data Services Com-munity

https://www.sdn.sap.com/irj/boc/ds

Search the SAP BusinessObjects forums on theSAP Community Network to learn from other SAPBusinessObjects Data Services users and startposting questions or share your knowledge withthe community.

Forums on SCN (SAP Community Network

https://www.sdn.sap.com/irj/scn/forums

Blueprints for you to download and modify to fityour needs. Each blueprint contains the necessarySAP BusinessObjects Data Services project, jobs,data flows, file formats, sample data, template ta-bles, and custom functions to run the data flows inyour environment with only a few modifications.

Blueprints

http://www.sdn.sap.com/irj/boc/blueprints

SAP BusinessObjects product documentation.Product documentation

http://help.sap.com/businessobjects/

Get information about supported platforms for SAPBusinessObjects Data Services.

In the left panel of the window, navigate to Doc-umentation > Supported Platforms > Busines-sObjects XI 3.x. Click the BusinessObjects DataServices link in the main window.

Products Availability Report

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


Introduction1 SAP BusinessObjects information resources

http://www.service.sap.com/

https://www.sdn.sap.com/irj/boc/ds

https://www.sdn.sap.com/irj/sdn/businessobjects-forum

http://www.sdn.sap.com/irj/boc/blueprints

http://help.sap.com/


Architecture

2

SAP BusinessObjects Metadata Management runs on the SAPBusinessObjects Enterprise platform which is designed for high performanceacross a broad spectrum of user and deployment scenarios. You can offloadprocessor intensive scheduling and processing to dedicated servers toimprove performance. The architecture is designed to meet the needs ofvirtually any business intelligence (BI) deployment.

This section describes how the components of SAP BusinessObjectsMetadata Management fit into the overall platform architecture and individualservices and components that make up SAP BusinessObjects Enterprise.This information will help administrators understand how to plan thedeployment, management, and maintenance of the metadata managementapplication.

Related Topics• Architecture overview on page 20• Metadata Management on BusinessObjects Enterprise components on

page 28

Architecture overviewThe following diagram shows the SAP BusinessObjects Enterprise (BOE)components that SAP BusinessObjects Metadata Management (BOMM)uses.


Architecture2 Architecture overview

The following table shows each SAP BusinessObjects Metadata Managementcomponent and which BusinessObjects Enterprise component it runs on.

SAP BusinessObjects Enterprisecomponent on which it runs

SAP BusinessObjects MetadataManagement component

BusinessObjects Enterprise PlatformApplication Server

Administration and Explorer applica-tions

Central Management System (CMS)Metadata Management CMS Respos-itory Objects

• Metadata Management Job Server(Adaptive Job Server)

• Adaptive Processing ServerMetadata Integrators and utilities


2ArchitectureArchitecture overview

SAP BusinessObjects Enterprisecomponent on which it runs

SAP BusinessObjects MetadataManagement component

Adaptive Processing ServerRelationship Server

Adaptive Processing ServerSearch Server

Related Topics• Web Application Server on page 23• Central Management System repository objects for MetadataManagement

on page 22• Metadata integrators on page 25• Search Server on page 27

Central Management System repository objects forMetadata Management

The Central Management System (CMS) stores information that describesthe SAP BusinessObjects Metadata Management application and theoperations of the servers that Metadata Management uses for processing.CMS uses these repository objects to manage SAP BusinessObjectsEnterprise, including the following tasks for Metadata Management:• Managing security

The CMS manages security information, such as user accounts, groupmemberships, and object rights that define user and group privileges toaccess the different features of Metadata Management.

• Managing servers

When you define multiple Job Servers to run metadata integrators, theCMS monitors these server and distributes the work processes amongthem. The CMS handles load balancing and automated clustering to avoidbottlenecks and maximize hardware efficiency.

For more information about CMS, refer to the BusinessObjects EnterpriseAdministrator's Guide.



Related Topics• Architecture overview on page 20• Managing security in Metadata Management on page 122

Web Application Server

SAP BusinessObjects Metadata Management requires a Java or Servletweb application server to process the server-side scripts that make up webapplications that:• perform administrative tasks on the Central Management Console (CMC).• comprise the Explorer through which you can view and analyze

relationships such as impact and lineage.

The supported web application servers include the following:• Apache Tomcat• WebSphere• WebLogic• Oracle Application Server

Note:For specific version compatibility, refer to the Products Availability Report inthe SAP BusinessObjects Support > Supported Platforms section of the SAPService Marketplace: http://service.sap.com/bosap-support.

Related Topics• Administration on page 23• SAP BusinessObjects Metadata Management Explorer on page 24

Administration

You use the Central Management Console (CMC) to perform SAPBusinessObjects Metadata Management administrative tasks such as thefollowing:

• Configure and run metadata integrators• Define source groups to subset the metadata when viewing relationships

such as Same As, Impact, and Lineage



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

• Administer security for the SAP BusinessObjects Metadata ManagementExplorer, Metapedia, metadata integrators, and source groups

• Run SAP BusinessObjects Metadata Management utilities

Related Topics• Metadata Management administration overview on page 118

SAP BusinessObjects Metadata Management Explorer

The SAP BusinessObjects Metadata Management Explorer is a web-basedinterface through which you can:

• View the metadata from the different sources in an organized and easyto understand way.

• Search for objects without the need to know the source or application inwhich it exists.

• Define Metapedia terms related to your business data and organize theterms into categories.

• Add annotations to an object.• Define custom attributes and values for an objects.• Run pre-defined reports that answer typical business questions such as

"Which Universe objects are not used in my reports?" or "Which reportsare using my tables?"

• View relationships between objects, reports and documents that youcreate with BusinessObjects Business Intelligence products. Relationshipsinclude the following:• Same As - Allows you to determine if an object in one source is the

same as an object in another source.• Related To - Allows you to determine if an object in one source is

related to an object in another source.• View impact and lineage of objects within the same source or within

different sources.• Impact analysis - Allows you to identify which objects will be affected

if you change or remove other connected objects.• Lineage analysis - Allows you to trace back from a target object to the

source object.• Create user-defined relationships for objects.



Related Topics• SAP BusinessObjects Metadata Management Explorer on page 195

Metadata integrators

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

into the SAP BusinessObjects Metadata Management 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

availability.• Each run as a separate process.

SAP BusinessObjects Metadata Management provides the following metadataintegrators:

Metadata collectedMetadata integrator name

Collects metadata about objects suchas universes, Crystal Reports, Web In-telligence documents, and Desktop In-telligence documents.

SAP BusinessObjects EnterpriseMetadata Integrator

Collects metadata about objects suchas Queries, InfoProviders, InfoObjects,Transformations, and DataSourcesfrom an SAP NetWeaver BusinessWarehouse system.

SAP NetWeaver Business WarehouseMetadata Integrator

Collects metadata about objects suchas catalogs, schemas, and tables fromthe CWM Relational Package.

Common Warehouse Model (CWM)Metadata Integrator

Collects metadata about objects suchas projects, catalogs, datasources, andmapping rules from a Data Federatorrepository.

SAP BusinessObjects Data FederatorMetadata Integrator



Metadata collectedMetadata integrator name

Collects metadata about objects suchas source tables, target tables, andcolumn mappings from a Data Servicesrepository.

SAP BusinessObjects Data ServicesMetadata Integrator

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

Sybase Power Designer, Embar-cadero ER/Studio, and Oracle De-signer

• Extract, Transform, and Load (ETL)metadata such as Oracle Ware-house Builder, and Microsoft SQLServer IntegrationServices (SSIS)

• OLAP and BI metadata such asIBM DB2 Cube Views, OracleOLAP, and Cognos BI Reporting

Meta Integration Metadata Bridge(MIMB) Metadata Integrator (alsoknown as MITI Integrator)

Collects metadata from relationaldatabase management systems(RDBMS) which can be DB2, MySQL,Oracle, SQL Server, Java DatabaseConnectivity (JDBC), or a BusinessOb-jects Universe connection. Collectedmetadata includes the definition of ob-jects such as tables, view, synonyms,and aliases.

Relational databases Metadata Integra-tor

You can also obtain third-party metadata integrators for other data sources.For more information about third-party metadata integrators, contact yoursales representative.

Related Topics• SAP BusinessObjects Enterprise metadata objects on page 273• Exploring Data Modeling metadata on page 336• Data Federator objects on page 371• BusinessObjects Data Services objects on page 348



• http://www.metaintegration.net/Products/MIMB/SupportedTools.html• Exploring Relational Database metadata on page 394• Deployment scenarios on page 36

Relationship Server

The Relationship Server computes metadata object relationships (such asdata lineage and change impact analysis). The SAP BusinessObjectsMetadata Management Explorer uses the results of these computedrelationships to display metadata relationship diagrams.

It is recommended that you install the Relationship Server on a differentcomputer than the web application server. An Adaptive Processing Serverof SAP BusinessObjects Enterprise must already be installed on thatcomputer.

You can deploy multiple Relationship Servers for load balancing andavailability.

Related Topics• Architecture overview on page 20• Deployment scenarios on page 36

Search Server

The Search Server allows you to find an object that exists in any sourcewhile viewing metadata on the SAP BusinessObjects Metadata ManagementExplorer. It uses the Lucene Search Engine.

The Search Server runs on an Adaptive Processing Server of SAPBusinessObjects Enterprise. You can deploy multiple search servers for loadbalancing and availability.

The Search Server constructs the search index during the execution of theMetadata Integrators, and the File Repository Server stores the compressedsearch index. The Search Server also updates the search index for changesto Metapedia terms and categories, custom attributes, and annotations. Ifthe Search Server is not available during the construction and updateprocesses, the search might return incorrect results. For these situations,



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

Metadata Management provides a utility to reconstruct the search index. Fordetails, see Recreating search indexes on page 185.

Related Topics• "Metadata Management Architecture"• Deployment scenarios on page 36

Metadata Management onBusinessObjects Enterprise components

The following table describes how SAP BusinessObjects MetadataManagement uses each pertinent SAP BusinessObjects Enterprisecomponent.

How SAP BusinessObjects Metadata Manage-ment uses component

SAP BusinessObjectsEnterprise component

Deploys the SAP BusinessObjects Metadata Man-agement application which consists of:• Metadata Management on CMC• Metadata Management Explorer

SAP BusinessObjectsEnterprise ApplicationServer

Manages the following for SAP BusinessObjectsMetadata Management:• Metadata Management servers• Metadata integrator source configurations• Source group configurations• Metadata Management utilities• Security (authentication and authorization)

Central ManagementConsole (CMC)


Architecture2 Metadata Management on BusinessObjects Enterprise components

How SAP BusinessObjects Metadata Manage-ment uses component

SAP BusinessObjectsEnterprise component

Responsible for maintaining a database of informa-tion about your SAP BusinessObjects Enterprisesystem. The data stored by the CMS includes infor-mation about users and groups, security levels, SAPBusinessObjects Enterprise content, and servers.For more information about the CMS, see SAPBusinessObjects Enterprise Administrator's Guide.

When you create a configuration for a metadataintegrator source, SAP BusinessObjects MetadataManagement stores the configuration in CMS.

Central ManagementServer (CMS)

Launches the scheduled execution of a metadataintegrator or a Metadata Management utility.

When you install SAP BusinessObjects MetadataManagement on an Adaptive Job Server, you alsoinstall metadata integrator types for sources in-stalled in CMS.

Metadata ManagementJob Server

Runs the following for SAP BusinessObjects Meta-data Management:• Relationship Service• Search Service• Test Connection Service for integrator sources

Adaptive ProcessingServer

Stores files associated with the execution of ametadata integrator or a search. These files includethe metadata integrator definitions, history logs, andsearch indexes.

File Repository Server


2ArchitectureMetadata Management on BusinessObjects Enterprise components


Architecture2 Metadata Management on BusinessObjects Enterprise components

Deployment

3

DeploymentTo provide flexibility, reliability, and scalability, you can install the componentsthat make up SAP BusinessObjects Enterprise on one or many machines.You can also install the components of SAP BusinessObjects MetadataManagement on one or many machines to take advantage of the samebenefits.

Server processes can be "vertically scaled" (where one computer runsseveral, or all, server-side processes) to reduce cost, or "horizontally scaled"(where server processes are distributed between two or more networkedmachines) to improve performance. You can also run duplicate instances ofa server process on the same machine, or across several networkedmachines.

For example with Metadata Management, you can install multiple AdaptiveJob Servers to run Metadata Integrators on separate computers to distributethe workload and improve performance. You can also install the SearchServer on an Adaptive Processing Server on a different computer from theAdaptive Job Servers. For sample deployments, see Deployment scenarioson page 36.

Related Topics• Planning your Metadata Management deployment on page 32• Deployment guidelines on page 33• Deployment scenarios on page 36

Planning your Metadata Management deployment

This section provides guidelines for assessing your organization's needsand suggestions for deployment scenarios. By evaluating your needs beforeyou deploy your SAP BusinessObjects Metadata Management system, youcan keep troubleshooting to a minimum.

The section includes examples and suggestions for deployment, but it isimportant to note that each deployment is unique. The flexibility of the SAPBusinessObjects Enterprise service-based architecture allows you to tailorthe deployment to serve your organization's requirements as precisely aspossible.


Deployment3 Deployment

Planning your deployment involves the following steps:1. Refer to the Products Availability Report in the SAP BusinessObjects

Support > Supported Platforms section of the SAP Service Marketplace:http://service.sap.com/bosap-support.

2. Review the key concepts you need to consider for your deployment,including operating system, database, and application serverconsiderations, in addition to security, performance and scalability, andhigh availability. See "Assessing your organization's environment" in theSAP BusinessObjects Enterprise XI 3.0 Deployment Planning Guide.

3. Choose an initial deployment architecture. Which deployment architecturewill serve your needs within the limits of your resources?

For suggestions and common configurations, see Deployment scenarioson page 36.

Deployment guidelines

Guidelines to deploy SAP BusinessObjects Metadata Managementcomponents include the following:• The Metadata Management Web applications should be on a separate

computer than the Metadata Integrators.• The Metadata Management repository should be on a separate computer

from the Metadata Management Web applications, Adaptive ProcessingServer, and Adaptive Job Servers to obtain a higher throughput.

• To improve database throughput, the Metadata Management repositoryshould be near the job server that processes the largest amount of data.Therefore, you can install the repository on the same computer as theMetadata Integrator that processes the largest amount of data.

• The Relationship Server should be on a separate computer than the webapplication server to obtain higher throughput.

• The Relationship Server can be combined with any Metadata Integrator(Job Server), or it can be on its own computer. The rationale for thiscombination is that Metadata Integrators usually run at night or othernon-business hours, and the Relationship Server runs during normalbusiness hours when users are viewing relationships (such as impactand lineage) on the Metadata Management Explorer.

• The Search Server can be combined with any Job Server or other server,or it can be on its own computer. The rationale for this combination is thatMetadata Integrators usually run at night or other non-business hours,


3DeploymentDeployment


and the Search Server runs during normal business hours when usersare searching on the Metadata Management Explorer.

• If your Metadata Integrators runs are constrained by a small executionwindow, deploy each Metadata Integrator on a separate computer.

• For high availability, you can deploy a Metadata Integrator on multiplecomputers. For more details, see the SAP BusinessObjects EnterpriseXI 3.0 Deployment Planning Guide.

Prerequisites for each component

To deploy a subset of SAP BusinessObjects Metadata Managementcomponents on each computer, you must have the necessary softwarealready installed on that computer. The following table shows the prerequisitesoftware for each component.

Prerequisite softwareFeature category

The CMS component of SAP BusinessObjects Enter-prise XI 3.0.1 and above

Metadata Management CMSRepository Objects

Note:You must install this component first(to build the Metadata Managementrepository). Then you can install therest of the Metadata Managementcomponents in any order on anycomputer.




• Metadata Management CMS Repository Objectscomponent must already be installed (not necessar-ily on this computer)

• Following components of SAP BusinessObjectsEnterprise XI 3.0.1 and above:• Adaptive Job Server• Adaptive Processing Server

• Client libraries for the source system installed onthis computer. For example, the SAP BusinessOb-jects Enterprise Metadata Integrator requires SAPBusinessObjects Enterprise Full Client installed onthis computer.

• For the BusinessObjects Enterprise Metadata Inte-grator to collect Crystal Reports or universes whosesources are SAP NetWeaver BW objects, you mustinstall the BusinessObjects XI Integration for SAPSolutions on SAP BusinessObjects Enterprise(BOE). This requirement is for reports that werecreated with theRefresh on Open option becausewhen the Metadata Integrator collects the metadatafrom the BOE system, the BOE system will connectto the source BW system to refresh the data auto-matically.• The BusinessObjects Enterprise Metadata Inte-

grator supports two drivers: SAP BW MDXQuery and SAP Operational Data Store.

• The BusinessObjects XI Integration for SAPSolutions has prerequisites that you must install.For more information, see the BusinessObjectsXI Integration for SAP Installation Guide.

Installing this Metadata Integrator installs the Meta-data Management Job Server (MMJobServer).

Metadata Integrators

Note:You must install this component on asupported Windows platform.


• Adaptive Processing Server component of SAPBusinessObjects Enterprise XI 3.0.1 and above

MetadataManagementRelationshipServer






• Adaptive Processing Server component of SAPBusinessObjects Enterprise XI 3.0.1 and above

Metadata Management SearchServer



• Web Application Server where SAP BusinessOb-jects Enterprise applications are deployed

Note:If you are manually installing the Web Application, youyou must copy a .war file.

Web Application

Related Topics• To manually deploy web application server components on page 62

Deployment scenarios

After you determine the needs of your users and the resources required forthe deployment, you can develop an initial deployment plan for SAPBusinessObjects Metadata Management.

This section describes sample scenarios for administrators planning aninstallation of Metadata Management. It is important to note that the optimalconfiguration for your deployment will depend on many factors: hardwareconfiguration, database software, reporting requirements, operating system,clock speed, hyperthreading, disk speed, application server configuration,load frequency, and many more.

Every deployment is unique, and these examples are provided only asguidelines.



Scenario 1: Performance in small execution window

This scenario illustrates a situation in which your Metadata Integrators runmight take several hours to complete, and you want to ensure it has enoughresources to complete as fast as possible. The following diagram shows howthe components of SAP BusinessObjects Enterprise (BOE) and SAPBusinessObjects Metadata Management (BOMM) are deployed on sevencomputers.

The diagram shows:• 1 back-end server to host CMS framework servers (SJ-CMS-01).• 1 processing server to host the Metadata Management Search Server

(SJ-PS-01).• 4 processing servers to host the Metadata Integrators. The assumptions

are that:



• The CWM Integrator is run very infrequently. Therefore, the CWMMetadata Metadata Integrator and RDBMS Metadata Integrator canbe installed on the same computer (SJ-PS-02).

• The Relationship Server is run during the day and can be installed ona computer with any Metadata Integrator, which is usually run at night.The The SAP NetWeaver BW Metadata Integrator (BW Integrator) isrun frequently and processes a large amount of metadata. Therefore,it is installed on its own computer with the Relationship Server(SJ-PS-03).

• The Data Services Metadata Integrator (DS Integrator) is run frequentlyand processes a large amount of metadata. Therefore, it is installedon its own computer (SJ-PS-04).

• The BusinessObjects Enterprise Metadata Integrator (BOE Integrator)is run frequently and processes a large amount of metadata. Therefore,it is installed on its own computer (SJ-PS-05).

• 1 web application server (SJ-WS-01) to host CMC applications, includingthe Metadata Management application.

• 1 back-end database server for the Metadata Management repository(SJ-DB-01).

Scenario 2: Performance and small number of computers

This scenario illustrates a situation in which your Metadata Integrators runmight take several hours to complete, but you have a limited number ofcomputers. The following diagram shows how the components of SAPBusinessObjects Enterprise and SAP BusinessObjects MetadataManagement are deployed on four computers.



The diagram shows:• 1 back-end server (SJ-CMS-01) to host CMS framework servers.• 1 processing server (SJ-PS-01) to host the Metadata Management Search

Server, the SAP BusinessObjects Data Services Metadata Integrator,RDBMS Metadata Integrator, and the SAP NetWeaver BusinessWarehouse (BW) Metadata Integrator.

The rationale to combine these components is that the execution time snot very long for each of these Metadata Integrator and they can bescheduled to run at different times.



• 1 processing server (SJ-PS-02) to host the CWM Metadata Integrator,SAP BusinessObjects Enterprise Metadata Integrator (BOE Integrator),the Relationship Server, and SAP BusinessObjects Metadata Managementrepository (BOMM Repository). The assumption is that the CWM Integratorruns very infrequently compared to the BusinessObjects EnterpriseIntegrator.

Note:To improve database throughput, the Metadata Management repositoryshould be near the job server that processes the largest amount of data.Therefore, you can install the repository on the same computer as theMetadata Integrator that processes the largest amount of data.

• 1 web application server (SJ-WS-01) to host CMC applications, includingthe Metadata Management application.

Scenario 3: High availability

This example shows a scenario in which you want to ensure that computersare always available to run Metadata Integrators and the Relationship Server,and therefore you have redundant installations. The following diagram showsa possible deployment of redundant Metadata Integrators and RelationshipServers across multiple computers.



This diagram shows the following:• The SAP BusinessObjects Data Services (DS), Relational Database

(RDBMS), and SAP NetWeaver Business Warehouse (BW) MetadataIntegrators are replicated on two processing servers (SJ-PS-01 andSJ-PS-03).

• The CWM and SAP BusinessObjects Enterprise Metadata Integratorsare replicated on two processing servers (SJ-PS-02 and SJ-PS-04).

• The Relationship Server is repicated on two processing servers (SJ-PS-02and SJ-PS-03).





Installation for Windows

4

Preparing to install MetadataManagement

Pre-installation overview

SAP BusinessObjects Metadata Management provides an open and flexiblearchitecture that supports a multitude of deployment and configurationscenarios. Before you install the product you should:• Ensure that that your network and systems meet the basic requirements

for an SAP BusinessObjects Metadata Management installation.• Obtain the product software by electronic download or on CD/DVD, as

well as any required licensing keycodes.• Review the SAP BusinessObjects Metadata Management Release Notes

and the section Architecture on page 19.• Ensure that the user who will run the installation setup program has

adequate permissions to complete the installation tasks.• Determine where the product components should be installed and consider

how you should prepare your infrastructure and set up your environment,including server locations.

• Decide the database server to use for the SAP BusinessObjects MetadataManagement repository and prepare the database.

• Determine your installation method.

The following sections list the software and system requirements and theinstall methods available to you for installing SAP BusinessObjects MetadataManagement.

Note:The following Metadata Management components can only be installed onWindows (you cannot install them on UNIX):• Metadata Integrators• Search Server (provides ability to search metadata on the Metadata

management Explorer)• Relationship Server

Related Topics• Architecture on page 19


Installation for Windows4 Preparing to install Metadata Management

• License keys on page 97

System requirements

For a detailed list of supported environments and hardware requirements,refer to the Products Availability Report in the SAP BusinessObjects Support> Supported Platforms section of the SAP Service Marketplace: http://service.sap.com/bosap-support. This document includes specific version andpatch-level requirements for databases, applications, web application servers,web browsers, and operating systems.

Generally, the following components must be preinstalled and configuredcorrectly before you can install SAP BusinessObjects Metadata Management:• Microsoft Windows 2003 operating system - Required for the Metadata

Integrators and Search Server components of Metadata Management.• Solaris, AIX, or Linux operating system - Optional for the Metadata

Management CMS Repository Objects and Web Applications components.• Microsoft Internet Explorer• SAP BusinessObjects Enterprise XI 3.0 FP1 required components for the

specific Metadata Management component to be installed on thiscomputer. See Prerequisites for each component on page 34.

Metadata Management uses the Web application server and Java 2Software Development Kit (JDK) that BusinessObjects Enterprise uses.

Note:For UNIX, you must increase the memory setting for Web Logic in thefollowing directory: Weblogic_install/wlserver_10.0/samples/domains/wl_server/bin/setDomainEnv.sh. Change the value of theparameter -XX:MaxPermSize from 128m to 256m .

Note:To install Metadata Management, you must be the BusinessObjectsEnterprise Administrator.

Network requirements

When installing SAP BusinessObjects Metadata Management on multiplecomputers, you must ensure that:


4Installation for WindowsPreparing to install Metadata Management



• each target machine can communicate over TCP/IP with the machinerunning the Central Management Server (CMS).

• the target machines can communicate over TCP/IP with each other. Inparticular:• your Metadata Integrators must be able to communicate with the

machine that is running the Metadata Management repository.• your Search Server must be able to communicate with the machine

that is running the web application server for the MetadataManagement Explorer and machines where Metadata Integrators aredeployed.

For more information on the communication between components, refer toArchitecture on page 19.

User permissions for installing Metadata Management

To successfully install SAP BusinessObjects Metadata Management onWindows, the user running the setup program must have the permissionslisted in the table below:



Required permissionsCategory

Administrative privileges on the local machine.Operating Sys-tem

TCP/IP access to all machines where you want to installcomponents - all specified ports must be available.

Network

You must be the SAP BusinessObjects Enterprise Adminis-trator.

SAPBusinessOb-jects Enterprise

Rights to add and drop database objects (such as tables andviews), plus rights to read, write, and edit table rows.

Database

It is recommended that you use the same user account forinstalling BusinessObjects Enterprise and your web applica-tion server.

To deploy Metadata Management web applications usinga user account different from the one used to install theweb application server, see "Minimum user rights for de-ploying web applications" in the BusinessObjects Enter-prise XI 3 Installation and Configuration Guide.

Web applicationserver

Choose components and determine component distribution

You can choose to install SAP BusinessObjects Metadata Managementcomponents on one or more computers based on available resources andyour deployment planning. For guidelines and suggested scenarios todistribute the software components, see Deployment on page 32.

Note:• You must install the Metadata Management CMS Repository Objects on

the same computer as the SAP BusinessObjects Enterprise CMS.• You can install the Metadata Management CMS Repository Objects and

Web Application on Windows, UNIX, or Linux platforms.• You must install the Metadata Integrators, Relationship Server, and Search

Server on a supported Windows platform that already has the AdaptiveProcessing Server installed on it.

The following table shows the software components and theirsub-components that you can choose.



DescriptionComponentFeature cateogry

Includes definitions and location informa-tion for the SAP BusinessObjects Metada-ta Management application, repository,and other objects.

Metadata ManagementCMS Repository Objects

Metadata Manage-mentCMSReposito-ry Objects




Extracts information from an SAP Busines-sObjects Enterprise repository that in-cludes metadata objects such as SAPBusinessObjects Crystal Reports, WebIntelligence documents, and Desktop Intel-ligence documents.

SAP BusinessObjects En-terprise Metadata Integrator

Metadata Integra-tors

Extracts information from a NetWeaverBusiness Warehouse system which in-cludes metadata objects such as Queries,InfoProviders, InfoObjects, Transforma-tions, and DataSources.

SAP NetWeaver BusinessWarehouse Metadata Inte-grator

Extracts information from the CWM Rela-tional Package that includes definitions ofmetadata objects such as catalogs,schemas, and tables.

Common Warehouse Mod-el (CWM) Metadata Integra-tor

Extracts information from an RDBMS thatincludes definitions of metadata objectssuch as catalogs, schemas, stored proce-dures, and aliases.

Supported relational databases includeDB2, MySQL, Oracle, SQL Server,Teradata, or a Universe connection us-ing JDBC or ODBC. For complete de-tails, see the Supported Platforms doc-ument.

Relational Databases(RDBMS) Metadata Integra-tor

Extracts information from an SAP Busines-sObjects Data Services repository whichincludes definitions of metadata objectssuch as source tables and columns forETL jobs, datastores and configurations,and flat files.

SAP BusinessObjects DataServices Metadata Integra-tor

SAP BusinessObjects DataFederator Metadata Integra-tor




Extracts information from an SAP Busines-sObjects Data Federator repository whichincludes definitions of metadata objectssuch as projects, catalogs, datasources,and mapping rules.

Extracts the following metadata from othersources:• Data Modeling metadata such as

Sybase Power Designer, EmbarcaderoER/Studio, and Oracle Designer

• ETL metadata such as OracleWarehouse Builder, and Microsoft SQL ServerIntegration Services (SSIS)

• OLAP and BI metadata such as IBMDB2 Cube Views, Oracle OLAP, andCognos 8 BI Reporting

For more information, seehttp://www.metaintegration.net/Products/MIMB/Documentation/.

Meta Integration MetadataBridge (MIMB) MetadataIntegrator

Processes object relationships (for exam-ple, impact and lineage).

Metadata Manage-ment RelationshipServer

Provides search capability on SAP Busi-nessObjects Metadata Management Ex-plorer.

Metadata Manage-ment Search Server



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



Provides web applications that:• administer SAP BusinessObjects

Metadata Management on the CentralManagement Console (CMC)

• comprise the SAP BusinessObjectsMetadata Management Explorer

Note:If SAP BusinessObjects Enterprise hasmanually deployed the web application,follwo the steps in the Manually deployweb application procedure.

Web Application

Related Topics• Architecture overview on page 20

Repository database requirements and preparation

The SAP BusinessObjects Metadata Management repository is a databasethat stores all metadata that the Metadata Integrators collect. You use theinformation in the repository to analyze relationships between objects, aswell as to analyze impact and lineage between objects. For example, youcan find the tables and columns used by your Business Intelligence reportsand documents.

You can either create a new database for the repository or use an existingrepository. The SAP BusinessObjects Metadata Management installationprocess will either create new tables or upgrade the existing tables withinthe repository.

Related Topics• Setting up a new database on page 52• Exploring SAP BusinessObjects Enterprise metadata on page 272



Setting up a new database

This procedure creates a SAP BusinessObjects Metadata ManagementRepository database and configures it for the user who will connect to it. Theinstallation process will create the tables within the Metadata ManagementRepository.

1. Create a new database on your database server.Compatible database types include DB2, Microsoft SQL Server, MySQL,Oracle, and Oracle RAC. For the most current list of supported databasesoftware and version requirements, see the Products Availability Reportavailable on the SAP support site: https://service.sap.com/bosap-support.

Note:• If you create a new DB2 8.x database:

• In the creation wizard, set the code set to UTF-8.• Create three buffer pools, one for each page size: 8K, 16K and

32K. The buffer pool size should be set to 1000.• Create one temporary system table space for the 32K buffer pool.• Create one regular table space for the 32K buffer pool.

• If you create a new DB2 9.x database:• In the creation wizard, set the code set to UTF-8 and the default

buffer pool and table space page size to 32K.

2. Create a new user and assign a secure password.3. Ensure that the new user has permission to create, modify, and delete

database objects so that Metadata Management can modify the databaseas required.

Note:If you are not the owner of the database, you must have permissions toperform the necessary operations.

Related Topics• To configure your Metadata Management repository on page 59




Installation scenarios

The following installation methods are available to you for installing SAPBusinessObjects Metadata Management on Windows:• Standard installation – Installs from the installation wizard.• Migration – Upgrades an existing SAP BusinessObjects Metadata

Management repository during installation.• Remote Job Server installation – Installs a Remote Job Server component

for a Metadata Integrator to collect metadata from an SAPBusinessObjects Enterprise XI R2 system.

• Copy integrator configurations – Copies integrator source configurationsfrom a development to test environment or from a test to productionenvironment.

• Back up and restore configurations -- Backs up and restores integratorsource configuraitons Metadata Management utility configurations, andintegrator source groups.

• Distributed deployment – Installs a subset of Metadata Managementcomponents on each computer that has the prerequisite software.

Related Topics• Standard installation of Metadata Management on page 54• Remote Job Server Installation on page 76• Migration on page 111• Deployment on page 32

License keys

You purchase a license key for the SAP BusinessObjects MetadataManagement features that you want.

To purchase license keys:• Contact your sales representative.• Contact your regional office.

Related Topics• To enter product key code on page 100



• Updating the license key on page 115

Standard installation of MetadataManagement

Before beginning your installation, review the Pre-installation overview toensure that you have prepared all necessary systems.

The following instructions lead you through the standard installation stepsof setting up your SAP BusinessObjects Metadata Management on Windows:1. To begin running the installation program on page 542. To accept the license agreement on page 553. To enter user information and a product key code on page 554. To specify the CMS log on information on page 565. To select components to install on page 576. To configure your Metadata Management repository on page 597. To configure your existing Web application server on page 608. To start the installation on page 619. To manually deploy web application server components on page 62

After your installation successfully completes, you access MetadataManagement from the Central Management Console (CMC) of SAPBusinessObjects Enterprise.

Related Topics• Pre-installation overview on page 88• Accessing Metadata Management for administrative tasks on page 119

To begin running the installation program

To run the SAP BusinessObjects Metadata Management installation program:

1. Log on to your computer using an account with local Windowsadministrator privileges and access to your network.

2. If you downloaded SAP BusinessObjects Metadata Management fromElectronic Software Delivery, open the Setup.exe file or Autorun.exe. Or,insert the SAP BusinessObjects Metadata Management Installation CD


Installation for Windows4 Standard installation of Metadata Management

into your CD-ROM drive (if the installer does not automatically open, openAutorun.exe from the top level of the CD contents).

3. On the "Welcome to the BusinessObjects Metadata ManagementInstallation Wizard" window, click Next.

Related Topics• Pre-installation overview on page 88

To accept the license agreement

At the "License Agreement" window, review and accept the license agreementfor SAP BusinessObjects Metadata Management. You must accept theagreement to continue with the installation setup.

1. Review the License Agreement.2. Select I accept the License Agreement.

You cannot continue unless you accept the License Agreement.

3. Click Next to continue the installation setup.The "User Information" screen displays.

To enter user information and a product key code

On the "User Information" screen, enter user information and provide aproduct code for your SAP BusinessObjects Metadata Managementinstallation.

1. Provide your user credentials in the Full Name and Organization fields.

This information personalizes your installation and is recorded in theregistry.

2. Enter a valid code in the Product Keycode field.

Note:You enter a single product keycode during Metadata Managementinstallation. If you need to change the keycode after installation, use the"License Keys" management area of the Central Management Console(CMC).

3. Click Next.


4Installation for WindowsStandard installation of Metadata Management

Related Topics• Updating the license key on page 115

To specify the CMS log on information

At the "BusinessObjects Enterprise Server Login" window, specify connectioninformation for the SAP BusinessObjects Central Management Server (CMS).If applicable, you also specify values for Secure Sockets Layer (SSL) options.

1. Specify the following connection information to log on to the CentralManagement Server (CMS).

DescriptionOption

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

The CMS is responsible for maintaining a databaseof information about your SAP BusinessObjectsEnterprise system. The data stored by the CMSincludes information about users and groups, secu-rity levels, BusinessObjects Enterprise content, andservers. For more information about the CMS, seeSAP BusinessObjects Enterprise Administrator'sGuide.

Note:If you are installing the Remote Job Server, specifythe CMS that you will use to configure and scheduleintegrator source runs.

Server Name

If you use the Secure Sockets Layer (SSL) protocolfor all network communication between clients andservers in your BusinessObjects Enterprise deploy-ment, select the Enable SSL.

Enable SSL

The CMS user name to connect to the CMS server.

The default value is Administrator.User



DescriptionOption

The password to connect to the CMS server to registerand run the Metadata Integrator.Password

The CMS authentication mode. The default value isEnterprise. See the SAP Business Objects Admin-istrator's Guide for available modes.

AuthenticationMode

2. If you selected Enable SSL, fill in the values for the following options onthe SSL window:• SSL Certificates Folder• Server SSL Certificate File• SSL Trusted Certificate File• SSL Private Key File• SSL Private Key File Passphrase FileFor more information, see "Configuring servers for SSL" in your SAPBusinessObjects Enterprise Administrator's Guide.

3. Click Next.The "Select Features" screen displays.

To select components to install

At the "Select Features" window, select or deselect SAP BusinessObjectsMetadata Management components that you want to install on this computer.For a description of the feature categories and components that you canselect or deselect, see Choose components and determine componentdistribution on page 91.

Note:The Installation Wizard displays the Metadata Management componentsthat you can install and cannot install, based on the prerequisite softwarethat is installed on this computer. For details, see Prerequisites for eachcomponent on page 34.

1. Click the icon for a component you want to select or deselect.



Each component displays a drop-down menu that allows you to choosefrom the following options:

• Selected components will be installed on local hard drive — Installsonly the selected component in the tree for that feature.

• Entire feature will be installed on local hard drive — Installs allcomponents in the tree for that feature.

• Entire feature will be unavailable — No components for that featureare installed. An X appears next to the deselected component.

Note:

• If you deselect the Metadata Management Relationship Server, ensurethat it is installed on at least one computer in your enterprisedeployment. The Relationship Server is required to processrelationships (such as impact and lineage) of metadata objects.

• The Metadata Management web application option is available if youhave installed the Web Application option in the SAP BusinessObjectsEnterprise software. The web application installation method is thesame in both BusinessObjects Enterprise and Metadata Management.Therefore, the installer checks whether you have manually orautomatically installed web services, and automatically chooses thesame installation option in Metadata Management. If you havemanually deployed the web application in BusinessObjects Enterprise,follow the Manually deploy web application server componentsprocedure in this guide to manually deploy the web application inMetadata Management.



2. To calculate whether sufficient disk space is available for your selectedcomponents, click Disk Cost.In a new window the software displays storage space available on thelocal machine and mapped network drives. Drives that do not have enoughdisk space for the currently selected components are highlighted.Click OK to return to the "Select Features" window.

3. If you want to revert to the original configuration of the component list,click Reset.

4. Click Next.If you selected the CMS InfoObjects component, the "ConfigureBusinessObjects Metadata Management Repository database" windowopens.

To configure yourMetadataManagement repository

The "Configure BusinessObjects Metadata Management Repositorydatabase" window appears if you selected the CMS Repository Objectscomponent.



On the "Configure BusinessObjects Metadata Management Repositorydatabase" window, enter the connection information for your SAPBusinessObjects Metadata Management Repository. Then you can createthe repository, upgrade it, or make no changes to it.

1. Select the database type from the Connection type drop-down list.2. Enter the connection information for the database type.

If your database type is Oracle RAC, enter the connection string. Afterinstallation, if you want to improve performance, you can change theconnection string in the Central Management Console. For details, seeViewing and editing repository information on page 189.

3. Enter the User name and Password for the Metadata ManagementRepository.

4. Click Next (this action also validates your input values).The "Repository status " window appears

5. The first time you run the installation program, the Repository statuswindow selects the Create repository option by default. The installationprogram will create the Metadata Management tables in the specifieddatabase.

If you run the installation program again and want to preserve the existingMetadata Management Repository, selectSkip repository configuration.If you want to create a new repository (either in the same database or anew database) select the Create repository checkbox.

6. Click Next to continue with the installation setup.The "Configure Web Application Server " window appears if your WebApplication Server is Tomcat.

Related Topics• Viewing and editing repository information on page 189

To configure your existing Web application server

The "Configure Web Application Server" window appears if you selected theWeb Application component.

As part of the installation setup, you provide information about the webapplication server that will work with your SAP BusinessObjects Metadata



Management applications to perform administrative tasks on the CentralManagement Console or to view metadata relationships on the MetadataManagement Explorer.

The Metadata Management installation wizard detects the web applicationserver that your SAP BusinessObjects Enterprise system is using on thiscomputer. Therefore, most of the information is pre-populated in the fieldson the " Configure Web Application Server configuration" window. To properlyinstall web components on your web application server, you must providethe password for your existing web application server.

1. If your web application server is Apache Tomcat, you must provide thename of the current web application server instance (for example“localhost”) in the Instance field.

2. If your web application server is WebLogic, WebSphere, or OracleApplication Server, you must provide the Admin password.

3. Click Next to continue with the installation setup.The "Start Installation" screen displays.

To start the installation

The "Start Installation" window is the final screen in the installation setup.

1. Review the components that will be installed and any associated settings.2. If you want to make changes, use theBack button. All entries are retained;

you do not need to re-enter any information.

Note:

If you are running the setup.exe program from the command line, andhave the -w filename parameter switch enabled, this is the point atwhich you can Cancel the installation process to have the .ini file writtenwith all the installation parameter information. This .ini file can then beused in silent and scripted installations.

3. Click the Next button to start the installation process.The "Updating System" window shows the progress of copying the files.



To manually deploy web application servercomponents

To manually deploy the web application server components (WAR files), youmust also have manually deployed the web application server componentsin SAP BusinessObjects Enterprise. You must create a webapplication-specific WAR file using the wdeploy tool, and then manuallydeploy the web application server components. The following sectiondescribes how to manually deploy the web application server componentson a Tomcat application server.

Note:If you are manually deploying the SAP BusinessObjects Enterprise WebApplication Server, you must also manually install those web applicationserver components. For the list of WAR files to deploy, see the most recentversion of the SAP BusinessObjects Enterprise Installation and DeploymentGuide for Windows and UNIX. For information about deploying onadministrative consoles such as WebLogic, Websphere, and SAP ApplicationServer, see theSAPBusinessObjects EnterpriseWeb Application DeploymentGuide for Windows or the SAP BusinessObjects Enterprise Web ApplicationDeployment Guide for UNIX.

Note:The following procedure assumes that you have installed the same versionsof SAP BusinessObjects Metadata Management and SAP BusinessObjectsEnterprise into the default installation folder. You must have the same versionnumbers to ensure that both web application server components workseamlessly. This procedure also assumes that you do not have previousversions of the software installed on the same machine.

1. In the wdeploy tool on the machine where you installed SAPBusinessObjects Metadata Management, run the wdeploy predeploycommand to prepare a single web application, or wdeploy predeployallto prepare all web applications. WAR files are typically installed to<LINK_DIR>/BusinessObjects Metadata Management12.1/java/applications.For example, to create Tomcat WAR files, enter the following:

wdeploy tomcat6 -DAPP=bomm predeploywdeploy tomcat6 -DAPP=metadatamanagement predeploy



2. Copy the following directories to the machine where the web server isrunning (for example, Tomcat), maintaining the directory structure exactly.• Deployment directory. For example, <LINK_DIR>/Business

Objects/deployment.• WAR files:bomm.war and metadatamanagement.war. For example,

<LINK_DIR>/Business Objects/BusinessObjects MetadataManagement 12.1/java/applications.

• JAVA SDK. For example, <LINK_DIR>/Business Objects/javasdk.

3. Modify the web server configuration file with the correct information, suchas the port server number. For example you can find the Tomcatconfiguration file in <LINK_DIR>/BusinessObjects/deployment/config.tomcat6.

4. On the application server using the wdeploy tool, run the wdeploydeployonly command.For example, to deploy the Tomcat processed WAR files, type thefollowing:

wdeploy tomcat6 -DAPP=bomm deployonlywdeploy tomcat6 -DAPP=metadatamanagement deployonly

Note:The wdeploy tool does not detect whether SAP BusinessObjectsEnterprise web application is installed on the same version of theapplication server.

Silent installationA silent installation is one that you run from the command line to install SAPBusinessObjects Metadata Management, rather than following the installwizard. When you run a silent installation, you specify the parameters to beused for the install either on the command line or in an input file (also calleda response file).

Silent installation is particularly useful when you need to perform multipleinstallations, as you can save time and avoid being prompted for informationby the installation program.

You can also use the silent installation command in your own scripts. Forexample, if your organization uses scripts to install software on machines,you can insert the silent installation command into your scripts.


4Installation for WindowsSilent installation

The silent install command line includes a series of parameters that provideinformation for installation settings and directory paths. You can also specifyoptions that control the level of prompts during an install.

Related Topics• To create a response file on page 107• To start the silent installation on page 110

To create a response file

You run the installation setup program to write the installation settings to aspecified response file. The file is generated once the installation setupprogram is ready to start the installation.

To create the response file:

1. Open a command line console and navigate to the folder that containsthe installation files.

2. Mount the device that contains the installation files.

Note:If you run the installation script without copying the files to a temporarylocation, you will be prompted to specify a temporary location for theinstallation.

3. In the command line, type the silent installation command.• For Windows:

Type setup.exe -w and the file path for the response file you want togenerate.

setup.exe -w responseFilePath

• For UNIX:

Type ./install.sh -w and the file path for the response file you want togenerate.

./install.sh -w responseFilePath


Installation for Windows4 Silent installation

Note:When you specify responseFilePath, make sure you include the nameof the file you want to generate.

4. Press Enter to launch the installation setup program.5. Follow the instructions on the screen to enter your preferred installation

settings until you reach the final screen of the setup program.

Note:The installation program validates the settings that you enter on eachscreen, and then records the settings in the response file at the finalscreen. If the values for any settings change after installation, run thesetup program again to validate the settings.

6. Stop the installation setup when you reach the final screen in theinstallation setup program.• For Windows:

Click Cancel to abort the installation setup.

• For UNIX:

Press CTRL + X to abort the installation setup.

You can access the response file from the directory you specified in step 2.

To start the silent installation

You need a response file residing in a known directory. The MACHINE NAMEparameter must be specified in the response file if you are replicating aninstallation. If the parameter is not specified, the local server name will beused by default.


2. In the command line, type the following information:• For Windows:

setup.exe -r responsefile

• For UNIX:

./install.sh -r responsefile



-r responsefile Specifies the name of the response file you want theinstallation setup program to read for installation parameters.

3. If you want to override values in the response file, type the parametersin the command line.For example, if you want to override the license key, type the PIDKEYparameter and value in the command as follows:• For Windows:

setup.exe -r responseFilePath\install.ini PIDKEY=1111-2222-3333-444

• For UNIX:

./install.sh -r responseFilePath/install.iniPIDKEY=1111-2222-3333-444

4. Press Enter to launch the installation.The installation setup program runs in the background.

Related Topics• To create a response file on page 107

Silent install parameters

The following table lists the most common parameters used in a silentinstallation of SAP BusinessObjects Metadata Management. To use aparameter, place it on the command line after the installation command andafter the path for the installation files. Or, you may use these parameters inthe installation .ini file.

Note:These parameters are case sensitive.


Installation for Windows4 Silent installation

DescriptionInstallation parameter

Specifies that the user is onlyprompted when the installation iscomplete.

/qn+

Specifies that the user is notprompted during the install, or whenthe install is complete.

/qn


/qa /qb

Specifies the machine and directorywhere you want to install the productcomponents.

For example, C:\ProgramFiles\Business Objects

INSTALLDIR

Specifies your base product activa-tion keycode.PIDKEY

Specifies the port used for thedatabase type. Each database typehas a default port number if it is notspecified.

DATABASEPORT

Specifies which components will beinstalled. Each component is speci-fied, comma separated and groupedwithin quotes.

ADDLOCAL



Related Topics• To start the silent installation on page 110

MigrationWhen you install SAP BusinessObjects Metadata Management 12.1, youcan upgrade your version 11.7 or 12.0 repository to version 12.1 to preserveyour existing metadata source definitions.

Related Topics• Objects that migrate on page 111• Migrating a Metadata Management repository on page 70

Migrating from 11.7 to 12.x

When you upgrade a BusinessObjects Metadata Manager 11.7 repositoryto SAP BusinessObjects Metadata Management 12.x, the following objectsmigrate to the Central Management Server (CMS) repository:• Metadata Integrator configurations• Configurations for Metadata Management utilities (compute the lineage

staging table and recreate the search index)• Schedules to run the Metadata Integrators and utilities

Annotations, custom attributes, and preferences that you defined in version11.7 migrate to the version 12.x repository.

If you migrate from Metadata Management 11.7 to 12.x, the following objectsdo not migrate:• Users – Metadata Management 12.x uses the security services that SAP

BusinessObjects Enterprise provides. Therefore, you must define andmanage users of Metadata Management through the Central ManagementConsole (CMC).

• Log files from Metadata Integrator and utility runs – Metadata Management12.x uses the scheduling and file repositories that BusinessObjectsEnterprise provides. Therefore, the logs are now managed as part of theinstance of the scheduled run.


Installation for Windows4 Migration

Note:If you upgrade from version 11.7, you must install the Relationship Serveron a Windows computer that has an Adaptive Processing Server installed.The Relationship Server component is new with version 12.1 of SAPBusinessObjects Metadata Management. It provides object relationshipanalysis such as impact and lineage.

Related Topics• Migrating a Metadata Management repository on page 70

Migrating from 12.x to 12.x

When you move to a different BusinessObjects Enterprise system (sameversion or different version), you can preserve your existing SAPBusinessObjects Metadata Management metadata source definitions byusing the Metadata Management installer and using the same MetadataManagement repository.

Note:If you upgrade from version 12.0, you must install the Relationship Serveron a Windows computer that has an Adaptive Processing Server installed.The Relationship Server component is new with version 12.1 of MetadataManagement. It provides object relationship analysis such as impact andlineage.

If you move to a new BusinessObjects Enterprise system (either upgradethe version or not) the following objects migrate:• Metadata integrator source configurations• Metadata Management utility configurations• Annotations• Custom attributes• Metapedia terms• Metadata Management Explorer preferences

The following objects do not migrate when you move to a newBusinessObjects Enterprise system:• Schedules and metadata integrator history runs• Users and permissions• Integrator source groups


4Installation for WindowsMigration

Related Topics• Migrating Metadata Management objects to a different CMS on page 72

Migrating a Metadata Management repository

When you install SAP BusinessObjects Metadata Management version 12.1,you can upgrade an 11.7 or 12.0 repository to version 12.1. Perform thisMetadata Management repository migration on a computer that has SAPBusinessObjects Enterprise XI 3.1 Central Management Server (CMS)installed.

1. Review Release Notes for the version of SAP BusinessObjects MetadataManagement you will be installing.

2. Use your database backup utilities program to back up your existing SAPBusinessObjects Metadata Management repository.

3. Start the installation setup.After you downloaded the product from Service Marketplace, open thesetup.exe file.

4. On the "Welcome to the SAP BusinessObjects Metadata ManagementInstallation Wizard" window, click Next.

5. Go through the following steps of a standard installation:a. To accept the license agreement on page 55b. To enter user information and a product key code on page 55c. To specify the CMS log on information on page 56

6. At the "Select Features" window, select the components that you wantto install on this computer.a. Select the Metadata Management CMS Repository Objects component.

You must install this component first.b. You must install at least one Relationship Server on the Central

Management System cluster, not necessarily on the same computeras the Metadata Management CMS Repository Objects component.When you upgrade from a previous version, the Relationship Serveris not selected by default.

Note:The Relationship Server component is new with version 12.1 of SAPBusinessObjects Metadata Management. It provides object relationshipanalysis such as impact and lineage. You must install the Relationship



Server on a Windows computer that has an Adaptive ProcessingServer installed.

c. You can select other components if you want to install them on thissame computer.

d. Click Next.The "Configure SAP BusinessObjects Metadata Management Repositorydatabase" window appears.

7. To upgrade an existing repository, enter the following information:a. Select the database type from the Connection type drop-down list.b. Enter the connection information for the database type.c. Enter the user and password for the existing repository.d. Click Next (this action also validates your input values).

8. The "Repository Status" window appears. The option selected by defaultdepends on the version of the repository you specified and the versionyou are installing.a. If you specify a repository whose version is older than the version that

you are installing, the "Repository Status" window displays theUpgrade repository option selected by default.

ActionSituation

Select Upgrade repository.You want to upgrade the repository andpreserve the data.

Select Create repository.You want to delete the existing reposi-tory and create a new one in the samedatabase.

b. If you specify a repository that is the same version as the version youare installing, the Repository status window displays the Skiprepository configuration option selected by default.

ActionSituation

Select Skip repository configura-tion.

You want to keep the repositoryand preserve the data.


4Installation for WindowsMigration

ActionSituation

Select Create repository.You want to delete the existingrepository and create a new one inthe same database.

c. If you specify a repository that is a later version than the version youare installing, the Repository status window displays the Createrepository option selected by default.

Create repository is your only choice because the repository needsto match the version.

9. In the "Installation Completed" window, click OK.

Related Topics• Objects that migrate on page 111

Migrating Metadata Management objects to adifferent CMS

Use this procedure when you want to move your SAP BusinessObjectsMetadata Management system to a different SAP BusinessObjects Enterprisesystem. The source and target BusinessObjects Enterprise system shouldbe 12.x.

1. Go through the following steps of a standard installation:a. To accept the license agreement on page 55b. To enter user information and a product key code on page 55c. To specify the CMS log on information on page 56

2. At the "BusinessObjects Enterprise Server Login" window, specifyconnection information for the different CMS.

3. Follow the procedure in To select components to install on page 574. At the "Configure SAP BusinessObjects Metadata Management Repository

database" window, specify the connection information for your existingMetadata Management repository.



5. At the "Repository Status" window, select the Skip repositoryconfiguration option.

6. In the installation completed window, click OK.7. If you want to use the same users and user groups, use the Import Wizard

to export them from the existing CMS and import them on the target CMS.a. In the Import Wizard on the source CMS, specify a BIAR file that is

accessible to both the source and target CMS machines, and selectthe users and groups that have permissions to the MetadataManagement integrator source configurations. You can deselectobjects that you do not want to export.

b. On the target CMS, import the BIAR file, select "Import users andusers groups" on "Select objects to import" screen. You can deselectobjects that you do not want to import.

• Recreate the users and groups and grant permissions to the MetadataManagement objects.

Related Topics• Adding users and assigning access levels to a group on page 131

Copying integrator configurationsUse this procedure if you want to copy your integrator source configurationsfrom a development environment to a test environment, or from testenvironment to a production environment.

Note:Life Cycle Management is not supported for promoting integrator sourceconfigurations.

You must have Metadata Management version 3.1 on both the source andtarget CMS machines.

1. Use the SAP BusinessObjects Enterprise Import Wizard to create anoutput BIAR file for Metadata Management integrator source configurationon the source CMS.a. On the "Destination environment" screen, specify a BIAR file that is

accessible to both the source and target CMS machines.b. On the "Select objects to import" screen, select only the Import

application folders and objects option.c. On the "Select application folders and objects" screen, select only

Integrator Sources under Metadata Management.


4Installation for WindowsCopying integrator configurations

Note:You can select which integrator sources you want to backup (export).

d. Optionally on the "Select objects to import" screen, select the usersand groups that have permissions to the Metadata Managementintegrator source configurations.

2. On the target CMS, use the Import Wizard to import the generated BIARfile.

3. Do the following steps for each imported integrator source.a. On the Central Management Console, 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 openthe Properties page.

c. Save the Properties page.This action allocates the correct MMJobServer and updates theconfiguration information.

4. Restart the CMS system and Web application.

Backing up and restoring MetadataManagement configurations

Use these procedures when you want to backup and restore configurationsfrom one SAP BusinessObjects Metadata Management system to another.

Note:Use the backup utility in your Relational Database Management System toback up the Metadata Management repository which contains the followingobjects:• Annotations• Collected metadata• Custom attributes• Metapedia terms

Related Topics• Backing up configurations on page 75• Restoring configurations on page 75


Installation for Windows4 Backing up and restoring Metadata Management configurations

Backing up configurations

You must have SAP BusinessObjects Metadata Management version 3.1on both the source and target SAP BusinessObjects Enterprise machines.

To back up your configurations, use the SAP BusinessObjects EnterpriseImport Wizard to create an output BIAR file for Metadata Managementconfiguration information on the source BusinessObjects Enterprise system:1. On the "Destination environment" screen, specify a BIAR file that is

accessible to both the source and target BusinessObjects Enterprisemachines.

2. On the "Select objects to import" screen, select only the Importapplication folders and objects option.

3. On the "Select application folders and objects" screen, select MetadataManagement.

4. On the "Select objects to import" screen, select the users and groups thathave permissions to the Metadata Management integrator sourceconfigurations.

5. On the next screen, select the users and groups that have permissionsto the Metadata Management integrator source configurations.

The following configuration information is backed up as a result of thisprocedure:• CMS repository properties• Metadata Integrator source configuration• Metadata Management utilities configurations• Source groups• Security information (users, groups, and their permissions)

Restoring configurations

You must have SAP BusienssObjects Metadata Management version 3.1on both the source and target SAP BusinessObjects Enterprise machines.

To restore the configurations on the target BusinessObjects Enterprisesystem:

1. Use the Import Wizard to import the generated BIAR file.


4Installation for WindowsBacking up and restoring Metadata Management configurations

2. Do the following steps for each imported integrator source.a. On the Central Management Console, 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 openthe Properties page.

c. Save the Properties page.This action allocates the correct MMJobServer and updates theconfiguration information.

3. Restart the BusinessObjects Enterprise system and Web application.

Remote Job Server InstallationSAP BusinessObjects Metadata Management XI 3 can collect metadata froman SAP BusinessObjects Enterprise XI R2 system by using the Remote JobServer. The following diagram shows the relationship of this Remote JobServer component to the other SAP BusinessObjects Metadata Mangement(BOMM) components and the SAP BusinessObjects Enterprise (BOE)components


Installation for Windows4 Remote Job Server Installation

If you want to collect metadata from a BusinessObjects Enterprise XI R2system, you must:1. Install the BOMM Remote Job Server and the BOE Metadata Integrator

on a computer that has BOE XI Release 2 client or server componentsinstalled.

Note:If any of your Crystal Reports or Web Intelligence documents were createdwith the Refresh on Open option, you must also configure the databaseclients to connect to the source databases. This connection is requiredbecause whenever the report or document is opened (even to read themetadata when the BOE Metadata Integrator collects the metadata), BOEXI Release 2 automatically refreshes the data.

2. During installation, configure the Remote Job Service to accept requestsfrom BusinessObjects Enterprise XI 3 to run the BOE Metadata Integratoron BusinessObjects Enterprise XI R2.

3. Rename the Input and Output File Repository Servers on BusinessObjectsEnterprise XI 3 to conform to the naming conventions on BusinessObjectsEnterprise XI R2.

Related Topics• Installing a Remote Job Server on page 77• Renaming File Repository Servers on page 78• Modifying the configuration of a Remote Job Service on page 79

Installing a Remote Job Server

Perform this SAP BusinessObjects Metadata Management Remote JobServer installation on a computer that has SAP BusinessObjects EnterpriseXI R2 full client or server installed.

During installation, you configure the Metadata Management Remote JobService to accept requests from BusinessObjects Enterprise XI 3 to run theMetadata Integrator on BusinessObjects Enterprise XI R2.

1. Go through the first five steps of a standard installation:a. To begin running the installation program on page 54b. To accept the license agreement on page 55c. To enter user information and a product key code on page 55d. To specify the CMS log on information on page 56


4Installation for WindowsRemote Job Server Installation

Note:You specify the logon information for the CMS system that you willuse to configure and schedule integrator source runs.

e. To select components to install on page 57If the Installation Wizard detects that BusinessObjects Enterprise XI R2is installed on this computer, the "Select Features" window shows onlythe BusinessObjects Enterprise Metadata Integrator component enabled.

2. Keep the BusinessObjects Enterprise Metadata Integrator componentselected and click Next.

3. On the "Configure BusinessObjects Metadata Management Remote JobServer service port" screen, verify the port number that the Remote JobService will use to listen for requests from BusinessObjects EnterpriseXI 3 to run the Metadata Integrator. If you do not want the default portnumber 5005, enter a new value.

4. Click Next.5. On the "Start Installation" screen, verify that the Remote Job Server

displays in the list of "Components selected for installation" and clickNext.The "Updating System" window shows the progress of copying the files.

After you install the Remote Job Server, you must rename the Input andOutput File Repository Servers on your BusinessObjects Enterprise XI 3system to follow XI Release 2 naming conventions.

Related Topics• Standard installation of Metadata Management on page 54• Renaming File Repository Servers on page 78• Modifying the configuration of a Remote Job Service on page 79

Renaming File Repository Servers

For the Remote Job Service to work, you must rename the Input and OutputFile Repository Servers (FRSs) on your SAP BusinessObjects Enterprise XI3 system to conform to the naming convention on BusinessObjects EnterpriseXI Release 2. In XI Release 2, the Input FRS must start with Input and theOutput FRS must start with Output.



1. Log On to the Central Management Console (CMC) of BusinessObjectsEnterprise XI 3 with a valid administrator user name and password or auser name that has Full Control access level on the CMC.

2. Click the Servers tab on the left or the Servers link under "Organize".3. Select "hostname.InputFileRepository" from the "Server Name" list, and

select Manage > Properties from the top menu bar.4. Change the name of the File Repository Server to the following:

Input.hostname.fileserver

5. Click Save & Close.6. Restart the renamed server by clicking Actions > Restart Server in the

top menu bar.7. Select "hostname.OutputFileRepository" from the "Server Name" list,

and select Manage > Properties from the top menu bar.8. Change the name of the File Repository Server to the following:

Output.hostname.fileserver

9. Click Save & Close.10. Restart the renamed server by clicking Actions > Restart Server in the

top menu bar.

Related Topics• Installing a Remote Job Server on page 77• Modifying the configuration of a Remote Job Service on page 79

Modifying the configuration of a Remote Job Service

After you install the SAP BusinessObjects Metadata Management RemoteJob Server, you can change its configuration.

1. On the computer where SAP Business Objects Enterprise XI R2 resides,launch the Remote Job Service from the Windows Start menu.Start > Program Files > BusinessObjects > Metadata Management> Remote Service Configuration .The "Metadata Management Service Configuration" window appears.

2. The "General" tab describes the service and indicates its status. You canset the following options:



DescriptionOption

Possible values are Automatic and Manual. The defaultvalue is Automatic.

Startup type

If the service is running, you can click Stop. If the service isstopped, you can click Start.

Service sta-tus

3. The "Java" tab defines the location of the Java runtime environment usedby the Remote Service. You can change the following options:



DescriptionOption

Reserved for future use.User Default

The directory where the Java SDK is installed.Java Home

Reserved for future use.JavaOptions

The default value is 512 MB.

Consult your JVM documentation for more informationabout changing your Java memory settings.

Initial memo-ry pool (MB)

The default value is 1024 MB.

Consult your JVM documentation for more informationabout changing your Java memory settings.

Maximummemorypool(MB)

4. The "Listener" tab defines the port to listen for service requests andconnectivity to the Central Management Service on BusinessObjectsEnterprise XI 3 that will send service requests.You can set the following options:



DescriptionOption

Number of the port that the listener service will use to listenfor requests to run the BusinessObjects Enterprise MetadataIntegrator.

Applicationport

Host name of the CMS (Central Management Server) onBusinessObjects Enterprise XI 3 that will send requests torun the Metadata Integrator on BusinessObjects EnterpriseXI R2.

CMS Servername

The CMS user name to connect to the CMS server onBusinessObjects Enterprise XI 3.

The default value is Administrator. If you want a userother than Administrator to run the Metadata Integrator,change the value to the appropriate name.

User name

The password to connect to the CMS server to register andrun the Metadata Integrator. The default is no password.

Password

The CMS authentication mode. The default value is Enter-prise. See the BusinessObjects Enterprise Administrator'sGuide for available modes.

Authentica-tion mode

5. Click Test port if you want to verify that the port number is available. TheRemote Job Service uses this port to listen for requests fromBusinessObjects Enterprise XI 3 to run the Metadata Integrator.

6. Click Test connection if you want to verify that the Remote Service canconnect successfully to the CMS on BusinessObjects Enterprise XI 3.

Related Topics• Installing a Remote Job Server on page 77

After installing Metadata Management

VerifyingMetadataManagement servers are running

After installing SAP BusinessObjects Metadata Management, verify that theMetadata Management servers are running and enabled.

1. From the CMC Home page, go to the "Servers" management area.


Installation for Windows4 After installing Metadata Management

2. Expand theService Categories node and selectMetadataManagement.

The Servers List includes a State column that provides the status foreach server in the list.

3. Verify that the following Metadatda Management servers are "Running"and "Enabled."• "AdaptiveProcessingServer"• "MMJobServer"

4. If a Metadata Management server is not running or enabled, do thefollowing:a. Select the server name from the list.b. Open theActions drop-down menu and selectStart Server or Enable

Server.

Related Topics• Managing Metadata Management servers on page 120

Metadata Integrator server groups

The SAP BusinessObjectrs Metadata Management installer creates a newserver group when a new Integrator is deployed. For example, the ServerGroup BusinessObjects Enterprise Metadata Integrator is created for theBusinessObjects Enterprise Integrator. this server group is used by thescheduler to run the integrator process on the correct Metadata ManagementJob Server.

You must not create, replace or change a deployed Metadata ManagementServer Group. Doing so could cause the Metadata Management Job Serverto stop working. In this case, you must re-install the Integrators.

Updating the license key

To update the SAP BusinessObjects Metadata Management license keycode in the Central Management Console (CMC), you must have SAPBusinessObjects Enterprise XI 3.0_HF1 installed.

Situations when you might need to update your license key code for MetadataManagement include the following:


4Installation for WindowsAfter installing Metadata Management

• Update an expired key code• Upgrade from a trial version• Include additional features that you have purchased

To update the license key:

1. Go to the "License Keys" management area of the CMC.2. If you are upgrading from a trial version of the product, be sure to delete

the Evaluation key prior to adding any new license keys or productactivation keycodes.a. From the list of key codes, select the Evaluation key code.b. Click Delete.

3. Type the new key in the Add Key field.

Note:Key codes are case-sensitive.

4. If you are upgrading from a trial version of the product, be sure to deletethe Evaluation key prior to adding any new license keys or productactivation keycodes.

5. Click Add.The key is added to the list.

Related Topics• To enter product key code on page 100• To enter user information and a product key code on page 55

Uninstalling Metadata ManagementUninstalling SAP BusinessObjects Metadata Management removes theintegrator configurations. If you want to keep your configurations, do notuninstall Metadata Management. To keep the existing integratorconfigurations, install another version on top of an existing version (forexample install Metadata Management 12.1 on top of 12.0) and select theUpgrade repository option.

To uninstall Metadata Management:

1. Go to Start > Settings > Control Panel > Add/Remove Programs (orChange/Remove Programs).

2. Select BusinessObjects Metadata Management, and click Remove.


Installation for Windows4 Uninstalling Metadata Management

Note:After you uninstall Metadata Management, the Metadata Managementdirectory in the Business Objects installation directory is not deleted becausethe following files are not removed:• zip files in ccmrestore/integrators• MM/config/InfoObjectDelee.list• files in MM/log• files in MM/xml


4Installation for WindowsUninstalling Metadata Management


Installation for Windows4 Uninstalling Metadata Management

Installation for UNIX

5

Preparing to install MetadataManagement

Pre-installation overview

SAP BusinessObjects Metadata Management provides an open and flexiblearchitecture that supports a multitude of deployment and configurationscenarios. Before you install the product you should:• Ensure that that your network and systems meet the basic requirements

for an SAP BusinessObjects Metadata Management installation.• Obtain the product software by electronic download or on CD/DVD, as

well as any required licensing keycodes.• Review the SAP BusinessObjects Metadata Management Release Notes

and the section Architecture on page 19.• Ensure that the user who will run the installation setup program has

adequate permissions to complete the installation tasks.• Determine where the product components should be installed and consider

how you should prepare your infrastructure and set up your environment,including server locations.

• Decide the database server to use for the SAP BusinessObjects MetadataManagement repository and prepare the database.

• Determine your installation method.

The following sections list the software and system requirements and theinstall methods available to you for installing SAP BusinessObjects MetadataManagement.

Note:The following Metadata Management components can only be installed onWindows (you cannot install them on UNIX):• Metadata Integrators• Search Server (provides ability to search metadata on the Metadata

management Explorer)• Relationship Server

Related Topics• Architecture on page 19


Installation for UNIX5 Preparing to install Metadata Management

• License keys on page 97

System requirements

For a detailed list of supported environments and hardware requirements,refer to the Products Availability Report in the SAP BusinessObjects Support> Supported Platforms section of the SAP Service Marketplace: http://service.sap.com/bosap-support. This document includes specific version andpatch-level requirements for databases, applications, web application servers,web browsers, and operating systems.

Generally, the following components must be preinstalled and configuredcorrectly before you can install SAP BusinessObjects Metadata Management:• Microsoft Windows 2003 operating system - Required for the Metadata

Integrators and Search Server components of Metadata Management.• Solaris, AIX, or Linux operating system - Optional for the Metadata

Management CMS Repository Objects and Web Applications components.• Microsoft Internet Explorer• SAP BusinessObjects Enterprise XI 3.0 FP1 required components for the

specific Metadata Management component to be installed on thiscomputer. See Prerequisites for each component on page 34.

Metadata Management uses the Web application server and Java 2Software Development Kit (JDK) that BusinessObjects Enterprise uses.

Note:For UNIX, you must increase the memory setting for Web Logic in thefollowing directory: Weblogic_install/wlserver_10.0/samples/domains/wl_server/bin/setDomainEnv.sh. Change the value of theparameter -XX:MaxPermSize from 128m to 256m .

Note:To install Metadata Management, you must be the BusinessObjectsEnterprise Administrator.

Network requirements

When installing SAP BusinessObjects Metadata Management on multiplecomputers, you must ensure that:


5Installation for UNIXPreparing to install Metadata Management



• each target machine can communicate over TCP/IP with the machinerunning the Central Management Server (CMS).

• the target machines can communicate over TCP/IP with each other. Inparticular:• your Metadata Integrators must be able to communicate with the

machine that is running the Metadata Management repository.• your Search Server must be able to communicate with the machine

that is running the web application server for the MetadataManagement Explorer and machines where Metadata Integrators aredeployed.

For more information on the communication between components, refer toArchitecture on page 19.

UNIX permissions

SAP BusinessObjects Metadata Management will be installed in the samedirectory where SAP BusinessObjects Enterprise is installed. To installMetadata Management on UNIX, the user account under which the installis run must have read, write, and execute permissions to the directory whereBusinessObjects Enterprise is installed. Root privileges are not required toinstall Metadata Management.

Caution:If you attempt an installation with root privileges, you will be unsuccessful.

The following table summarizes all the required permissions for installingMetadata Management.



Required permissionsCategory

Read, write, and execute permissions to the directory whereBusinessObjects Enterprise will be installed .

Operating Sys-tem

TCP/IP access to all machines where you want to install com-ponents - all specified ports must be available.

Network

You must be the BusinessObjects Enterprise Administrator.BusinessOb-jects Enter-prise

Rights to add and drop database objects (such as tables andviews), plus rights to read, write, and edit table rows.

Database

It is recommended that you use the same user account for in-stalling BusinessObjects Enterprise and your web applicationserver.

To deploy Metadata Management web applications usinga user account different from the one used to install the webapplication server, see "Minimum user rights for deployingweb applications" in the BusinessObjects Enterprise XI 3Installation and Configuration Guide for UNIX.

Web applica-tion server

Choose components and determine component distribution

You can choose to install SAP BusinessObjects Metadata Managementcomponents on one or more computers based on available resources andyour deployment planning. For guidelines and suggested scenarios todistribute the software components, see Deployment on page 32.

Note:• You must install the Metadata Management CMS Repository Objects on

the same computer as the SAP BusinessObjects Enterprise CMS.• You can install the Metadata Management CMS Repository Objects and

Web Application on Windows, UNIX, or Linux platforms.• You must install the Metadata Integrators, Relationship Server, and Search

Server on a supported Windows platform that already has the AdaptiveProcessing Server installed on it.



The following table shows the software components and theirsub-components that you can choose.


Includes definitions and location informa-tion for the SAP BusinessObjects Metada-ta Management application, repository,and other objects.

Metadata ManagementCMS Repository Objects

Metadata Manage-mentCMSReposito-ry Objects




Extracts information from an SAP Busines-sObjects Enterprise repository that in-cludes metadata objects such as SAPBusinessObjects Crystal Reports, WebIntelligence documents, and Desktop Intel-ligence documents.

SAP BusinessObjects En-terprise Metadata Integrator

Metadata Integra-tors

Extracts information from a NetWeaverBusiness Warehouse system which in-cludes metadata objects such as Queries,InfoProviders, InfoObjects, Transforma-tions, and DataSources.

SAP NetWeaver BusinessWarehouse Metadata Inte-grator

Extracts information from the CWM Rela-tional Package that includes definitions ofmetadata objects such as catalogs,schemas, and tables.

Common Warehouse Mod-el (CWM) Metadata Integra-tor

Extracts information from an RDBMS thatincludes definitions of metadata objectssuch as catalogs, schemas, stored proce-dures, and aliases.

Supported relational databases includeDB2, MySQL, Oracle, SQL Server,Teradata, or a Universe connection us-ing JDBC or ODBC. For complete de-tails, see the Supported Platforms doc-ument.

Relational Databases(RDBMS) Metadata Integra-tor

Extracts information from an SAP Busines-sObjects Data Services repository whichincludes definitions of metadata objectssuch as source tables and columns forETL jobs, datastores and configurations,and flat files.

SAP BusinessObjects DataServices Metadata Integra-tor

SAP BusinessObjects DataFederator Metadata Integra-tor




Extracts information from an SAP Busines-sObjects Data Federator repository whichincludes definitions of metadata objectssuch as projects, catalogs, datasources,and mapping rules.

Extracts the following metadata from othersources:• Data Modeling metadata such as

Sybase Power Designer, EmbarcaderoER/Studio, and Oracle Designer

• ETL metadata such as OracleWarehouse Builder, and MicrosoftSQL Server Integration Ser-vices (SSIS)

• OLAP and BI metadata such as IBMDB2 Cube Views, Oracle OLAP, andCognos 8 BI Reporting

For more information, seehttp://www.metaintegration.net/Products/MIMB/Documentation/.

Meta Integration MetadataBridge (MIMB) MetadataIntegrator

Processes object relationships (for exam-ple, impact and lineage).

Metadata Manage-ment RelationshipServer

Provides search capability on SAP Busi-nessObjects Metadata Management Ex-plorer.

Metadata Manage-ment Search Server






Provides web applications that:• administer SAP BusinessObjects

Metadata Management on the CentralManagement Console (CMC)

• comprise the SAP BusinessObjectsMetadata Management Explorer

Note:If SAP BusinessObjects Enterprise hasmanually deployed the web application,follwo the steps in the Manually deployweb application procedure.

Web Application

Related Topics• Architecture overview on page 20

Repository database requirements and preparation

The SAP BusinessObjects Metadata Management repository is a databasethat stores all metadata that the Metadata Integrators collect. You use theinformation in the repository to analyze relationships between objects, aswell as to analyze impact and lineage between objects. For example, youcan find the tables and columns used by your Business Intelligence reportsand documents.

You can either create a new database for the repository or use an existingrepository. The SAP BusinessObjects Metadata Management installationprocess will either create new tables or upgrade the existing tables withinthe repository.

Related Topics• Setting up a new database on page 52• Exploring SAP BusinessObjects Enterprise metadata on page 272



Setting up a new database

This procedure creates a SAP BusinessObjects Metadata ManagementRepository database and configures it for the user who will connect to it. Theinstallation process will create the tables within the Metadata ManagementRepository.

1. Create a new database on your database server.Compatible database types include DB2, MySQL, Oracle, and OracleRAC. For the most current list of supported database software and versionrequirements, see the Products Availability Report available on the SAPsupport site: https://service.sap.com/bosap-support.

Note:• If you create a new DB2 8.x database:

• In the creation wizard, set the code set to UTF-8.• Create three buffer pools, one for each page size: 8K, 16K and

32K. The buffer pool size should be set to 1000.• Create one temporary system table space for the 32K buffer pool.• Create one regular table space for the 32K buffer pool.

• If you create a new DB2 9.x database:• In the creation wizard, set the code set to UTF-8 and the default

buffer pool and table space page size to 32K.• If you create a new Oracle RAC database:

• Create a property file to contain the connection string.

Use the following format for each connection string you specifywithin the property file:

Connection_string_id=Oracle_RAC_connection_string

Where:• Connection_string_id identifies this specific connection

string , and this Connection_string_id should not containthe "=" character.

• Oracle_RAC_connection_string is the connection stringitself, and it must be on one line.




2. Create a new user and assign a secure password.3. Ensure that the new user has permission to create, modify, and delete

database objects so that Metadata Management can modify the databaseas required.

Note:If you are not the owner of the database, you must have permissions toperform the necessary operations.

Related Topics• To configure your Metadata Management repository on page 103

Installation scenarios

The following installation methods are available to you for installing SAPBusinessObjects Metadata Management on UNIX:• Standard installation – Installs from the command line using a response

file containing installation setup parameters.• Silent installation – Installs from the command line.• Migration – Upgrades an existing Metadata Management repository during

installation.• Distributed deployment – Installs a subset of Metadata Management

components on each computer that has the prerequisite software.

Related Topics• Standard installation of Metadata Management on UNIX on page 98• Migration on page 111• Deployment on page 32

License keys

You purchase a license key for the SAP BusinessObjects MetadataManagement features that you want.

To purchase license keys:• Contact your sales representative.• Contact your regional office.



Related Topics• To enter product key code on page 100• Updating the license key on page 115

Standard installation of MetadataManagement on UNIX

Before beginning your installation, review the Pre-installation overview toensure that you have prepared all necessary systems.

The following instructions lead you through the standard installation stepsof setting up your SAP BusinessObjects Metadata Management on UNIX:

1. To begin running the installation program on page 982. To accept the license agreement on page 993. To specify the installation directory on page 994. To enter product key code on page 1005. To specify the CMS log on information on page 1006. To select components to install on page 1027. To configure your Metadata Management repository on page 1038. To configure your existing Web application server on page 1049. To start the installation on page 10410. To manually deploy web application server components on page 62

After your installation successfully completes, you access MetadataManagement from the Central Management Console (CMC) of SAPBusinessObjects Enterprise.

Related Topics• Pre-installation overview on page 88• Accessing Metadata Management for administrative tasks on page 119

To begin running the installation program

To run the SAP BusinessObjects Metadata Management installation program:


Installation for UNIX5 Standard installation of Metadata Management on UNIX

1. Log on to your computer using an account that has read, write, andexecute permissions to the directory where SAP BusinessObjectsEnterprise is installed.

Note:You must install Metadata Management in the same directory asBusinessObjects Enterprise because Metadata Management uses someof the same libraries as BusinessObjects Enterprise.

2. Start the installation setup by running ./install.sh.3. On the "Welcome to the BusinessObjects Metadata Management

Installation Wizard" screen, press Enter to begin your installation.

Related Topics• Pre-installation overview on page 88

To accept the license agreement

At the "License Agreement" screen, review and accept the license agreementfor SAP BusinessObjects Metadata Management. You must accept theagreement to continue with the installation setup.

1. Review the License Agreement.2. Select I accept the License Agreement.

You cannot continue unless you accept the License Agreement.

3. Press Y to continue the installation setup.The "Specify installation directory" screen displays.

To specify the installation directory

1. At the "Directory Selection" screen, enter the home directory for your SAPBusinessObjects Enterprise installation.

Note:You must install SAP BusinessObjects Metadata Management in thesame directory as BusinessObjects Enterprise because MetadataManagement uses some of the same libraries as BusinessObjectsEnterprise.


5Installation for UNIXStandard installation of Metadata Management on UNIX

2. Press Enter to continue the installation setup.

To enter product key code

At the "Enter Product Keycode" screen, provide a product keycode for yourSAP BusinessObjects Metadata Management installation.

1. Enter a valid code in the Product Keycode field.

Note:You enter a single product keycode during Metadata Managementinstallation. If you need to change the keycode after installation, use the"License Keys" management area of the Central Management Console(CMC).

2. Press Enter to continue the installation setup.

Related Topics• Updating the license key on page 115

To specify the CMS log on information

At the "BusinessObjects Enterprise Server Login" screen, specify connectioninformation for the SAP BusinessObjects Central Management Server (CMS).If applicable, you also specify values for Secure Sockets Layer (SSL) options.

1. Specify the following connection information to log on to the CentralManagement Server (CMS).



DescriptionOption

Host name of the CMS (Central Management Server).This value is required. The default value is localhost.

If the CMS is not on the default port number 6400,specify a colon and the port number after the CMSname. For example, mycmsname:6408

The CMS is responsible for maintaining a databaseof information about your SAP BusinessObjectsEnterprise system. The data stored by the CMSincludes information about users and groups, secu-rity levels, BusinessObjects Enterprise content, andservers. For more information about the CMS, seeSAP BusinessObjects Enterprise Administrator'sGuide.

Note:If you are installing the Remote Job Server, specifythe CMS that you will use to configure and scheduleintegrator source runs.

CMS Hostname

If you use the Secure Sockets Layer (SSL) protocolfor all network communication between clients andservers in your BusinessObjects Enterprise deploy-ment, select the Enable SSL. By default, this op-tion is not selected.

Enable SSL


The default value is Administrator.User name

The password to connect to the CMS server to registerand run the SAP BusinessObjects Metadata Integra-tor.

Password

The CMS authentication mode. The default value isEnterprise. See the SAP Business Objects Admin-istrator's Guide for available modes.

AuthenticationType



2. If you selected Enable SSL, fill in the values for the following options onthe SSL screen:• SSL Certificates Folder• Server SSL Certificate File• SSL Trusted Certificate File• SSL Private Key File• SSL Private Key File Passphrase FileFor more information, see "Configuring servers for SSL" in yourBusinessObjects Enterprise Administrator's Guide.

3. Press Enter.The "Select Features" screen displays.

To select components to install

At the "Select Features" window, select or deselect SAP BusinessObjectsMetadata Management components that you want to install on this computer.

1. Enter an X next to each component you want to select.

Note:Only the following Metadata Management components can be installedon UNIX:• Metadata Management CMS Repository Objects - This component

displays if the CMS server is installed on this computer.• Web Application - This component displays if the Web application

server is installed with SAP BusinessObjects Enterprise.

Note:The Metadata Management web application option is available if youhave installed the Web Application option in the SAP BusinessObjectsEnterprise software. The web application installation method is thesame in both BusinessObjects Enterprise and Metadata Management.Therefore, the installer checks whether you have manually orautomatically installed web services, and automatically chooses thesame installation option in Metadata Management. If you havemanually deployed the web application in BusinessObjects Enterprise,follow the Manually deploy web application server componentsprocedure in this guide to manually deploy the web application inMetadata Management.



Remember:You must install the Relationship Server on at least one Windowscomputer in your enterprise deployment. The Relationship Server isrequired to process relationships (such as impact and lineage) of metadataobjects.

For a description of the components, see Choose components anddetermine component distribution on page 91.

2. Press Enter.If you selected the CMS Repository Objects component, the "MetadataManagement Repository Database Type" screen displays.

To configure yourMetadataManagement repository

The "Metadata Management Repository Database Type " screen appearsif you selected the CMS Repository Objects component.

1. Select the database type from the numbered list.2. Press Enter to continue.3. On the "Metadata Management Repository Information" screen, enter

the connection information for the database type.If your database type is Oracle RAC,• Specify the path of the file that contains the connection string in the

Oracle RAC String File Location text box• Specify the connection string ID in the Oracle RAC SID text box.After installation, if you want to improve performance, you can changethe connection string in the Central Management Console. For details,see Viewing and editing repository information on page 189.

4. Press Enter (this action also validates your input values).The "Repository Status" screen appears.

5. The first time you run the installation program, the Repository statuswindow selects the Create a new repository option by default. Theinstallation program will create the Metadata Management tables in thespecified database.

If you run the installation program again and want to preserve the existingSAP BusinessObjects Metadata Management Repository, select Skiprepository configuration. If you want to create a new repository (either



in the same database or a new database), select Create a newrepository.

6. Press Enter to continue with the installation setup.The "Enter Web Application Server configuration" screen appears if yourWeb Application Server is Tomcat.

To configure your existing Web application server

The " Enter Web Application Server configuration" screen appears if youselected the Web Application component.

As part of the installation setup, you provide information about the webapplication server that will work with your SAP BusinessObjects MetadataManagement applications to perform administrative tasks on the CentralManagement Console or to view metadata relationships on the MetadataManagement Explorer.

The Metadata Management installation program detects the web applicationserver that your SAP BusinessObjects Enterprise system is using on thiscomputer. Therefore, most of the information is pre-populated in the fieldson the " Enter Web Application Server configuration" screen. To properlyinstall web components on your web application server, you must providethe password for your existing web application server.

1. If your web application server is Apache Tomcat, you must provide thename of the current web application server instance (for example“localhost”) in the Instance field.

2. If your web application server is WebLogic, WebSphere, or OracleApplication Server, you must provide the Admin password.

3. Press Enter to continue with the installation setup.

To start the installation

The "BusinessObjects Metadata Management Setup" screen is the finalscreen in the installation setup.

1. Review the components that will be installed and any associated settings.2. If you want to make changes, pres Ctrl-B. All entries are retained; you

do not need to re-enter all the information.



Note:

If you are running the ./install.sh program from the command line,and have the -w filename parameter switch enabled, this is the pointat which you can Cancel the installation process to have the .ini filewritten with all the installation parameter information. This .ini file canthen be used in silent and scripted installations.

3. Press Enter to start the installation process.The "In Progress" screen shows the progress of copying the files.

To manually deploy Web Application Servercomponents on UNIX

To manually deploy the web application server components (WAR files), youmust also have manually deployed the web application server componentsin SAP BusinessObjects Enterprise. You must create a webapplication-specific WAR file using the wdeploy tool, and then manuallydeploy the web application server components. The following sectiondescribes how to manually deploy the web application server componentson a Tomcat application server.

Note:If you are manually deploying the SAP BusinessObjects Enterprise WebApplication Server, you must also manually install those web applicationserver components. For the list of WAR files to deploy, see the most recentversion of the SAP BusinessObjects Enterprise Installation and DeploymentGuide for Windows and UNIX. For information about deploying onadministrative consoles such as WebLogic, Websphere, and SAP ApplicationServer, see theSAPBusinessObjects EnterpriseWeb Application DeploymentGuide for Windows or the SAP BusinessObjects Enterprise Web ApplicationDeployment Guide for UNIX.

Note:The following procedure assumes that you have installed the same versionsof SAP BusinessObjects Metadata Management and SAP BusinessObjectsEnterprise into the default installation folder. You must have the same versionnumbers to ensure that both web application server components workseamlessly. This procedure also assumes that you do not have previousversions of the software installed on the same machine.



1. In the wdeploy tool on the machine where you installed SAPBusinessObjects Metadata Management, run the wdeploy predeploycommand to prepare a single web application, or wdeploy predeployallto prepare all web applications. WAR files are typically installed to<LINK_DIR>/bobje/enterprise120/java/applications.For example, to create Tomcat WAR files, enter the following:

wdeploy tomcat6 -DAPP=bomm predeploywdeploy tomcat6 -DAPP=metadatamanagement predeploy

2. Copy the following directories to the machine where the web server isrunning (for example, Tomcat), maintaining the directory structure exactly.• Deployment directory. For example, <LINK_DIR>/deployment.• WAR files:bomm.war and metadatamanagement.war. For example,

<LINK_DIR>/bobje/enterprise120/java/applications.• JAVA SDK. For example, <LINK_DIR>/Business Objects/javasdk.

3. Modify the web server configuration file with the correct information, suchas the port server number. For example you can find the Tomcatconfiguration file in <LINK_DIR>/deployment/config.tomcat6.

4. On the application server using the wdeploy tool, run the wdeploydeployonly command.For example, to deploy the Tomcat processed WAR files, type thefollowing:

wdeploy tomcat6 -DAPP=bomm deployonlywdeploy tomcat6 -DAPP=metadatamanagement deployonly

Note:The wdeploy tool does not detect whether SAP BusinessObjectsEnterprise web application is installed on the same version of theapplication server.

Metadata Integrator server groupsThe SAP BusinessObjectrs Metadata Management installer creates a newserver group when a new Integrator is deployed. For example, the ServerGroup BusinessObjects Enterprise Metadata Integrator is created for theBusinessObjects Enterprise Integrator. this server group is used by thescheduler to run the integrator process on the correct Metadata ManagementJob Server.


Installation for UNIX5 Metadata Integrator server groups

You must not create, replace or change a deployed Metadata ManagementServer Group. Doing so could cause the Metadata Management Job Serverto stop working. In this case, you must re-install the Integrators.

Silent installationA silent installation is one that you run from the command line to install SAPBusinessObjects Metadata Management, rather than following the installwizard. When you run a silent installation, you specify the parameters to beused for the install either on the command line or in an input file (also calleda response file).

Silent installation is particularly useful when you need to perform multipleinstallations, as you can save time and avoid being prompted for informationby the installation program.

You can also use the silent installation command in your own scripts. Forexample, if your organization uses scripts to install software on machines,you can insert the silent installation command into your scripts.

The silent install command line includes a series of parameters that provideinformation for installation settings and directory paths. You can also specifyoptions that control the level of prompts during an install.

Related Topics• To create a response file on page 107• To start the silent installation on page 110

To create a response file

You run the installation setup program to write the installation settings to aspecified response file. The file is generated once the installation setupprogram is ready to start the installation.

To create the response file:


2. Mount the device that contains the installation files.


5Installation for UNIXSilent installation

Note:If you run the installation script without copying the files to a temporarylocation, you will be prompted to specify a temporary location for theinstallation.

3. In the command line, type the silent installation command.• For Windows:

Type setup.exe -w and the file path for the response file you want togenerate.

setup.exe -w responseFilePath

• For UNIX:

Type ./install.sh -w and the file path for the response file you want togenerate.

./install.sh -w responseFilePath

Note:When you specify responseFilePath, make sure you include the nameof the file you want to generate.

4. Press Enter to launch the installation setup program.5. Follow the instructions on the screen to enter your preferred installation

settings until you reach the final screen of the setup program.

Note:The installation program validates the settings that you enter on eachscreen, and then records the settings in the response file at the finalscreen. If the values for any settings change after installation, run thesetup program again to validate the settings.

6. Stop the installation setup when you reach the final screen in theinstallation setup program.• For Windows:

Click Cancel to abort the installation setup.

• For UNIX:

Press CTRL + X to abort the installation setup.

You can access the response file from the directory you specified in step 2.


Installation for UNIX5 Silent installation

Silent install parameters

The following table lists the most common parameters used in a silentinstallation of SAP BusinessObjects Metadata Management. To use aparameter, place it on the command line after the installation command andafter the path for the installation files. Or, you may use these parameters inthe installation .ini file.

Note:These parameters are case sensitive.


Specifies that the user is onlyprompted when the installation iscomplete.

/qn+


/qn


/qa /qb

Specifies the machine and directorywhere you want to install the productcomponents.

For example, C:\ProgramFiles\Business Objects

INSTALLDIR

Specifies your base product activa-tion keycode.PIDKEY


5Installation for UNIXSilent installation


Specifies the port used for thedatabase type. Each database typehas a default port number if it is notspecified.

DATABASEPORT

Specifies which components will beinstalled. Each component is speci-fied, comma separated and groupedwithin quotes.

ADDLOCAL

Related Topics• To start the silent installation on page 110

To start the silent installation

You need a response file residing in a known directory. The MACHINE NAMEparameter must be specified in the response file if you are replicating aninstallation. If the parameter is not specified, the local server name will beused by default.


2. In the command line, type the following information:• For Windows:

setup.exe -r responsefile

• For UNIX:

./install.sh -r responsefile

-r responsefile Specifies the name of the response file you want theinstallation setup program to read for installation parameters.

3. If you want to override values in the response file, type the parametersin the command line.


Installation for UNIX5 Silent installation

For example, if you want to override the license key, type the PIDKEYparameter and value in the command as follows:• For Windows:

setup.exe -r responseFilePath\install.ini PIDKEY=1111-2222-3333-444

• For UNIX:

./install.sh -r responseFilePath/install.iniPIDKEY=1111-2222-3333-444

4. Press Enter to launch the installation.The installation setup program runs in the background.

Related Topics• To create a response file on page 107

MigrationWhen you install SAP BusinessObjects Metadata Management 12.1, youcan upgrade your version 11.7 or 12.0 repository to version 12.1 to preserveyour existing metadata source definitions.

Related Topics• Objects that migrate on page 111• Migrating a Metadata Management repository on page 70

Objects that migrate

When you upgrade a BusinessObjects Metadata Manager 11.7 or 12.0repository to SAP BusinessObjects Metadata Management 12.1, the followingobjects migrate to the Central Management Server (CMS) repository:• Metadata Integrator configurations• Configurations for Metadata Management utilities (compute the lineage

staging table and recreate the search index)• Schedules to run the Metadata Integrators and utilities


5Installation for UNIXMigration

Annotations, custom attributes, and preferences that you defined in version11.7 or 12.0 migrate to the version 12.1 repository.

If you migrate from Metadata Management 11.7 to 12.x, the following objectsdo not migrate:• Users – Metadata Management 12.x uses the security services that SAP

BusinessObjects Enterprise provides. Therefore, you must define andmanage users of Metadata Management through the Central ManagementConsole (CMC).

• Log files from Metadata Integrator and utility runs – Metadata Management12.x uses the scheduling and file repositories that BusinessObjectsEnterprise provides. Therefore, the logs are now managed as part of theinstance of the scheduled run.

If you move to a new CMS (either upgrade the version or not) the followingobjects migrate:• Metadata integrator source configurations• Metadata Management utility configurations• Annotations• Custom attributes• Metapedia terms• Metadata Management Explorer preferences

The following objects do not migrate when you move to a new CMS:• Schedules and metadata integrator history runs• Users and permissions• Integrator source groups

Related Topics• Migrating a Metadata Management repository on page 70

Migrating a repository

When you install SAP BusinessObjects Metadata Management version 12.1,you can upgrade an 11.7 or 12.0 repository to version 12.1. Perform thisMetadata Management repository migration on a computer that has SAPBusinessObjects Enterprise XI 3.1 Central Management Server (CMS)installed.


Installation for UNIX5 Migration

1. Review Release Notes for the version of SAP BusinessObjects MetadataManagement you will be installing.

2. Use your database backup utilities program to back up your existing SAPBusinessObjects Metadata Management repository.

3. Start the installation setup.After you downloaded the product from Service Marketplace, run ./install.sh.

4. On the "Welcome to the SAP BusinessObjects Metadata ManagementInstallation Wizard" window, press Enter.

5. Go through the following steps of a standard installation:a. To accept the license agreement on page 99b. To enter product key code on page 100c. To specify the CMS log on information on page 100

6. At the "Select Features" window, select the components that you wantto install on this computer.a. Select the Metadata Management CMS Repository Objects component.

You must install this component first.b. You must install at least one Relationship Server on the Central

Management System cluster, not necessarily on the same computeras the Metadata Management CMS Repository Objects component.When you upgrade from a previous version, the Relationship Serveris not selected by default.

Note:The Relationship Server component is new with version 12.1 of SAPBusinessObjects Metadata Management. It provides object relationshipanalysis such as impact and lineage. You must install the RelationshipServer on a Windows computer that has an Adaptive ProcessingServer installed.

c. You can select other components if you want to install them on thissame computer.

d. Press Enter.The "Configure SAP BusinessObjects Metadata Management Repositorydatabase" window appears.

7. Enter the following information to upgrade an existing repository:a. Select the database type from the numbered list, and press Enter to

continue.


5Installation for UNIXMigration

b. On the "Metadata Management Repository Information" screen, enterthe connection information for the database type.

c. Enter the user and password for the existing repository.d. Press Enter (this action also validates your input values).

8. The "Repository Status" screen appears. The option selected by defaultdepends on the version of the repository you specified and the versionyou are installing.a. If you specify an existing older version repository than the version you

are installing, the Repository status screen displays the Upgraderepository option selected by default.

ActionSituation

Select Upgrade repository .You want to upgrade the repositoryand preserve the data.

Select Create repository.You want to delete the existingrepository and create a new one inthe same database.

b. If you specify a repository that is the same version as the version youare installing, the Repository status screen displays the Skiprepository configuration option selected by default.

ActionSituation

Select Skip repository configu-ration.

You want to keep the repositoryand preserve the data.

Select Create repository.You want to delete the existingrepository and create a new onein the same database.


Installation for UNIX5 Migration

c. If you specify a repository that is a later version than the version youare installing, the Repository status screen displays the Createrepository option selected by default.

Create repository is your only choice because the repository needsto match the version.

9. In the "Installation Completed" screen, press Enter.

Related Topics• Objects that migrate on page 111

Updating the license keyTo update the SAP BusinessObjects Metadata Management license keycode in the Central Management Console (CMC), you must have SAPBusinessObjects Enterprise XI 3.0_HF1 installed.

Situations when you might need to update your license key code for MetadataManagement include the following:• Update an expired key code• Upgrade from a trial version• Include additional features that you have purchased

To update the license key:

1. Go to the "License Keys" management area of the CMC.2. If you are upgrading from a trial version of the product, be sure to delete

the Evaluation key prior to adding any new license keys or productactivation keycodes.a. From the list of key codes, select the Evaluation key code.b. Click Delete.

3. Type the new key in the Add Key field.

Note:Key codes are case-sensitive.

4. If you are upgrading from a trial version of the product, be sure to deletethe Evaluation key prior to adding any new license keys or productactivation keycodes.

5. Click Add.


5Installation for UNIXUpdating the license key

The key is added to the list.

Related Topics• To enter product key code on page 100• To enter user information and a product key code on page 55

Uninstalling Metadata Management onUNIX

To uninstall SAP BusinessObjects Metadata Management:

1. Go to the directory where SAP BusinessObjects Enterprise is installed.2. Run AddOrRemoveProducts.sh and select BusinessObjects Metadata

Management.3. Press Enter.

Note:After you uninstall Metadata Management, the log files for the integratorsource runs and utility runs will not be deleted. These log files are locatedin the Business Objects installation directory in the following subdirectoryMetadataManager/MM/log.


Installation for UNIX5 Uninstalling Metadata Management on UNIX

Administration

6

Metadata Management administrationoverview

SAP BusinessObjects Metadata Management is a web application thatextracts metadata about objects from different source systems and storesthe metadata in a repository. Source systems include Business Intelligence(SAP BusinessObjects Enterprise and SAP NetWeaver Business Warehouse),Data Modeling, Data Integration (SAP BusinessObjects Data Services andSAP BusinessObjects Data Federation), and Relational Database systems.

When you access SAP BusinessObjects Metadata Management as a userwith Full Control access level on the Central Management Console of SAPBusinessObjects Enterprise, you can perform the following tasks:

• Ensure that the SAP BusinessObjects Enterprise servers required toperform Metadata Management tasks are enabled and running (seeManaging Metadata Management servers on page 120)

• Configure integrator sources from which to collect metadata (seeConfiguring sources for Metadata Integrators on page 133)

• Run Integrators to collect metadata (see Running a Metadata Integratoron page 158)

• View the status of Metadata Integrator collection jobs (see Viewingintegrator run progress and history on page 175)

• Organize Metadata Integrator Sources into groups for relationship analysis(see Grouping Metadata Integrator sources on page 177)

• Manage user security of Metadata Integrator sources, source groups,Metapedia, and Metadata Management utilities (see Managing securityin Metadata Management on page 122

• Compute and store end-to-end impact and lineage information forReporting (see Computing and storing lineage information for reportingon page 179)

• Manage the Metadata Management search indexes (see Running thesearch index recreation utility on page 188)

• View and edit the Metadata Management repository information (seeViewing and editing repository information on page 189)


Administration6 Metadata Management administration overview

AccessingMetadataManagement for administrativetasks

To perform SAP BusinessObjects Metadata Management administrativetasks, you must have Full Control access level on the Central ManagementConsole (CMC) of SAP BusinessObjects Enterprise.

1. Access the CMC in one of the following ways:• Type directly into your browser the name of the computer you are

accessing.

http://webserver:8080/CmcApp/

Replace webserver with the name of the web server machine. If youchanged this default virtual directory on the web server, you need totype your URL accordingly. If necessary, change the default portnumber to the number you provided when you installedBusinessObjects Enterprise.

• SelectBusinessObjects Enterprise Central Management Consolefrom the program group on the Windows Start menu.

Start > Programs > BusinessObjects XI 3.0 > BusinessObjectsEnterprise > BusinessObjects Enterprise Central ManagementConsole.

2. Log on to the Central Management Console (CMC) of BusinessObjectsEnterprise with a valid administrator user name and password or a username that has Full Control access level on the Central ManagementConsole of BusinessObjects Enterprise.

For details, see "To log on to the CMC from your browser" in theBusinessObjects Enterprise Administrator's Guide.

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

the top of the CMC Home page.


6AdministrationMetadata Management administration overview

These various links to Metadata Management are circled in the followingscreen shot of the CMC Home page.

Related Topics• Accessing Metadata Management Explorer on page 197

Managing Metadata Management servers

The appropriate SAP BusinessObjects Enterprise servers must be runningand enabled to perform the SAP BusinessObjects Management Managementtasks. The following table shows the required BusinessObjects Enterpriseservers to perform each Metadata Management tasks.



SAP BusinessObjects Metadata Management task

Servername

View Relation-ship Diagramsuch as Impactor Lineage

Search onMetadataManage-mentExplor-er

Run ReportLineage orSearch In-dex utility

Run otherMetadata In-tegrator

Run Busines-sObjectsEnter-prise MetadataIntegrator

YesYesYesYesYesAdaptiveProcessingServer

NoYesYesYesYesCentral Man-agementServer

NoYesYesYesYesInput FileRepository

NoNoYesYesYesMetadataManagementJob Server

NoNoYesYesYesOutput FiIeRepository

NoNoNoNoYesCrystal Re-ports Applica-tion Server

NoNoNoNoYesDesktop Intel-ligence Re-port Server

NoNoNoNoYesWeb Intelli-gence Re-port Server

Related Topics• To ensure that the servers for Metadata Management are running on

page 122



To ensure that the servers for Metadata Management are running

1. From the CMC Home page, go to the "Servers" management area.2. In the navigation tree on the left, expand the "Service Categories" node

and select Metadata Management to view the list of Adaptive ProcessingServers and Job Servers configured for Metadata Management.

The "Servers List" includes the following columns for each server in thelist:• A "State" column that provides the status for the server.• An "Enabled" column that indicates whether the server is enabled or

disabled.

3. Verify that the servers required for SAP BusinessObjects MetadataManagement have the values "Running" and "Enabled" in these columns.

4. If a required server is not running or enabled, do the following:a. Select the server name from the list.b. Open theActions drop-down menu and selectStart Server or Enable

Server.

Related Topics• Managing Metadata Management servers on page 120

Managing security in Metadata Management

SAP BusinessObjects Metadata Management uses the security servicesthat SAP BusinessObjects Enterprise provides.

You use BusinessObjects Enterprise security to create users and authorizesuser access for the following Metadata Management objects:• Metadata Management application• Integrator Sources• Source Groups• Metapedia

The CMS manages security information, such as user accounts, groupmemberships, and object rights that define user and group privileges. Whena user attempts an action on a Metadata Management object, the CMS



authorizes the action only after it verifies that the user's account or groupmembership has sufficient privileges.

Related Topics• Users and groups on page 123• Access levels for Metadata Management tasks on page 124

Users and groups

When you set up your system, the CMS allows you to create user accountsand groups within SAP BusinessObjects Enterprise, or reuse existing useraccounts and groups that are stored in a third-party system, such as LDAPor Windows Active Directory (AD). The CMS supports third-partyauthentication, so users can log on to BusinessObjects Enterprise with theircurrent LDAP, or Windows AD credentials.

BusinessObjects Enterprise provides the following default groups:

DescriptionDefault groupname

Members of this group have Full Control access level on SAPBusinessObjects Metadata Management administrative andExplorer tasks. By default, the Administrator group containsonly the Administrator user.

Administrator

Members of this group have only the View access level onMetadata Management administrative and Explorer tasks. Eachuser is a member of the Everyone group.

Everyone

You might want to create Metadata Management groups, as the followingtable describes.

Table 6-2: Suggested Metadata Management groups

DescriptionGroup

Can perform all Metadata Management administrative andExplorer tasks because members of this group have FullControl access level on Metadata Management folder.

Metadata Manage-ment Administrator



DescriptionGroup

Can run and schedule Metadata Integrators.Metadata Manage-ment Operator

Can create custom metadata, edit values of custom at-tributes and define Metapedia categories and terms.Members of this group have Full Control access level onthe Metapedia folder.

Metadata Manage-ment Data Stew-ard

Can define and edit annotations, custom attributes, andtheir values in the Metadata Management Explorer.

Metadata Manage-ment Power user

Can only view metadata in the Metadata Management Ex-plorer.

Metadata Manage-ment User

Related Topics• Access levels for Metadata Management tasks on page 124

Access levels for Metadata Management tasks

Access levels are groups of rights that users frequently need. These groupsallow administrators to set common security levels quickly and uniformlyrather than require that individual rights be set one by one.

SAP BusinessObjects Enterprise provides predefined access levels that arebased on a model of increasing rights. Beginning with View and ending withFull Control, each access level builds upon the rights granted by the previouslevel. By default, the Administrator group has Full Control access level andthe Everyone group has View access level.

The following table describes the default rights for each access level.



RightsAccess level

• View objects• View instances

View

• View objects• Edit objects• Schedule documents• Reschedule documents• View instances• Delete instances• Pause and resume document instances

Schedule

• Add objects• View objects• Edit objects• Modify rights• Delete objects• Schedule documents• Reschedule documents• View instances• Delete instances• Pause and resume document instances

Full Control

You can also create and customize your own access levels, which can greatlyreduce administrative and maintenance costs associated with security.

Related Topics• Type-specific rights for Metadata Management objects on page 125• "Working with access levels" in the BusinessObjects EnterpriseAdministrator's Guide.

Type-specific rights for Metadata Management objects

Type-specific rights affect only specific object types, such as integratorsources or Metapedia objects. The following tables describe the SAPBusinessObjects Metadata Management administration and Explorer tasksthat are allowed for each type-specific right.



Note:You must be part of the Administrator group to perform any actions in the"Applications" area of the CMC. Because actions on the MetadataManagement utilities and repository are in the "Applications" area, you mustbe part of the Administrator group to do the following tasks:• Configure, run, modify, or delete Metadata Management utilities• Change the user name and password for the Metadata Management

repository

Table 6-3: Metadata Management administration tasks allowed for each right

Administration tasks allowedRightMetadata Managementobject

• Access the Metadata Managementarea of the Central ManagementConsole

• Access Metadata Management inthe Application area of the CentralManagement Console

View ob-jects

Metadata Managementfolder

Change limits for integrator source runsEdit ob-jects

Manage user security for MetadataManagement

Modifyrights

View integrator sources, their run histo-ry, their logs, and so on.

View ob-jectsIntegrator Sources fold-

erCreate new integrator sourcesAdd ob-

jects

View source groupsView ob-jects

Source Groups folder

Create new source groupsAdd ob-jects




View the properties of integratorsources

View ob-jects

Integrator Source

• Edit the properties of integratorsources

• Edit the schedule parameters (suchas log level and run mode)

Edit ob-jects

Delete integrator sourcesDelete ob-jects

• Delete integrator source instances• Delete the integrator source sched-

ule

Delete in-stances

• Schedule the integrator source• Run the integrator source now• Rerun an integrator source instance

Scheduledocu-ments

• Reschedule the integrator sourceinstance

• Rerun an integrator source instance

Resched-ule docu-ments

Manage user security for integratorsources

Modifyrights

• View the history of the integratorsource

• View database log of the integratorsource instance

View in-stances

• Stop the integrator source instance• Pause the integrator source instance• Resume the integrator source in-

stance

Pause andresumedocumentinstances




View the properties of source groupsView ob-jects

Source Group

Edit the properties of source groupsEdit ob-jects

Delete the source groupDelete ob-jects

Manage user security for source groupsModifyrights

Manage user security for MetapediaModifyrightsMetapedia folder



Table 6-4: Metadata Management Explorer tasks allowed for each right

Explorer tasks allowedRightMetadata Managementobject

• Logon to the Metadata ManagementExplorer

• View all of the metadata objects andtheir relationships

• View the custom attributes and val-ues

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

from View Lineage option on "Doc-uments List" in InfoView.

View ob-jects

Metadata Managementfolder

• Update Preferences page• Edit custom attributes and display

order• Edit custom attribute values• Edit annotations• Edit user-defined relationships be-

tween objects

Edit ob-jects

• Create new custom attribute• Associate custom attribute to an

object type• Update Preferences page• Create custom attributes and display

order• Create custom attribute values• Create annotations• Create user-defined relationships

between objects

Add ob-jects

Delete custom attributesDelete ob-jects



Explorer tasks allowedRightMetadata Managementobject

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

View ob-jects

Metapedia folder

• Edit Category• Edit Term (including Approval)• Add Terms to Categories• Relate Terms• Associate objects to a Term• Deleted Related Terms• Delete Associated Objects• Delete associated Terms

Edit ob-jects

• Create Category• Create Term• Import to Excel

Add ob-jects

• Delete Category• Delete Term

Delete ob-jects

Related Topics• Access levels for Metadata Management tasks on page 124

Creating Metadata Management users and groups

To create users and groups for SAP BusinessObjects Metadata Management,you must have Full Control access level on the Central Management Console(CMC) of SAP BusinessObjects Enterprise.

1. Log on to the CMC and go to the "Users and Groups" management area.2. To create a new user:

a. On the Manage menu, point to New and click New User.b. To specify the information on the "New User" dialog box, use the

instructions in the topic "To create an Enterprise user account" in the



BusinessObjects Enterprise Administrator's Guide, in the chapter"Managing Users and Groups."

c. Click Create & Close.

3. To create a new group:a. On the Manage menu, point to New and click New Group.b. On the "Create New New Group" dialog box, enter the group name

and description.For example, to create a Metadata Management Operator group, enter" Metadata Management Operator " in Group Name and enter " Usersthat run and schedule Metadata Integrators " in Description.

c. Click OK.

Related Topics• Adding users and assigning access levels to a group on page 131• Assigning rights to users for a Metadata Management object on page 132

Adding users and assigning access levels to a group

In SAP BusinessObjects Enterprise, you can designate a group to administerother users. For example, in SAP BusinessObjects Metadata Management,you might use the group named "Metadata Management Operator" for theusers that you want to run and schedule Metadata Integrators as the followingsteps show. For more information about delegated administration, refer tothe SAP BusinessObjects Enterprise Administration Guide.

To add users to the group and assign access levels:

1. In the "Users and Groups" management area of the CMC, click GroupList in the Tree panel.

2. Select the name of the group to which you want to add users.For example, select Metadata Management Operator.

3. On the Manage menu, point to Security, and click User Security.4. Click Add Principals to add users.5. Select the user names that you want in the group, click >, and click Add

and Assign Security.6. Select the access level that you want, click the right arrow button, and

click OK.



For example, select Schedule for the sample group MetadataManagement Operator.

7. On the "User Security" page, click Close.

Related Topics• Creating Metadata Management users and groups on page 130• Assigning rights to users for a Metadata Management object on page 132

Assigning rights to users for a Metadata Management object

To assign rights to a group or user for an SAP BusinessObjects MetadataManagement object:

1. Go to the Metadata Management area on the CMC.2. Take one of the following actions to select the Metadata Management

object.• To assign rights to an individual object instance (for example, a specific

integrator source or source group ):• Select the Metadata Management object from the Tree panel.• Select the name of the object from the list of names on the right

side of the screen.• To assign rights to all instances of an object type (for example, all

integrator sources or all source groups), select the MetadataManagement object from the Tree panel.

When you choose only the object in the tree, the child objects(individual object instances) inherit the rights. For more information,see "Determining effective rights" in the SAP BusinessObjectsEnterprise Administrator's Guide in the chapter "Setting Rights."

3. On the Manage menu, point to Security, and click User Security.4. Click Add Principals.

The "Add Principals" page displays both groups and users by default inthe "Available users/groups" area.

5. Select the group or user names that you want.For example, select the name of your new groupMetadataManagementOperator.



To select more than one user or group name, hold the Ctrl key and clickeach additional name.

6. Click > to move the selected names to the "Selected users/groups" area,and click Add and Assign Security.

7. Select the access level that you want.For the sample groupMetadataManagementOperator, selectSchedule.

8. To assign the access level, click > and click OK.The "User Security: Integrator Sources" page now shows the principalsand access level that you assigned.

9. Click Close on the "User Security" page.

Related Topics• Creating Metadata Management users and groups on page 130• Adding users and assigning access levels to a group on page 131• "Managing security settings for objects in the CMC" in theBusinessObjects Enterprise Administrator's Guide

Configuring sources for Metadata Integrators

SAP BusinessObjects Metadata Integrators extract metadata from repositorysources that you configure, and they populate the SAP BusinessObjectsMetadata Management Repository with the collected metadata.

When you install SAP BusinessObjects Metadata Management, you canselect the following Metadata Integrators:• SAP BusinessObjects Enterprise Metadata Integrator• Common Warehouse Metamodel (CWM) Metadata Integrator• SAP BusinessObjects Data Federator Metadata Integrator• SAP BusinessObjects Data Services Metadata Integrator• Relational Database Metadata Integrator• Meta Integration Metadata Bridge (MIMB) Metadata Integrator - also

known as MITI Integrator

You can also obtain third-party metadata integrators for other data sources.For more information about third-party metadata integrators, contact yoursales representative.



Configuring sources for SAP BusinessObjects EnterpriseMetadata Integrator

This section describes how to configure the SAP BusinessObjects MetadataIntegrator for the SAP BusinessObjects Enterprise repository which ismanaged by SAP BusinessObjects Central Management Server (CMS). ThisIntegrator collects metadata for Universes, Crystal Reports, Web Intelligencedocuments, and Desktop Intelligence documents.

Note:Ensure that you selected the CMS Metadata Integrator when you installedSAP BusinessObjects Metadata Management.

To configure the BusinessObjects Enterprise Integrator, you must have theCreate or Add right on the integrator source.

1. Log on to the CMC and access the Metadata Management area. Fordetails, see Accessing Metadata Management for administrative taskson page 119.The "Metadata Management" page opens with the Integrator Sourcesnode selected in the navigation tree on the left.

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

4. On the "New Integrator Source" page, enter the following information.

DescriptionOption

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

Name

(Optional) Text to describe this metadata integratorsource.Description



DescriptionOption

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

The CMS is responsible for maintaining a databaseof information about your BusinessObjects Enter-prise system. The data stored by the CMS includesinformation about users and groups, security levels,BusinessObjects Enterprise content, and servers.For more information about the CMS, see Busines-sObjects Enterprise Administrator's Guide.

Note:The version of BusinessObjects Enterprise installedon the Metadata Management host must match theversion of BusinessObjects Enterprise that this CMSmanages.

CMS Server Name


The default value is Administrator. If you want auser other than Administrator to run the Metada-ta Integrator, change the value to the appropriatename.

User Name

The password to connect to the CMS server to registerand run the Metadata Integrator.Password

The process that CMS uses to verify the identity of auser who attempts to access the system. The defaultvalue is Enterprise. See theBusinessObjects Enter-prise Administrator's Guide for available modes.

AuthenticationMethod

The name of the InfoView user to invoke the MetadataManagement lineage diagrams when View Lineageis selected for each document in the "Documents List"of InfoView.

The default value is Administrator.

InfoView Integra-tion User



DescriptionOption

The password of the InfoView user to connect to theMetadatda Management Explorer to display the lin-eage diagram for a document in InfoView. The defaultis no password.

Password

5. If you want to verify that Metadata Management can connect successfullybefore you save this source, click Test connection.

6. Click Save.The newly configured source appears in the list of Integrator Sources onthe right of the Metadata Management page.

Related Topics• Running a Metadata Integrator immediately on page 158• Defining a schedule to run a Metadata Integrator on page 159• Viewing integrator run progress and history on page 175

CheckpointingSAP BusinessObjects Metadata Management can run the SAPBusinessObjects Enterprise Metadata Integrator for extended periods of timeto collect large quantities of objects. If unexpected problems occur duringobject collection, Metadata Management automatically records warning,error, and failure incidents in your log file for you to analyze later.

As additional failure management, Metadata Management uses an automaticcheckpointing mechanism with preset "safe start" points to ensure thatprocessing restarts from the nearest "safe start" point (instead of from thebeginning of the job). Regardless of reason for the failure (power outage,accidental shutdown, or some other incident), the next time you run theBusinessObjects Enterprise Metadata Integrator, it restarts from the safestart point to finish object collection in the least amount of time.

Configuring sources for SAP NetWeaver Business WarehouseMetadata Integrator

This section describes how to configure the Metadata Integrator for SAPNetWeaver Business Warehouse.



Note:Ensure that you selected the SAP NetWeaver Business Warehouse MetadataIntegrator when you installed SAP BusinessObjects Metadata Management.

To configure an SAP NetWeaver Business Warehouse integrator source,you must have the Create or Add permission on the integrator source.

1. Log on to the CMC and access the Metadata Management area.The "Metadata Management" page opens with the Integrator Sourcesnode selected in the tree on the left.

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 SAP NetWeaver BusinessWarehouse.

4. On the "New Integrator Source" page, enter the following information.

DescriptionOption

Name that you want to use for thisintegrator source. The maximumlength of an integrator source nameis 128 characters.

Name

(Optional) Text to describe thissource.

Description

One of the following connection typesfor this source:• Custom Application Server• Group/Server Selection

Connection Type

SAP Application Server host namewhen Connection Type is CustomApplication Server.

Application Server

SAP NetWeaver BW Message Serverhost name when Connection Typeis Group/Server Selection.

Message Server

SAP group name when ConnectionType is Group/Server Selection.

Group/Server

ID number for the SAP NetWeaverBW client.

Client



DescriptionOption

Number for the SAP NetWeaver BWsystem.

System Number

(Optional) String that contains theinformation required by SAProuterto set up a connection between theMetadata Integrator and the SAPNetWeaver BW system. The stringcontains the host name, the serviceport, and the password, if one wasgiven.

SAProuter String

Name of the user that will connect tothe SAP NetWeaver BW system.

SAP User

Password for the user that will con-nect to the SAP NetWeaver BW sys-tem.

SAP Password

Language to use for the descrip-tions of SAP NetWeaver BW ob-jects. Specify the 2-character ISOcode for the language (for example,en for English).

Language

5. To verify that Metadata Management can connect successfully beforeyou save this source, click Test connection.

6. Click Save.

The newly configured source appears in the list of Integrator Sources on theright of the Metadata Management page.

Related Topics• SAP router string information:http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4f/992df1446d11d189700000e8322d00/content.htm

• Running a Metadata Integrator immediately on page 158• Defining a schedule to run a Metadata Integrator on page 159• Viewing integrator run progress and history on page 175



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



Configuring sources for CommonWarehouseMetamodel (CWM)Metadata Integrator

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

Note:Ensure that you selected the CWM Metadata Integrator when you installedSAP BusinessObjects Metadata Management.

To configure the CWM Integrator, you must have the right to Create or Addthe integrator source.

1. Log on to the CMC and access the Metadata Management area. Fordetails, see Accessing Metadata Management for administrative taskson page 119.The "Metadata Management" page opens with the Integrator Sourcesnode selected in the tree on the left.

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

4. On the "CWM Integrator Configuration" page, enter the followinginformation.

DescriptionOption

Name that you want to use for this source. The maximumlength of an integrator source name is 128 characters.

SourceName

(Optional) Text to describe this source.Description



DescriptionOption

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

This value is required. The file should be accessible fromthe computer where the Metadata Management webbrowser is running.

Click the Browse button to find the file.

Note:Metadata Management copies this file to the Input FileRepository Server on SAP BusinessObjects Enterprise.Therefore, if the original file is subsequently updated, you musttake the following steps to obtain the updates before you runthe Integrator again:• Update the configuration to recopy the CWM file.

a. From the Integrator Sources list, select the CWM inte-grator source name and click Action > Properties.

The file name displays in the comments under theFile 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 becausethe old schedule has a copy of the previous file.a. With the CWM integrator source name still selected in

the Integrator Sources list, click Action > Schedules.b. Select the Recurrence and Parameter options that you

want.c. Click Schedule.

File Name





Configuring sources for SAP BusinessObjects Data FederatorMetadata Integrator

This section describes how to configure the Metadata Integrator for SAPBusinessObjects Data Federator.

Note:Ensure that you selected the SAP BusinessObjects Data Federator MetadataIntegrator when you installed SAP BusinessObjects Metadata Management.

To configure an SAP BusinessObjects Data Federator integrator source,you must have the Create or Add right on the 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 maximumlength of an integrator source name is 128 characters.

Name


Name or IP address of the computer where the DataFederator Designer resides. For example, if you installedthe Data Federator Designer on the same computer asthe Data Federator Integrator, type localhost.

DF DesignerServer Address

Port number for the Data Federator Designer. The defaultvalue is 3081.

DF DesignerServer Port

Name of the user that will connect to the Data FederatorDesigner.

User name

Password for the user that will connect to the Data Fed-erator Designer.

Password

5. If you want to verify that Metadata Management can connect successfullybefore you save this source, click Test connection.



Configuring sources for SAP BusinessObjects Data ServicesMetadata Integrator

This section describes how to configure the Metadata Integrator for SAPBusinessObjects Data Services.

Note:Ensure that you selected the SAP BusinessObjects Data Services MetadataIntegrator when you installed SAP BusinessObjects Metadata Management.



To configure the Data Services Integrator, you must have the Create or Addright on the 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 maximumlength of an integrator source name is 128 characters.Name


The database type of the Data Services repository. Theavailable database types are:• DB2• Microsoft SQL Server• MySQL• Oracle• Sybase

Database Type

Name of the computer where the Data Services reposi-tory resides.Computer Name

Port number of the database.Database PortNumber



DescriptionOption

The name of the database, data source, or service name.Specify the following name for the database type of theData Services repository:• DB2 - Data source name

• Microsoft_SQL_Server - Database name

• Oracle - SID/Service name

• Sybase - Database name

Datasource,Database Name,or Service name

Name of the user that will connect to the Data Servicesrepository.Database User

The password for the user that will connect to the DataServices repository.

Database Pass-word

6. If you want to verify that Metadata Management can connect successfullybefore you save this source click Test Connection.

7. Click Save.The newly configured source appears in the list of Integrator Sources onthe right of the Metadata Management window.


Configuring sources for Meta Integration Metadata BridgeMetadata Integrator

This section describes how to configure the Metadata Integrator for MetaIntegration® Metadata Bridge (MIMB). For a description of the objectscollected by the MIMB Integrator, see the MIMB documentation athttp://www.metaintegration.net/Products/MIMB/Documentation/.




Note:Ensure that you selected the Meta Integration Metadata Bridge (MIMB)Metadata Integrator when you installed SAP BusinessObjects MetadataManagement.

To configure the MIMB Integrator, you must have the Create or Add righton the integrator source.



3. In the Integrator Type drop-down list, selectMeta IntegrationMetadataBridge.

4. On the "New Integrator Source" page, enter values for Name andDescription. The maximum length of an integrator source name is 128characters.

5. In the Bridge drop-down list, select the type of integrator source fromwhich you want to collect metadata and follow the instructions on the userinterface to configure the connection information.


Related Topics•• Running a Metadata Integrator immediately on page 158• Defining a schedule to run a Metadata Integrator on page 159• Viewing integrator run progress and history on page 175

Configuring sources for Relational DatabaseMetadata Integrator

This section describes how to configure and run the Metadata Integrator fora DB2, JDBC, Microsoft SQL Server, MySQL, or Oracle relational database.




Note:Ensure that you selected the Relational Database System Metadata Integratorwhen you installed SAP BusinessObjects Metadata Management.

To configure the Relational Database Integrator, you must have the Createor Add right on the integrator source.


2. To access the "New Integrator Source" page, take one of the followingactions:• 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 in Connection Type.

DescriptionOption

Name that you want to use for thissource. The maximum length of anintegrator source name is 128 charac-ters.

Name

(Optional) Text to describe thissource.Description



DescriptionOption

The type of database for which youwant to collect metadata. Select oneof the following database types:• Universe Connection for secure

connections defined in CMS. Foroptions specific to a universeconnection source, see Configur-ing sources for universe connec-tions on page 151.

• DB2• Microsoft SQL Server• MySQL• Oracle• JDBC (Java Database Connectiv-

ity) for databases such as Terada-ta. For options specific to a JDBCsource, see Configuring sourcesfor JDBC connections onpage 148.

Connection Type

The name of the Central Manage-ment System (CMS) connection.

You must select a value for Con-nections when Connection Typeis set to Universe Connection.The drop-down list displays the se-cure connections defined in theCMS.

Connections

Host name on which the databaseserver is running.Computer name

Port number of the database.Database port number

The name of your DB2 database,Microsoft SQL Server database,MySQL database, or Oracle databaseservice (SID).

Database Name, or Service name



DescriptionOption

The name of the user or owner of thedatabase or data source.Database User

The password of the user for thedatabase or data source.Database Password

(Optional) Specify the name of theschema that you want to import fromthis source database. If you do notspecify a schema name:• Metadata Management imports

all available schemas for SQLServer or DB2.

• Metadata Management uses theuser name to import the schemafor Oracle.

Table Schema applies to the follow-ing connection types:• DB2• Microsoft SQL Server• Oracle

Table Schema

5. Click Test connection if you want to verify that Metadata Managementcan connect successfully before you save this source.



Configuring sources for JDBC connectionsIf you plan to use a JDBC source (such as Teradata) for the RelationalDatabase Metadata Integrator, do the following steps:



1. Obtain the JDBC driver from your database server web site or utilitiesCD.

2. Unzip the JDBC driver into a folder such as the following:

c:\temp\teradata

3. Log on to the CMC and access the SAP BusinessObjects MetadataManagement area. For details, see Accessing Metadata Managementfor administrative tasks on page 119.The "Metadata Management" page opens with the Integrator Sourcesnode selected in the tree on the 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


5. In the Integrator Type drop-down list, select Relational Database.6. Specify the following JDBC connection parameters:

DescriptionJDBC parameter

Name that you want to use for thissource.Name

(Optional) Text to describe thissource.Description

Select JDBC from the drop-down list.Connection Type

Name of the JDBC driver class thatyou obtained in step 1 above.Driver

URL address that specifies the JDBCconnection to the database.URL

(Optional) The name of the catalogin the Teradata database.Catalog



DescriptionJDBC parameter

Name of the user or owner of thedatabase.Database User

Password for the user of thedatabase.Database Password

(Optional) Specify the name of theschema that you want to import fromthis 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 mustset Library Files to the classpath onthe computer where the integratorruns.

Library files



Related Topics• Configuring sources for Relational Database Metadata Integrator on

page 145• Running a Metadata Integrator immediately on page 158• Defining a schedule to run a Metadata Integrator on page 159• Viewing integrator run progress and history on page 175



Configuring sources for universe connectionsThe Relational Database Integrator can collect metadata from secureduniverse connections that use JDBC and ODBC. For the most current list ofsupported universe connection types, refer to the Release Notes.

To configure a universe connection source that uses a JDBC or ODBCconnection:

1. If you want to configure a universe connection source that uses a JDBCconnection, 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 ODBCconnection, ensure that the ODBC Datasource exists in the computerwhere the integrator will run.

3. Log on to the CMC and access the SAP BusinessObjects MetadataManagement area. For details, see Accessing Metadata Managementfor administrative tasks on page 119.The "Metadata Management" page opens with the Integrator Sourcesnode selected in the tree on the 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


5. In the Integrator Type drop-down list, select Relational Database.6. Specify the following universe connection parameters:



DescriptionOption

Name that you want to use for this source.Name


Select Universe Connection from the drop-down list.ConnectionType

The name of the Central Management System (CMS) con-nection. The drop-down list displays the secure connectionsdefined in the CMS.

Connections

(Optional) Specify the name of the schema that you want toimport from this source database. If you do not specify aschema name:• Metadata Management imports all available schemas for

SQL Server or DB2.• Metadata Management uses the user name to import the

schema for Oracle.

TableSchema

The full paths to the Java library files (separated by semi-colons)required by the Universe Connection. For example:

Note:In a distributed deployment, you must set Library Files tothe classpath on the computer where the integrator runs.

Library Files



Related Topics• Configuring sources for Relational Database Metadata Integrator on

page 145• Running a Metadata Integrator immediately on page 158• Defining a schedule to run a Metadata Integrator on page 159• Viewing integrator run progress and history on page 175



Managing integrator sources and instances

You manage integrator sources and instances in the SAP BusinessObjectsMetadata Management area of the CMC.

From the list of configured integrator sources, you can select an integratorsource and perform a task from Manage or Actions in the top menu toolbar.

You can perform the following tasks from the Manage menu.

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 integratorsource on page 156) and its associated schedules, source runs,and logs.

Delete

Remove all integrator source runs. This option keeps the sourceconfiguration, 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 MetadataIntegrator source (see Viewing integrator run progress andhistory on page 175).

History

View and edit the configuration information for this MetadataIntegrator source.Properties

Run the Metadata Integrator at regular intervals (seeDefining a schedule to run a Metadata Integrator onpage 159).

Schedule



DescriptionAction task

Run the Metadata Integrator immediately (see Running aMetadata Integrator immediately on page 158).Run now

Related Topics• Viewing and editing an integrator source on page 154• Deleting an integrator source on page 156• Changing log level on page 164• Changing limits on page 156

Viewing and editing an integrator source

You can view and modify the definition of an integrator source in its"Properties" dialog box to change its 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. On the "Integrators Sources" page of SAP BusinessObjects MetadataManagement, select the integrator source that you want by clickinganywhere on the row except its type.

Note:If you click the integrator source type, you display the version andcustomer support information for the integrator.

2. Access the "Properties" dialog box in one of the following ways:• Double-click the row for the integrator source.• Click the down arrow next to Actions in the top menu tool bar and

select Properties.

The following example shows the "Properties" pane of the "IntegratorConfiguration" page.



3. You can change any property for the integrator source, except its typeand name.

4. To verify the database connection information on this "Integrator SourceProperties" dialog box, click Test connection.

5. Click Save to save your changes to the configuration.6. To change parameters such as Log Level or Update Option

(BusinessObjects Enterprise Integrator only), expand the Schedule nodein the tree on the left and click Parameters.

Related Topics• Defining a schedule to run a Metadata Integrator on page 159



Deleting an integrator source

You might want to delete an integrator source in situations such as thefollowing:

• You want to rename your integrator source

Note:If you rename your integrator source, you lose all the previously collectedmetadata.

• You no longer need your integrator source

To delete an integrator source, you must have the right to Delete theintegrator source.

1. On the "Integrators Sources" page of SAP BusinessObjects MetadataManagement, select the integrator source that you want by clickinganywhere on the row except its type.

Note:If you click the source type, you display the version and customer supportinformation for the integrator.

2. Click the down arrow next to "Manage" in the top menu tool bar and selectDelete > Integrator Source.

Note:If you delete an integrator source, you also delete the metadata from thatsource that was stored in the Metadata Management repository.

3. Reply to the confirmation prompt.

Changing limits

Each time you run a metadata integrator or SAP BusinessObjects MetadataManagement utility, SAP BusinessObjects Metadata Management createsa new instance and log files for it. By default, the maximum number ofinstances to keep is 100. When this maximum number is exceeded, SAPBusinessObjects Enterprise deletes the oldest instance and its associatedlog file.



Note:The Log Cleanup utility deletes the database log in the Metadata Managementrepository for each instance that was deleted.

To change the limits to delete integrator source instances, you must haveFull Control access level on the Metadata Management folder.

1. In CMC home page, select the Metadata Management link or tab on theleft.The "Metadata Management" page opens with the Integrator Sourcesnode selected in the Tree panel.

2. Select the Metadata Management top node in the Tree panel.3. On the Action menu, click Limits.

The "Limits: Metadata Management" window appears.

4. If you want to change the default value of 100 maximum number ofinstances 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.

5. If you want to specify a maximum number of instances to keep for aspecific 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 instancecount per object per user.

e. Click Update to save your changes.

6. If you want to specify a maximum number of days to keep instances fora specific user or group: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 instancecount per object per user.

e. Click Update to save your changes.

7. To close the "Limits: Metadata Management" window, click the X in theupper right corner.

Running a Metadata Integrator

Run the Metadata Integrator to collect the metadata for each source that youconfigured. When you select the Integrator Sources in the Tree panel onthe left on the SAP BusinessObjects Metadata Management page in theCMC, all configured integrator sources display. When you select an integratorsource on the right side of the screen, you can can run it immediately ordefine a schedule to run it.

Related Topics• Running a Metadata Integrator immediately on page 158• Defining a schedule to run a Metadata Integrator on page 159

Running a Metadata Integrator immediately

To run a Metadata Integrator immediately, you must have the right to Runthe integrator source.

1. In CMC home page, select the SAP BusinessObjects MetadataManagement link or tab on the left.The Metadata Management page opens with Integrator Sources selectedin the Tree pane on the left.



2. From the list of configured sources that appears on the right, select theintegrator source that you want by clicking anywhere on the row exceptits type.

Note:If you click the integrator source type, you display the version andcustomer support information for the integrator. If you double-click therow, you open the "Properties" dialog box for the integrator source.

3. Click the down arrow next to Actions in the top menu tool bar and selectRun Now.

Tip:You can also click the icon "Run selected object(s) now" in the icon barunder Manage and Actions.

4. 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 click Schedule, the "Integrator History" pageautomatically displays.

5. Click the Refresh icon to update the status.

For more details about the "Integrator History" page, see Viewingintegrator run progress and history on page 175.

6. If you use impact and lineage reports on the Reports tab of the MetadataManagement Explorer, you must recompute the contents of the lineagestaging table to incorporate changes from the Integrator runs. For moreinformation, see Computing and storing lineage information for reportingon page 179.

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 toSchedule the integrator source.

1. In CMC home page, select the SAP BusinessObjects MetadataManagement link or tab on the left.



The Metadata Management page opens with the Integrator Sourcesnode selected in the Tree panel on the left.

2. From the list of configured sources that appears on the right, select thesource from which you want to collect metadata by clicking anywhere onthe row except its type.

Note:If you click the source type, you display the version and customer supportinformation for the metadata integrator.

3. Click the down arrow next to "Actions" in the top menu tool bar and selectSchedule.The "Instance Title" pane of the "Schedule" page appears with the nameof the configured source.

4. If you do not want the default value for Instance Title, change it to aunique name that describes this schedule.

5. Select the Recurrence node on the left to choose the frequency in theRun object drop-down list.



6. Choose the additional relevant values for the selected recurrence option.For details, see Recurrence options on page 162.

7. If you want to send notification when the integrator has run, select theNotification node on the left. For more information about Notification,see the SAP BusinessObjects Enterprise Administrator's Guide.

8. If you want to trigger the execution of a Metadata Integrator when anevent occurs, select the Events node on the left. For more informationabout Events, see the SAP BusinessObjects Enterprise Administrator'sGuide.



9. Select the Parameters node on the left to change the default values forrun-time parameters for the metadata integrator. For details, see Commonrun-time parameters for metadata integrators on page 166.

10. Click Schedule.11. If you use impact and lineage reports on the Reports tab of the Metadata

Management Explorer, you must recompute the contents of the lineagestaging table to incorporate changes from the Integrator runs. Similar tosetting up a regular schedule to run an Integrator, you can set up aschedule to compute the lineage staging table at regular intervals. Formore information, see Computing and storing lineage information forreporting on page 179.

Recurrence optionsWhen you schedule an integrator source or an SAP BusinessOjbectsMetadata Management utility, you can choose the frequency to run it in theRecurrence option. The following table describes each recurrence optionand shows the additional relevant values that you must select for eachrecurrence option.

DescriptionRecurrence Option

The utility will run when you click Schedule .Now

The utility will run once only. Select the values for StartDate/Time.Once

The utility will run every N hours and X minutes. Selectthe values for:• Hour(N)• Minute(X)• Start Date/Time• End Date/Time

Hourly

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

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

Weekly



DescriptionRecurrence Option

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

Monthly

The utility will run on the Nth day of each month. Selectthe following values:• 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 following values:• Start Date/Time• End Date/Time

First Monday ofMonth

The utility will run on the last day of each month. Selectthe following values:• Start Date/Time• End Date/Time

Last Day of Month

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

X Day of Nth Week ofthe Month

The utility will run on the days you specified as "run"days on a calendar you have created in the "Calen-dars" management area of the CMC.

Calendar

Related Topics• Defining a schedule to run a Metadata Integrator on page 159• Scheduling the lineage report utility on page 182



Changing log levelFor each Metadata Integrator run, SAP BusinessObjects MetadataManagement writes information in the following logs:

• Database Log - Use the database log as an audit trail. This log is in theMetadata Management Repository. You can view this log while theMetadata Integrator is running.

The default logging level for the database log is Information which writesinformational messages, such as number of reports processed, as wellas any warning and error messages. It is recommended that you keepthe logging level for the database log at a high level so that it does notoccupy a large amount of disk space.

• File Log - Use the file log to provide more information about a MetadataIntegrator run. The 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 Metadata Integrator run completed.

The default logging level for the file log is Configuration which writesstatic configuration messages, as well as informational, warning, anderror messages. You can change the logging level for the file log if youwant more detailed information. If your logs are occupying a large amountof space, you can change the maximum number of instances or days tokeep logs. For details, see Changing limits on page 156.

To change the logging level, you must have the Schedule right on theintegrator source.

1. On the Metadata Management page in the CMC, select the IntegratorSources node in the tree on the left to display all configured integratorsources.

2. Select the integrator source for which you want to change the logginglevel by clicking anywhere on the row except its type.

Note:If you click the integrator type, you display the version and customersupport information for the integrator.

3. Click the down arrow next to Actions in the top menu tool bar and selectSchedule.

4. Click the Parameters node in the tree on the left.



5. From the drop-down list, select the logging level that you want forDatabase Log Level or File Log Level. You can choose one of thefollowing levels:

DescriptionOption

Turn off logging any messagesOff

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

Each logging level logs all messages at that level or higher. Therefore,the default logging level Information logs informational, warning, and errormessages. If you change the logging level to Warning, Metadata



Management logs warning and error messages. Similarly, if you changethe logging level to Integrator trace, Metadata Management logs trace,configuration, informational, warning, and error messages

6. Click Schedule.

Future runs of the Metadata Integrator for this source system will use thelogging level you specified.

Common run-time parameters for metadataintegrators

When you schedule an integrator source, you can change the default valuesof the run-time parameters in the Parameters option. The following tabledescribes the run-time parameters that are applicable to all metadataintegrators. For information about run-time parameters that apply to onlyspecific metadata integrators, see the topics in Related Topics below.

DescriptionRun-time parameter

This log is in the SAP BusinessObjects Metadata ManagementRepository. You can view this log while the Metadata Integratoris running.

The default logging level is Information. Usually you cankeep the default logging level. However, if you need to providemore detailed information about your integrator run, you canchange the level to log tracing information. For a descriptionof log levels, see Changing log level on page 164.

Database Log Level

The Metadata Integrator creates this log in in the Business Ob-jects installation directory and copies it to the File RepositoryServer. You can download this log file after the Metadata Integra-tor run completed.

The default logging level for this log is Configuration. Usu-ally you can keep the default logging level. However, if youneed to debug your integrator run, you can change the levelto log tracing information. For a description of log levels, seeChanging log level on page 164.

File Log Level




This option only appears for an SAP BusinessObjects Enter-prise Metadata Integrator.

In prior versions, the Full Extract parameter default valuewas true to delete the current metadata in Metadata Manage-ment and collect all metadata fro this source.

In version 12.1, the Full Extract parameter now provides twochoices:• Delete existing objects before starting object collection

This choice is the default and is consistent with the priordefault behavior of Full Extract.

• Update existing objects and add newly selected ob-jects

Note:It is recommended that you specify Delete existing objectsbefore starting object collection the first time you run the SAPBusinessObjects Enterprise Metadata Integrator, but specifyUpdate existing objects and add newly selected objects forsubsequent runs.

Update Option:

Delete existing objectsbefore starting objectcollection

Update existing objectsand add newly selectedobjects

The Metadata Management Job Server creates a Java processto perform the metadata collection. Use the JVM Argumentsparameter to configure run-time parameters for the Java process.For example, if the metadata source is very large, you mightwant to provide more memory than the default.

JVM Arguments

Optional run-time parameters for the metadata integratorsource. For more information, see Run-time parameters for SAP BusinessObjects Enterprise metadata integrator on page 168.

Additional IntegratorArgu-ments

Related Topics• Run-time parameters for BusinessObjects Enterprise metadata integrator



• Run-time parameters for SAP NetWeaver BW metadata integrator onpage 172

Run-time parameters for SAP BusinessObjects Enterprisemetadata integrator

User collectionThe SAP BusinessObjects Enterprise metadata integrator provides run-timeparameters to adjust memory usage when collecting user permissions. Youspecify these run-time parameters on the "Parameters" page when youschedule a BusinessObjects Enterprise integrator source. To access the"Parameters" page:1. Choose Start > Programs > SAP BusinessObjects XI 3.1 >

BusinessObjects Enterprise > BusinessObjects Enterprise CentralManagement Console.

2. From the drop-down list, choose Metadata Management.3. Select your integrator source.4. In the "Integrator Source Properties" window, choose Schedule and then

Parameters.

DefaultvalueDescriptionRun-time pa-

rameter

2

Maximum number of concurrent processes tocollect metadata.

In a multiprocessor environment, you can in-crease this value. It is recommended that youset this value to the number of processors onyour system.

Set this parameter in Additional IntegratorArguments on the "Parameters" page.

ppc



DefaultvalueDescriptionRun-time pa-

rameter

25

Maximum number of requests that can be servicedby the collection process before automaticallyrestarting the process to release memory.

If you do not have a large number of users, youcan increase this value.

Note:An out-of-memory error occurs If you set thisvalue too high for the number of users on yoursystem.


pplimit

false

Enable or disable user permissions collection

Specify true to enable user permissions collec-tion.

Note:If you disable user permissions collection, Im-pact analysis for users will not be available.


collectUserPermissions

-Xmx1024m

Maximum memory allocation for the collectionprocess.

If the amount of memory is available, you canset this value as high as -Xmx1500m, where"m" indicates megabytes.

Set this parameter in JVM Arguments on the"Parameters" page.

-Xmx



The following example changes values for parameters pplimit and ppc inAdditional Integrator Arguments. The default value -Xmx1024m appearsin JVM Arguments.

Selective CMS object collectionSelective collection of CMS metadata through the SAP BusinessObjectsEnterprise Metadata Integrator reduces processing time. To view a completepicture of the information in your BusinessObjects Enterprise system, runthe integrator multiple times, specifying a different component for each run.Also, you might want to incrementally collect CMS metadata for a large SAPBusinessObjects Enterprise deployment by using selective collection.

To add metadata to the previous metadata collections, select the Updateexisting objects and add newly selected objects option. For example, ifyou have collected Web Intelligence documents on the first run, then youcollect Crystal Reports on the second run, then you will see the WebIntelligence documents and Crystal Reports metadata together in the SAPBusinessObjects Metadata Management Explorer. The first time you scheduleand run a metadata collection for a specific object type, all metadata for thatobject is collected. Subsequent runs will only collect changes since the lastrun.

To delete metadata from previous metadata collections, select the Deleteexisting objects before starting object collection option. For example, ifyou have collected Web Intelligence documents on a previous run, and thenchoose 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. Anyoneusing the SAP BusinessObjects Metadata Management Explorer can seethe contents of these folders. However, you must have the proper permissionsto be able to run collections on the objects in these folders. In your Personalfolder, only you or an administrator can run a collection on those objects.

Note:SAP BusinessObjects Enterprise Metadata Integrator does not collectmetadata from Inboxes or Categories.

DescriptionOption

Specifies the names of the folders thatyou want in the collection using a JavaRegular Expression. For example,• an asterisk (*) means that all folders

are collected.• folderName collects metadata

within a specific folder. It will alsocollect metadata in any associatedsubfolders.

• folderName* an asterisk at the endof a string value includes all folderswith that string.

• folderName|folderName a pipe(also called vertical bar separator)between folder names includes oneor the other folder. For example,Sales|Finance means either theSales or the Finance folder.

• ^(?!folderName$) excludes thefolder with this specific folder name.

• ^(?!folderName) excludes anyfolders that start with this specificfolder name.

• (?!folderName) excludes anyfolders that has this specific foldername within the name.

Folder Name Expression



DescriptionOption

Collect the SAP BusinessObjects En-terprise universe metadata in the fold-ers specified in the Folder Name Ex-pression option.

Note:If you uncheck this option, and chooseto collect any report that uses a uni-verse, the integrator collects the uni-verse metadata as well.

Collect Universes

Collects Web Intelligence documentsand source universes from Publicand/or Personal folders.

Collect Web Intelligence Documentsand source Universes

Collects Desktop Intelligence docu-ments and source universes fromPublic and/or Personal folders.

Collect Desktop Intelligence Docu-ments and source Universes

Collects Crystal Reports and associat-ed universes from Public and/or Person-al folders.

Collect Crystal Reports and associatedUniverses

Related Topics• View the collection results on page 176

Run-time parameters for SAPNetWeaver BWmetadata integrator

The SAP NetWeaver Business Warehouse metadata integrator providesrun-time parameters to adjust the number of threads to use when collectingmetadata from the SAP system and to filter the queries or workbooks tocollect.

To access the "Parameters" page for the integrator source:1. ChooseStart >Programs >BusinessObjects XI 3.1 >BusinessObjects

Enterprise > BusinessObjects Enterprise Central ManagementConsole.

2. From the drop-down list, choose Metadata Management.



3. Select your integrator source.4. Click the down arrow next to "Actions" in the top menu tool bar and select

Schedule.

The "Instance Title" pane of the "Schedule" page appears with the nameof the configured source.

5. Select the Parameters node from the tree on the left.6. You can change the following run-time parameters for the SAP NetWeaver

BW metadata integrator.


Specifies the number of threads touse when collecting metadata fromthe SAP system. You might want toincrease the number of threads ifyour SAP NetWeaver BW system hasa large number of objects and it hasavailable work processes.

The default value is 5. In a multipro-cessor environment, you can in-crease this value. The number ofthreads is limited by the number ofprocessors configured on the SAPNetWeaver BW server. If the num-ber of threads is greater than theavailable processors, the thread isput on a queue and will be pro-cessed when a processor becomesavailable.

Number of Threads




Specifies the names of the queriesthat you want in the collection usinga Java Regular Expression. For ex-ample:• * an asterisk (*) means that all

queries are collected.• queryName* an asterisk at the

end of a string value includes allqueries with that string.

• queryName|queryName a pipe(also called vertical bar separator)between query names includesone or the other query. For exam-ple, Sales|Finance means eitherthe Sales or the Finance query.

• ^(?!queryName$) excludes thequery with this specific queryname.

• ^(?!queryName) excludes anyqueries that start with this specificquery name.

• (?!queryName) excludes anyqueries that has this specificquery name within the name.

Query Name Expression

Specifies the names of the work-books that you want the MetadataIntegrator to collect using a JavaRegular Expression.

Examples are similar to those forQuery Name Expression

Workbook Name Expression

Related Topics• Common run-time parameters for metadata integrators on page 166• Running a Metadata Integrator immediately on page 158• Defining a schedule to run a Metadata Integrator on page 159



• Viewing integrator run progress and history on page 175• Changing log level on page 164

Viewing integrator run progress and history

When you select the Integrator Sources in the Tree panel on the left onthe SAP BusinessObjects Metadata Management page in the CMC, allconfigured integrator sources display. Next to each source name is the dateand time when the Integrator was last run for that source.

To view all runs for a metadata integrator source, you must have the rightto View integrator sources:

1. From the list of all configured integrator sources, select the name of thesource 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.• Status of each schedule.• "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 baror click Actions > Database Log to view the progress messages of theintegrator run.

By default, Metadata Management writes high-level messages (such asnumber of universe processed and number of reports processed) to thelog. You can change the message level on the configuration page for theintegrator source. For details, see Changing log level on page 164.



5. In the top menu bar of the "Integrator History" page, use either theActionsdrop-down list or the icons to perform any of the following options:

DescriptionOption

Run this integrator immediatelyRun Now

Stop the execution of this integrator instance if it is currentlyrunning.

Stop

Pause the execution of this integrator instance if it has astatus of Pending or Recurring.

Pause

Resume the execution of this integrator instance if it is cur-rently paused.

Resume

Define a new schedule to execute this integrator.Reschedule

View messages that indicate which metadata objects havebeen collected from the integrator source.

Database log

Refresh the status of this integrator instance.Refresh

Delete this integrator instance from the history list.Delete

View the collection results

After you have successfully run a Metadata Integrator, you can view theresults in the SAP BusinessObjects Metadata Management Explorer.

1. ChooseStart >Programs >BusinessObjects XI 3.1 >BusinessObjectsMetadata Management > Metadata Management Explorer.

2. Log on to the appropriate system with your username and password, andthen click Log On.

3. Under the Business Intelligence category, find the integrator source thatyou used for your object collections.

4. Click the collection object to display more information about it.

Related Topics• Selective CMS object collection on page 170• Navigating metadata on page 201



Grouping Metadata Integrator sources

SAP BusinessObjects Metadata Management provides the capability togroup Metadata Sources into groups such as Development System, TestSystem, and Production System. After the groups are defined, you can viewimpact and lineage diagrams for a specific Source Group.

Related Topics• Creating source groups on page 177• Modifying source groups on page 178

Creating source groups

You must have the Add or Create right on the SAP BusinessObjectsMetadata Management root folder to create a Metadata Integrator sourcegroup.

1. Log on to the Central Management Console (CMC) if you have not alreadydone so. For details, see Accessing Metadata Management foradministrative tasks on page 119.

2. Click the Metadata Management link on the CMC Home page.3. Select Source Groups node in the tree on the left on the "Metadata

Management" page.4. Access the "Source Group" window in one of the following ways:

• Click the second icon "Create a Source Group" in the menu bar ontop.

• In the menu bar on top, click Manage > New > Source Group.

5. 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 "MetadataManagement" page.



Modifying source groups

You must have the Edit right on the Metadata Integrator source group.

1. Access the SAP BusinessObjects Metadata Management area on theCentral Management Console (CMC) if you have not already done so.For details, see Accessing Metadata Management for administrative taskson page 119.

2. Select Source Groups node in the tree on the left on the "MetadataManagement" 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.

Deleting source groups

You must have the Delete right on the Metadata Integrator source group.

1. Access the SAP BusinessObjects Metadata Management area on theCentral Management Console (CMC) if you have not already done so.For details, see Accessing Metadata Management for administrative taskson page 119.

2. Select Source Groups node in the tree on the left on the "MetadataManagement" 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.



Managing Metadata Management utilities

SAP BusinessObjects Metadata Management provides the following utilities:

DescriptionUtility

Computes and stores end-to-end impact and lineage informationfor Reporting on the Report tab of the Metadata ManagementExplorer.

Metadata Management provides a configured Lineage Re-port utility that you can run without creating a new configu-ration. You can create a schedule for this configuration orrun it immediately.

Lineage Re-port

After instances of Lineage Report and Search Index utiltieshave been deleted, deletes the corresponding database logsfrom the Metadata Mangement repository.

Metadata Management provides a configured Logs Cleanuputility for you to run.

Logs Cleanup

Recreates Metadata Management search indexes.

Metadata Management provides a configured Search Indexutility that you can run without creating a new configuration.You can create a schedule for this configuration or run itimmediately.

Search Index

Related Topics• Computing and storing lineage information for reporting on page 179• Running the search index recreation utility on page 188

Computing and storing lineage information for reporting

The SAP BusinessObjects Metadata Management Repository provides alineage staging table, MMT_Alternate_Relationship, that consolidatesend-to-end impact and lineage information across all sources. You can createreports from this table. To view the reports on the Reports tab of the Metadata



Management Explorer, they must be Crystal Reports (see Defining customreports on page 208).

Before generating reports that rely on this lineage staging table, you shouldupdate the lineage information in the lineage staging table. You can eitherschedule or update the lineage staging table on demand to ensure thosereports contain the latest lineage information.

The following activities can change the lineage information, and it isrecommended that you run the lineage computation after any of theseactivities occur:

• Run an Integrator to collect metadata from a source system (see Runninga Metadata Integrator on page 158).

• Change preferences for relationships between objects (see Changingpreferences for relationships on page 264). The data in the lineage stagingtable uses the values in Impact and Lineage Preferences and ObjectEquivalency Rules to determine impact and lineage relationships acrossdifferent integrator sources.

• Establish or modify a user-defined relationship of type Impact or SameAs (see Establishing user-defined relationships between objects onpage 260).

Configuring a lineage report utilityTo configure a lineage report utility, you must be part of the Administratorgroup.

SAP BusinessObjects Metadata Management provides a default configurationfor the Lineage Report utility that has Mode set to Optimized. You mightwant to configure another Lineage Report utility with Mode set to Full if youwant to run this utility to recalculate all of the lineage information in the lineagestaging table.

1. Login to the Central Management Console (CMC) if you have not alreadydone so. For details, see Accessing Metadata Management foradministrative tasks on page 119.

2. Select Applications from the navigation list at the top of the CMC Homepage.

3. Select Metadata Management in the "Applications Name" list.4. Click the down arrow next to "Action" in the top menu tool bar and select

Manage Utilities.



5. On the "Utilities Configurations" page, click the down arrow next to"Manage" in the top menu tool bar and selectNewUtility Configuration...

6. Select Lineage Report Utility from the Utility Type drop-down list.7. Type a Name and Description for the utility.8. If you want to recalculate the entire impact and lineage information, change

the default Mode in which you want to run the utility:• 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 runbecause it recalculates impact and lineage information across allintegrator sources.

• Optimized is the default mode. Optimized mode recalculates impactand lineage information for only the integrator sources that containchanges since the last time the computation was run. For example, ifonly one Integrator was run, the computation only recalculates impactand lineage information corresponding to that integrator source andupdates the lineage staging table.

9. Click Save.The new name appears on the new Utility Configurations page.

Related Topics• Computing and storing lineage information for reporting on page 179• Scheduling the lineage report utility on page 182• Running the lineage report utility on demand on page 184

Modifying the configuration of a lineage report utilityYou can modify the Description and Mode in the configuration of a lineagereport utiltiy. To modify the configuration of a lineage report utility, you mustbe part of the Administrator group.



3. Select Metadata Management in the "Applications Name" list.



4. Click the down arrow next to "Action" in the top menu tool bar and selectManage Utilities.

5. On the "Utilities Configurations" page, click the down arrow next to "Action"in the top menu tool bar and select Properties

6. Select Lineage Report Utility from the Utility Type drop-down list.7. You can modify the following options:

• Description• ModeFor a description of these modes, refer to Configuring a lineage reportutility on page 180.

8. Click Save.

Related Topics• Computing and storing lineage information for reporting on page 179• Scheduling the lineage report utility on page 182• Running the lineage report utility on demand on page 184

Scheduling the lineage report utilityTo compute the lineage information at regular intervals, define a schedulefor it. To schedule the lineage report utility, you must be part of theAdministrator group.

1. At the top of the CMC Home page, select Applications from thenavigation list.


Manage Utilities.A list of utility configurations appear.

4. On the Utility Configurations page, select the name of the utilityconfiguration that you want to schedule.

5. In the top menu tool bar, click the down arrow next to "Actions" and selectSchedule.

6. If you do not want the default value lineage utility for Instance Title,change it to a value you want.

7. To define the frequency to execute this utility, expand Recurrence, selectthe frequency in the Run object drop-down list, and select the additionalrelevant values for the recurrence option. For a list of the recurrence



options and the additional values, see Recurrence options on

page1628. 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 be notified when this utility runs successfully or when it

fails, expandNotification, and fill in the appropriate information. For moreinformation about Notification, see the BusinessObjects EnterpriseAdministrator's Guide.

10. If you want to trigger the execution of this utility when an event occurs,expand Events, and fill in the appropriate information. For moreinformation about Events , see the BusinessObjects EnterpriseAdministrator's Guide.

11. Click Schedule.



Running the lineage report utility on demandTo compute and repopulate the lineage staging table on demand, you mustbe part of the Administrator group.



3. Select Metadata Management in the "Applications Name" list.4. Click the down arrow next to Action in the top menu tool bar and select

Manage Utilities.The list of configured utilities displays with the date and time each waslast run.

5. From the "Utility Configurations" list, select the name of the utility youwant to run.

6. Determine the mode to run the lineage report computation.• If you want to compute and repopulate the entire lineage staging table,

you can go to the next step because the default value for the Modeoption is Full.

• If you want to recalculate lineage for only the integrator sources thatcontain changed and new data, do the following:a. Double-click the name of the utility to open the "Lineage Report

Utility Configuration" page.b. Select Optimized in the Mode option.

Note:If you select Full Mode, the computation can take a long time to runbecause it recalculates impact and lineage information across all integratorsources.

7. 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 anotherlineage report utility run. Starting another utility run might cause deadlocksor delays. The same behavior might occur if you stop the utility and startanother instance right away because the process might still be runningin the repository.



8. To view the status of the utility run, select the utility configuration nameand click Action > History.a. To see the progress of the computation run, click the icon for View

the database log in the top menu bar of the "Utility History" page.b. The "Schedule Status" column can contain the following values:

• Failed• Running• Success

c. The "Log File" column contains a Download link that you can click toview the log file after the lineage report utility completes.

9. To close the "Utility History" page, click the X in the upper right corner.10. On the "Utility Configurations" page, click the Refresh icon to update the

"Last Run" column for the utility configuration.

Recreating search indexes

The search feature of SAP BusinessObjects Metadata Management Explorerallows you to search for an object that might exist in any metadata integratorsource. When you run a metadata integrator source, Metadata Managementupdates the search index with any changed metadata.

You might need to recreate the search indexes in situations such as thefollowing:

• If the Search Server was disabled and could not create the index whilerunning a metadata integrator source.

• The search index is corrupted.

Related Topics• Configuring a search index utility on page 186• Running the search index recreation utility on page 188



Configuring a search index utilityTo configure a search index recreation utility, you must be part of theAdministrator group.

SAP BusinessObjects Metadata Management provides a default searchindex utility configuration for all integrator sources. You might want to createanother configuration if you want to recreate the search index for only oneintegrator source.




Manage Utilities.5. On the "Utilities Configurations" page, click the down arrow next to

"Manage" in the top menu tool bar and selectNewUtility Configuration...6. Select Search Index Utility from the Utility Type drop-down list.7. Type a Name and Description for the utility.8. Choose the Integrator Source Name for which you want to run the utility:

• All Integrator Sources recreates the search index for all integratorsources that you have configured.

• The specific name of an Integrator Source.



9. Click Save.The new utility name appears on the new Utility Configurations page.

Related Topics• Recreating search indexes on page 185• Running the search index recreation utility on page 188

Modifying the configuration of a search index utilityYou can modify the Description and Integrator Source Name in theconfiguration of a search index utiltiy. To modify the configuration of a searchindex utility, you must be part of the Administrator group.






Manage Utilities.5. On the "Utilities Configurations" page, click the down arrow next to "Action"

in the top menu tool bar and select Properties6. Select Search Index Utility from the Utility Type drop-down list.7. You can modify the following options:

• Description• Integrator Source Name

• All Integrator Sources recreates the search index for all integratorsources that you have configured.

• The specific name of an Integrator Source.

8. Click Save.

Related Topics• Recreating search indexes on page 185• Running the search index recreation utility on page 188

Running the search index recreation utilityTo recreate search indexes for the Metadata Explorer, you must have FullControl access level on the SAP BusinessObjects Metadata Managementfolder.




Manage Utilities.A list of utility configurations appear.

5. Select the recreate index utility that you want to run.6. In the top menu tool bar, click Action > Run Now.7. To view the status of the utility run, select the utility configuration name

and click Action > History.



a. To see the progress of the computation run, click the icon for Viewthe database log in the top menu bar of the "Utility History" page.

b. The "Schedule Status" column can contain the following values:• Failed• Running• Success

c. The "Log File" column contains a Download link that you can click toview the log file after the lineage report utility completes.

8. To close the "Utility History" page, click the X in the upper right corner.9. On the "Utility Configurations" page, click the Refresh icon to update the

"Last Run" column for the utility configuration.

Viewing and editing repository information

To view SAP BusinessObjects Metadata Management repository connectioninformation, such as database type and server name, you must have FullControl access level on the Metadata Management folder.

To edit the database user and password for the repository, you must be partof the Administrator group.

If the database type of the repository is an Oracle RAC database, you canchange the connection string if you are part of the Administrator group.

1. Access and login to the Central Management Console (CMC) if you havenot already done so.


3. In the "Applications Name" list, select Metadata Management.4. Click the down arrow next to Action in the top menu tool bar and select

Configure Repository.The connection information for the Metadata Management repository wasdefined 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 forfailover.



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

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

Related Topics• Accessing Metadata Management for administrative tasks on page 119

Exporting objects to XML

SAP BusinessObjects Metadata Management provides an XML export utility,MMObjectExporter.bat, which allows you to export repository objects to anXML file. The utility is installed on the machine on which you installed thisproduct. You specify its output by using required and optional command linearguments.

To export objects to XML

1. From a command prompt, navigate to the SAP Business Objectsinstallation directory's subdirectory location MetadataManagement\MM\bin.

2. Invoke the XML export utility by typing and running the commandMMObjectExporter with the appropriate arguments from the followingtable.



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 MetadataManagement to create, including the full path. If this argument containsblank spaces, you must enclose the argument in quotation marks. Includeonly the full path and file name for this argument. Do not include the wordfilename.

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



DescriptionOption

(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 specifiedby this argument are also included in the XML output. However, thisargument has an optional name list to limit the object selection to aspecific set of objects. The object type is limited to those shown in theobject type XML specification's <object-type> element type attributein the file MetadataManagement\MM\xml\ObjectTypes.xml, and mustbe spelled and cased the same. The type attribute is also used tospecify the logical name of the table containing objects of that type.

If there are no objects found in the repository that meet the mainObjectrequirements, then the utility exits with an error message. If some butnot all of the objects are found, the utility generates the XML file butwrites a warning message about the objects that were not found to thelog.

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

(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



DescriptionOption

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

includeRelation-ships

(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. Thelocation 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. By default, the value of thisargument is MetadataManagement/MM/xml/ObjectExportSchema.xml.Use this argument to override the default name or the default location inorder to specify a network-accessible location for the XSD file.

xsdUrl

After the utility runs, Metadata Management creates an XML file accordingto the specified arguments.

Example:

In this example, at a command prompt positioned in the installationdirectory's subdirectory location MetadataManagement\MM\bin, the userenters the following command and arguments:

mmobjectexporter 82 "c:\temp\first exported.xml"boeUser Jane boePassword My1PasswordmainObject Universe

The entries represent the following:



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 export-ed.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.

boePasswordMy1Password

Uses the mainObject argument to select all Universes in the configura-tion. Alternatively, the argument could be more specific. For example,using the syntax mainObject "Universe=MyUniverse" selects only theUniverse named MyUniverse. Using the syntax mainObject "Uni-verse=MyUniverse,YourUniverse" selects the two Universes namedMyUniverse and YourUniverse. The parents and children of these objectswould also be included, because the arguments for includeParents andincludeChildren are not invoked, and so they default to TRUE.

mainObject Universe



SAP BusinessObjectsMetadata ManagementExplorer

7

Metadata Management ExplorerSAP BusinessObjects Metadata Management Explorer is a web applicationthat organizes metadata from different source systems (such as BusinessIntelligence and Data Integration systems) into a directory structure throughwhich you can easily navigate and analyze the metadata.

This section describes the following tasks that you can perform on MetadataManagement Explorer:

• Accessing Metadata Management Explorer on page 197

• Viewing objects in the Metadata Management Explorer on page 199

• Searching for objects on page 202

• Viewing custom reports on page 207

• Defining custom reports on page 208

• Viewing relationships between objects on page 212 (such as Same As,Lineage, and Impact) within a source and between different sources.

• Metadata Management Metapedia on page 231

• Adding annotations for user notes on page 221

• Exporting relational objects on page 245 to a Common WarehouseModeling (CWM) XML file.

• Establishing user-defined relationships between objects on page 260between objects in the same or different sources.

• Changing preferences for relationships on page 264 for impact and lineageand object equivalency.

Metadata Management Administrator configures the source systems andexecutes programs that extract metadata from the source systems and loadit into the Metadata Management Repository. For more information, seeMetadata Management administration overview on page 118.


SAP BusinessObjects Metadata Management Explorer7 Metadata Management Explorer

Accessing Metadata Management Explorer

To access the SAP BusinessObjects Metadata Management Explorer toexplore metadata objects or to view relationships of objects across metadataintegrator sources, you must have at least View access level on the MetadataManagement application.

To perform tasks other than viewing on the Metadata Management Explorer(such as defining a Metapedia term or custom attribute), you must have theappropriate access level. For more information, see Access levels forMetadata Management tasks on page 124.

1. Access the Metadata Management Explorer in one of the following ways:• Type the name of the computer you are accessing directly into your

browser.

http://webserver:8080/bomm/

Replace webserver with the name of the web server machine. If youchanged this default virtual directory on the web server, you must typeyour URL accordingly. If necessary, change the default port numberto the number you provided when you installed BusinessObjectsEnterprise.

• In InfoView, click Open in the top menu bar and select MetadataManagement Explorer.

2. On the "Log On to BusinessObjects Metadata Management - Explorer"window, enter a valid user name and password for a user name that hasat least View access level on the Metadata Management application.

3. If you are viewing the "Document List" window in InfoView, you can selecta document from the list and display the Metadata Management lineagediagram for it by taking one of the following actions:• Right-click and choose View Lineage.• Click Action in the menu bar and select View Lineage.

Note:By default, Metadata Management Explorer sessions time out after 20minutes of non-use. When the session expires, you must log in again.


7SAP BusinessObjects Metadata Management ExplorerMetadata Management Explorer

Metadata Management Explorer user interface

Use the following tools to manage the metadata.

DescriptionIcon

Add Annotation: add user notes for objects. See Addingannotations on page 221.

Add Object to Tray: export objects or define relationshipsbetween objects. See Selecting objects to export on page248 and Establishing user-defined relationships betweenobjects on page 260.

Added to Object Tray: indicates that the object is currentlyin the Object Tray. See Selecting objects to export on page248 and Establishing user-defined relationships betweenobjects on page 260 for more information.

Relationship attribute: shows relationship type or source totarget mapping that exists between two objects. SeeGraphical view on page 216.

Edit Annotation: edit or delete user notes for objects. SeeEditing annotations on page 222.

Lookup Object: shows available databases, catalogs, andschemas. See Setting object equivalency rules for SameAs relationships on page 267 for more information.


SAP BusinessObjects Metadata Management Explorer7 Metadata Management Explorer

Viewing objects in the MetadataManagement Explorer

The SAP BusinessObjects Metadata Management Explorer displays thefollowing top-level categories that represent the different types of integratorsources that can populate the Metadata Management Repository:

• Business Intelligence - Source systems include SAP BusinessObjectsEnterprise.

• Data Modeling - Source systems include CWM (Common WarehouseModeling).

• Data Integration - Source systems include SAP BusinessObjects DataFederator, BusinessObjects Data Integrator, and SAP BusinessObjectsData Services.

• Relational Databases - Source systems include DB2, MySQL, Oracle,SQL Server, Java Database Connectivity (JDBC), or an SAPBusinessObjects Universe connection.

A category displays if a source has been configured for the MetadataIntegrator belonging to that category. Metadata integrators are programsthat extract metadata from the source systems and load it into the MetadataManagement Repository. Metadata Management administration overviewon page 118 describes how to configure a source for each Metadata Integrator.

Directory home page

The Directory home page of the SAP BusinessObjects Metadata ManagementExplorer shows each configured integrator source, grouped under thecategory in which it belongs.


7SAP BusinessObjects Metadata Management ExplorerViewing objects in the Metadata Management Explorer

This sample Directory page shows:

• The top-level categories• Under each category are the names of sources that the Metadata

Management Administrator configured for each Metadata Integrator.• Business Intelligence

This example shows source name MySales that was configured forthe SAP BusinessObjects Enterprise (BOE) Metadata Integrator.

• Data Integration

This example shows source names My DF Source and DIREPO thatwere configured for the Data Integration Metadata Integrator.

• Relational Databases

This example shows source names Forenza DW and Forenza Sourcethat were configured for the Relational Databases Metadata Integrator.

• Data Modeling

This example shows the CWM Sales source name that was configuredfor the Common Warehouse Modeling (CWM) Metadata Integrator.

• Under each source name are the first three metadata object types that itcontains, and the number in parenthesis indicate the number of instancesfor that type.• The sample shows object types Universes, Reports, and CMS

Folders under source MySales.• The sample shows object types Projects, Jobs, and Work Flows

under source DIREPO.


SAP BusinessObjects Metadata Management Explorer7 Viewing objects in the Metadata Management Explorer

• The sample shows object types Server Instances, Databases, andSchemas under sources Forenza DW and Forenza Source.

• The sample shows object types Databases, Schemas, and Tablesunder source CWM Sales.

Click More to display all object types in the source. The source page alsoopens when you click the source name. For a description of the objects typesthat can exist within sources for each Metadata Integrator, see the followingsections:

• SAP BusinessObjects Enterprise metadata objects on page 273• Exploring CWM objects on page 338• BusinessObjects Data Services objects on page 348• Relational Database objects on page 395

Navigating metadata

From the Directory home page of the SAP BusinessObjects MetadataManagement Explorer, you can navigate to the metadata object types ineach configured integrator source.

Click an object type name under a source to display more information aboutit. If an object type contains other object types, click each object type nameto display its information.

For example, to navigate to the universe object Total Order Value:• Under the Business Intelligence category on the Directory home page,

click Universes(9) under the My Sales source name.• On the "Universe Clases" list, click Universe Objects(8) under Fact

Sales Order.• On the "Universe Objects" list, click the measure Total Order Value to

open the metadata object page onto the Overview tab as follows.


7SAP BusinessObjects Metadata Management ExplorerViewing objects in the Metadata Management Explorer

Each metadata object page shows the navigation path at the top. You canclick any link in the navigation path to return to that level. This page for theuniverse object "Total Order Value" shows the following navigation path.

Directory > Business Intelligence (MySales) > Universes (MySales) >Universes Classes (Fact Sales Order) > Universes Objects (Total OrderValue)

Related Topics• Navigating SAP BusinessObjects Enterprise metadata on page 278

Searching for objectsThe search feature of SAP BusinessObjects Metadata Management Explorerallows you to search for an object that might exist in any source.

You can do a basic search for an object by typing some or all of the followingattributes and clicking Search:

• Name• Description• Annotation• Custom attributes• Business terms• Categories

To search on a variety of conditions including object type, fields, or values,use the advanced search feature.


SAP BusinessObjects Metadata Management Explorer7 Searching for objects

Related Topics• Search scope on page 203• Search string parameters on page 203• Advanced search on page 204• Search results on page 206

Search scope

The scope of the search depends on where you are in the SAPBusinessObjects Metadata Management Explorer:

• When you enter the search string on the home page of the MetadataManagement Explorer, you search the entire Metadata ManagementRepository.

• When you navigate into the objects of an Integrator source, you have theoption to search only objects within the current integrator source.

Search string parameters

The search string that you enter into the Search text box can consist of:

• One word

• Multiple words

If you do not enclose the search string in double quotes, SAPBusinessObjects Metadata Management searches for an object type,technical name, business name, description, or annotation that containsat least one of the words.

The results with all words are more relevant and appear at the beginningof the result list.

• A phrase—Enclose the search string in double quotes to search for thephrase in the same exact order of words.

The search string can contain single- and multiple-character wild cardsearches. The wild card character can appear anywhere in the searchstring.


7SAP BusinessObjects Metadata Management ExplorerSearching for objects

The search string can contain single- and multiple-character wild cardsearches. The wild card character can appear anywhere in the searchstring.

• For a single-character wild card search, use the "?" symbol. Forexample, to search for "test" or "text", you can use the search string:

te?t

• For a multiple-character wild card search, use the "*" symbol. Forexample, to search for "custom" or "customer", you can use the searchstring:

cust*

• Combination of word and phrase. For example

"name of" cust*

Advanced search

The advanced search function allows you to add multiple conditions to narrowyour search. You can define each condition by object type, attribute, matcha word, or by a value.

To access the advanced search feature, on the right side of the Search box,click Advanced. The list of available object types depends on the searchscope (repositories) selected.

Define the first condition by selecting from any or all of the followingdrop-down lists:

• Select an object Type by which to narrow your search; for example, onlyTables.

• Select an Attribute by which to narrow your search; for example, onlyan Name.• ANY Field—Searches all fields• Name—Searches only Name fields• Description—Searches only the Description field for the object• Annotation—Searches the Annotation field• Custom attributes—Searches on the selected custom attribute



• Business terms—Searches on Metapedia terms• Categories—Searches on Metapedia categories

• Select how to restrict the search on the Value field by selecting one ofthese options for Match:• ANY Word—Returns objects that include any of the words in the Value

field• All Words—Returns only objects that include all of the words in the

Value field• Fuzzy match—Returns objects that resemble any of the words in the

Value field• Metapedia keyword—Returns objects that include the Metapedia

keyword in the Value field• Metapedia synonym—Returns objects that resemble the Metapedia

synonym in the Value field• Value—Type a value using the same guidelines described in Search

string parameters on page 203.

To add more conditions to further restrict your search, click Add conditionand enter the desired values. You can restrict the search for the same objecttype to meet all of the displayed conditions by selecting Match ALL. Towiden the search to include one or more of the conditions, select MatchANY.

Click Search.

Click Clear to return the fields to their default values.

Example:

The following example shows the conditions to search for reports that areTop Secret, with names that contain "Sales" and have a Usage Rating of4.


7SAP BusinessObjects Metadata Management ExplorerSearching for objects

Search results

Suppose you search for objects that match the search string cust*.

The left side of the search results page lists the object type categories andthe total number of objects found within each category that match the searchstring. The following example shows these categories: Columns, CustomFunctions,Data Flows, Procedures,Reports, Tables,Universe Classes,Universe Objects, and Views.

Each category name is a link to a page that displays the objects found withinthat category. For example, clicking Tables displays the list of table namescontaining the search string cust*.



The right side of the search results page is an alphabetic list of object namesthat match the search string.

The results for each object include:

• Name of the object.

Click the object name to go to the SAP BusinessObjects MetadataExplorer page where you can view information such as the object's impactand lineage details.

Click Back on the Web browser to return to the search results.

• Short description, if any• Full path of the object• Option to add the object to the Object Tray. You use the Object Tray to

establish relationships between objects. For details, see Establishinguser-defined relationships between objects on page 260.

If the search results exceed 10 objects, use the links at the bottom of thepage to display the other results pages.

Note:

Changes such as defining custom attributes or setting custom attribute values,adding Metapedia terms, or adding annotations will affect your search results.The Metadata Management Explorer automatically refreshes your searchresults after a default maximum time of 60 seconds. You can change thisdefault value in the Delay time before changes in Explorer affects thesearch results (seconds) option on the "Preferences" page.

Metadata integrator runs affect the search results as soon as the integratorprocesses finish.

Viewing custom reportsSAP BusinessObjects Metadata Management Explorer provides customreports from the Reports tab on the Metadata Management Explorer. Thesecustom reports help you perform the following analyses and answer typicalbusiness questions such as the following:

• Usage analysis - Where are objects used and what are their attributes• Which reports use a specific universe?• Which universe objects are not used in my reports?


7SAP BusinessObjects Metadata Management ExplorerViewing custom reports

• Which reports are using my tables?• Which data flows use this table?

• Lineage analysis - Trace objects from target to sources• What is the lineage of selected reports?• What is the lineage of selected tables?• What is the lineage of selected views within a database source?

• Impact analysis - What targets are affected if I change a specific source• What is the change impact of the selected tables in a source?• What is the change impact of the selected columns in a source?

See the Report tab on the Metadata Management Explorer for a completelist of reports available.

Defining custom reportsYou can define your own Crystal Reports on the SAP BusinessObjectsMetadata Management tables and view them on the Metadata ManagementExplorer.

Metadata Management supports the following features in a Crystal Report:

• Tables• SQL Command objects• Subreports• Parameter Prompts

This section includes the following topics:

• Metadata Management Views to query for your Crystal Reports onpage 208

• Typical usage scenarios on page 210• Enabling your reports in Metadata Management Explorer on page 211

Metadata Management Views to query for yourCrystal Reports

You can query the following views in the SAP BusinessObjects MetadataManagement Repository for your own Crystal Reports.


SAP BusinessObjects Metadata Management Explorer7 Defining custom reports

DescriptionView in Metadata ManagementRepository

Consolidates various elements of relation-al databases so that you can obtain allrequired information about a relationalobject from a single view.

MMRV_Relational_Model

Consolidates all classes and objects of anSAP Business Objects Universe.

Note:This view does not maintain the hierarchi-cal structure of Classes and objects(nested classes and nested objects).

MMRV_Universe_Model

Consolidates all information about flatfiles, file records and file elements.MMRV_Flat_File_Model

Consolidates information about the differ-ent object types to help you understandobject relationships more easily.

MMRV_Relationship

Consolidates information about sourceand target relationships.MMRV_ST_Relationship

Consolidates information about derivedtables within a universe and their relation-ships with other objects.

MMRV_Universe_Derived_Table

Consolidates information about derivedcolumns within a universe and their rela-tionships with other objects.

MMRV_Universe_Derived_Column

Consolidates information about relation-ships between a universe and reports.MMRV_Report_Universe

Consolidates information about relation-ships between reports and a relationalcolumn.

MMRV_Report_Columns


7SAP BusinessObjects Metadata Management ExplorerDefining custom reports

DescriptionView in Metadata ManagementRepository

Reporting table for end-to-end impact andlineage information across all sources.

Note:Ensure that you compute and store theimpact and lineage information before youuse this view for reporting. For more infor-mation, see Computing and storing lin-eage information for reporting on page 179.

MMD_Alternate_Relationship

Typical usage scenarios

You may want to customize your own Crystal Reports on the SAPBusinessObjects Metadata Management Repository views and tables fortypical usage scenarios such as the following:

• Find the table names and schema names of a given column.

Use the MMRV_Relational_Model view to query the table names andschema names.

• Find all the tables and columns with a specific column data type, or findall tables and columns used in a given report.

Join the MMRV_Relational_Model view and MMD_Relational_Columntable to obtain the tables and columns with the specified data type.

• Find all the databases and schemas used in a given report.

Use the MMRV_Relational_Model view to query the database and schemanames for a given report.

• Write custom impact and lineage reports.

Use the MMD_Alternate_Relationship view to query the impact and lineageacross sources.


SAP BusinessObjects Metadata Management Explorer7 Defining custom reports

Enabling your reports in Metadata ManagementExplorer

After you have defined your own Crystal Reports that query the SAPBusinessObjects Metadata Management tables, you enable these reportsto display in Metadata Management Explorer.

To enable your reports to appear on the Reports tab:

1. Place your report files in the following directory:

%CATALINA_HOME%\webapps\bomm\WEB-INF\reports

2. In the same directory, create a reportname.rptproperties file with thefollowing information that will appear on the Reports tab for each report.

DescriptionProperty name

Name of the report. Can contain HTML tags.name

(Optional) Description of the report. Can beblank and can contain HTML tags.description

(Optional) Question that this report answers.Can be blank and can contain HTML tags.question

(Optional) List of categories (separated bysemicolons) for the report. A report can be partof multiple categories.

categories

(Optional) Source database for this report. Thisfield specifies whether the source is the Metada-ta Management Repository or an Integratorsource database. The default value is MM_TYPE.

Either leave the default value MM_TYPE orspecify the technical name for the Integrator.

source-type


7SAP BusinessObjects Metadata Management ExplorerDefining custom reports

DescriptionProperty name

(Optional) Class name of the connection handlerif your report connects to a data source that isnot handled by the default connection handler.The default connection handler supports DB2,MySQL, Oracle, SQL Server, and Sybase datasources.

For more information, see the SAP MetadataManagement Developer's Guide.

connection-handler

(Optional) List of subreports (separated bysemicolons) contained in this report.subreports

For example, the properties file might contain the following lines:

name=Utilization count by universedescription=For each universe, count the number of reports.subreports=Utilization count by universe totalsquestion=How many reports use a universe or a particularobject in my universe ? Which objects are frequently usedor not used at all?categories=Usage Reports;

Viewing relationships between objectsWhen you analyze metadata, you often analyze relationships betweenobjects. Each Metadata Integrator obtains the following relationships from asource system and you can view them on the SAP BusinessObjects MetadataManagement Explorer.


SAP BusinessObjects Metadata Management Explorer7 Viewing relationships between objects

Where dis-playedWho definesDescriptionRelationship

On Same Astab of the ob-ject's Explorerpage

Metadata Inte-grator

An alias is another name for an object in adifferent system. For example, an alias namein one database might refer to a relationaltable in a different database.

A synonym is another name for an object inthe same system. For example, a synonymfor a relational table exists in the samedatabase as the table.

Alias or Syn-onym

In the directo-ry structure ofthe MetadataManagementExplorer


The meaning of this relationship is specific tothe source application.

For example in the Business Intelligencecategory, a report can contain multiple uni-verse objects. An association relationshipexists between the report and each universeobject.

In the Data Integration category, a job cancontain multiple data flows. An associationrelationship exists between the job and eachdata flow.

Association

On corre-sponding rela-tionship analy-sis tab of theobject's Ex-plorer page

You define.You define this relationship. For an example,see Establishing user-defined relationshipsbetween objects on page 260.

Related To


7SAP BusinessObjects Metadata Management ExplorerViewing relationships between objects

Where dis-playedWho definesDescriptionRelationship

On Same Astab in a tabu-lar format

On Impactand Lineagetabs with adashed linebetween thetwo objects(each withina differentsource sys-tem) that arethe same


You can alsodefine.

The object is the same as another object. Thisrelationship can exist only between objectsof the same type.

For example, a Same As relationship canexist between each object in a test systemand its corresponding object in a productionsystem.

Same As

In the directo-ry structure ofthe MetadataManagementExplorer


In a hierarchy, the parent is a level above thechild. In a parent-child relationship, a parentcan have several children, but a child canhave only one parent.

For example, a table can have multiplecolumns, but a column can belong to only onetable.

In the Business Intelligence category, a uni-verse can have multiple classes, but a classcan belong to only one universe.

Parent-Child

On the Relat-ed To tab ofthe object'sExplorer page

Metadata In-tegrator

You can alsodefine.

The primary key is a unique value that identifiesan object. A foreign key identifies another objectfrom an object. Foreign keys in other tablesmust have a matching primary key value.

Primary Key -Foreign Key



Viewing impact and lineage of objects

To view the impact and lineage of objects within a source, you navigate orsearch through the SAP BusinessObjects Metadata Management Explorerto the object (such as a report, table, or column) and click the Impact orLineage tab.

The Impact and Lineage tab displays in a graphical view or in a tabular view.For either view, you can select the Show intermediate objects option inEdit Settings to display only the first source and final target objects.

See the following sections for details about the object relationships withineach Metadata Integrator source:

• Viewing relationships for universe objects and reports on page 289.• Viewing relationships of CWM objects on page 340.• Viewing relationships in a database source on page 401.• Viewing Data Services object relationships on page 358.

Options to view relationships

When viewing Same As, Related To, Impact, and Lineage relationships, youcan toggle between graphical and tabular views, edit the display settings,and maximize the display to better use viewing space.

This section describes these configurable options.

Graphical and tabular views of relationships

Within Same As, Related To, Impact, and Lineage relationship views, the"View" pull-down menu allows you to toggle between graphical and tabularviews. You can also switch between these views when you edit the settingsto view relationships.

Related Topics• Understanding settings to view relationships on page 219



Graphical viewBy default, the Related To, Impact, and Lineage tabs of the SAPBusinessObjects Metadata Explorer show a graphical view for target andsource objects.

Each object displays as a graphic on which you can do the following actions:

• Move the pointer over to display information such as:• Universe name and universe class for a universe object• Schema name and database name for a table• Table name and schema name for a column

• Click an item to display its Metadata Explorer page.

Between two objects there is a relationship attribute icon, over which youcan move the pointer to display information such as:

• Selection or aggregation between universe objects and a report in anSAP BusinessObjects Enterprise source

• Transformation name and mapping between source and target columnsin a Data Integrator source

For example, the following graphical view shows the Lineage for universeobject Total Order Value.

The relationship attribute displays the mapping expression that the DIREPOsource system uses to transform the Quantity column.



Tabular viewThe tabular view shows a row for each target object and source object withthe following information:

DescriptionColumn name

The target object receives the data that has thefollowing characteristics:• Was calculated from the source object,

• Was transformed from the source object, or

• Comes directly from the source object

Target

The source object provides data that is copied ortransformed to become part of the target object.

For example, in the Business Intelligence catego-ry, a relational column object and a report fieldobject can have a source-target relationship.

Source

The number of objects through which the datapasses from this source to the final target, or fromthis target to the first source.

Steps from Target, or

Steps from Source

Relationship between the source and targetRelationship Attributes




If the target is a measure, this column contains:• Transformation name, which is the name of the

universe object.• Mapping expression which is the calculation to

obtain the value for the measure.

If the source data was transformed from an ETLsystem, this column contains:• Transformation name, which is the data flow

name in a Data Integrator source.• Mapping expression within the transform.

Mapping

Example:

The following tabular view shows the Lineage for universe object TotalOrder Value.

The Mapping column in this example shows:• For the source measure Total Order Value:

Transformation Name: Total Order ValueMapping Expression: sum(DBO.FACT_SALES_ORDER.TOTAL_ORDER_VALUE)



• For the source columns UNITPRICE, QUANTITY, and DISCOUNT:

Transformation Name: df_SalesOrderFactMapping Expression: (("ORDER DETAILS".UNITPRICE *"ORDER DETAILS".QUANTITY) - ("ORDERDETAILS".DISCOUNT * ("ORDER DETAILS".QUANTITY* "ORDER DETAILS".UNITPRICE)))

Understanding settings to view relationships

When viewing the relationships Same As, Related To, Impact, and Lineage,you use the Edit Settings button to change the viewing options that SAPBusinessObjects Metadata Management displays for that view.

You can control the display settings to determine the source group used,whether to show Intermediate objects, Where Clause objects, and UserImpact, as well as whether to show a grapical or tabular view.

Note:Some settings are applicable only to certain views. The options you seedepends on which relationship view is displayed.

To change settings when viewing relationshipsWhile viewing the relationships Related To, Impact, or Lineage:

1. Click the Edit Settings button.The Settings window appears.

2. Make changes to the following interface elements to control therelationship display settings:



DescriptionOption

From the drop-down list, select a source group. The drop-down list contains names if your administrator has definedsource groups to focus relationship analysis on a subsetof metadata integrator sources.

Use sourcegroup

Select the check box to show intermediate objects. If thisoption is not selected, only the first source object and finaltarget object are displayed.

Showintermedi-ate objects

Select the check box to show Where Clause objects.Show WhereClause objects

Select the check box to show User Impact.Show User Im-pact

From the drop-down list, choose "Graphical" or "Tabular"to switch between these types of relationship displays. Ifyou are viewing a table on the Lineage tab, the drop-downlist includes "Column Mappings", which allows you to viewthe mapping expressions used to obtain values in eachcolumn.

View

Related Topics• Grouping Metadata Integrator sources on page 177• Impact analysis for users and groups on page 306• Viewing column mappings for tables on page 366

Maximize and restore view

To get a larger view of complex graphs or tables in Related To, Impact, andLineage relationship views, you can fill the available screen with the currentview by clicking the Maximize View hyperlink.

When in a maximized view, you can toggle between graphical and tabularview, or edit the settings of the view. All other user interface elements areunavailable until you click the Restore View hyperlink to return the view toits original size.



Adding annotations for user notesYou can add user notes to any object. If an object has an annotation, anannotation icon appears next to it. Click the icon to display the annotation.The Overview page of the object also displays the annotation, along withany description.

Adding annotations

To add an annotation to an object:

1. Navigate to an object to which you want to add an annotation.2. Click Add Annotation to open the text box to add your note.

3. Type your note and click OK.

4. The annotation appears on the Overview page for the object.


7SAP BusinessObjects Metadata Management ExplorerAdding annotations for user notes

Editing annotations

To edit an annotation for an object:

1. Navigate to an object for which you want to edit an annotation.

You can either go directly to the Explorer page for the object or to a listof objects that contains the object.

For example, the following list of columns for the table SALES_CHANNELshows that the column SALES_CHANNEL_DESC has an annotation.


SAP BusinessObjects Metadata Management Explorer7 Adding annotations for user notes

2. Click the edit annotation icon.3. To change the annotation, type in the text box and click OK.4. To delete the annotation, delete the text and click OK.

Custom attributesCustom attributes allow you to add information to existing objects using theSAP Metadata Management Explorer. For example, you can define a customattribute to:

• Add additional object descriptions• Assign a data steward to objects• Tag objects as containing senstive information• Rate object relevancy• Link an object to a Web site

Users with the right to Add objects to the Metadata Management folder cancreate custom attributes that apply to object types and enter values for customattributes. Then users with the right to View the Metadata Management foldercan view and search on those custom attributes.

Related Topics• Creating custom attributes on page 224• Entering values for custom attributes on page 228


7SAP BusinessObjects Metadata Management ExplorerCustom attributes

Creating custom attributes

A user with the right to Add objects to the SAP BusinessObjects MetadataManagement folder defines a custom attribute, specifies possible values forit, and associates it with an object type.

Related Topics• Adding, defining, and associating custom attributes on page 224• Deleting a custom attribute on page 227• Reordering the display of custom attributes on page 227

Adding, defining, and associating custom attributes

Users with the right to Add objects to the SAP BusinessObjects MetadataManagement folder can add a custom attribute, specify possible values forit, and associate the attribute with an object type.

When creating a custom attribute, you specify a name, label (display name),the data type of the information, and optionally valid values.

1. Log in to the Metadata Management Explorer with a user name that hasthe Administrator role.

2. From the Explorer Directory or Reports tab view, click the CustomAttributes link.The Custom Attributes worksheet displays.

3. Click Add.Metadata Management adds a row to the worksheet.

4. Select the first cell, type a Name, and press Tab to move to the next cell.5. Type a Label (display name) and press Enter or press Tab to go to the

next cell.Metadata Management adds the prefix CA. to the custom attribute name.

6. Optionally type a description for the custom attribute.7. In the Type column, select a data type from the drop-down list:

• Boolean• Decimal• Integer


SAP BusinessObjects Metadata Management Explorer7 Custom attributes

• String• URL

8. Except for Boolean attribute types, optionally double-click in the ValidValues cell to define it (Metadata Management accepts any value bydefault).The Valid values (attribute name) dialog box displays.

9. Select one of the following options:

DescriptionOption

Lets the user configure any value for the attribute (default).Any value

Enter minimum and maximum values to limit the value to arange. For decimal types, enter a zero before the decimalpoint.

Range

Enter a value and click Add to add the value to the list. Re-peat for additional values that the attribute will accept.

List of val-ues

10. Click OK.The list of values appears in the cell.

11. Double-click in the cell under the Apply to column to select from a list ofavailable object types to which this custom attribute will apply.a. Double-click individual object types to move them to the Add custom

attribute to list. Or, use the Shift and Ctrl keys to select consecutiveor nonconsecutive (respectively) object types, then click the right arrow.

b. Click OK.The following example shows the custom attribute "Usage Rating" beingapplied to two object types, Reports and Tables.



12. Click Save Changes.

Note that you can change the view by selecting filters from the drop-downlist for each column. The filters include:

• Sort Ascending• Sort Descending• (Show all)• (Empty)• (Not empty)

After an Administrator has defined a custom attribute for an object type, userswith the User role can view, enter values for, or search on these customattributes.

Related Topics• Entering values for custom attributes on page 228

Modifying a custom attribute

Users with the right to Edit objects to the SAP BusinessObjects MetadataManagement folder can modify a custom attribute.


2. Edit the label or description by clicking in the cell and editing the text.



3. Add to any Valid Values lists by double-clicking in the cell and addingvalues. (You cannot delete existing values from the list.) Click OK.

4. To modify which objects this attribute applies, double-click in the cellunder the Apply to column.a. Double-click individual object types to move them to the Add custom

attribute to list. Or, use the Shift and Ctrl keys to select consecutiveor nonconsecutive (respectively) object types, then click the right arrow.

b. Click OK.


Deleting a custom attribute

User with the right toDelete objects from the SAP BusinessObjects MetadataManagement folder can delete a custom attribute.


2. Select a row by clicking the row number so the row appears highlightedin blue.

3. Click Delete.Metadata Management displays a warning message to confirm whetheryou want to delete the attribute.

Note:Metadata Management deletes the attribute even if values have beenentered for associated objects.

Reordering the display of custom attributes

Add custom attributes per Adding, defining, and associating custom attributeson page 224.

Users with the right to Edit or Add objects to the SAP BusinessObjectsMetadata Management folder can change the display order of customattributes within an object type in various views (but not in the objectworksheet view).



All custom attributes display in the object overview. However only the topthree custom attributes (based on the order you configure) display in objectpop-up boxes and other relationship views.

1. On the Custom Attributes worksheet, click theCustomAttributes DisplayOrder link.

2. Select an available object type, select a Custom attribute, and click Upor Down to rearrange the order.


Entering values for custom attributes

After a user with the right to Add objects to the SAP BusinessObjectsMetadata Management folder has associated custom attributes to objects,you can then enter values for these attribute(s). You can enter values for anindividual object, or you can enter annotations and custom attributes formultiple objects using the object worksheet.

Related Topics• Entering a value for a custom attribute for an object on page 228• Entering values for multiple attributes for an object type on page 229• Customizing the object worksheet display on page 230

Entering a value for a custom attribute for an object

After a user with the right to Add objects to the SAP BusinessObjectsMetadata Management folder has added, defined, and associated one ormore custom attributes to an object, you can then enter values for theattribute(s).

1. Navigate to an object for which you want to enter values for the customattributes.

2. Click the Edit Custom Attributes link.A dialog box opens for the attributes that apply to that object.

3. Type or select the values for the attributes to configure and click OK.Metadata Management adds the custom attribute to the list of attributesfor that object. Custom attributes appear in italic text on the Overview tabfor the object and in object pop-up boxes in relationships views.



Related Topics• Adding, defining, and associating custom attributes on page 224• Entering values for multiple attributes for an object type on page 229

Entering values for multiple attributes for an object type

Users with the right to Add objects to the SAP BusinessObjects MetadataManagement folder can enter values for multiple attributes for an object typeusing the object worksheet.

1. Navigate to the object type for which you want to configure attributes.2. Click the Edit Objects link.

The object worksheet displays.

3. Type or select the values in each cell for the attributes to configureincluding annotations and custom attributes.Metadata Management saves the value when you navigate away fromthe cell (when you press Tab or Enter or click in another cell).



Example:

The following example shows the custom attributes Top Secret, UsageRating, and Data Steward being set for four reports. The bottom of theworksheet indicates the user who last modified a custom attribute orannotation.

Related Topics• Adding, defining, and associating custom attributes on page 224• Entering a value for a custom attribute for an object on page 228• Customizing the object worksheet display on page 230

Customizing the object worksheet display

Users with the right to Add or Edit objects to the SAP BusinessObjectsMetadata Management folder can customize the object worksheet display.

You can customize the display of the object worksheet in one of two ways:

• Click Customize to display the Show/Hide/Order dialog box.

To show or hide columns, select or clear the check boxes and click OK.



To move a column up or down (corresponds to left or right respectivelyon the object worksheet), select (highlight) a column name and click Upor Down, then click OK.

• Each worksheet column has a drop-down menu that lets you hide thecolumn. Click Customize to open the Show/Hide/Order dialog box todisplay hidden columns.

Example:

The following example clears the check boxes in front of columns Keywordsand CMS Server to hide them on the worksheet.

Metadata Management MetapediaSAP BusinessObjects Metadata Management Metapedia allows you toimplement a business glossary of terms related to your business data andorganize the terms hierarchically.


7SAP BusinessObjects Metadata Management ExplorerMetadata Management Metapedia

The business glossary you create in Metapedia allows you to form avocabulary of words and phrases, or notation systems. Initially, you use thisvocabulary to describe content, and then later business users can easilysearch for the content using familiar business vocabulary and synonyms, orefficiently navigate to terms through the Metadata Management Explorerinterface.

Using Metapedia promotes a common, consistent understanding of businessterms within an organization, allowing business users access to informationusing terms from the perspective of business users. At the same time, datastewards have an easy mechanism to promote data governance.

You access Metapedia from theMetapedia tab in the Metadata ManagementExplorer.

This sample of a Metapedia window shows the following elements below the"Metapedia" tab:

• Top row buttons, which are active depending on the context of the currenttask

• Left-hand pane, here showing All Terms selected and sample categoriesof Financial and Healthe Care created by a user

• Filter terms fields, used for filtering the larger list of terms based on stringsearching criteria you can set

• Sample terms and their descriptions created by a user

The contents of the Metapedia window change to context-appropriateelements for each task you perform.


SAP BusinessObjects Metadata Management Explorer7 Metadata Management Metapedia

Understanding terms and categories

SAP BusinessObjects Metadata Management Metapedia is based on theconcept of how terms are associated with metadata objects and organizedinto categories.

A Metapedia term is a word or phrase that defines a business concept inyour organization. You create a term to describe a business concept, givingthe term a name and description, and optionally, a list of synonyms andkeywords. Then you can associate a metadata object with the term, andrelate the term with other terms.

A Metapedia category is the organization system for grouping terms to denotea common functionality. Categories can contain sub-categories, and you canassociate terms to more than one category.

Note:The names of terms and categories are not case sensitive. Therefore, termor category names of “Inventory” and “inventory” would functionally be thesame.

Example:

You create the terms Gross Revenue and Net Revenue, and place themin a category called Financial. However, in your organization, many businessusers refer to Net Revenue as profit, which you do not intend to use as aMetapedia term. In the creation of the Net Revenue term, the data stewardcould apply the word profit as a synonym. Then, when a business usersearches Metapedia for profit, Metapedia returns the metadata objectsassociated with Net Revenue.

Further, the data steward could associate Gross Revenue and Net Revenue,so when a business user searches for one of the terms, metadatainformation about the other is also available.

Related Topics• Working with Metapedia terms and categories on page 234



Data steward and security

The concept of the data steward has important implications on security inSAP BusinessObjects Metatadata Management Metapedia. Only a datasteward has Full Access rights to Metapedia, which allows a data stewardto do the following:

• Create, edit, and delete terms.• Approve terms.• Relate an approved term to other approved terms.• Associate approved terms with metadata objects (a report, CMS objects,

a column, and so on).

A user who is not a data steward can view and search for approved terms.

Related Topics• Managing security in Metadata Management on page 122

Working with Metapedia terms and categories

The usefulness of SAP BusinessObjects Metadata Management Metapediais based on the number and quality of your terms and categories. A datasteward can add terms and categories to Metapedia, either manually orthrough the import of an Excel file. This section describes creating andmanaging terms and categories.

Creating terms

A data steward can create terms to add to the SAP BusinessObjects MetadataManagement Metapedia business glossary. To create a term:

1. With "All Terms" selected in the left-hand navigation pane of the Metapediawindow, click Create Term.The Create Term window appears.

2. Enter a value for the "Name" field. (Non-alphanumeric characters andspaces are permitted in term names.)

3. Enter a value for the "Description" field.



4. Enter a value for the "Synonyms" field. This step is optional.5. Enter a value for the "Keywords" field. This step is optional.6. Select a data steward from the "Data Steward" drop-down list. This step

is optional.When you later view the properties for this term, an email icon appearsnext to this data steward. The email created is sent to this user name,not the data steward's email address as it is registered in SAPBusinessObjects Enterprise.

7. If you want to approve the term, you can click the "Approved" checkboxto mark the term as Approved. This step is optional.Terms that are not approved can be viewed only by data stewards. Aftera data steward has marked a term as Approved, all users can view theterm.

8. Click OK.The Properties for Term window is displayed.

The new term is created and available in the list of terms shown when "AllTerms" is selected in the main Metapedia window.

Editing properties of terms

After one or more terms have been created, a data steward can edit theproperties of a term. To edit the properties of a term:

1. In a window from which the term is available ("All Terms" or the categoryfor which the term is associated), click the name of the term.The "Properties for Term" window appears.

2. Click Edit Properties.An editable "Properties for Term" window appears. This window containsthe same information as the "Create terms" window. The fields for theterm's properties are editable and populated with the current values.

3. Make any changes to the properties of the term, and click OK.The changes appear in the resulting window.

The changes to the properties of the term are saved.



Relating terms

After two or more terms have been created, a data steward can relate terms.

To relate terms:

1. In a window from which one of the terms is available ("All Terms" or thecategory for which the term is associated), click the name of a term.The Properties for Term window appears.

2. Click Relate Terms.The Relate Terms window appears.

3. Check the box next to each term you want to associate with this term.You can filter the listed terms to search a large list of terms.

4. Click OK.The Properties for Term window appears, showing a listing of relatedterms.

All the terms you selected are now related terms.

Related Topics• Filtering terms on page 243

Deleting terms

A data steward can delete terms.

Note:There is no undo option after terms are deleted. You must have delete accessrights on the SAP BusinessObjects Metadata Management Metapedia folder(set in the Central Management Console) to delete terms.

To delete terms:

1. With All Terms selected in the left-hand navigation pane, check the boxfor all terms you want to delete and click Delete Terms.A confirmation dialog appears.

2. Click OK.The list of terms shown when All Terms is selected in the main Metapediawindow is repopulated without the deleted terms.



The selected terms are deleted.

Creating categories

A data steward can create categories or sub-categories to add to the SAPBusinessObjects Metadata Management Metapedia business glossary. Tocreate a category or sub-category:

1. With Categories or a pre-existing category selected in the left-handnavigation pane, click Create Category.

Note:If Categories is selected, this process creates a new category. If apre-existing category is selected, this process creates a sub-category ofthat category.

The Create Category window appears.

2. Enter a value for the "Name" field. (Non-alphanumeric characters andspaces are permitted in term names.)

3. Enter a value for the "Description" field. This step is optional.4. Select a Data Steward from the "Data Steward" drop-down list. This step

is optional.5. Enter a value for the Keywords field. This step is optional.6. Click OK.

The Properties for Category window is displayed.

The new category or sub-category is created and available in the list ofcategories.

Editing properties of categories

After one or more categories have been created, a data steward can editthe properties of a category.

To edit the properties of a category:

1. In a window from which the category is available, select the category andclick Edit Category.The "Properties for Category" window appears.

2. Make any changes to the properties of the category, and click OK.



The changes appear in the resulting window.

The changes to the properties of the category are saved.

Deleting a category

A data steward can delete categories.

Note:There is no undo option after categories are deleted. You must have deleteaccess rights on the Metapedia folder (set in the Central ManagementConsole) to delete categories.

To delete a category:

1. Select the category you want to delete and click Delete Category.A confirmation dialog appears.

2. Click OK.The list of categories in the main Metapedia pane is repopulated withoutthe deleted category.

The selected category is deleted.

Associating a term with categories

To organize terms, a data steward can associate each term with one or morecategories. To associate terms with one or more categories:

1. WithAll Terms selected in the left-hand pane of the "Metapedia" window,check the box for each term you want to associate with a category.

2. Click the Add to Category button.The "Add to Category" screen appears.

3. Check the box for each Category to which you want to associate the termor terms.

4. Click OK.

The terms are now associated with the selected categories.



Importing and exporting terms and categories with Excel

SAP BusinessObjects Metadata Management allows data stewards to performbatch import and export of Metapedia terms and categories using Excelspreadsheets. This capability allows you to capture terms and categories ina spreadsheet before placing them in Metapedia and, conversely, to exportcontent from Metapedia to serve as a backup that you can share, modify,and import back into Metapedia.

You can import terms using a standard import, which requires using thestandard spreadsheet provided with the installation of Metadata Management,or by using a custom import, in which you structure a spreadsheet in anorganized manner of your choice and provide Metadata Management theformat of the data through a series of dialogs.

Note:This implementation supports Excel 97 through Excel 2003 file formats. Itdoes not support the Excel 2007 file format.

Standard importTo use a standard import of terms and categories through Excel, you musthave the standard spreadsheet provided with the installation of this productprepared with the data you want to import into SAP BusinessObjects MetadataManagement Metapedia.

To import terms and categories from Excel using a standard import:

1. In the "Metapedia" screen, click Import from Excel.The "Import from Excel - Select a file" dialog appears.

2. Click Browse.A Windows "Choose file" dialog appears.

3. Browse to and select the Excel file for import. Click Open.The "Import File" field of the "Import from Excel" dialog is populated withthe path and file name of the selected file.

4. Click Next.The "Import from Excel - Select options" dialog gives the option tooverwrite existing terms and categories with the contents of of the Excelfile, if any duplicates exist. If you want to overwrite the existing terms andcategories, check the box. If not, leave the box empty.



5. Click Finish.Metadata Management imports the terms and categories from the Excelfile, and the "Import from Excel - Finished" dialog appears.

6. Click Close.

Metapedia is populated with the terms and categories from the Excel file.

Custom importIf you perform an import from Excel from a spreadsheet other than thestandard spreadsheet provided with the installation of this product, you mustperform a custom import. To perform a custom import:

1. In the "Metapedia" screen, click Import from Excel.The "Import from Excel - Select a file" dialog appears.

2. Click Browse.A Windows "Choose file" dialog appears.

3. Browse to and select the Excel file for import. Click Open.The "Import File" field of the "Import from Excel" dialog is populated withthe path and file name of the selected file.

4. Click Next.The "Import from Excel - Select a sheet for terms" dialog appears.

5. For the "Sheet Containing Term Mapping Data" pull-down list, select thespreadsheet in the file that defines how terms are to be mapped.

6. Fill in the row numbers for the "Header Row", the "Data Begin Row", and"Data End Row".These row numbers define the rows in the spreadsheet that contain thedata to import. SAP BusinessObjects Metadata Management will importdata only from these rows.

7. Click Next.The "Import from Excel - Match columns for terms" dialog appears witheach pull-down list populated with the data found in the rows definedpreviously.

8. Select the appropriate properties from the drop-down lists for "Name","Associated Categories", "Description", "Keywords", "Synonyms", "DataSteward", and "Approved".



The data in these columns is used for the properties of the terms afterthey are imported to SAP BusinessObjects Metadata ManagementMetapedia.

9. Click Next.The "Import from Excel - Select a sheet for categories" dialog appears.

10. If you want to import categories, for the "Sheet Containing Term MappingData" pull-down list, select the spreadsheet in the file that defines howcategories are to be mapped.

11. Fill in the row numbers for the "Header Row", the "Data Begin Row", and"Data End Row".These row numbers define the rows in the spreadsheet that contain thedata to import. Metadata Management will import data only from theserows.

12. If you have no categories in your spreadsheet to import, check "Skipimporting categories".

13. Click Next.The "Import from Excel - Match columns for categories" dialog appearswith each pull-down list populated with the data found in the rows definedpreviously.

14. Select the appropriate properties from the drop-down lists for "Name","Description", "Keywords", and "Data Steward".The data in these columns is used for the properties of the terms afterthey are imported to Metapedia.

15. Click Next.The "Import from Excel - Select options" dialog gives the option tooverwrite existing terms and categories with the contents of of the Excelfile, if any duplicates exist. If you want to overwrite the existing terms andcategories, check the box. If not, leave the box empty.

16. Click Finish.Metadata Management imports the terms and categories from the Excelfile, and the "Import from Excel - Finished" dialog appears.

17. Click Close.

Metapedia is populated with the terms and categories from the Excel file.



Exporting to ExcelA data steward can export SAP BusinessObjects Metadata ManagementMetapedia terms and categories to Excel. To export to Excel:

1. In the "Metapedia" screen, click Export to Excel.The "Export to Excel" dialog appears as SAP BusinessObjects MetadataManagement creates an Excel file containing the Metapedia data. Uponcompletion, the Windows "File Download" dialog appears.

2. Click "Save" to save the fileThe Windows "Save As" dialog appears.

3. Choose a path and name for the file, and click Save.By default, the file name is Metapedia_<timestamp>.xls.

4. Click Close on the "Export to Excel" dialog.

The contents of Metapedia are not copied into an Excel file.

Custom attributes in Metapedia

A data steward can add custom attributes to SAP BusinessObjects MetadataManagement Metapedia terms and categories through the "Custom Attributes"window. Additionally, you can use custom attributes for other SAPBusinessObjects Metadata Management objects within Metapedia.

Custom attributes associated with a term or category are listed in theProperties window for the term or category.

Related Topics• Custom attributes on page 223

Metapedia search

All SAP BusinessObjects Metadata Management Metapedia users canconduct searches for approved terms in the following ways.



DescriptionSearchmethod

The capability of the SAP Metadata Management Explorer tosearch for objects through the "Search" box is available inMetapedia, and searches you perform outside of Metapediaalso contain Metapedia terms and categories in the search re-sults.

Search box

When viewing terms with "All Terms" showing or when viewingterms associated with a category, you can filter the list of termsto show only terms meeting certain criteria. Filtering operatesby matching a string pattern you set on the name, description,or Data Steward of terms.

Filtering terms

When you associate objects with terms, Metapedia conductsa quick search in the background to find related documents. Ifquick search does not find any related documents, you cancustomize the quick search options or choose to use MetadataManagement Explorer Advanced search.

Quick Search

Note:Data stewards have the ability also to conduct searches for terms that arenot approved.

Related Topics• Searching for objects on page 202• Filtering terms on page 243• Object association and quick search on page 244

Filtering terms

A useful method of searching for terms is to filter terms to display only theterms that meet criteria you set. To filter terms:

1. In a view that lists terms, set the "By column" drop-down list to Approved(choose Yes or No), Name, Description, or Data Steward.The "By column" setting determines the column of the "All Terms" paneon which the filter criteria are applied.

2. For the next drop-down list, set the value to Starts with, Ends with, orContains.This setting determines how the string pattern matching is to be applied.



3. For the "Pattern" field, type the string pattern to search for within theproperties of the terms.

4. Click Filter.

The pane now lists only terms that meet the filter criteria. If no terms meetthe criteria, then no terms are listed.

Object association and quick search

After the creation of a business glossary of terms in SAP BusinessObjectsMetadata Management Metapedia, a data steward can make the terms evenmore useful by associating metadata objects with appropriate terms.

One method of object association is to find object to associate to a termusing the Metadata Management Object Tray.

A second method of object association is to search for objects. When youattempt to associate objects with terms, Metapedia conducts a Quick Searchin the background to find related documents. If the Quick Search finds relateddocuments, you can select the documents and automatically associate theterm to them. If Quick Search does not find any suitable related documents,you can customize the search options or choose to use MetadataManagement Explorer Advanced search to find other objects.

Using the Object Tray to associate objects

To associate an object with a term using the Object Tray:

1. In a screen from which the term is available ("All Terms" or the categoryfor which the term is associated), click the name of the term.The "Properties for Term" screen appears.

2. Click Associate from Object Tray.The "Associate from Object tray" screen appears. This screen containsa list of the items currently in the Object Tray.

3. Check the box next to each object that you want to associate with thisterm.

4. Click OK.The "Properties for Term" screen returns to focus.



The term and each of the objects you selected are now associated.

Associating objects with Quick Search

To associate an object with a term using Quick Search:

1. In a screen from which the term is available ("All Terms" or the categoryfor which the term is associated), click the name of the term.The "Properties for Term" screen appears.

2. Click Associate Objects.SAP BusinessObjects Metadata Management performs a Quick Searchfor objects that could be associated with the term. The "Associate Objects"screen appears. This screen contains a list of the items found by QuickSearch.

3. If Quick Search found objects to associate with the term, check the boxnext to each object that you want to associate with this term.

4. If Quick Search was unable to find any objects, you can refine the QuickSearch options click Search, or you can perform an Advanced Search.

5. Click OK.The "Properties for Term" screen returns to focus.

The term and each of the objects you selected are now associated.

Exporting relational objectsSAP BusinessObjects Metadata Management provides you with the abilityto export relational objects from a Data Integration, Relational Database, orData Modeling source in the Metadata Management repository to one of thefollowing files:

• A general-purpose Common Warehouse Modeling (CWM) XML file thatincludes all relational object types. You can select the following objectsto export to a general-purpose CWM XML file:

• Database• Catalog• Schema• Table• View


7SAP BusinessObjects Metadata Management ExplorerExporting relational objects

• Procedure• A CWM XML file that contains a subset of the relational objects that you

import into BusinessObjects Enterprise to create a universe. You canselect the following objects to export to a CWM XML file that will be usedto create a universe:

• Database - Metadata Management exports a relational database asa catalog.

• Catalog - You can only select one catalog to create a universe. All ofthe selected schemas, tables, and views must belong to the samecatalog.

• Schema

• Table

• View - Metadata Management exports a view as a table when youexport to a universe.

Note:In an RDBMS system, a Server Instance corresponds to a Database and aDatabase corresponds to a Catalog.

The following table lists the relational objects and metadata that MetadataManagement exports for each object.

Exported metadataRelational object type

Attributes such as nameCatalog

Attributes such as nameSchema

Attributes such as name

If Same As relationship exists:• Annotation

• Business name

• Business description

Table


SAP BusinessObjects Metadata Management Explorer7 Exporting relational objects

Exported metadataRelational object type

Attributes such as name


• Business name


View

Attributes such as name, data type, length


• Business name


If column is a primary key:

• Constraint reference based on primary keyorder in columns

If column is a foreign key:

• If the target table is included in the export andthe target columns are part of the primary key,Metadata Management exports the foreign key

If lineage information exists and export is foruniverse creation:

• Path from server instance, database, schema,table

Column

Attributes such as name, data type and parametertype (in, out, inout, return)Procedure parameter



Note:When you export a parent object, Metadata Management also exports all ofits child objects. For example, if you export a table, Metadata Managementexports the table and all of the columns it contains. Similarly, if you export aschema, Metadata Management exports the schema and all of the tables(and their columns) contained within the schema.


• Selecting objects to export on page 248

• Exporting objects to a general-purpose CWM XML file on page 249

• Exporting objects to create a universe on page 253

Selecting objects to export

To select objects to export, you add them to the Object Tray.

To add relational objects to the Object Tray for exporting:

1. Navigate to the first object that you want to export.

For example, suppose you want to export the DBO schema, a fact tableand it's dimension tables in a data warehouse. Navigate to DBO schemain the relational database Forenza DW.

Note:You cannot export objects collected by the MIMB Metadata Integrator.

2. Click Add to Object Tray to the right of the schema name.

An Object Tray icon with a check mark appears next to the schema name.

3. Navigate to Fact_Sales_Order table and click Add to Object Tray to theright of the table name.

An Object Tray icon with a check mark appears next to the table name.

4. In the navigation path at the top of the page, click the object type to returnto the list of objects.

For the sample navigation path, click Tables to return to the list of tables.

Directory > Relational Databases(Forenza DW) > Schemas (dbo) > Tables(FACT_SALES_ORDER)



5. Select the next object to add to this relationship.

In this example, select the DIM_CUSTOMER table.

6. Repeat steps 3 through 5 to add each table that you want in therelationship to the Object Tray.

In this example, add the DIM_EMPLOYEE, DIM_PRODUCT, andDIM_TIME tables.

When you return to the list of Tables, notice that the Object Tray icon witha check mark appears next to each table name that you added to theObject Tray.

Exporting objects to a general-purpose CWM XMLfile

To export objects to a general-purpose CWM XML file:

1. After Selecting objects to export on page 248, clickObject Tray (number)in the upper right corner of the Explorer page.

The number in parenthesis indicates the number of objects in the ObjectTray. In the example in the previous procedure, you click Object Tray (6).

2. On the Object Tray, select the objects that you want to export.a. To export a subset of objects in the Object Tray, select the check box

in front of the each object that you want.b. If you want to export a schema and all of the tables (and their columns)

contained in the schema, select the check box in front of schemaname.

c. If you want all of the objects of an object type, select the check boxfor the object type.

For example to select all table objects, select the check box in frontof Tables, as the following window shows.



3

5

3. Click Export to CWM.4. On the Export to CWM window, in the Export Name text box, type a

meaningful name for the CWM XML file to which you will export therelational objects.

5. If you selected tables that belong to multiple source systems for which aSame As relationship is available, the Define search priority forbusiness name and description area is enabled.

When SAP BusinessObjects Metadata Management exports an object,it also exports the business name and description for the object to theCWM XML file. By default, Metadata Management exports these businessvalues from the source system from which you selected the objects. Youmight want to change the source systems in the Define search priorityfor business name and description area for situations such as thefollowing:

• The business name and description do not exist in the source systemfrom which you export.



For example, suppose that the business name and description do notexist in Forenza DW for these tables, but descriptions for them existin the DIREPO source system.

To use the descriptions from the DIREPO source system, selectDIREPO from the Available sources list box and then use the rightarrow to move DIREPO to the Search priority box.

Although DIREPO appears second in the priority list, MetadataManagement exports the business name and description from itbecause these values do not exist in the first source system.

• The business name and description exist in the source system fromwhich you exports, but you want to use the business values from adifferent source system.

For example, you might want to export the business name anddescription for the tables in the DIREPO source system instead of thevalues in Forenza DW.

To change the priority order, move all sources from the Search prioritybox to the Available sources list box. Then move each source to theSearch priority box in the order that you want. In this example, moveDIREPO first, then Forenza DW.

Note:The original source from which you selected the objects must appear inthe Search priority box.



6. Click OK. The Export List window displays the following information:


Specifies the export name.Name

Contains a check mark if this exportis for universe creation.For universe creation

Indicates the status of the export.Possible values are:• Completed

• Failed

Status




Indicates the date and time that theexport file was created.Created

Contains error messages if any er-rors occur during the export. If noerror occurred, this column doesnot appear.

Error Message

Indicates actions you can performon the CWM XML file. Possiblevalues are:• Download - You can either open

the file to view it or save it to adirectory.

• Delete

Actions

7. Click Refresh to update the status.8. After the export completes, click the action Download to view the CWM

XML file or save it to a directory.9. If you viewed the CWM XML file, click the Web browser Back arrow icon

to return to the Metadata Management Explorer.

Exporting objects to create a universe

When you export objects for universe creation, you can import the CWMXML through the SAP BusinessObjects Enterprise Designer to create orupdate an existing universe.

To create a universe from the CWM XML file that you export, the objectsyou export must meet the following universe creation criteria:

• Only catalog, schema, table, or view objects were selected in the objecttray.



• Only one catalog is selected.

• All of the selected schema, table and view objects belong to the samecatalog.

Including column lineage information

When you export to create a universe, you can specify whether or not toinclude lineage information for the column from which the exported columnobtains its data.

You can choose one of the following three column lineage options:

• Do not include lineage information - Choose this option if you do notwant to include the column lineage information. This option is the default.

• Include lineage information from the current sources only - Choosethis option if you want the exported metadata to include where the columndata comes from within the same source system.

For example, the following diagram shows the lineage for tableTARGET_REASON across two sources. The current source system isForenza DW. If you select Include lineage information from the currentsources only when you export table TARGET_REASON, you exportcolumn lineage information from table FACT_SALES_ORDER (circledin the following diagram).

.• Include lineage information from all of the original sources - Choose

this option if you want the exported metadata to include where the columndata comes from in the original source system.

In the TARGET_REASON example, the original source system is DIREPO.If you select Include lineage information from all of the original sources,you export column lineage information from tables EMPLOYEES,ORDERS, and PRODUCTS (circled in the following diagram).



Note:SAP BusinessObjects Metadata Management does not include theintermediate columns in tables DIM_EMPLOYEE and ORDER DETAILSin the exported column lineage information.

.

Exporting to create a universe

To export objects to a CWM XML file to create a universe:

1. After Selecting objects to export on page 248, clickObject Tray (number)in the upper right corner of the Explorer page.

The number in parenthesis indicates the number of objects in the ObjectTray. In the example in the previous procedure, click Object Tray (6).

2. On the Object Tray, select the objects that you want to export.a. To export a subset of objects in the Object Tray, select the check box

in front of the each object that you want.b. If you want to export a schema and all of the tables (and their columns)

contained in the schema, select the check box in front of schemaname.

c. If you want all of the objects of an object type, select the check boxfor the object type.

For example to select all table objects, click the check box in front ofTables, as the following window shows.



3. Click Export to Universe.4. On the Export to Universe window, in the Export Name text box, type a

meaningful name for the CWM XML file to which you will export therelational objects.

For example, type Sales Universe.



5. Select one of the following lineage options. For examples of these options,see Including column lineage information on page 254.a. If you do not want to include the column lineage information, select

Do not include lineage information. This option is selected bydefault.

b. If you want to include column lineage information for tables within thesame source system, select Include lineage information from thecurrent sources only.

c. If you want to include the column lineage information from the originalsource system from which the data comes, select Include lineageinformation from all of the original sources.

6. Click OK. The Export List window displays the following information:




Specifies the export name.Name

Contains a check mark if this export is foruniverse creation.For universe creation

Indicates the status of the export. Possiblevalues are:• Completed

• Failed

Status

Indicates the date and time that the exportfile was created.Created

Contains error messages if any errors oc-cur during the export. If no error occurred,this column does not appear.

Error Message

Indicates actions you can perform on theCWM XML file. Possible values are:• Download - You can either open the file

to view it or save it to a directory.

• Delete

Actions

7. Click Refresh to update the status.



8. After the export completes, click the action Download to save the CWMXML file in a directory from which you can import it into the SAPBusinessObjects Enterprise Designer to create or update an existinguniverse.

User-defined relationships betweenobjects

The Metadata Integrators collect the most common relationships betweenobjects and the SAP BusinessObjects Metadata Explorer displays them onthe relationship analysis tabs Same As, Impact, and Lineage. However, youmight want to establish additional relationships for situations such as thefollowing:

• To group together objects that share a common business value or someother common factor. For example, you might want to group togetherreports that all pertain to a certain area, such as Sales; or you might wantto group together tables in a star schema.

If you establish and define a new relationship between objects, it appearson the Related To tab.

• To establish relationships for an object that SAP BusinessObjectsMetadata Management has not detected, such as tables for a storedprocedure.

If you establish an already defined relationship, it will appear in thecorresponding relationship analysis tab of the Explorer page for the object.


7SAP BusinessObjects Metadata Management ExplorerUser-defined relationships between objects

Establishing user-defined relationships betweenobjects

You add objects to the Object Tray and then go to the Object Tray to definea relationship.

1. Navigate to the first object for which you want to define a relationship.

For example, navigate to Fact_Sales_Order table to create a star schemarelationship with dimension tables in the DIREPO source.

2. Click Add to Object Tray to the right of the table name.An Object Tray icon with a check mark appears next to the table name.

3. In the navigation path at the top of the page, click Tables to return to thelist of tables.Directory >Data Integration(DIREPO)>Tables(FACT_SALES_ORDER)

4. Select the next table to add to this relationship.

In this example, select the DIM_CUSTOMER table.

5. Repeat steps 2 through 4 to add each table that you want in therelationship to the Object Tray.

In this example, add the DIM_EMPLOYEE, DIM_PRODUCT, andDIM_TIME tables.

When you return to the list of Tables, notice that the Object Tray icon witha check mark appears next to each table name that you added to theObject Tray.


SAP BusinessObjects Metadata Management Explorer7 User-defined relationships between objects

6. Click Object Tray (5) in the upper right corner of the Explorer page. Thenumber in parenthesis indicates the number of objects in the Object Tray.

7. On the Object Tray, click the check box in front of the each object forwhich you want to define a relationship. If you want all of the objects, clickthe check box at the top.

8. Click Establish Relationship.9. On the Establish Relationship window under Relationship Type, choose

one of the following relationships:• Add objects to a defined relationship

If you choose this default option, select one of the following definedrelationships from the drop-down list:

• Impact (User defined)• Same As (User defined)• Related To

• Add objects to a new relationship



If you choose this option, perform the following steps:

a. In the Relationship Name text box, type in a meaningful name.

For example, type Star Schema.

b. In the Relationship Description text box, type in a description foryour new relationship.

10. Click OK.

If you select an Impact, Lineage, or define a new relationship, the nextwindow displays the source objects and related objects in the relationship.

For this example, you want the fact table to be the source object and thedimension tables to be the related objects.


SAP BusinessObjects Metadata Management Explorer7 User-defined relationships between objects

11. If the objects are not listed correctly as a source object or as a relatedobject, select the object and click the arrow to move it to the correct box.

In the example above, the "Source Objects" box correctly shows tableFACT_SALES_ORDER, and the "Related Objects" box correctly showstables DIM_CUSTOMER, DIM_EMPLOYEE, DIM_PRODUCT, andDIM_TIME.

12. Click OK, click OK on the message that indicates the relationship wassuccessfully established, and click Return to Directory.

13. Click FACT_SALES_ORDER on the tables list to display the relationshipsfor this object.

14. Click the "Related To" tab to view the relationship that you defined.When you move the pointer over the relationship attribute icon, the pop-upwindow displays the name and description of the user-defined relationship.



Example:

Removing a user-defined relationship

1. Navigate to the object for which you want to delete a user-definedrelationship.

2. Go to the User Defined tab.3. Select the check box in front of the related object.4. Click Remove Relationship and click OK on the prompt that asks if you

want to remove the selected relationship.

Changing preferences for relationshipsTo ensure that SAP BusinessObjects Metadata Management recognizesthe same object in different source systems, you must set the appropriatepreferences.

This section describes the following topics which you can do from the"Preferences" page of the SAP BusinessObjects Metadata ManagementExplorer:

• Recognizing the same object in multiple source systems on page 265• Setting impact and lineage preferences on page 266• Setting object equivalency rules for Same As relationships on page 267• To set Object Equivalency Rules for Same As relationships on page 267


SAP BusinessObjects Metadata Management Explorer7 Changing preferences for relationships

Recognizing the same object in multiple sourcesystems

An object can exist in two or more metadata integrator sources systems.The source systems refer to the same physical object. For example, aCustomer table can exist in different metadata integrator sources, such asa relational database management system and an SAP BusinessObjectsEnterprise system. The different source systems qualify a table name withthe database name, catalog name, and schema name as the followingexamples show:

• In SQL Server, a fully-qualified table name has the following format:

databasehostname.catalogname.schemaname.tablename

For example,

server-01.ForenzaDW.dbo.customer

• In an SAP BusinessObjects Enterprise system, a fully-qualified tablename has the following format:

CMSservername.catalogname.schemaname.tablename

For example:

CMS-server1.SalesDW.DBO.customer

• In SAP BusinessObjects Data Federator, a fully-qualified table name hasthe following format:

databasename.catalogname.schemaname.tablename

For example:

server-02.ForenzaDW.SQLServer.customer

• In Oracle, a fully-qualified table name has the following format:

Oraclehost.Oracleinstance.schemaname.tablename


7SAP BusinessObjects Metadata Management ExplorerChanging preferences for relationships

For example:

server-03.ForenzaDW.scott.customer

You might need to set Impact and Lineage Preferences and ObjectEquivalency Rules to ensure that SAP BusinessObjects MetadataManagement treats the table as the same physical object in the Same Asrelationship, Impact and Lineage analysis tabs.

Setting impact and lineage preferences

You might need to set options in Impact and Lineage Preferences to ensurethat SAP BusinessObjects Metadata Management displays the correct Impactand Lineage analysis between metadata integrator source systems. Youwould specify these preferences once, when you first setup your sourcesystems.

To set Impact and Lineage Preferences, you must have the Edit or Createaccess level on the Metadata Management application.

1. Click Preferences in the upper right corner of the Metadata ManagementExplorer to display the Preferences page. The "Preferences" screenappears.

2. Under Impact and Lineage Preferences, choose the following options.a. What is the highest level used to determine if two relational

objects are the same?

The "highest level" refers to the fully-qualified name of an object. Fordetails, see Recognizing the same object in multiple source systemson page 265.

• The default level is schema, which means that MetadataManagement recognizes that tables are the same if the theirschemas have been defined to be equivalent. For example, thefollowing fully-qualified names refer to the same Customer table:

server-01.ForenzaDW.sa.customer

CMS-server1.SalesDW.DBO.customer



• Select table if you want a lower level. You might want to use thetable level if you want Metadata Management to recognize that atable is the same even though it has two different schema names.

• Select catalogor database if you want a higher level.

b. Should the comparison of two objects be case sensitive?

The default is Yes.

Select No if you do not want to consider the case to determine if twoobjects are the same.

3. If you changed the default values for the Impact and LineagePreferences, click Save.

4. If you use impact and lineage reports on the Reports tab, you mustrecompute the contents of the lineage staging table to incorporate yourchanged values for the Impact and Lineage Preferences. You can setup a similar schedule to compute the lineage staging table at regularintervals. For more information, see Computing and storing lineageinformation for reporting on page 179.

Setting object equivalency rules for Same Asrelationships

SAP BusinessObjects Metadata Management uses the values in Impactand Lineage Preferences with Object Equivalency Rules to determinethat an object with two different names is the same physical object. Forexample in SQL Server, user dbo is the same as user sa, and the highestlevel option in Impact and Lineage Preferences is set to schema. Therefore,dbo.TableA is the same as sa.TableA in a given catalog. MetadataManagement has already defined this object equivalency rule for you.

If you have other objects that have different high-level qualifiers, use theObject Equivalency Rules to tell Metadata Management that an object isthe same. You would specify these rules once, when you first setup yoursource systems.

To set Object Equivalency Rules for Same As relationships

1. Choose the Object Equivalency Rules options.



The Left Side represents the objects that you want to specify are thesame as the objects on the Right Side. Specify the following options foreach side:

• Context - Select the integrator source name from the drop-down list.The default is All which means all integrator sources configured onyour Metadata Management application.

2. After you select an integrator source name in Context, you can click theLookup Object icon next to the following options to choose a name foreach:• Database - The default is an asterisk (*) to indicate that the database

name on the Left Side is the same as on the Right Side.• Catalog - The default is an asterisk (*) to indicate that the catalog

name on the Left Side is the same as on the Right Side.• Schema - Enter the high-level qualifier of the tables for which you

want to define an equivalency rule.

For example, to define a rule for My DF source to indicate that the SAPBusinessObjects Data Federator datasource ForenzaDW should be thesame as the database ForenzaDW in your relational database system:

a. In the "Object Equivalency Rules" area of the "Preferences" page,click Add.

b. Select the check box for the new row under "Object EquivalencyRules".

c. For the Left Side Context, select the integrator source name My DFSource from the drop-down list.

d. Keep the default asterisk (*) inDatabase and Catalog.e. Click the Lookup Objects icon next to Schema and click Select next

to the database name ForenzaDW.



f. For the Right Side Context, select the integrator source name for yourrelational database system.

g. For the Right Side Database and Catalog, keep the default asterisk(*).

h. For the Right Side Schema, click the Lookup Objects icon and clickSelect next to the schema name dbo.

i. Click Save.

3. If you use impact and lineage reports on the "Reports" tab, you mustrecompute the contents of the lineage staging table to incorporate yourchanges to Object Equivalency Rules. For more information, seeComputing and storing lineage information for reporting on page 179.





SAP BusinessObjectsEnterprise Metadata

8

Exploring SAP BusinessObjectsEnterprise metadata

SAP BusinessObjects Metadata Management stores metadata about objectsin selected source systems. The software's Explorer organizes the metadatainto a directory structure so that users can navigate and explore the metadataobjects in an easy to understand way.

The directory structure in software's Explorer contains the followingcategories:

• Business Intelligence which contains sources such as SAPBusinessObjects Enterprise and SAP NetWeaver Business Warehouse.

• Data Integration which contains source systems such as SAPBusinessObjects Data Federator, BusinessObjects Data Integrator, andSAP BusinessObjects Data Services.

• Relational Databases which contains sources such as DB2, MySQL,Oracle, SQL Server, Java Database Connectivity (JDBC), or aBusinessObjects Universe connection.

• Data Modeling which contains sources such as CWM (CommonWarehouse Modeling)

The software's Explorer uses the following terms:

• Category - A category is a type of source system for which MetadataIntegrators collect metadata. The above list of categories show examplesof source systems for each category. When your administrator configuresa source system for Metadata Integrator, the source system displaysunder the appropriate category on the The software's Explorer.

• Instance - An instance is an occurrence of a Metadata Integrator ormetadata object. For example, an SAP BusinessObjects Enterprise source(such as MySales) is an instance of a Metadata Integrator in the BusinessIntelligence category. An example of a type of metadata object is a report,and an instance of a report is Product Sales by Customer.rpt.

• Metadata Integrator - A Metadata Integrator is a program that extractsmetadata from a source system and loads it into the MetadataManagement repository. Your administrator installs zero, one, or moreMetadata Integrators for each category and might configure multiplesource systems for each Metadata Integrator. For configuration


SAP BusinessObjects Enterprise Metadata8 Exploring SAP BusinessObjects Enterprise metadata

information, see Configuring sources for SAP BusinessObjects EnterpriseMetadata Integrator on page 134.

• Metadata object - A unit of information that a Metadata Integrator createsfrom an object in a source system. For example, an SAP BusinessObjectsEnterprise source contains objects such as universes, universe objects,and reports which the Metadata Integrator loads into the metadatamanagement repository as metadata objects Universe, Universe Object,and Report.

Related Topics• Navigating SAP BusinessObjects Enterprise metadata on page 278

SAPBusinessObjectsEnterprisemetadataobjects

An SAP BusinessObjects Enterprise source can contain different objecttypes, as the following table describes. The SAP BusinessObjects MetadataManagement Explorer shows the following object types if they exist in theSAP BusinessObjects Enterprise source.

Associated objectsDescriptionObject type

Universe classes, which cancontain:• Universe objects

• Dimensions• Details• Measures

• Universe filters

A universe is an object that contains the follow-ing:• Connection parameters for one or more

database middleware• Objects that map to either of the following

• Actual relational structures (such ascolumns, tables, and database func-tions) in the database

• Actual OLAP structures (DataStore ob-jects, InfoObjects, InfoCubes, andQueries)

Objects are grouped into classes.• A schema of the tables and joins in the

database (objects are built from thedatabase structures that you include inyour schema)

Universes


8SAP BusinessObjects Enterprise MetadataSAP BusinessObjects Enterprise metadata objects


Columns

Universe objects• Dimensions• Details• Measures

A "report" is a document that obtains datafrom universe objects and tables, format thedata, and deliver it inside and outside theorganization.

Reports can be any of the following types:• Crystal Reports

Crystal Reports can also obtain theirdata from DataStore objects, InfoObjects,InfoCubes, and Queries.

• Web Intelligence documents• Desktop Intelligence documents.

Reports

• Universes• Personal and Public fold-

ers• Documents (Desktop and

Web Intelligence)• Reports

A CMS Folder organizes universes, personaland public folders, documents, and reports bydepartment or area. The administrator for SAPBusinessObjects Enterprise can set objectrights and limits at the folder level rather thansetting them for each report or object.

CMS Folders

Databases• Schemas, which can con-

tain:• Tables

• Columns

• Views• Synonyms

A "server instance" is a database server towhich SAP BusinessObjects Enterprise con-nects to obtain the data that the reports formatand deliver.

Server In-stances

• Groups to which each userbelongs

A "user" is an administrator or end user inan SAP BusinessObjects Enterprise system.Users


SAP BusinessObjects Enterprise Metadata8 SAP BusinessObjects Enterprise metadata objects


• Users that belong to eachgroup

A "group " is a group of users in an SAPBusinessObjects Enterprise system. Theadministrator for SAP BusinessObjects En-terprise can set privileges for universe andreports at the group level rather than settingthem for each user.

Groups

An "SAP BW System" is an SAP NetWeaverBW server to which SAP BusinessObjectsEnterprise connects to obtain the data that thereports format and deliver.

SAP BW Sys-tem

Related Topics• SAP BusinessObjects Enterprise object relationships on page 275• SAP NetWeaver BW objects as sources on page 277• Exploring the universe metadata object on page 279• SAP NetWeaver BW objects used by a Crystal Report on page 297• Universe lineage from InfoCube on page 300• Crystal Report lineage from DataStore Object on page 301• Exploring the report metadata object on page 281• Exploring Users on page 284• Exploring Groups on page 284

SAPBusinessObjects Enterprise object relationships

The following diagram shows the relationships between the object types inSAP BusinessObjects Enterprise and their relationships to the databases inthe Server Instance that provide the data for the reports. The diagram shows:• Which object types can be associated with (contained within) other object

types• Which objects impact (provides data to) other objects, either directly or

with a mapping expression



Related Topics• SAP BusinessObjects Enterprise metadata objects on page 273


SAP BusinessObjects Enterprise Metadata8 SAP BusinessObjects Enterprise metadata objects

SAP NetWeaver BW objects as sources

The following diagram shows the relationships between the object types inSAP BusinessObjects Enterprise and their relationships to the object typesin the SAP NetWeaver BW that provide the data for the reports. The diagramshows these relationships:• Which object types are contained within other object types. Examples

include an InfoCube contain InfoObjects and a CMS Folder containsreports.

• Which objects impact (provides data to) other objects, either directly orwith a mapping expression. Examples include InfoObjects provide datato Universe objects, and the InfoObjects provide data to the reports inthe CMS folders.

For more details, see the chapter How SAP BW objects are mapped andused in a universe in the Universe Designer document Using SAP BW inUniverse Designer.



Related Topics• SAP BusinessObjects Enterprise object relationships on page 275

Navigating SAP BusinessObjectsEnterprise metadata

When you login to the SAP BusinessObjects Metadata Management Explorer,the Directory home page displays. To login, see Accessing MetadataManagement for administrative tasks on page 119.


SAP BusinessObjects Enterprise Metadata8 Navigating SAP BusinessObjects Enterprise metadata

The Directory home page shows each configured integrator source, groupedby the Metadata Integrator category in which it belongs.

The Business Intelligence category can include integrator sources such asSAP BusinessObjects Enterprise, SAP NetWeaver Business Warehouse,and other Business Intelligence sources. The sample Directory home pageshows the Business Intelligence category with a configured SAPBusinessObjects Enterprise repository source, MySales.

Under each source name are the first three metadata object types that itcontains, and the number in parenthesis indicate the number of instancesfor that type. The sample shows the My Sales source contains metadataobject types Universes, Reports, and CMS Folders.

Exploring the universe metadata object

An SAP BusinessObjects Enterprise source page shows a Universesmetadata object type with the first three instance names. Click Universesor Show All... to display all universe names.

The Universes metadata object page displays the following information:• The universe names that this SAP BusinessObjects Enterprise source

contains, listed in alphabetic order.• Under each universe name:

• Description• File name• Path


8SAP BusinessObjects Enterprise MetadataNavigating SAP BusinessObjects Enterprise metadata

• Universes Classes link with a number in parenthesis that indicatesthe number of universe classes

Exploring an instance of a universe

On the Universes metadata object page, click a universe name to displaythe universe instance page.

The universe instance page opens onto the Overview tab that displays:

• File name• Path• Connection Name• Author• Modified By• Cluster• Join Clause• Universe Classes section that lists:

• Name of each universe class associated with this universe• Under each universe class name, the associated metadata object

types (universe objects and universe filters) that it contains and anumber in parenthesis that indicates the number of instances for thatassociated metadata object.

To display details of the associated metadata objects, click either the nameof the universe class or the metadata object type under the name.

The Universe Objects section lists a line for each dimension, detail, andmeasure in this class with the following information:• Name• Description• Data type• Mapping expression (indicates the schema name, table name, and column

name on which the universe object is based)• Where clause

The following example displays the universe objects that universe class FactSales Order contains.



Click the name of a universe object to display more information about it. Theuniverse object page shows tabs Same As, Related To, Impact, Lineage,and User Defined where you can analyze relationships that universe objectTotal Order Value might have with other objects.

Related Topics• Viewing relationships for universe objects and reports on page 289• Navigating metadata on page 201

Exploring the report metadata object

An SAP BusinessObjects Enterprise source page displays a Reportsmetadata object with the first three report names.

Click Reports or Show All... to display all report names, as the followingexample shows for the MySales source.



The Reports metadata object page displays:

• The report names that the BusinessObjects Enterprise source contains,listed in alphabetic order.

• Under each report name• A short description, if it exists• Report type - This value can be one of the following:

• Crystal Report• Desktop Intelligence Document• Web Intelligence Document

• Owner - User name of the owner of the report or document• Date and time when the report was last modified• Path of the report within BusinessObjects Enterprise

For example, the path of report Product Sales by Customer.rpt is

Report Samples/MM Demo Reports

which is the name of the CMS folder (Report Samples) and subfolder(MM Demo Reports) that contains the report.

• The associated metadata object types that a report contains and anumber in parenthesis that indicates the number of instances for thatassociated metadata object. Each report type contains the followingassociated metadata objects:



Associated metadata objectsReport type

If the Crystal Report is directlyfrom tables, SAP BusinessObjectsMetadata Management displaysColumns

If the Crystal Report is from auniverse, Metadata Managementdisplays the following objects:• Universe Filters• Universe Objects• Columns -- Includes columns

that are not used directly in thefilters and universe objectsused in the report. Might alsoinclude columns when multipleobjects for the report have thesame name and MetadataManagement cannot uniquelyidentify the object.

Crystal Reports

Universe Filters

Universe Objects

Columns -- Includes columns thatare not used directly in the filtersand universe objects used in thedocument.

Desktop Intelligence Documents

Universe Filters

Universe Objects

Columns -- Includes columns thatare not used directly in the filtersand universe objects used in thedocument.

Web Intelligence documents



Exploring Users

An SAP BusinessObjects Enterprise source page shows the ApplicationUsers metadata object and the first three users. Click Application Usersor Show All... to display all users in the BusinessObjects Enterprise system.

The Application Users metadata object page displays:

• The user names that this BusinessObjects Enterprise source contains,listed in alphabetic order.

You can click each user name to display privileges.

• Under each user name, the following information displays:• Description• Full name• Groups (n), where n is the number of groups to which this user

belongs

You can click Groups to display the group names.

Related Topics• Finding user privileges to reports and universes on page 303• Exploring Groups on page 284

Exploring Groups

An SAP BusinessObjects Enterprise source page shows aGroupsmetadataobject and the first three group names. ClickGroups or ShowAll... to displayall group names in the BusinessObjects Enterprise system.

The Groups metadata object page displays:

• The group names that this BusinessObjects Enterprise source contains,listed in alphabetic order.

• Under each group name, the Users object type with a number inparenthesis that indicates the number of users that this group contains.

Click the group name to display the following details for each group:

• The Overview tab shows for each user in the group:



Group name•• Annotation, if any• Description of the group• Custom attribute, if any• Groups that belong to this group, if any• Users that belong to the group

• The Privileges tab shows the reports and universes that this group canaccess.

Related Topics• Finding group privileges to reports and universes on page 305• Exploring Users on page 284

Exploring personal folders

Personal folders can hold any reports that you specify. You can copy reportsfrom public folders and place them into your personal folder. You can alsoadd new reports. By default the configuration options do not include collectingpersonal folder metadata. You must configure and run personal foldercollection through the SAP BusinessObjects Enterprise Central ManagementConsole.

If you have subfolders within your personal folder and run a collection on themain folder, all subfolders and their objects are also included in the collection.If you have shortcuts to reports outside of your personal folder, those objectsare not included in the collection.



Related Topics• View personal folder collection results on page 286

View personal folder collection results

After you have successfully run the SAP BusinessObjects EnterpriseMetadata Integrator, you can view the collected metadata such as lineagethrough the SAP BusinessObjects Metadata Management Explorer.

1. ChooseStart >Programs >BusinessObjects XI 3.1 >BusinessObjectsMetadata Management > Metadata Management Explorer.

2. Under Business Intelligence, choose the integrator that ran your collection,and then click CMS Folders.

3. Under CMS Folders, click Show All.4. Click User Folders and then click on your personal folder name.

When you click your folder name, you will see a count of all the differentobject types in your folder. The number includes subfolders and reports.For example, Reports(5), CMS Folders(2) means that there are 5 reportsand 2 subfolders.

5. Select an object type to see a list of those kinds of objects.6. Open the report or document.

To view relationships about the report or document, click the appropriatetabs.

Related Topics• Navigating metadata on page 201• Exploring personal folders on page 285

Viewing relationships for universeobjects and reports

With SAP BusinessObjects Metadata Management Explorer you can viewrelationships between universe objects, reports, and documents that youcreate with SAP BusinessObjects Enterprise. You can also reviewrelationships between universe objects and tables in ETL systems such asSAP BusinessObjects Data Services.


SAP BusinessObjects Enterprise Metadata8 Viewing relationships for universe objects and reports

A Metadata Integrator obtains the following relationships from an SAPBusinessObjects Enterprise source, and you can view them on the tabs ofthe Metadata Management Explorer page for each universe object and report.

Relationships that can appear on this tabMetadata Explorer tab

• Tables and columns that are the same be-tween two systems, such as between a rela-tional database and a BusinessObjects Enter-prise system.

• You can also define this relationship for ametadata object that has a different name inanother metadata integrator source system(for example, a table name might have a differ-ent high-level qualifier). For the procedure, seeEstablishing user-defined relationships be-tween objects on page 260.

If no Same As relationship exists, a messagesindicates so.

Same As

• You can define your own relationships. Forexample, you might want to group togetherthat pertain to a specific business area, suchas Billing. For the procedure, see Establishinguser-defined relationships between objects onpage 260.

If no Related To relationship exists, a mes-sages indicates so.

Related To


8SAP BusinessObjects Enterprise MetadataViewing relationships for universe objects and reports


Shows a graphic of other metadata objects thatare affected by data within this metadata object.For example, a universe object can impact multiplereports. For more information, see Impact analysisfor a universe object on page 291.

If the metadata object is a universe or report, theImpact graphic shows the number of Users andthe number of Groups that have access to thespecific universe or report. Click the correspondingUsers and Groups node to view the names andpermissions. For more information, see Impactanalysis for users and groups on page 306.

Impact

Shows a graphic of the sources from which thismetadata object obtains its data. For example, areport column obtains its data from a universeobject which, in turn, obtains its data from a col-umn in a table in a relational database. For moreinformation, see• Lineage analysis for universe object on

page 291• Lineage analysis for a report on page 294

Lineage

If you establish your own relationship, you canview the following information for it:• Name of the related metadata object

• Name of the relationship

• Path of the related metadata object in theMetadata Explorer.

You can delete a user defined relationship fromthis tab.

If no User Defined relationship exists, a mes-sages indicates so.

User Defined



Viewing relationships for universe objects andreports

With SAP BusinessObjects Metadata Management Explorer you can viewrelationships between universe objects, reports, and documents that youcreate with SAP BusinessObjects Enterprise. You can also reviewrelationships between universe objects and tables in ETL systems such asSAP BusinessObjects Data Services.

A Metadata Integrator obtains the following relationships from an SAPBusinessObjects Enterprise source, and you can view them on the tabs ofthe Metadata Management Explorer page for each universe object and report.


• Tables and columns that are the same be-tween two systems, such as between a rela-tional database and a BusinessObjects Enter-prise system.

• You can also define this relationship for ametadata object that has a different name inanother metadata integrator source system(for example, a table name might have a differ-ent high-level qualifier). For the procedure, seeEstablishing user-defined relationships be-tween objects on page 260.

If no Same As relationship exists, a messagesindicates so.

Same As

• You can define your own relationships. Forexample, you might want to group togetherthat pertain to a specific business area, suchas Billing. For the procedure, see Establishinguser-defined relationships between objects onpage 260.

If no Related To relationship exists, a mes-sages indicates so.

Related To




Shows a graphic of other metadata objects thatare affected by data within this metadata object.For example, a universe object can impact multiplereports. For more information, see Impact analysisfor a universe object on page 291.

If the metadata object is a universe or report, theImpact graphic shows the number of Users andthe number of Groups that have access to thespecific universe or report. Click the correspondingUsers and Groups node to view the names andpermissions. For more information, see Impactanalysis for users and groups on page 306.

Impact

Shows a graphic of the sources from which thismetadata object obtains its data. For example, areport column obtains its data from a universeobject which, in turn, obtains its data from a col-umn in a table in a relational database. For moreinformation, see• Lineage analysis for universe object on

page 291• Lineage analysis for a report on page 294

Lineage

If you establish your own relationship, you canview the following information for it:• Name of the related metadata object

• Name of the relationship

• Path of the related metadata object in theMetadata Explorer.

You can delete a user defined relationship fromthis tab.

If no User Defined relationship exists, a mes-sages indicates so.

User Defined



Impact analysis for a universe object

This section shows what objects are affected by the data within an object.Section Lineage analysis for universe object on page 291 describes the lineage(source of data) for universe object Total Order Value.

Click the Impact tab to obtain the following impact analysis diagram whichshows• Three reports (SalesByYear, Product Sales by Customer_unv.rpt and

Product_Sales_By_Customer_webi) are affected by the data in the TotalOrder Value universe object.

• Two users and two groups have permissions to access each report. Fordetails about the users and groups information, see Impact analysis forusers and groups on page 306.

Lineage analysis for universe object

Lineage analysis allows you to trace back from a universe object to thesource. Use the Lineage tab to view the sources for an object.

The following sample Lineage tab displays the source for the Total OrderValue universe object. You can use the search function that sectionSearchingfor objects on page 202 describes to find the Total Order Value universeobject.



The Lineage tab shows that:

• The Total Order Value object uses data from the columnTOTAL_ORDER_VALUE within the MySales source system.

• The dashed line between column TOTAL_ORDER_VALUE in the DIREPOsource and column TOTAL_ORDER_VALUE within the MySales sourcesystem indicates that the two columns are the same.

• The DIREPO source system uses values from three columns (UNITPRICE,QUANTITY, and DISCOUNT) to produce the value in columnTOTAL_ORDER_VALUE.

Move the pointer over:

• The universe object on the far right of the diagram to display the universeclass, universe name, and the CMS server name.

• The column object to display the table name and schema name thatcontains the column. This example shows that TOTAL_ORDER_VALUEis in the FACT_SALES_ORDER table in the DBO schema.

• Relationship attribute icon to display information such as

• The universe object selects values directly from the column or theuniverse object aggregates the values from the column.



• The transformation name and mapping expression that the DataIntegrator source uses to produce a column value. The above sampleshows:

• The transformation name df_SalesOrderFact is the name of thedata flow in Data Integrator that extracts the Quantity column fromthe source table

• The mapping expression is the calculation for the value in columnTOTAL_ORDER_VALUE.

Click Tabular view to view the entire mapping expression, as the followingdiagram shows.

Click Tabular view to view this information for all objects, as the followingdiagram shows.

The tabular view displays a row for each target object and a source objectwith the following information:

• Steps from Target - Number of steps between this source and the finaltarget.

• Relationship Attributes - Relationship between this source and target

• Mapping (if any) - How the data from the source is mapped to the target.

The third row in this example displays target TOTAL_ORDER_VALUE withthree sources: UNITPRICE, QUANTITY, and DISCOUNT.

• Steps from Target is 3, which indicates that the data flowed from threedifferent object to reach the target, (universe object Total Order Value).



• The Relationship Type is Lineage, which indicates that the target columnobtains its data from the three source columns.

• Mapping expression displays the complete calculation for the value incolumn TOTAL_ORDER_VALUE.

Lineage analysis for a report

On the Reports page, click the Lineage tab to display a graphical view of thesource columns from which the universe objects obtain their data.

Note:You can also display this lineage graphical view from a document in the"Documents List" in InfoView.

This Lineage graphical view shows the following information:

• The tables for the universe objects in the MySales BusinessObjectsEnterprise system were loaded by the Data Integrator source DIREPO.

• The dashed lines between each column name in DIREPO and MySalesindicates that the columns are the same.

• In the MySales source, move the pointer over:

• Each universe object to display its universe class, universe name, andCMS server name.

• Each column name to display its table name and schema name. Thisinformation is the same as in the Mapping Expression in the Overviewtab.



• Each Relationship Attribute icon to display the relationship betweeneach universe object and the report and between each universe objectand the column in the source table.

This sample Relational Attribute shows:

• The transformation name Total Order Value which is the name ofthe measure that uses the value in in columnTOTAL_ORDER_VALUE.

• The mapping expression is the sum of the values in columnTOTAL_ORDER_VALUE in table DBO.FACT_SALES_ORDER.

• In the DIREPO source, move the pointer over the objects:

• Each column name to display its table name and schema name. Thisinformation is the same as in the Mapping Expression in the Overviewtab.



• The blue Relationship Attribute icon to display the transformationname and mapping expression for columns processed in the DIREPOsource.

This sample Relational Attribute shows:

• The transformation name df_SalesOrderFact which is the name of thedata flow in Data Integrator that extracts the Quantity column from thesource table

• The mapping expression is the calculation for the value in columnTOTAL_ORDER_VALUE. To display the complete calculation, clickTabular view.

You can select the Hide intermediate objects check box to display only thesource columns in DIREPO and the report in MySales. The following exampleshows that you can still display the mapping expression from the sourcecolumn.



Viewing relationships with SAPNetWeaver BW sources

On the SAP BusinessObjects Metadata Management Explorer, you candetermine the answers to questions such as the following:• Which universes or reports would be affected if you change the definition

of a specific SAP NetWeaver BW object?• From what SAP NetWeaver BW sources does the universe obtain its

data?

Related Topics• SAP NetWeaver BW objects used by a Crystal Report on page 297• Universe lineage from InfoCube on page 300• Crystal Report lineage from DataStore Object on page 301

SAPNetWeaver BWobjects used by aCrystal Report

In SAP BusinessObjects Enterprise (BOE), you can define Crystal Reportsthat use data from DataStore objects, InfoCubes, InfoObjects and Queriesin an SAP NetWeaver Business Warehouse (BW) system.

Note:

• You must install the BusinessObjects XI Integration for SAP Solutions onthe same computer as the BusinessObjects Enterprise (BOE) Metadata


8SAP BusinessObjects Enterprise MetadataViewing relationships with SAP NetWeaver BW sources

Integrator to provide connectivity between SAP BusinessObjectsEnterprise and SAP NetWeaver BW. This connectivity is required forCrystal Reports and Web Intelligence documents created with theRefreshon Open option because whenever the report or document is opened(even to read the metadata when the BOE Metadata Integrator collectsthe metadata), the SAP BusinessObjects Enterprise system connects tothe source system to refresh the data automatically.

• The BusinessObjects XI Integration for SAP Solutions has prerequisitesthat you must install. For more information, see the BusinessObjects XIIntegration for SAP Installation Guide.

The Crystal Reports field explorer lists the NetWeaver BW objectshierarchically. For example, an InfoCube named Z_BOBJ might contain theInfoObjects named Z_CUSTOM and Z_ORDERID, and these InfoObjectsmight contain the other InfoObjects. In an SAP NetWeaver BW system, theseInfoObjects are listed as attributes of the Z_CUSTOM and Z_ORDERIDInfoObjects.• InfoCube Z_BOBJ

• InfoObject Z_CUSTOM• 2Z_CUSTOM• 1Z_CUSTOM• 2Z_CADDR• 1Z_CADDR• 2Z_CFAX• 1Z_CFAX• 2Z_CPHONE• 1Z_CPHONE

• InfoObject Z_ORDERID• 2Z_ORDERID

Several of the InfoObjects have the same name except for a leading numericvalue. They all refer to the same InfoObject, and the numeric value is usedinternally by Crystal Report to determine the data format to use for theInfoObject. When the BusinessObjects Enterprise Metadata Integrator collectsmetadata about the objects used by a Crystal Report, it removes the leadingnumeric values because it is not part of the SAP NetWeaver BW object.

For example, a Crystal Report might use the following InfoObjects from theabove InfoCube:


SAP BusinessObjects Enterprise Metadata8 Viewing relationships with SAP NetWeaver BW sources

• InfoCube Z_BOBJ• InfoObject Z_CUSTOM

• 2Z_CFAX• 2Z_CPHONE

• InfoObject Z_ORDERID• 2Z_ORDERID

The SAP BusinessObjects Metadata Management Explorer shows thefollowing:• The names of only the InfoObjects that the report uses.

For the sample Crystal Report, the following lineage diagram showsInfoObjects Z_CFAX, Z_CPHONE, and Z_ORDERID in the BOE CMSintegrator source system.

• The hierarchical relationship of the InfoObjects as a mapping expressionwith the format [parent]-[child]

In the following lineage diagram, the relationship attribute tool tip to theright of InfoObject Z_CPHONE shows that 2Z_CPHONE which is a childof Z_CUSTOM.

• The name of the SAP NetWeaver BW query that produces each InfoObjectused by the Crystal Report

The relationship attribute tool tip shows the queryCB_QUERY_HIGH_Z_BOBJ.



Universe lineage from InfoCube

A Web Intelligence Document in an SAP BusinessObjects Enterprise systemcan obtain data from a universe that is defined on an SAP NetWeaver BWInfoCube, InfoObject, or Query.

Note:This lineage is the same for a Crystal Report from an SAP NetWeaver BWQuery.

To see the SAP NetWeaver BW objects from which a Web IntelligenceDocument obtains its data:1. On the Explorer of SAP BusinessObjects Metadata Management, navigate

to an instance of a Web Intelligence Document in your SAPBusinessObjects Enterprise system.

2. Click the "Lineage" tab to view the lineage analysis diagram.

In the following sample lineage analysis diagram, the right side showsthe following metadata objects in the SAP BusinessObjects Enterpriseintegrator source named localCMS:• A Web Intelligence Document named Web_InfoCube_Z_BOBJ that

obtains data from universe objects L00 City, L00 City Key, L00 CityName, and L00 City.

• Each universe object obtains its data from a specific InfoObject. Forexample, the universe object L00 City obtains its data from theInfoObject named Z_CITY.


SAP BusinessObjects Enterprise Metadata8 Viewing relationships with SAP NetWeaver BW sources

3. To view the name of the InfoCube and the hierarchy of SAP NetWeaverBW objects that provide the data, move the pointer over the relationshipattribute on the left side of a universe object .

In the above lineage diagram, the pop-up window for the relationshipattribute to the left of L00 City shows the following:• The InfoCube named Z_BOBJ contains the City InfoObject.• The Mapping Expression shows the hierarchy of InfoObjects under

Z_CITY that are listed as attributes of Z_CITY in the SAP NetWeaverBW system: LEVEL00 is an InfoObject under Z_CITY.

4. The left side of the lineage diagram shows the following metadata objectsin the SAP NetWeaver BW integrator source namedpapgvmwin001.dhcp.pgdev.sap.corp:• InfoObject named City• The transformations from which the InfoObject derives its data. In the

above example, the InfoObject named City obtains data from twotransformations: City (Master Data) and City (Texts).

• The BW Source Systems from which the transformations obtain theirdata. In the example, the transformation named City (Texts) obtainsits data from the BOBJ Source System.

5. To display the description for each object, change the value of the "View"drop-down list to Tabular.

Crystal Report lineage from DataStore Object

A Crystal Report in SAP BusinessObjects Enterprise can obtain its data froma DataStore Object in an SAP NetWeaver BW system.



To see the SAP NetWeaver BW objects from which a Crystal Report obtainsits data:1. On the Explorer of SAP BusinessObjects Metadata Management, navigate

to an instance of a Crystal Report in your SAP BusinessObjects Enterprisesystem.

2. Click the "Lineage" tab to view the lineage diagram.

3. Move the pointer over the relationship attribute on the left side of theCrystal Report to view the name of the SAP DataStore Object.

In the above lineage diagram, the pop-up window for the relationshipattribute shows the following:• The InfoObject was selected to be in the Crystal Report.• The Mapping Expression shows the InfoObject named

0BPPARTNER1.• The SAP DataStore Object name is 0BP_REL.

Viewing relationships of users andgroups

On the SAP BusinessObjects Metadata Management Explorer, you candetermine answers to questions such as the following:• Which users or groups would be affected if you change the definition of

a specific universe or report?


SAP BusinessObjects Enterprise Metadata8 Viewing relationships of users and groups

• What reports and universes can a specific user or group access?

This section describes the following topics:• Finding user privileges to reports and universes on page 303• Finding group privileges to reports and universes on page 305• Impact analysis for users and groups on page 306

Finding user privileges to reports and universes

1. Navigate to a specific user in the SAP BusinessObjects MetadataManagement Explorer. Ways to navigate to a user include the following:• In the Users section on the SAP BusinessObjects Enterprise source

page, click the user name.• In the Search area, enter the user name, and click the user name in

the search results.

2. Click the Privileges tab to display:• A Reports section that lists the name of each report that this user can

access and the permissions that this user has for that report.• A Universe section that lists the name of each universe that this user

can access and the permissions that this user has that universe.

3. You can expand or collapse the Reports section.The following example lists the name and permissions for each reportthat the Guest user can access.


8SAP BusinessObjects Enterprise MetadataViewing relationships of users and groups

For information about object rights that each permission contains, seePrivileges and object rights for users and groups on page 308.

4. If you want to find a specific report, enter the name or a portion of thename in the Name text box and click Filter.

5. You can expand or collapse the Universes section.The following example lists the name and permissions for each universethat the Guest user can access.

6. If you want to find a specific universe, enter the name or a portion of thename in the Name text box and click Filter.



Finding group privileges to reports and universes

1. Navigate to a specific user in the SAP BusinessObjects MetadataManagement Explorer. Ways to navigate to a user include the following:• In the Groups section on the SAP BusinessObjects Enterprise source

page, click the group name.• In the Search area, enter the group name, and click the group name

in the search results.

2. Click the Privileges tab to display• A Reports section that lists the name of each report that this group

can access and the permissions that this group has for that report.• A Universe section that lists the name of each universe that this group

can access and the permissions that this group has that universe.

3. You can expand or collapse the Reports section.4. If you want to find a specific report, enter the name or a portion of the

name in the Name text box and click Filter.5. Expand the Universes section to list the names of the universes that this

group can access and the permissions that the group has for eachuniverse.

For information about the object rights contained in each permission, seePrivileges and object rights for users and groups on page 308.

For example, the following Privileges tab shows Group Everyone hasaccess to Universes MySales and Sales.



6. If you want to find a specific universe, enter the name or a portion of thename in the Name text box and click Filter.

Impact analysis for users and groups

You might want to determine what users and groups can access a specificuniverse or report for situations such as the following:• You want to redefine objects in a universe and you want to see which

users are currently using the objects.• You have sensitive information in a report and you want to see all users

and groups who currently have access to determine if you need to changetheir privileges.

• You want to change the definition of the column and you want to determinethe reports that would be affected and who the users of those reports are.

• The data in a column was not transformed accurately and you want todetermine which users and groups have been receiving incorrect reports.

1. Navigate to a specific universe, report, or column in the SAPBusinessObjects Metadata Management Explorer. Ways to navigate tothese objects include the following:• On the SAP BusinessObjects Enterprise source page, click the

universe name in the Universes section or click the report name inthe Reports section.

• In the Search area, enter the name (or partial name with wildcardcharacters) of the universe, report , or column; then click the name inthe search results.

2. Click the Impact tab to obtain the impact analysis diagram.For example, the following Impact tab shows:• The universe object Customerid obtains its data from the

CUSTOMERID column.• Three reports (SalesByYear, Product_Sales_By_Customer_webi ,

and Product Sales by Customer_unv.rpt) are affected by the data inthe CUSTOMERID column.

• Two users and two groups have permissions to access each report.For more information, see Finding user privileges to reports anduniverses on page 303 and Finding group privileges to reports anduniverses on page 305.



3. In the impact analysis diagram, click the Users and Groups node.The Permissions window opens.

4. Click the Users tab to display the Account Name, Full Name, andPermissions of users that access the report or universe.

The following sample Permissions window lists the Account Name andFull Name of each user that can access the MySales universe and thespecific permissions that each user has on the MySales universe. Forinformation about object rights that each permission contains, seePrivileges and object rights for users and groups on page 308.

5. If you want to find a specific user name:a. On the Users tab, in the User Name text box, enter the name that you

want to find.b. Click Filter.



6. Click the Groups tab to display the names and permissions of groups thataccess the report.

The following example lists the Group Name for each group that canaccess the MySales universe and the specific permissions each grouphas on the MySales universe.

7. If you want to find a specific group name:a. On the Groups tab, in the Group Name text box, enter the name that

you want to find.b. Click Filter.

For information about the lineage (source of data) for objects, see sections• Lineage analysis for universe object on page 291• Lineage analysis for a report on page 294.

Related Topics• Privileges and object rights for users and groups on page 308

Privileges and object rights for users and groups

To simplify the display of privileges that each user or group has on reportsand universes, SAP BusinessObjects Metadata Management uses thefollowing permissions to represent multiple object rights.



Object rightsMetadata Explorer Per-mission name

• Modify Rights• Modify Rights to user owned objects• Allow discussion threads• Unlock Universe• Apply overload to user• Edit overloads• Edit access restrictions

Adminstrator

• Data Access• Use List of Values• Refresh List of Values• New List of Values• View SQL, Edit query• Show data values• Refresh reports data• Download files• Download files associated with object• Download files associated with report• Export reports data

Data Access

For more information about object rights, see the SAP BusinessObjectsEnterprise Administrator's Reference Guide.





SAP NetWeaver BusinessWarehouse Metadata

9

Exploring SAP NetWeaver BusinessWarehouse metadata

SAP BusinessObjects Metadata Management stores metadata about objectsin selected source systems. The software's Explorer organizes the metadatainto a directory structure so that users can navigate and explore the metadataobjects in an easy-to-understand way.

The directory structure in the software's Explorer contains the followingcategories:

CategoriesComponent

Includes source systems such as SAPBusinessObjects Enterprise and SAPNetWeaver Business Warehouse.

Business Intelligence

Includes source systems such as SAPBusinessObjects Data Federator,BusinessObjects Data Integrator, andSAP BusinessObjects Data Services.

Data Integration

Includes sources such as DB2, MySQL,Oracle, SQL Server, Java DatabaseConnectivity (JDBC), or a BusinessOb-jects Universe connection.

Relational Databases

Includes sources such as CWM (Com-mon Warehouse Modeling)Data Modeling

The software's Explorer uses the following terms:


SAP NetWeaver Business Warehouse Metadata9 Exploring SAP NetWeaver Business Warehouse metadata

DefinitionTerm

A category is a type of source systemfor which Metadata Integrators collectmetadata. The above list of categoriesshow examples of source systems foreach category. When your administra-tor configures a source system forMetadata Integrator, the source systemdisplays under the appropriate categoryon the software's Explorer.

Category

An instance is an occurrence of aMetadata Integrator or metadata object.For example, an SAP NetWeaverBusiness Warehouse source (such asMy SAP BW) is an instance of a Meta-data Integrator in the Business Intelli-gence category. An example of a typeof metadata object is an InfoCube, andan instance of a InfoCube is SalesOverview.

Instance

A Metadata Integrator is a program thatextracts metadata from a source sys-tem and loads it into the metadatamanagement repository. Your adminis-trator installs zero, one, or more Meta-data Integrators for each category andmight configure multiple source sys-tems for each Metadata Integrator.

Metadata Integrator

A unit of information that a MetadataIntegrator creates from an object in asource system. For example, an SAPNetWeaver Business Warehousesource contains objects such asQueries, InfoProvider, InfoObjects,Transformations, and DataSourceswhich the Metadata Integrator loadsinto the metadata management reposi-tory as metadata objects.

Metadata object


9SAP NetWeaver Business Warehouse MetadataExploring SAP NetWeaver Business Warehouse metadata

Related Topics• SAP NetWeaver Business Warehouse metadata objects on page 314

SAP NetWeaver Business Warehousemetadata objects

An SAP NetWeaver Business Warehouse (BW) integrator source can containdifferent metadata object types. The SAP BusinessObjects MetadataManagement Explorer shows the following object types if they exist in theSAP NetWeaver BW integrator source.

Structure and associated objectsDescriptionObject type

An aggregation level contains a set ofcharacteristics and key figures from a real-time InfoCube. The InfoCube characteris-tics that are not contained in the aggrega-tion level are aggregated. Selections canbe specified for the characteristics in anaggregation level.

Virtual InfoProvider in SAPNetWeaver BW system.

AggregationLevel

You use the Crystal Reports Designer tocreate report definitions for formatted re-ports . From the BEx open dialog , choosea BEx query to be the basis of the format-ted report .

A formatted report created by inte-grating Crystal Reports into SAPNetWeaver BW.

Crystal Re-port

A DataSource contains a number of logical-ly-related fields that are arranged in a flatstructure and contain data to be transferedinto SAP NetWeaver BW.

Object that makes data for a busi-ness unit available to SAPNetWeaver BW.

DataSource


SAP NetWeaver Business Warehouse Metadata9 SAP NetWeaver Business Warehouse metadata objects


A DataStore object describes a consoli-dated dataset from one or more InfoS-ources. This dataset can be evaluatedusing a BEx query.

A DataStore object consists of a key (forexample, document number or position)and data fields that, as key figures, canalso contain character fields (for exam-ple, customer). You can use a delta up-date to update data from a DataStoreobject into InfoCubes or other DataStoreobjects in the same system or in a differ-ent system.

In contrast to multi-dimensional datastores for InfoCubes, data in DataStoreobjects is stored in transparent, flatdatabase tables.

Object that stores consolidated andcleaned-up transaction data on thedocument level (basic level).

DataStoreobject

Characteristics are grouped together intodimensions in order to store them in a starschema table (dimension table). An In-foCube can have up to 16 dimension tableswith three dimensions predefined by SAP(Time, Unit, and Packet).

A logical grouping of characteristicswithin an InfoCube.

Dimension

Each InfoProvider is assigned to an In-foArea. The resulting hierarchy is dis-played in the Data Warehousing Work-bench.

In addition to their properties as an Info-Providers, InfoObjects can also be as-signed to different InfoAreas.

Element for grouping meta-objectsin the SAP NetWeaver BW system.

InfoArea


9SAP NetWeaver Business Warehouse MetadataSAP NetWeaver Business Warehouse metadata objects


An InfoCube is a set of relational tablesthat are created in accordance with the starschema: a large fact table in the center,with several dimension tables surroundingit.

Type of InfoProvider.

An InfoCube describes a self-contained dataset (from the report-ing view), for example, for abusiness-oriented area. Thisdataset can be evaluated with theBEx query.

InfoCube

InfoObjects are subdivided into character-istics, key figures, units, time characteris-tics, and technical characteristics (such asrequest numbers).

Business evaluation objects (forexample, customers or sales) arecalled InfoObjects in SAPNetWeaver BW.

InfoObject

There are two types of InfoProviders. Onetype includes objects that contain physicaldata such as InfoCubes, DataStore objectsand InfoObjects (characteristics with at-tributes or texts). The other type includesobjects that are not physical data stores,such as InfoSets, VirtualProviders andMultiProviders.

Superordinate term for SAPNetWeaver BW objects into whichdata can be loaded or which repre-sent a view of the data. As a rule,you can report on this data usingBEx queries.

InfoProvider

Unlike the classic InfoSet, this view of datais BW-specific. In the InfoSet builder, InfoS-ets are created and changed. InfoSets al-low you to use the query designer to definereports.

Type of InfoProvider.An InfoSet is a semantic view ofDataStore objects, InfoObjects(characteristics with master data)and InfoCubes that allows you tocreate reports on these objects,particularly on the joins betweenthese objects.

InfoSet

Structure that consists of InfoObjects andis used as a non-persistent store to con-nect two transformations.

Describes the quantity of all thedata available for a businesstransaction or a type of businesstransaction (for example, cost cen-ter accounting).

InfoSource




The MultiProvider itself contains no data;its data comes exclusively from the Info-Providers on which it is based (collatedusing a union operation). You can assem-ble a MultiProvider from different combi-nations of InfoProviders.

MultiProviders, like InfoProviders, areobjects or views that are relevant for re-porting.

Type of InfoProvider that combinesdata from several InfoProviders andmakes it available for reporting.

MultiProvider

Open Hub destinations can be databasetables or flat files.

An object within the open hubservice that contains all informa-tion about a target system for da-ta in an InfoProvider. The targetsystem can be an external datamart, analytical application, andother application such as DataServices.

Open HubDestination

A query corresponds to one InfoProvider,although you can define any number ofqueries for each InfoProvider.

You define a query in the BEx QueryDesigner by selecting InfoObjects orreusable query elements (structures, forexample) for an InfoProvider. You canmodel the view of the InfoProvider databy allocating filters, rows, columns, andfree characteristics.

Combination of characteristics andkey figures (InfoObjects) that allowyou to analyze the data in an Info-Provider.

Query

You can define one or more query viewsfor a query. You define a query view bysaving the current status of a data providerin an SAP NetWeaver BW application.

Modified view of the data in a queryor an external InfoProvider.

Query Views




Source systems can be:• SAP systems• SAP NetWeaver BW systems• Flat files for which metadata is main-

tained manually in SAP NetWeaver BWand data is transferred to SAPNetWeaver BW using a file interface

• Database management systems intowhich data is loaded from a databasesupported by SAP using DB Connect,without using an external extractionprogram.

• Relational sources that are connectedto BI using UD Connect

• Web Services that transfer data to SAPNetWeaver BW by push

• Non-SAP systems for which data andmetadata is transferred using stagingBAPIs

System that is available to SAPNetWeaver BW for data extractionand transfer purposes.

Source Sys-tem

With the help of the transfer rules, you candetermine how the fields for the transferstructure are assigned to the InfoObjectsof the communication structure.

Determine how the data for aDataSource is to be transferred tothe InfoSource. The uploaded datais transformed using transfer rules.

TransferRules

When data is loaded from one BI objectto another BI object, the data is runthrough a transformation.

A transformation converts the records ina data package from the format of thesource structure into the format of thetarget structure. A transformation con-sists of at least one transformation rule.

Functions for unloading, loading,and formatting data between differ-ent data sources and data targetsthat use data streams.

Transformations




An update rule is specified for each keyfigure and the corresponding characteris-tics of the InfoSource.

Specify how the data (key figures,time characteristics, and character-istics) is updated to data targetsfrom the communication structureof an InfoSource.

Update rules

The Web template contains placeholdersfor Web items, data providers, and com-mands.

An HTML document that deter-mines the structure of a Web appli-cation.

Web Tem-plate

Queries are inserted into workbooks soyou can display them. When you insert aquery, a link is made between the cell ar-eas of the worksheet and the data of theInfoProvider on which the query is based.

Microsoft Excel workbook with oneor more embedded NetWeaver BWqueries.

Workbook

SAP NetWeaver BW object relationships

The following logical diagram gives an overview of the relationships betweenthe SAP NetWeaver BW object types:• Which SAP NetWeaver BW object types can be associated with (contained

within) other SAP NetWeaver BW object types.• Which SAP NetWeaver BW object types can impact (provide data to):

• SAP BusinessObjects Enterprise objects• Other SAP NetWeaver BW objects

Note:The line from InfoArea to Transformation to Open Hub destination to DataServices indicates that InfoProviders provide data to Open Hub Destinationobjects which provide data to non-SAP NetWeaver BW systems such asSAP BusinessObjects Data Services.



Related Topics• SAP NetWeaver Business Warehouse metadata objects on page 314

SAP NetWeaver BW object attributes collected

When you run the SAP NetWeaver Business Warehouse metadata integrator,it collects the following attributes about each SAP NetWeaver BW object anddisplays them in the following SAP BusinessObjects Metadata Managementattributes in the Explorer.



Metadata objectMetadata Managementattribute

NetWeaver BW at-tribute

SAP NetWeaver BW SystemClient NumberClient ID

InfoObjectData TypeData Type

SAP NetWeaver BW SystemHostHost

All except SAP NetWeaverBW System

Last Changed OnLast Changed On


Last Changed ByLast Changed By


DescriptionLong Description

InfoObjectOutput LengthOutput Length


Business NameShort Description

InfoObjectInfoObject TypeSubtype of InfoOb-ject

SAP NetWeaver BW SystemSystem NumberSystem Number


Technical NameTechnical Name

TransformationTransformation TypeTransformation Type

SAP NetWeaver BW SystemBW VersionVersion

Web TemplateWebTemplate TypeWeb Template Type

For example, the resulting Explorer page shows an InfoArea with the followingattributes:• Business Name: Business Objects QA• Technical Name: BUSINESSOBJECTS_QA• Description: Business Objects QA• Last Changed On: 2008-02-12 22:10:48.0• Last Changed By: HENRIK

This InfoArea contains the following objects:



• One InfoCube with the Business Name "Business Objects Cus" whichcontians:• Eight dimentions• 11 InfoObjects

To display additional metadata, click the object type. For example, clickInfoObject (11) under the InfoCube Business Objects Cus to view thenames of each InfoObject with its description, InfoObject Type, Data Type,Output Length, and an indication whether it contains other InfoObjects.



Navigating SAP NetWeaver BusinessWarehouse metadata

When you log in to the SAP BusinessObjects Metadata ManagementExplorer, the Directory home page appears. To log in, see AccessingMetadata Management for administrative tasks on page 119.

The Directory home page shows each configured integrator source, groupedby the Metadata Integrator category in which it belongs.


9SAP NetWeaver Business Warehouse MetadataNavigating SAP NetWeaver Business Warehouse metadata

The Business Intelligence category can include integrator sources such asSAP BusinessObjects Enterprise, SAP NetWeaver Business Warehouse,and other Business Intelligence sources. The sample Directory home pageshows the Business Intelligence category with a configured SAP NetWeaverBusiness Warehouse source, SAP BW.

Under each source name are the first three metadata object types that itcontains, and the number in parentheses indicate the number of instancesfor that type. The sample shows the SAP BW source contains metadataobject types InfoArea, InfoCube, InfoObject, and more.

Exploring the InfoCube metadata object

An SAP NetWeaver Business Warehouse source page shows the InfoCubemetadata object type with the first three instance names. Click InfoCube orShow All... to display all InfoCube names. The following sample InfoCubesmetadata object page shows four InfoCube instances.


SAP NetWeaver Business Warehouse Metadata9 Navigating SAP NetWeaver Business Warehouse metadata

The InfoCube metadata object page displays the following information:• The business name for each InfoCube that this SAP NetWeaver Business

Warehouse source contains, listed in alphabetical order.• Under each InfoCube business name is the following metadata:

• Description• Date and time it was last changed• User name who changed it• Dimensions link with a number in parenthesis that indicates the number

of Dimensions that exist within the InfoCube• InfoObjects link with a number in parenthesis that indicates the number

of InfoObjects

Exploring an InfoCube instance

On the "InfoCubes" metadata object page, click an InfoCube name to displaythe InfoCube instance page.


9SAP NetWeaver Business Warehouse MetadataNavigating SAP NetWeaver Business Warehouse metadata

The InfoCube instance page opens onto the Overview tab that displays thefollowing information:• Technical Name of InfoCube

The sample InfoCube instance page shows the technical nameOBWTC_C02

• Description of InfoCube

The above sample page shows the description BW Statistics - OLAP

• Date and time when the InfoCube was last changed• Name of the user who last changed the InfoCube• The names of the Dimensions that this InfoCube contains, listed in

alphabetical order. Under each InfoCube name is the following metadata:• Description of Dimension• InfoObjects link with a number in parentheses that indicates the

number of InfoObjects• The names of the InfoObjects that this InfoCube contains, listed in

alphabetical order. Under each InfoObject name is the following metadata:


SAP NetWeaver Business Warehouse Metadata9 Navigating SAP NetWeaver Business Warehouse metadata

• Description of InfoObject• InfoObject type• Data Type• Output Length• If this InfoObject consists of other InfoObjects, InfoObjects link with

a number in parentheses that indicates the number of InfoObjects

Viewing relationships of SAPNetWeaverBW objects

With SAP BusinessObjects Metadata Management Explorer you can viewrelationships between the various BW objects (such as InfoAreas,InfoProviders, InfoObjects, and Queries) and reports that you create withSAP NetWeaver Business Warehouse\. You can also view relationshipsbetween BW objects and reports and universes in SAP BusinessObjectsEnterprise.

Related Topics• Impact analysis of a BW source system on page 327• Impact of BW source on Web Intelligence Documents on page 329• Impact of BW Open Hub table on Crystal Report on page 330• Lineage of web templates on page 331• Lineage of a BW Crystal Report on page 333

Impact analysis of a BW source system

An SAP NetWeaver BW source system provides data to both reports withinSAP NetWeaver BW and to reports and universes within SAPBusinessObjects Enterprise. Therefore, before you make a change (suchas add a column) to the structure of SAP NetWeaver BW source system, itis recommended that you see what reports would be impacted.

To see the reports that a SAP NetWeaver BW source system impacts:1. On the Explorer of SAP BusinessObjects Metadata Management, navigate

to an instance of an SAP NetWeaver BW source system.2. Click the Impact tab to view the impact analysis diagram.


9SAP NetWeaver Business Warehouse MetadataViewing relationships of SAP NetWeaver BW objects

Example:

The following impact analysis diagram shows that the SAP NetWeaver BWsource system named Z_CITY ultimately provides data to the followingreports in the SAP BusinessObjects Enterprise system named CMS:• Crystal Report named SAP_MDX_ZBOBJ_ZCITY• Crystal Report named SAP_MDX_ZBOBJ_ALL

The intermediate objects in this impact analysis diagram are as follows:• In the SAP BW Metadata Integrator source:

• The Z_CITY BW source system impacts (provides data to) thetransformation named City (Texts).

• The City (Texts) transformation produces the InfoObject named City.• The dashed line between the City InfoObject in the SAP BW> Metadata

Integrator source and the Z_CITY InfoObject in the BOE CMS MetadataIntegrator source indicates that they are referring to the same object.

• In the BOE CMS Metadata Integrator source:• The Z_CITY InfoObject is the source object for the Crystal Reports

named SAP_MDX_ZBOBJ_ZCITY and SAP_MDX_ZBOBJ_ ALL.• The tool tip on the relationship attribute for SAP_MDX_ZBOBJ_ ALL

shows that the InfoObject Z_CITY is in the InfoCube Z_BOBJ.


SAP NetWeaver Business Warehouse Metadata9 Viewing relationships of SAP NetWeaver BW objects

Impact of BWsource onWeb IntelligenceDocuments

An SAP NetWeaver BW source system can provide data to universes in SAPBusinessObjects Enterprise, and the universe objects can be used to buildWeb Intellience Documents. Therefore, before you make a change (such asdelete a column) to the structure of SAP NetWeaver BW source system, itis recommended that you see what universe objects and Web IntellienceDocuments would be impacted.

To see Web Intelligence Documents that a SAP NetWeaver BW sourcesystem impacts:1. On the Explorer of SAP BusinessObjects Metadata Management, navigate

to an instance of an SAP NetWeaver BW source system.2. Click the "Impact" tab to view the impact analysis diagram.

In this sample impact analysis diagram, the left side shows the followingmetadata objects in the SAP NetWeaver BW integrator source namedSAP BW:• BW Source System named Business Objects QA• Transformation named City (Master Data) which produces the

InfoObject named City• Transformation named Customer (Master Data) which produces the

InfoObject named Customer

The right side of the diagram shows the following metadata objects in theSAP BusinessObjects Enterprise integrator source named BOE CMS:• InfoObject named Z_CITY which provides data to the following two

Crystal Reports



SAP_MDX_ZBOBJ_ZCITY•• SAP_MDX_ZBOBJ_ALL

• InfoObject named Z_CUSTOM which provides data to Universe objectsL00 Customer

• Web Intelligence Document named WEB_UNIV_SAP_TEST whichobtains data from Universe objects L00 Customer

3. Move the pointer over the relationship attribute on the left side of auniverse object to view the name of the SAP NetWeaver BW object thatprovides the data for the universe object.

In the above example, the pop-up window for the relationship attributepreceding L00 Customer shows the Query name SAP BW query:QRY_CUSTOMER_HIERARCHY.

Impact of BW Open Hub table on Crystal Report

The Open Hub Services of SAP NetWeaver BW provides data to externalapplications such as SAP BusinessObjects Data Services. Data TransferProcesses (DTPs) extract data from BW InfoProviders and load the data toOpen Hub Destination objects. Data Services imports the BW Open HubDestination objects as Open Hub tables. A data flow in Data Services canthen read the data from the Open Hub table, transform it, and load a targettable which can be used as the source table for a Crystal Rerpot in SAPBuisnessObjects Enterprise.

The following impact analysis diagram shows the following three metadataintegrator sources and the relationships of the objects between them. Thedashed line between objects indicate that two different integrator sourcesare referring to the same physical object.• In the BW integrator source named papgvmwin001, the Open Hub

Destination object named ZPALAV127 provides data to the Open Hubtable ZPALAV127 in the Data Services system named ds-ohd.

• In the Data Services integrator source named ds-ohd, data from the OpenHub table ZPALAV127 is loaded into table TARGET1.

• In the BusinessOjbects Enterprise integrator source named LocalCMS,table TARGET1 contains columns Z Country, Z Date, and 0datapakidwhich provide data to the report CrystalReport_DS-BW-CMS.



Related Topics• Viewing impact and lineage of Open Hub tables on page 365

Lineage of web templates

An SAP NetWeaver BW source system can provide data to web templatesthat are used for BEx Web application.

To see where the data for a web template comes from:1. On the Explorer of SAP BusinessObjects Metadata Management, navigate

to an instance of a web template on your SAP NetWeaver BW sourcesystem.


For example, the following lineage diagram shows that the web templatenamed ORSTT_C01_T01 obtains its data from the following NetWeaverBW objects:• Query named Daily Evaluation - Graphic (BW_BEX)• Query named Daily Evaluation - Table (BW_BEX)



3. To display the description for each object, take one of the following actions:• Move the pointer over each object in the lineage diagram. The above

example shows the description "Daily Evaluation - Table (BW_BEX)"for the Query and when it was last changed.

• Change the value of the "View" drop-down list to Tabular. The examplebelow shows the descriptions of all of the objects (Web Template,Queries, and InfoCubes).



Lineage of a BW Crystal Report

An SAP NetWeaver BW source system can provide data to Crystal Reportswithin the SAP NetWeaver BW system.

To see where the data for a Crystal Report comes from:1. On the Explorer of SAP BusinessObjects Metadata Management, navigate

to an instance of a Crystal Report on your SAP NetWeaver BW sourcesystem.


For example, the following lineage diagram shows that the Crystal Reportwith the generated name D5F1K10TKJCSIBR05RWQ obtains its datafrom the following NetWeaver BW objects:• Query named SEC_zbobj_HR1• InfoCube named Business Objects Cus• Transformation named 3GS1561BKXQI5FLVQABA• InfoSource named Business Objects QA



3. To display the description for each object, take one of the following actions:• Move the pointer over each object in the lineage diagram. The above

example shows the description "orders per country hierarchy" for theCrystal Report and when it was last changed.

• Change the value of the "View" drop-down list to Tabular. The tabularview shows the descriptions of all of the objects in the above lineagediagram.



Data Modeling Metadata

10

Exploring Data Modeling metadataSAP BusinessObjects Metadata Management stores metadata about objectsin selected source systems. Metadata Management Explorer organizes themetadata into a directory structure so that users can navigate and explorethe metadata objects in an easy to understand way.

The directory structure in Metadata Management Explorer contains thefollowing categories:

• Business Intelligence which contains sources such as SAPBusinessObjects Enterprise.

• ETL (Extract, Transform, Load) which contains sources such asBusinessObjects Data Integrator

• Relational Databases which contains sources such as DB2, Oracle, orSQL Server


Metadata Management Explorer uses the following terms:

• Category - A category is a type of source system for which MetadataIntegrators collect metadata. The above list of categories show examplesof source systems for each category. When your administrator configuresa source system for Metadata Integrator, the source system displaysunder the appropriate category on the Metadata Management Explorer.

• Instance - An instance is an occurrence of a Metadata Integrator ormetadata object. For example, a CWM source (such as CWM Sales) isan instance of a Metadata Integrator in the Data Modeling category. Anexample of a type of metadata object is a table, and an instance of a tableis FACT_SALES_ORDER.

• Metadata Integrator - A Metadata Integrator is a program that extractsmetadata from a source system and loads it into the MetadataManagement Repository. Your administrator installs zero, one, or moreMetadata Integrators for each category and might configure multiplesource systems for each Metadata Integrator. For configurationinformation, seeConfiguring sources for CommonWarehouseMetamodel(CWM) Metadata Integrator on page 139.


Data Modeling Metadata10 Exploring Data Modeling metadata

• Metadata object - A unit of information that a Metadata Integrator createsfrom an object in a source system. For example, a Data Modeling sourcecontains objects such as databases, schemas, and tables which theMetadata Integrator loads into the Metadata Management as metadataobjects Databases, Schemas, and Tables.


• Navigating data modeling metadata on page 337

• Viewing relationships of CWM objects on page 340

Navigating data modeling metadataWhen you login to the SAP BusinessObjects Metadata Management Explorer,the Directory home page displays. To login, see on page 44.

The Directory home page shows each configured source, grouped by theMetadata Integrator category in which it belongs.

The above sample page shows the following categories:

• Business Intelligence (SAP BusinessObjects Enterprise is an exampleof this type of Metadata Integrator source)

• Data Modeling (CWM is an example of this type of Metadata Integratorsource)

• Relational Databases (Oracle is an example of this type of MetadataIntegrator source)

• ETL (Data Integrator is an example of this type of Metadata Integratorsource)


10Data Modeling MetadataNavigating data modeling metadata

Each category name is a link to display all sources configured for thatMetadata Integrator.

Exploring CWM objects

The SAP BusinessObjects Metadata Management Explorer page for a CWMsource shows the following main object types:

• Databases

• Schemas

• Tables (which contain columns)

To explore the Data Modeling objects:

1. Click Data Modeling on the Directory home page to display the DataModeling category page.

This sample category page shows one CWM source name CWM Sales.Under the name are the object types that belong to it. This example showsthe following object types:

• Databases (1)

• Schemas (1)

• Tables (10)

The number in parenthesis indicate the number of instances for thatobject.


Data Modeling Metadata10 Navigating data modeling metadata

2. Click the source name CWM Sales to display more details about theseobjects.

The Data Modeling page shows:• Data modeling source name. This example shows theCWMSales source

name in the navigation path at the top and as the heading.

• File name

• Description of the file

• Main object types that this data modeling file contains. This exampleshows the following main object types for this CWM file:

• One database named ds_forenza_dw

• The first three tables AGG_MULTIFACT, AGG_REGION_SALES, andBAD_ORDERS

• One schema named dbo

• Under each main object, the object types that it contains and a numberin parenthesis that indicates the number of instances for that object. Thisexample shows that table AGG_MULTIFACT contains 5 columns.

• Click the name of an object to open its Metadata Explorer page.


10Data Modeling MetadataNavigating data modeling metadata

Exploring an instance of a modeling object

On theData Modeling category page, click a specific object name to displaydetails about the object. For example, clickAGG_MULTIFACT orColumns(5)to display the following details for each column:

The Overview tab for this table shows the:

• Names of the columns that the AGG_MULTIFACTtablecontains.

• Data type, length, and other attributes for each column.

Viewing relationships of CWM objectsWhen you analyze metadata, you often analyze relationships betweenobjects. In SAP BusinessObjects Metadata Management Explorer, you cando the following tasks:

• Same As relationships on page 341

• Impact analysis for a table on page 341

• Lineage analysis on page 342


Data Modeling Metadata10 Viewing relationships of CWM objects

Same As relationships

You can use CWM to capture modeling information about your database.You can then use this modeling information to create a data warehouse onwhich to create an SAP BusinessObjects universe and create BusinessIntelligence reports. CWM can also capture business-level information thatdisplays in the Same As relationship in SAP BusinessObjects MetadataManagement.

The Same As tab shows a metadata object that exists in other sourcesystems, but it is the same physical object. For example, navigate to thetable FACT_SALES_ORDER in the CWM Sales source system to view thefollowing Same As tab.

This example shows that the table AGG_MULTIFACT in the Data Modelingsource CWM Sales is the same physical table that exists in other sourcesystems: SAP BusinessObjects Enterprise source MySales, Data Integratorsource DIREPO, and relational database source Forenza DW.

Impact analysis for a table

Impact analysis allows you to identify which objects will be affected if youchange or remove other connected objects. In other words, what other objectsare affected by the data within this object. The Impact tab on an object'sExplorer page displays the other objects that this object impacts.


10Data Modeling MetadataViewing relationships of CWM objects

This example shows a partial view of the impact analysis for tableFACT_SALES_ORDER in the CWM Sales source.

• The dashed line between table FACT_SALES_ORDER in CWM Salesand table FACT_SALES_ORDER in MySales means that this is the samephysical table that is referred to in both source systems.

• Table FACT_SALES_ORDER impacts the following reports:

• Product_Sales_By_Customer_webi

• Product Sales by Customer_unv.rpt

• SalesByYear

Lineage analysis

Lineage analysis allows you to trace back from a data modeling object tothe source. Use the Lineage tab to view the sources for an object. Thefollowing example shows that the AGG_MULTIFACT table obtains it's datafrom tables in the DIREPO system.



This example shows the lineage analysis for the AGG_MULTIFACT tablethat sectionExploring an instance of amodeling object on page 340 describes.It shows that the data in AGG_MULTIFACT table came from the DataIntegrator DIREPO system.

When there are many intermediate objects, you might need to scroll the pageto view all objects. This example selects the option Hide intermediateobjects to display only the source and final target objects on the page.


10Data Modeling MetadataViewing relationships of CWM objects



SAP BusinessObjects DataServices Metadata

11

Exploring Data Services MetadataSAP BusinessObjects Metadata Management stores metadata about objectsin selected source systems. Metadata Management Explorer organizes themetadata into a directory structure so that you can easily navigate and explorethe metadata objects.



• Data Integration - Source systems include SAP BusinessObjects DataFederator, BusinessObjects Data Integrator, and SAP BusinessObjectsData Services.

• Relational Databases which contains sources such as DB2, MySQL,Oracle, SQL Server, Java Database Connectivity (JDBC), or aBusinessObjects Universe connection.

• Data Modeling which contains sources such as CWM (CommonWarehouse Modeling) .


• Category - A category indicates the type of source system from whichMetadata Integrators collect metadata. The above list of categories showsexamples of source systems that would fit into each category. When youradministrator configures a source system for Metadata Integrator, thatsource system displays under the appropriate category in the MetadataManagement Explorer.

• Instance - An instance is an occurrence of a Metadata Integrator ormetadata object. For example, a Data Integrator source (such as therepository named DIREPO) is an instance of a Metadata Integrator in theData Integration category. For example a table would be a type ofmetadata object and an instance of a table could be namedFACT_SALES_ORDER.

• Metadata Integrator - A Metadata Integrator is a program that extractsmetadata from a source system and loads it into the MetadataManagement Repository. Your administrator installs zero, one, or moreMetadata Integrators for each category and might configure multiplesource systems for each Metadata Integrator. For configuration


SAP BusinessObjects Data Services Metadata11 Exploring Data Services Metadata

information, see Configuring sources for SAP BusinessObjects DataServices Metadata Integrator on page 142.

• Metadata object - A unit of information that a Metadata Integrator createsfrom an object in a source system. For example, a Data Services sourcecontains objects such as jobs, work flows, and data flows which theMetadata Integrator loads into the Metadata Management as metadataobjects called Jobs, Work Flows, and Data Flows.

Related Topics• Navigating Data Services metadata on page 347• Viewing Data Services object relationships on page 358

Navigating Data Services metadataWhen you login to the SAP BusinessObjects Metadata Management Explorer,the Directory home page displays. To log in, see Accessing MetadataManagement Explorer on page 197.

The Directory home page shows each configured source grouped by theMetadata Integrator category in which it belongs. The Data Integrationcategory can contain SAP BusinessObjects Data Federator sources,BusinessObjects Data Integrator, and SAP BusinessObjects Data Servicessources.

Under each source name are the first three metadata object types that itcontains, and the number in parenthesis indicate the number of instancesfor that type. The sample shows the DIREPO source contains metadataobject types Projects, Jobs, Work Flows, and more.


11SAP BusinessObjects Data Services MetadataNavigating Data Services metadata

BusinessObjects Data Services objects

An SAP BusinessObjects Data Services source can contain different typesof objects. Some objects can be associated with (contained within) morethan one object type. Many object types can be associated with (contain)one or more additional objects, as indicated in the following table. Forexample, a job can contain a data flow instance and that same data flowinstance can belong to more than one job.


Job

A project is a reusable object that allowsyou to group jobs. A project is the high-est level of organization provided byData Services.

Projects

Custom functions

Data flows

Tables (as a result oflookup_ext in scripts)

Work flows

A job is an object you can execute andcontains steps that you want executedtogether.

Jobs


SAP BusinessObjects Data Services Metadata11 Navigating Data Services metadata


Custom functions

Custom transforms

Data flows

Flat files

Nested schemas

Open Hub DestinationTables as sources

SAP NetWeaver BWDataSources/InfoS-ources as targets

Stored procedures

Tables

Data flows extract, transform, and loaddata. Everything having to do with data,including reading sources, transformingdata, and loading targets, occurs insidea data flow.

Data flows

Custom functions

Data flows

Tables (as a result oflookup_ext in scripts)

Work flows

A work flow defines the decision-makingprocess for executing data flows.Work flows




Nested schemas

Open Hub DestinationTables in a BWSource datastore

SAP NetWeaver BWDataSources/InfoS-ources in a BW Targetdatastore

Stored procedures

Tables

A datastore represents connection con-figurations between Data Services anddatabases or applications. Datastoreconfigurations allow Data Services toaccess metadata from a database orapplication and read from or write to thatdatabase or application while Data Ser-vices executes a job.

Datastores

Flat files

A file format is a set of properties thatdescribe the structure of a flat file. Youuse a file format to connect Data Ser-vices to source or target data when thedata is stored in a file rather than adatabase table.

File Formats

File recordsA flat file can be used as either a sourceor a target in a Data Services data flow.Flat Files

ParametersCustom Functions are functions writtenin the Data Services Scripting Language.You can use them in Data Services jobs.

CustomFunctions

noneCustom Transforms are ABAP programsthat you create and can use as trans-forms in R/3 data flows.

CustomTransforms

DatabasesThe database server to which DataServices connects to extract data fromor into which to load.

Server In-stances

ColumnsA table is a collection of records (recordsare also referred to as rows) in a relation-al database.

Tables




Columns

Source objects that \Data Services usesto read data from InfoProviders in anSAP NetWeaver Business Warehousesystem.

Open HubDestinationTables

Exploring Data Services sources metadata

To view all of the object types within an SAP BusinessObjects Data Servicessource:

1. Click Data Integration on the Directory home page.

Under each source name, the directory lists the first three object typescontained in the source. The number of instances of an object typeappears in parenthesis after that object type.

2. Click More... to display all object types in the source. The source pagealso opens when you click the source name.

For example, click the source name DIREPO or More... to display all ofthe object types within the DIREPO source.



From top to bottom, each source page displays the navigation path,information about the source, and object type information. The examplesource page for Data Integration (DIREPO) shows:

• The navigation path Directory > Data Integration(DIREPO)

Click Directory to return to the Directory home page. Click DataIntegration to display all configured sources for that category.

• Information about a Data Integration source which includes itsdescription, database name, database type, and database host.

• Object types Projects, Jobs, Work Flows, and Data Flows. Thenumber in parenthesis indicates the number of instances for that objecttype.

Scroll down to view more object types such as Datastores, FileFormats, Flat Files, Custom Functions, Customer Transforms,Server Instances, and Tables.

• The first three instance names display under each object type.



Under each instance name, find associated object types containedwithin that instance. The number of instances of an associated objecttype appears in parenthesis after that object type. This example showsassociated object type Jobs under each project instance name.

Exploring Data Services objects

To display all instances of an object type, click the object type name or ShowAll... on the SAP BusinessObjects Data Services source page. The objecttype page displays up to 10 instance names. When more than 10 instancesexist, click the links at the bottom of the page to display additional groups of10 instances.

For example, if you click Jobs or Show All... on the sample DIREPO sourcepage, the "Jobs" metadata object page displays the following:• The job names that the DIREPO source contains, listed in alphabetic

order.• Under each job name, the associated object types that it contains and a

number in parenthesis indicating the number of instances for thatassociated object. For example, the job OracleApps_Sales_Loadcontains associated object types Work flows and Custom Functions.

Exploring data flow metadata

To view only data flow objects, click Data Flows or Show All... on the SAPBusinessObjects Data Services source page. The "Data Flows" metadataobject page displays the following:

• The data flow names that the Data Services source contains, listed inalphabetic order.

• Under each data flow name, the associated object types that it containsand a number in parenthesis that indicates the number of instances forthat associated object.

For example, a data flow might contain associated objects Tables andFlat Files.



Exploring an instance of a data flow

On the Data flow metadata object page, click a data flow name to displaythe objects it contains. Or you can use Search on the SAP BusinessObjectsMetadata Management Explorer to find a specific data flow.

For example, navigating to data flow DF_SalesOrderFact would open ontothe "Overview" tab which displays the objects in this data flow.

The Overview tab for data flow DF_SalesOrderFact shows table namesBAD_ORDERS, DIM_CUSTOMER, DIM_EMPLOYEE,FACT_SALES_ORDER, ORDER DETAILS, and ORDERS. Under each tablename, additional information includes:

• Additional attribute - Value that indicates how SAP BusinessObjects DataServices uses this table.



Data Services usageAdditional attribute value

Extracts data from this table.Source

Loads data into this table.Target

Compare the data in this table withthe source table.Compare table in table comparison

Retrieve a value from this table basedon the value in another source tableor file.

Lookup table in lookup() andlookup_ext() functions

Generates the next value in a series,after determining the last value in theseries.

Key generation table in Key Genera-tion transform and function

This example shows the following attribute values:

• Lookup table in lookup_ext() function indicating that DataServices uses the lookup_ext() function to obtain a value from theDIM_EMPLOYEE and DIM_CUSTOMER tables.

• Source indicating that Data Services extracts data from ORDERDETAILS and ORDERS tables.

On the Explorer page for the source table, the Impact relationshipanalysis tab displays a graphical representation of the source impacting(providing data for) the target.

• Target indicating that Data Services loads data intoFACT_SALES_ORDER and BAD_ORDERS tables.

On the Explorer page for the target table, the Lineage relationshipanalysis tab shows a graphical representation of the target obtainingdata from the source. For more information, see Viewing impact andlineage of tables on page 361.

• Schema for the table• Database in which the table resides• Object types contained in each table and the number of instances of that

type. This example shows Columns for each table.



Exploring datastore metadata

Datastores represent connection configurations between SAPBusinessObjects Data Services and databases or applications. Datastoreconfigurations allow Data Services to access metadata from a database orapplication and read from or write to that database or application while DataServices executes a job.

To view information about datastores, click Datastores or Show All... onthe "Data Integration" source page.

This example Datastores metadata object page shows:• The name of each datastore instance follows this format:

Datastore_name-configuration_name

Each datastore can have multiple configurations, and each configurationspecifies different connection information. For example, you can associatea configuration to a test database and a different configuration to aproduction database.

• Under the name of each datastore is:• A description (if any)• Whether or not Change Data Capture (CDC) is enabled



• The associated object types that the datastore contains and a numberin parenthesis indicating the number of instances for that associatedobject.

Note:Currently, SAP BusinessObjects Metadata Management displays datastoresfor all databases and applications that Data Services supports, exceptmemory datastores.

Exploring a table instance

Each instance of a table is associated with specific attributes andrelationships. The SAP BusinessObjects Metadata Management Explorerdisplays a tab for each relationship.

This sample page for FACT_SALES_ORDER shows the following tabs:

• Overview - Displays additional attributes, schema name, database name,and list of columns with their data type and length.

• Same As - Displays another system that uses same column. SeeViewingSame As relationships on page 361.

• Related To - Displays relationships that you define (if any) for this table.See Establishing user-defined relationships between objects on page 260.



• Impact - Displays the objects that depend on the data in this table. SeeViewing Data Services object relationships on page 358.

• Lineage - Displays the sources (if any) for this table. See Viewing impactand lineage of tables on page 361.

• User Defined - Displays relationships (if any) that you define. SeeEstablishing user-defined relationships between objects on page 260.

Exploring a column instance

Each instance of a column has individual attributes and relationshipsassociated with it. The SAP BusinessObjects Metadata Management Explorerdisplays a tab for each relationship.

• "Overview" - Displays attributes such as whether or not it is a primary keyor foreign key, data type, and length.

• " Same As" - Displays any synonyms or aliases (if any) for this column.See Viewing synonyms and alias relationships on page 402.

• " Related To" - Displays primary key - foreign key relationships (if any)that exist for this column. See Viewing primary key and foreign keyrelationships on page 404.

• "Impact" - Displays objects that depend on data in this column. SeeViewing Data Services object relationships on page 358.

• "Lineage" - Displays the sources (if any) for this column.

• "User Defined" - Displays relationships (if any) that you define.

See Establishing user-defined relationships between objects on page 260.

Viewing Data Services objectrelationships

With SAP BusinessObjects Metadata Management Explorer you can viewrelationships between tables and columns in your Data Services sources.The tabs on the Metadata Management Explorer page for each table orobject display the following relationships.


SAP BusinessObjects Data Services Metadata11 Viewing Data Services object relationships


• Alias for database.• Synonym for table or view .• Tables and columns that are the same between

two systems, such as between a Data Servicesrepository and a relational database.

• User-defined relationship (for example, be-tween a table in a Data Services and the sametable in a BusinessObjects Enterprise system).For the procedure, see Establishing user-de-fined relationships between objects onpage 260.

Note:A message will indicate if no relationship exists.

Same As

• Primary Key - Foreign Key• You can also create a user-defined relationship

to appear in this tab. For the procedure, seeEstablishing user-defined relationships be-tween objects on page 260.


Related To

Shows a graphic of objects that are affected bydata in this object.

You can also define this relationship (for exam-ple, between a file format and a target table).For the procedure, see Establishing user-de-fined relationships between objects on page 260.

Impact

Shows a graphic of the sources from which thisobject gets its data.Lineage


11SAP BusinessObjects Data Services MetadataViewing Data Services object relationships


If you establish a custom relationship, you canview the following information for it:• Name of the related object• Name of the relationship• Path of the related object in the Metadata Ex-

plorer.

You can delete a user-defined relationshipfrom this tab.

Note:A message will indicate if no user-defined relation-ship exists.

User Defined

Note:You must set the option Calculate column mapping while saving dataflow to ensure that the Metadata Management integrator extracts impactand lineage relationships. Set this option in the Tools > Options > Designer> General window of the Data Services Designer.

In Metadata Management Explorer, you can view the following relationships:

• Viewing Same As relationships on page 361• Viewing impact and lineage of tables on page 361.• Viewing impact and lineage of Open Hub tables on page 365• Viewing impact and lineage of columns on page 367.

Note:Currently, Metadata Management displays impact and lineage only for tables,their columns, and flat files. Other objects (such as COBOL copybooks,DTDs, hierarchies, XML schemas) do not display impact or lineage. For acomplete list of all Data Services objects for which Metadata Managementdoes and does not automatically display impact and lineage, see theCompatibilities and Limitations section of the Release Notes.



Viewing Same As relationships

The Same As tab shows if a table or column is the same between twosystems, such as between an SAP BusinessObjects Data Services repositoryand a relational database.

For example, if you navigate to the table FACT_SALES_ORDER (see sectionExploring a table instance on page 357) you could view the following SameAs tab.

In this example, the table FACT_SALES_ORDER in the Data Services sourceDIREPO is used in other Metadata Integrator systems (Forenza DW, MySales,and CWM Sales).

Viewing impact and lineage of tables

The Explorer page for the table displays graphical representations of:

• The impact of a table on other objects when the table is a source.

• The source lineage for a table when the table is a target.

You might want to view the Impact tab of a table to see whether or not itaffects any of the following:• DataSources/InfoSources in the Persistent Storage Area of your SAP

NetWeaver Business Warehouse system• Reports in your SAP BusinessObjects Enterprise system



The following example shows that table FACT_SALES_ORDER affects fourreports: Product Sales by Customer_unv.rpt, SalesByYear, Product Salesby Customer_webi and Product Sales by Customer.rpt.

With many intermediate objects, you might need to scroll the page horizontallyto view all objects. You can clear the option Show intermediate objects inEdit Settings to display only the source and final target objects on the page,as the above example shows.

Move the pointer over the relationship attribute icon to display how thedata is mapped to the final target from the intermediate universe object. Thisexample shows that the mapping is a SELECT statement.

You can also select Tabular in the View drop-down list to display a longimpact analysis in table format. The following example shows part of thetabular view for the table FACT_SALES_ORDER.



The value in Steps from Source indicates the number of steps that the datain the first source object goes through to reach the objects listed in Target.For each step, the tabular view shows the source object, target object, andrelationship attributes. Relationship attributes includes the relationship typeand mapping (if applicable).

This example shows that the FACT_SALES_ORDER table is the same tablethat is in the source DIREPO system and the target MySales system.



This part of the tabular view for table FACT_SALES_ORDER shows thatdata in the source table FACT_SALES_ORDER goes through the followingnumber of steps to reach the final target reports:

• Two steps to final target report Product Sales by Customer.rpt

• Three steps to final target reports:

• Product_Sales_by_Customer_webi

• Product Sales by Customer_unv.rpt

• SalesByYear

In the third step, universe object Quantity in universe class Fact Sales Orderin the MySales BusinessObjects Enterprise system has the followingrelationships with the following objects in the MySales BusinessObjectsEnterprise system:

• Impact relationship with report "Product Sales by Customer_unv.rpt"

• Impact relationship with report "SalesByYear"



Viewing impact and lineage of Open Hub tables

You might want to view the Impact tab of an Open Hub table in SAPBusinessObjects Data Services to see whether or not it affects any reportsin your SAP BusinessObjects Enterprise system. Similarly, you might wantto see what InfoProvider in the BW system is the source of the data for theOpen Hub table in Data Services.

The following example shows that the Open Hub table ZPALAV127 impactsthe report CrystalReport_DS-BW-CMS. The intermediate steps show thefollowing relationships:• In the Data Services system named ds-ohd impacts, the Open Hub table

ZPALAV127 provides data to the table TARGET1.• In the BusinessObjects Enterprise system named LocalCMS, TARGET1

is the source table for the universe objects Z Country, Z Date, and0datapakid. These universe objects are mapped to the reportCrystalReport_DS-BW-CMS.

The following example shows that the Open Hub table ZPALAV127 obtainsits data from the following lineage:• The Open Hub table ZPALAV127 obtains its data from the XPALAV127

Open Hub Destination object in the SAP NetWeaver BW system namedpapgvmwin001.

• In the BW system papgvmwin001, the XPALAV127 Open Hub Destinationobtains its data through the transformation CUBE Z_BOBJ->DEST fromthe InfoCube Business Objects Cus.



Related Topics• Impact of BW Open Hub table on Crystal Report on page 330

Viewing column mappings for tables

When you view the lineage diagram for a table, you can select ColumnMappings in the View drop-down list to see how the data for each columnwas obtained. The following example shows that the DW_Key column usesa lookup_ext function to obtain values in the column DBO.DIM_EMPLOYEE.



Viewing impact and lineage of columns

The Explorer page for a column displays graphical representations of:

• The impact of a column on other objects when the column is a source.• The source lineage for a column when the column is a target.

To view the impact and lineage of columns:

1. Use Search, or navigate to the Explorer page for the column.

For example, suppose you have a column Address in table Customers.You can use Search and enter Address as the search string to find theExplorer page for it.

2. Click the Impact tab to view the targets affected by this source column.



3. Move the pointer over the Relationship Attribute icon between thesource and target objects within the DIREPO source system to displaythe transformation name (df_CustomersDimension) which is the data flowthat extracts the data from the Address column in Customer table andloads it into the Address column in Dim_Customer table.

4. Move the pointer over the graphic of each object to display its information,such as table name, schema name, and description.

5. Click a final target object on the right and click the Lineage tab on itsExplorer page to view all of its sources. For example, clickProduct_Sales_By_Customer_webi report and click the Lineage tab toview the following Lineage analysis.



SAP BusinessObjects DataFederator Metadata

12

Data Federator Metadata Integratoroverview

SAP BusinessObjects Data Federator is an Enterprise Information Integration(EII) application that provides a uniform, coherent and integrated view ofdistributed and heterogeneous data sources. Data Federator allows you toconsolidate your various data sources into one coherent set of virtual targettables that reporting tools can query and be confident that the data arereliable, trustworthy and up-to-date. For example, you can create a universeusing SAP BusinessObjects Designer or create a query directly against thevirtual target tables using Crystal Reports. For more information about DataFederator, see the SAP BusinessObjects Data Federator User Guide.

Data Federator Metadata Integrator extracts information from a DataFederator repository and stores the collected metadata in the SAPBusinessObjects Metadata Management Repository. The collectedinformation includes metadata about the Data Federator objects, such asdatasource tables and target tables on which the reports and documents arebased.

Exploring Data Federator MetadataSAP BusinessObjects Metadata Management stores metadata about objectsin selected source systems. Metadata Management Explorer organizes themetadata into a directory structure so that you can easily navigate and explorethe metadata objects.


• Business Intelligence which contains sources such as SAPBusinessObjects Enterprise

• Data Integration which contains sources such as:• BusinessObjects Data Integrator and SAP BusinessObjects Data

Services• SAP BusinessObjects Data Federator

• Relational Database which contains sources such as DB2, Oracle, orSQL Server


SAP BusinessObjects Data Federator Metadata12 Data Federator Metadata Integrator overview



ExplanationTerm

A category indicates the type of source system from whichMetadata Integrators collect metadata. The above list of cate-gories shows examples of source systems that would fit intoeach category. When your administrator configures a sourcesystem for Metadata Integrator, that source system displaysunder the appropriate category in the Metadata ManagementExplorer.

Category

An instance is an occurrence of a Metadata Integrator ormetadata object. For example, a Data Federator source name(such as My DF Source) is an instance of a Metadata Integratorin the Data Integration category. An example of a type ofmetadata object is a deployed version of a project and an in-stance could be named Forenza deployment.

Instance

A Metadata Integrator is a program that extracts metadata froma source system and loads it into the Metadata ManagementRepository. Your administrator installs zero, one, or moreMetadata Integrators for each category and might configuremultiple source systems for each Metadata Integrator.


A unit of information that a Metadata Integrator creates froman object in a source system. For example, a Data Federatorsource contains objects such as deployed versions of projects,target catalogs, and target schemas which the Metadata Inte-grator loads into the Metadata Management as metadata ob-jects called Deployed versions, Catalogs, and targetSchema.

Metadata ob-ject

Data Federator objectsAn SAP BusinessObjects Data Federator source can contain different objecttypes, as the following table describes.


12SAP BusinessObjects Data Federator MetadataData Federator objects

DescriptionObject type

A project is an object that groups a set of target tables, datasources together with mapping rules between these entities.Only deployed versions of projects are collected by the DataFederator Metadata Integrator. A project can have multipledeployed versions, each deployed in a different catalog on oneor more instances of Query Server.

Projects

A deployed version of a project is an operational copy of aproject that applications access through Query Server.

Deployed ver-sions

A query server behaves like a relational database through whichapplications can query the source tables to produce target rows.

Query Server

Each deployed version contains two catalogs:• A datasource catalog is a collection of datasources. Its name

has the following format: target_catalog_name/sources (Forexample, /OP/sources)

• A target catalog is a collection of target tables. Its name hasthe following format: target_catalog_name (For example,/OP)

Catalogs

A datasource schema is the definition of a datasource table’scolumns and primary keys.

Datasourceschemas

A datasource represents the external source of data from whichData Federator produces rows in a target table. A datasourcecan be a relational database, a text file, or an XML file. Only finalversions of datasources are collected by the Data FederatorMetadata Integrator.

Datasources

A target schema is a set of target tables. A project can onlycontain one target schema, and its name is always tar-getSchema.

Targetschemas


SAP BusinessObjects Data Federator Metadata12 Data Federator objects

DescriptionObject type

Target tables are virtual tables (similar to a view). They do notcontain data, but mapping rules define how Query Server ob-tains the target rows at run time from datasource tables, domainand lookup tables. A deployed version can contain both mappedand integrated target tables, or it can contain only deployedintegrated target tables.

Target tables

A mapping rule describes how Query Server generates therows in a target table from the datasources. Mapping rules caninclude filters, formulas, and relationships to convert values inyour datasource to values expected in the target.

Mapping rules

A column is a dimension that defines a single type of data.Columns

Data Federator object relationships

Some objects can be associated with (contained within) more than one objecttype. Many object types can be associated with (contain) one or moreadditional objects, as indicated in the following diagram. For example, adeployed version of a project always contains two catalogs, one for the targetschema and the other for datasources. The following diagram shows thedifferent relationships between SAP BusinessObjects Data Federator objects.


12SAP BusinessObjects Data Federator MetadataData Federator objects

Navigating Data Federator MetadataThe SAP BusinessObjects Metadata Management Explorer to view theDirectory home page shows each configured source grouped by the MetadataIntegrator category in which it belongs.


SAP BusinessObjects Data Federator Metadata12 Navigating Data Federator Metadata

Example:

This example shows an SAP BusinessObjects Data Federator source withthe name My DF source under the Data Integration category. Under thesource name, the directory lists the first three object types contained in thesource. The number of instances of an object type appears after that objecttype in parenthesis.

Exploring Data Federator sources metadata

To view all of the object types within an SAP BusinessObjects Data Federatorsource, click its name. For example, if you click My DF source, the resultslooks like the following:


12SAP BusinessObjects Data Federator MetadataNavigating Data Federator Metadata

This example source page for "Data Integration (My DF source)" displays:

• Object types such as "Projects", "Deployed versions", "Query servers","Catalogs", "Schemas", "Datasource tables", "Target tables", and "Mappingrules". Scroll down to view more object types. The number in parenthesisindicates the number of instances for that object type.



• Under each object type find the first three instance names. In the previousexample, find instance names DF_Target_on_Target and Forenza underobject type Projects.

Under each instance name, find associated object types contained withinthat instance. The number of instances of an associated object typeappears in parenthesis after that object type. This example showsassociated object type "Deployed versions" under each project instancename.

• If you do not see all of your instances for an object type on the "DataFederator" source page, click Show All to display a page that lists all ofthe instances for the object type. You can also click the object type nameto display all instances.

Exploring deployed versions metadata

To view only deployed version objects, click Deployed versions or ShowAll on the "Data Federator" source page.

The Deployed versions metadata object page shows the following:• The deployed version names that the SAP BusinessObjects Data

Federator source contains, listed in alphabetic order from left to right, topto bottom.

• Under each deployed version name, this page shows:• Query Server address• Query Server Port• Deployment catalog

• The associated object types that the deployed version contains. Thenumber in parenthesis indicates the number of instances for thatassociated object. For example, the deployed version"Forenza_deployment" contains associated objects "Schemas (3)" and"Catalogs (2)".

Exploring catalog metadata

Each deployment contains two catalogs: one for the datasources and onefor the target tables.



To view the catalogs for a deployed version, clickCatalogs under a deployedversion name on the "Deployed versions" objects page.

The "Catalogs metadata" object page displays:

• The target catalog and the datasource catalog.

The target catalog name is the same name that you entered in the SAPBusinessObjects Data Federator Designer when you deployed the project.The datasource catalog name has the suffix /sources appended. Forexample, if you entered the catalog name /Forenza when you deployedForenza deployment, the "Catalogs metadata" object page displays targetcatalog /Forenza and source catalog /Forenza/sources.

• Under each catalog name, the associated object type that it contains anda number in parenthesis that indicates the number of instances for thatassociated object.

For Data Federator, the catalog objects contain only schema objects. Atarget catalog contains only one schema named targetSchema. Adatasource catalog can contain multiple schemas.

Exploring datasource tables

Datasources represent connection configurations between SAPBusinessObjects Data Federator and database tables. Datasources allowData Federator to access metadata from a database table and read fromthat table while Query Server obtains the data from it to populate a targettable.

To view only datasource table objects, click Datasources tables or ShowAll on the "Data Federator source" page.

Exploring target tables metadata

An SAP BusinessObjects Data Federator target catalog always has oneschema, targetSchema, that contains the target tables.

To view the target table objects for a specific deployed version

1. Navigate to the "Catalogs metadata object" page for a deployed version.



2. Click Schemas under the target catalog. For example, click Schemasunder the target catalog /Forenza.

3. On the Schemas metadata object page, click either targetSchema orTarget tables (n) to display the target tables metadata page. The numberin parenthesis indicates the number of target tables. For example, supposeyou click targetSchema for the catalog /Forenza. The resulting "Targettables" metadata page looks like the following:

This sample "Target tables" metadata object page displays:• The table names that the /Forenza target catalog contains, listed in

alphabetic order.• The associated object types that each target table contains and a number

in parenthesis that indicates the number of instances for that associatedobject. For example, the table FACT_SALES_ORDER shows: Columns(8), Mapping rules (1)

Exploring a target table instance

For each instance of a target table, SAP BusinessObjects MetadataManagement Explorer displays the following tabs:



DescriptionTab

Displays schema name, Catalog name, list of columns, andmapping rules.

Overview

Displays the same table that exists in another MetadataManagement source.

Same As

Displays relationships that you define (if any) for this table.Related To

Displays the objects that depend on the data in this table.Impact

Displays the sources (if any) for this table.Lineage

Displays relationships (if any) that you define.User Defined

Related Topics• Viewing Overview tab of a target table on page 381• Viewing Same As relationships on page 385• Viewing impact and lineage of tables on page 386



• User-defined relationships between objects on page 259

Viewing Overview tab of a target table

This Overview tab for a target table displays the first five columns and firstfive mapping rules.• To display all columns for a target table, click Columns (n). The number

in parenthesis indicates the number of target tables.



• To display all mapping rules for a target table, click Mapping rules (n).

Exploring a column instance

Each instance of a column has individual attributes and relationshipsassociated with it. The SAP BusinessObjects Metadata Management Explorerdisplays a tab for each relationship.

DescriptionRelationship

Displays attributes such as whether or not it allows nulls.Overview

Displays other Metadata Management source systems that alsocontain this column.

Same As

Displays relationships that you define (if any) for this table.Related To

Displays objects that depend on data in this column.Impact

Displays the sources (if any) for this table.Lineage

Displays relationships (if any) that you define.User Defined

Related Topics• Viewing Data Federator object relationships on page 382• Viewing impact and lineage of columns on page 388

Viewing Data Federator objectrelationships

With SAP BusinessObjects Metadata Management Explorer you can viewrelationships between tables and columns in your SAP BusinessObjectsData Federator sources. This section contains topics that discuss theserelationships.

Related Topics• Relationship tabs on Metdata Management Explorer on page 383• Viewing Same As relationships on page 385• Viewing impact and lineage of tables on page 386


SAP BusinessObjects Data Federator Metadata12 Viewing Data Federator object relationships

• Viewing impact and lineage of columns on page 388

Relationship tabs onMetdataManagement Explorer

The tabs on the SAP BusinessObjects Metadata Management Explorer pagefor each table or object display the following relationships.


12SAP BusinessObjects Data Federator MetadataViewing Data Federator object relationships

Relationships that can appear on this tabMetadata Ex-plorer tab

• Tables and columns that are the same between two Meta-data Management source systems, such as between a DataFederator application and a relational database.

• User-defined relationship (for example, between a table inan SAP BusinessObjects Data Federator and the same tablein an SAP BusinessObjects Enterprise system).


Same As

• Primary Key• You can also create a user-defined relationship to appear

in this tab.


Related To

Shows a graphic of objects that are affected by data in thisobject.

You can also define this relationship (for example, betweena file format and a target table).

Impact

Shows a graphic of the sources from which this object getsits data.

Lineage

If you establish a custom relationship, you can view the fol-lowing information for it:• Name of the related object• Name of the relationship• Path of the related object in the Metadata Explorer.

You can delete a user-defined relationship from this tab.


User Defined

Note:



Currently, Metadata Management displays impact and lineage only fordatasource tables, text files, and XML files, target tables and their columns.Lookup and domain tables do not display in Metadata Management. For acomplete list of all Data Federator objects for which Metadata Managementdoes and does not automatically display impact and lineage, see"Compatibilities and Limitations" in the Metadata Management ReleaseNotes.

Setting object equivalency rules for Data Federator

SAP BusinessObjects Metadata Management uses the values in Impact andLineage Preferences with Object Equivalency Rules to determine that anobject with two different names is the same physical object. For example, inSAP BusinessObjects Data Federator, the datasource ForenzaDW is thesame as the schema dbo in your relational database system, and the highestlevel option in "Impact and Lineage Preferences" is set to schema. Therefore,ForenzaDW.TableA is the same as dbo.TableA.

If you have other objects that have different high-level qualifiers, use theObject Equivalency Rules to tell Metadata Management that an object is thesame. You specify these rules once, when you first setup your sourcesystems.

Related Topics• To set Object Equivalency Rules for Same As relationships on page 267

Viewing Same As relationships

The "Same As" tab shows if a table or column is the same between twosystems, such as between an SAP BusinessObjects Data Federatorrepository and a relational database.

For example, suppose you navigate to the table FACT_SALES_ORDER toview the following "Same As" tab.



In this example, the table FACT_SALES_ORDER in the Data Federatorsource My DF Source is used in other Metadata Integrator systems (ForenzaDW, DIREPO, CWM Sales, and MySales).

Viewing impact and lineage of tables

The Explorer page for the table displays graphical representations of:• The impact of a table on other objects when the table is a datasource.• The source lineage for a table when the table is a target.

You might want to view the "Impact" tab of an SAP BusinessObjects DataFederator table to see whether or not it affects any reports in your SAPBusinessObjects Enterprise system. Or you might want to view the "Lineage"tab to see the sources from which a Data Federator table obtains its data.

The following sample "Impact" and "Lineage" tabs show examples of eachsituation.



In this example, the AGG_MULTIFACT target table is used in the MySalesSAP BusinessObjects Enterprise system for universe objects (such as ActualSales and Forecasted Sales), which are used in the DF_Deski report.

This lineage example shows that table FACT_SALES_ORDER obtains itsdata from the following tables using mapping rule mr_SalesOrderFact:• Two datasource tables, Orders and Orders Details• Two virtual target tables which obtain their data as follows:

• DIM_CUSTOMER uses mapping rule mr_CustomerDimension toobtain data from table Customers.

• DIM_EMPLOYEE uses mapping rule mr_Employee to obtain datafrom table Employee.

You can also click tabular view to display the impact analysis in table format.



Viewing impact and lineage of columns

The Explorer page for a column displays graphical representations of:• Other objects affected by a column on the Impact tab• On the Impact tab of a column, you can click a final object, such as a

report in an SAP BusinessObjects Enterprise system, and click theLineage tab of the report to display all columns in SAP BusinessObjectsData Federator target tables that affect the contents of the report.

• The sources for a column on the Lineage tab

Related Topics• To view the lineage of a report back to Data Federator tables on page 389

To view the impact and lineage of columns

1. Use Search, or navigate to the Explorer page for the column. For example,suppose you have a column Total_Order_Value in tableSales_Fact_Order. You can use Search and enter Total_Order_Valueas the search string to find the Explorer page for it.

2. Click the Impact tab to view the targets affected by this source column.

With many intermediate objects, you might need to scroll the page to viewall objects. The above example selects the option Hide intermediateobjects to display only the source and final target objects.

This example shows that column Total_Order_Value impacts the followingfinal target objects:• Sales column within the same My DF source Data Federator system.• Actual_Sales column in the DIREPO Data Integrator system.



• DF_Deski report in the MySales BusinessObjects Enterprise system.

3. Move the pointer over the graphic of each object to display its information,such as table name, schema name, and catalog name.

4. Move the pointer over the "relationship attribute" icon to display how thedata is mapped to each final target from the intermediate object. Thisexample shows that the mapping is a SELECT statement between theintermediate universe object and the final target report DF_Deski.

To view the lineage of a report back to Data Federator tables

1. On the Impact tab for a column, click a final object, such as a report inan SAP BusinessObjects Enterprise system. For example, click DF_Deskireport in the previous Impact tab.

2. Click the Lineage tab of the report to display all columns in SAPBusinessObjects Data Federator target tables that affect the contents ofthe report. For example, click the Lineage tab to view the following Lineageanalysis.

3. Move the pointer over the graphic of each object to display its information,such as table name, schema name, and catalog name. This exampleshows that column Total_Order_Value is in Target tableFACT_SALES_ORDER in schema targetSchema and catalog /OP2.

4. Move the pointer over each Relationship Attribute icon between thesource and target objects within the My DF source system to display themapping rule name that extracts the data from source column and loadsit into the column in target table.

5. WIth many intermediate objects, you might need to scroll the page toview all objects. The following example clears the option Show



intermediate objects in Edit Settings to display only the first sourceobject and final target object.

Move the pointer over the relationship attribute icon to display the mappingrule name of each column in My DF source system. This example showsmapping rule mr_SalesOrdersFact for column Discount.

To view the lineage of a column

1. Click the Lineage tab to view all of sources for a column. For the samplecolumn Total_Order_Value, the following lineage analysis displays.



2. Move the pointer over the graphic of each object to display its information,such as table name, schema name, and catalog name. This exampleshows that column Quantity is in table Order Details in schemaForenzaSource and catalog /OP2/sources.





Relational DatabaseMetadata

13

Exploring Relational Database metadataSAP BusinessObjects Metadata Management stores metadata about objectsin selected source systems. Metadata Management Explorer organizes themetadata into a directory structure so that users can navigate and explorethe metadata objects in an easy to understand way.



• ETL (Extract, Transform, Load) which contains sources such asBusinessObjects Data Integrator

• Relational Databases which contains sources such as DB2, MySQL,Oracle, SQL Server, and Java Database Connectivity (JDBC). You canuse JDBC to specify a Teradata source



• Category - A category is a type of source system for which MetadataIntegrators collect metadata. The above list of categories show examplesof source systems for each category. When your administrator configuresa source system for Metadata Integrator, the source system displaysunder the appropriate category on the Metadata Management Explorer.

• Metadata Integrator - A Metadata Integrator is a program that extractsmetadata from a source system and loads it into the MetadataManagement Repository. Your administrator installs zero, one, or moreMetadata Integrators for each category and might configure multiplesource systems for each Metadata Integrator. For configurationinformation, see Configuring sources for Relational Database MetadataIntegrator on page 145.

• Metadata object - A unit of information that a Metadata Integrator createsfrom an object in a source system. For example, an SQL Server databasesource contains objects such as databases, schemas, and tables whichthe Metadata Integrator loads into the Metadata Management as metadataobjects Databases, Schemas, and Tables.


Relational Database Metadata13 Exploring Relational Database metadata

• Instance - An instance is an occurrence of a Metadata Integrator ormetadata object. For example, an SQL Server database source (such asForenza DW) is an instance of a Metadata Integrator in the RelationalDatabase category. An example of a type of metadata object is a table,and an instance of a table is FACT_SALES_ORDER.


• Navigating relational database metadata on page 395

• Viewing relationships in a database source on page 401

Navigating relational database metadataWhen you login to the SAP BusinessObjects Metadata Management Explorer,the Directory home page displays. To login, see Accessing MetadataManagement Explorer on page 197.

The Directory home page shows each configured source, grouped by theMetadata Integrator category in which it belongs.

Click Relational Database to display only the sources for this category.

Relational Database objects

The SAP BusinessObjects Metadata Explorer page for a relational databasesource shows the following object types if they exist in the source. Eachobject type can also contain associated objects, as the following table shows.


13Relational Database MetadataNavigating relational database metadata


Databases

A server instance is thedatabase, data source, orservice in the relationaldatabase managementsystem.

Server Instances

Schemas

A database is one ormore large structuredsets of persistent data,usually associated withsoftware to update andquery the data. A relation-al database organizes thedata and relations be-tween them into tables.

Databases

Synonyms

Views

Tables

Procedures

A schema is the definitionof a table in a relationaldatabase.

Schemas

Columns

A table is a collection ofrecords (records are alsoreferred to as rows) in arelational database.

Tables

Columns

A view is a subset ofcolumns or rows in a ta-ble or joined tables that auser can access.

Views

ParametersA procedure is a se-quence of instructions toperform a specific task.

Procedures


Relational Database Metadata13 Navigating relational database metadata

Exploring the Relational Database category

To view all the integrator sources in the Relational Database category:

1. Click Relational Database on the Directory home page.

The Relational Database category page shows:• The configured sources for the Relational Database Metadata

Integrator.• Under each source name are the first several metadata object types

that it contains, and the number in parenthesis indicates the numberof instances for that type. For example, a typical relational databasecontains object types Server Instances, Databases, and Schemas.

2. Click More... to display all object types in the source. You can also clickthe name of the source to display all of its object types.

For example, click Forenza Source or More... to see that this sourcecontains object types Server Instances, Databases, Schemas, Tables, Views, and Procedures.



Exploring Relational Database objects

To display all instances of an object type, click the object type name or ShowAll... For example, click Tables or Show All... to display all table instances.

Each metadata object page lists 10 instance names, in alphabetic order, thatthe source contains. If more than 10 tables exist, click the page links at thebottom to display each set of 10 instance names.



Exploring a table

Each instance of a table has individual attributes and relationships associatedwith it. The SAP BusinessObjects Metadata Management Explorer displaysthe following tabs for these attributes and relationships:

• Overview - Displays information about the table such as schema name,database name, and list of columns with their data type, length, and otherattributes.

• Same As - Displays any synonyms or aliases for this table. See Viewingsynonyms and alias relationships on page 402.

• Related To - Displays any relationships that you define for this table. SeeViewing relationships in a database source on page 401.

• Impact - Displays any objects that depend on the data in this table. SeeViewing impact and lineage on page 405.

• Lineage - Displays the sources (if any) for this table.

• User Defined - Displays any relationships that you define. SeeEstablishinguser-defined relationships between objects on page 260.

Exploring an instance of a column

Click a column name to display its properties and relationships associatedwith it. The SAP BusinessObjects Metadata Management Explorer displaysthe following tabs for the properties and relationships:

• Overview - Displays attributes such as Primary key, data type, and if itallows null values.

• Same As - Displays any synonyms or aliases (if any) for this table. SeeViewing synonyms and alias relationships on page 402.

• Related To - Displays primary key - foreign key relationships (if any) thatexists for this column. See Viewing primary key and foreign keyrelationships on page 404.

• Impact - Displays the objects that depend on the data in this column. SeeViewing impact and lineage on page 405.

• Lineage - Displays the sources (if any) for this table.



• User Defined - Displays relationships (if any) that you define. SeeEstablishing user-defined relationships between objects on page 260.

Exploring an instance of a view

Click a view name to display its properties and relationships associated withit. For example, click the Summary of Sales by Quarter view to display thefollowing Overview tab.

This page displays the following properties for the view:

• Schema name• Database name• SQL - Create view statement• List of columns with their data type, length, and other attributes

Note:For an Oracle materialized view, this Overview page shows the followingadditional properties:• Materialialized View: Yes• Refresh mode• Refresh method• Fast refreshable• Rewrite enabled



• Staleness• Last refresh date

Click the Lineage tab to display the tables, views, or combination of tablesand views from which the view is created. For the Summary of Sales byQuarter view, the following Lineage tab shows that this view is created from:

• Order Subtotals view, which is created from table Order Details

• Orders table

Note:When a view has a dependent obejct in another schema or database, theRelational Database Metadata Integrator collects metadata about thatdependent object. However, if the dependent object is another view, it doesnot collect metadata for that dependent object. Therefore, if the dependentobject is a view, you will not see it in the lineage diagram.

Viewing relationships in a databasesource

With SAP BusinessObjects Metadata Management Explorer you can viewrelationships between schemas, tables, and columns in your relationaldatabase sources. Metadata Management Explorer displays the followingrelationship analysis tabs:

• Same As tab: identifies an object that exists in different source systems,is a Synonym, or is Alias

• Related To tab: Primary Key - Foreign Key

• Impact: identifies other objects that are affected by data within this object.

• Lineage: identifies the sources of the data within this object.

• User-Defined: You can also establish user-defined relationships (seeEstablishing user-defined relationships between objects on page 260).


13Relational Database MetadataViewing relationships in a database source

Viewing synonyms and alias relationships

A synonym is another name for an object in the same system. For example,a synonym for a relational table exists in the same database as the table.

An alias is another name for an object in a different system. For example,an alias name in one database might refer to a relational table in a differentdatabase.

If synonyms or aliases exist in a relational database source, the MetadataExplorer shows it as an object type on the source page. The following sampleODS source page shows the Schemas object type has an instance ODSthat contains synonyms: Synonyms (2).

Note:SAP BusinessObjects Metadata Management displays synonyms for tablesand views only. Synonyms for other objects (such as functions andprocedures) do not display in the Metadata Management Explorer. For asynonym of a synonym on a table or view, Metadata Management displaystwo synonyms for the table or view.

Click Synonyms (2) to display more information about the two synonyms.The following Explorer pages shows that the synonyms contain views.


Relational Database Metadata13 Viewing relationships in a database source

Click the name of one of these synonyms to display information about theview. The Overview tab shows the following information:

• Schema name

• Database name

• SQL SELECT statement that the CREATE VIEW statement contains

• The Columns section lists a line for each column with its name, data typeand other attributes

The following example shows the "Overview" tab for PATH_VIEW.

Click the "Same As" tab to display the synonyms that are the same as theview.



Viewing primary key and foreign key relationships

If a column is a primary key or a foreign key, the SAP BusinessObjectsMetadata Management Explorer shows that relationship in the Related Totab. For example, column CUSTOMERID in table DIM_CUSTOMER is theprimary key as indicated by the key icon next to its name. The followingRelated To tab shows this relationship.

The graphical representation shows the current column with a blue shadedcolumn name. In this example, the relationship attribute shows the relationshipname "Primary-Foreign key" between the two columns.

Move your pointer to display the table name and schema name that containseach column. This example shows that the column CUSTOMERID is a foreignkey in table FACT_SALES_ORDER.



Viewing impact and lineage

Impact analysis allows you to identify which objects will be affected if youchange or remove other connected objects. In other words, what other objectsare affected by the data within this object. The Impact tab on an object'sExplorer page displays the other objects that this object impacts.

Impact and lineage relationships can exist between objects within the samesource (such as between a view and a table), and between objects in twodifferent sources (such as a target column in a Data Integrator source anda report in an SAP BusinessObjects Enterprise source).

The following example shows the Impact tab for column Address in tableCustomers.

This graphical view on the Impact tab shows:

• The impact of the Customer.Address column on objects within the ForenzaSource relational database system. Move the pointer over these objectsto display their object types, names, and schema. In this example, thetwo objects are views.

• The same Customer.Address column is used in the DIREPO DataIntegrator system, which loads it into a target table. Move the pointer overthe target table to display its name and schema. In this example, thetarget table is Dim_Customer.

• The same Dim_Customer.Address column is used in the MySalesBusinessObjects Enterprise system, which uses it for universe objectAddress that is used in reports "Product_Sales_by_Customer_webi" and"Product Sales by Customer.rpt."



Click a target object in the Data Integrator system and click the Lineage tabto show the corresponding lineage analysis. For example, click the targetAddress column in the DIREPO Data Integrator system and click the Lineagetab to show the following lineage analysis. This lineage analysis shows thatthe Dim_Customer.Address column in DIREPO obtains its data from theCustomer.Address column in Forenza Source.

In Edit Settings, clear Show intermediate objects to display just the firstsource column in the Relational Database source system and the final targetreports in the BusinessObjects Enterprise source system. The followingexample shows the Customer.Address column in the Forenza Source systemand the final target reports "Product_Sales_by_Customer_webi" and "ProductSales by Customer.rpt" in the MySales system.

You can also click tabular view to display a long impact analysis in a tableformat. The following example shows part of the tabular view for the Addresscolumn in table Customer.



This tabular view of the Impact tab shows that data in the source columnAddress goes through the following number of steps to reach the final targetobjects:

• Five steps to final target report "Product_Sales_by_Customer_webi"

• Four steps to final target reports "Product Sales by Customer.rpt."

For each step, the tabular view shows the source object, target object,relationship types, and mapping (if applicable). In this example, the tabularview shows information such as the following:

• In the first step, Address column in table Customer in the Forenza Sourcerelational database system has the following relationships:



• Same As relationship with column Customer.Address in the DI REPOsource system

• Impact relationship with the following objects in the same ForenzaSource relational database system:

• Address column in the Invoices view

• Address column in the Orders Qry view

• In the second step, Address column in table Customer in the DI REPOsource system has:

• An Impact relationship with Address column in the Dim_Customertable in the DI REPO source system

• The transformation df_CustomersDimension, which is the data flowin the DI REPO source system that extracts the data from the Customertable and loads the data into the Dim_Customer table.

• In the third step, Address column in table Dim_Customer in the DI REPOsource system has the following relationships:

• Same As relationship with the Address column in the Dim_Customertable in the MySales BusinessObjects Enterprise system

This Same As relationship appears three times because the Addresscolumn affects three target objects.

• In the fourth step, Address column in table Dim_Customer in the MySalesBusinessObjects Enterprise system has the following relationships withthe following objects in the MySales BusinessObjects Enterprise system:

• Impact relationship with the Address universe object in the DimCustomer universe class

• Impact relationship with report "Product Sales by Customer.rpt"

• Impact relationship with report "Product_Sales_by_Customer_webi"

• In the fifth step, Address universe object in the Dim Customer universeclass has an Impact relationship with report"Product_Sales_by_Customer_webi."



IndexAaccess levels

descriptions 124accessing Metadata Management 119add collected metadata 170administration

tasks for Metadata Management 118annotation

adding to object 221editing for object 222

Apache Tomcat 5.5configuration details 60

Bbacking up

integrator configurations 75BOE components

that BOMM uses 20BOMM components

run on BOE servers 20BusinessObjects Enterprise

metadata objects 273NetWeaver BW object relationships 277object relationships 275

BusinessObjects Enterprise componentshow Metadata Management uses 28

BusinessObjects Enterprise Integratorconfiguring 134

BusinessObjects Enterprise sourcemetadata objects 278relationships of objects within 286, 289

BusinessObjects Enterprise sourcesusers contained in 284

Ccatalogs

definition 371in deployed version 373

categorydefinition 272

CMSconnection information 56, 100

CMS personal folders 285CMS repository

Metadata Management objects 22collect

Crystal Reports 170universes 170Web Intelligence documents 170

collection resultsCrystal Reports 176Web Intelligence 176

columnsdefinition 371for target table 381

Common Warehouse Metamodel MetadataIntegratorconfiguring 139

components of Metadata Management 47, 91compute Relationship Table now 184configuration

BusinessObjects Enterprise metadataintegrator 168

configurations, SAP BusinessObjects MetadataManagementbacking up 74, 75restoring 75


configuringCommon Warehouse Metamodel Metadata

Integrator 139Metadata Integrator, BusinessObjects

Enterprise 134Data Federator Metadata Integrator 141Data Services Metadata Integrator 142Meta Integration Metadata Bridge (MIMB)

Metadata Integrator 144NetWeaver Business Warehouse Metadata

Integrator 136configuring Metadata Integrator

JDBC connections 148Relational Database 145universe connections 151

creating source groups 177Crystal Report

lineage from BW ODS 301custom attributes

usage 223customer support 17

DData Federator Metadata

catalogs 377datasources 378navigating 374object relationships 373object types 371target tables 378

Data Federator Metadata Integratorconfiguring 141overview 370

Data Federator objectsobject equivalency rules 385object relationships 373object types 371Same As relationships 385

data flowData Services object 354

data flow objectsin Data Services 353

Data Servicesdata flow objects 353object relationships 358Same As relationship 361support 17

Data Services Metadata Integratorconfiguring 142

Data Services sourceobjects contained in 348

Data Services source systemimpact on Crystal Reports 365

datasourcecatalog 377definition 371

datasource schemadefinition 371

deleting source groups 178deployed version

definition 371viewing target tables 378

deployment scenariohigh availability 40performance 37performance on small number of computers

38Directory home page 199distributing Metadata Management components

33

EEdit Settings

options to view relationships 219establish relationships

procedure to 260establish user-defined relationships

reasons to 259Explorer

categories in directory structure 370tasks you can do 196


Index

Explorer (continued)viewing Data Federator object types 375

export relational objectsprocedure to 248

Ggroups

finding privileges of 305object rights 308

Hhigh availability deployment scenario 40history of Metadata Integrator runs 175home page of Metadata Management Explorer

199

Iimpact analysis

of relational table 405Impact relationship

definition 383of a column 388of a table on a report 386

InfoCubenavigating to 324

installationscenarios 53, 97starting on UNIX 104starting on Windows 61UNIX permissions 90

installing metadata integrators 133instance

definition 272integrator configurations

backing up 74, 75restoring 75

integrator sourceschanging limits for 156

integrator sources (continued)configuring 133managing tasks 153types of 118viewing and editing 154

JJDBC connection sources

configuring 148

Kkey coe 55

Llicense key

updating 83, 115License keys

description 53, 97lineage

to source table 405viewing from InfoView for Web Intelligence

documents 134Lineage relationship

definition 383for a column 388

lineage report utilityconfiguring 180options 182

lineage staging table 179recalculate lineage information 180

lineage utilityrun now 184

log levelchanging 164

log, viewing for lineage utility 184logging level

descriptions 164logs, viewing 175


Index

Mmapping rule

definition 371for target table 381

Meta Integration Metadata Bridge (MIMB)Metadata Integratorconfiguring 144

Metadata Explorer search indexmodifiying utility to recreate 187recreating 188

metadata integratorscheduling 159

Metadata Integratorchanging log level 164definition 272

Metadata Integrator historyviewing 175

Metadata Integrator logsdescription 164viewing 175

Metadata Integrator, Common WarehouseModelconfiguring 139

metadata integratorsrun-time parameters 166running 162server groups 83, 106when you install Metadata Management

133Metadata Integrators

definition 25prerequisites 34running 158running immediately 158selecting 57tasks 153

Metadata Managementaccess levels 124accessing 119administration tasks 118architecture 20

Metadata Management (continued)choosing components 47, 91CMS repository objects 22configuring repository 59license agreement 55product key code 55, 100running installation program 54software requirements 45, 89standard installation on UNIX 98standard installation on Windows 54uninstalling on UNIX 116uninstalling on Windows 84users and groups 123utilities 179

Metadata Management componentsdistributing 33prerequisites 34selecting 57, 102

Metadata Management repositorycreating database for 52, 96requirements 51, 95

metadata objectdefinition 272

Metapediadata steward 234import and export data 239overview 231search 242

MMT_Alternate_Relationship tabledescription 179scheduling computation of 182

modifying source groups 178

Nnavigating to reports 306navigating to universes 306NetWeaver Business Warehouse Metadata

Integratorconfiguring 136


Index

NetWeaver Business Warehouse metadataobjectsdescriptions 314

NetWeaver BW metadata integratorrunning 172

NetWeaver BW objectsInfoCube 325used in Crystal Report 297

NetWeaver BW sourcerelationships of objects within 327

NetWeaver BW source systemimpact on Crystal Reports 330impact on Web Intelligence Documents

329, 331impact relationship on objects 327lineage of Crystal Report 333relationship of objects 319, 320

network requirements 45, 89

Oobject collection

selective 170object equivalency rules

definition 267preferences for relationships 264setting 267, 385

object relationshipsin Data Services 358

Open Hub tables in Data Servicesimpact on Crystal Reports 365

Oracle Application Server 10g R3configuration details 60

Oracle materialized viewsmetadata collected for 400

Pparameters to run metadata integrators 166performance deployment scenario 37

small number of computers 38

permissionsobject rights 308

personal foldercollection results 286

personal foldersexplore 285

pre-installation tasksoverview 44, 88

preferences for relationshipschanging 264

privilegesof groups 305

Qqualified table name

in multiple source systems 265Query Server

definition 371

RRelational Database Metadata Integrator

configuring 145Relationship Server

description 27prerequisites 34

relationships between objectsdefinitions 212primary key and foreign key 404synonyms and alias 402

Remote Job Serverchanging configuration of 79collecting metadata from BusinessOjbects

Enterprise XI R2 76installing 77renaming File Repository Servers 78

report metadata object 281reports

finding users that can access 303impact on users and groups 306


Index

Reports tablineage staging table 179

Repository, Metadata Managementcreating 59

repository, SAP BusinessObjects MetadataManagementexporting to xml 190migrating 70, 112

response filefor silent installation 64, 107

restoringintegrator configurations 75

rightsfor Metadata Management objects 125

running metadata integrators 162, 166

SSame As relationship

in Data Services 361object equivalency rules 267qualified table name 265

SAP BusinessObjects Enterprise universelineage from SAP NetWeaver BW objects

300SAP BusinessObjects Metadata Management

benefits 16configurations, backing up 74, 75configurations, restoring 75exporting repository to xml 190overview 14repository, migrating 70, 112

SAP NetWeaver Business Warehouse systemnavigating metadata objects 323

schedulingmetadata integrator 159

scope of search 203search for objects

advanced search 204scope of 203wildcard characters 203

search index recreation utilityconfiguring 186

search index, recreating 188modifying configuration 187

Search Serverdescription 27prerequisites 34

searching for objectsresults 206

security 122for Metadata Management 22

selecting Metadata Management components57, 102

server groupsfor metadata integrators 83, 106

serversrequired for Metadata Management 120status for Metadata Management 122verify runnings 82

silent installationdescription 63, 107parameters 66, 109response file 64, 107starting 65, 110

source groupscreating 177deleting 178metadata sources 177modifying 178

SSL optionsspecifying 56, 100

support, Data Services 17

Ttable lineage

column mappings view 366graphical view 361

target schemadefinition 371

Test indextermin cell of a table 134


Index

time outMetadata Management sessions 119

type-specific rightsMetadata Management objects 125

Uuniverse connection sources

configuring 151universes

finding users that can access 303impact on users and groups 306

UNIXinstallation 98

UNIX permissionsrequired for installation 90

updating license key 83, 115upgrade

objects that migrate 68, 69, 111users

privileges to reports and universes 303creating 130metadata 284navigating to 303object rights 308privileges 303

users and groupsaccess levels for 123

utilities, Metadata Managementdescription 179

utiltieschanging limits for 156

Vviews

metadata collected for 400

Wweb application server

configuration details 60Web application server 23Web Intelligence documents

viewing lineage from InfoView 134WebLogic 10

configuration details 60WebLogic 9

configuration details 60WebSphere 6.1

configuration details 60WebSphere Community Edition 2.0

configuration details 60


Index


Index