This guide describes the purpose, installation, configuration, and usage of
SAP® BusinessObjects™ Metadata Management.
The expected audience for this technical information include:
•Administrators who install and configure SAP BusinessObjects Metadata
Management and its components.
•Application developers, business report designers, consultants, and
database administrators who perform any of the following tasks:
•Browse and search metadata to determine relationships and analyze
the impact of changes to source data.
•Define and maintain Business Intelligence reports.
•Extract data, build and maintain data warehouses, or integrate data
from multiple sources.
•Define, organize, and maintain business terms.
SAP BusinessObjects Metadata
Management overview
SAP BusinessObjects Metadata Management is a Web-based application
that provides an integrated view of metadata and their relationships across
all of the products used in a Business Intelligence project.
Metadata is definitional data that provides information about data managed
within 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, or
characteristics of the data
As the following diagram illustrates, the software collects and unifies metadata
from data sources such as:
•Data Integration technologies, such as SAP BusinessObjects Data
Services and SAP BusinessObjects Data Federator
•Modeling utilities
1
You can enrich the collected metadata with the following information, which
you can use to search for objects and perform analysis on the resulting
objects.
•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 sensitive
information.
•Metapedia terms and categories–You can implement a business glossary
of terms related to your business data and organize the terms
hierarchically.
You can export relational objects from the SAP BusinessObjects Metadata
Management repository to a Common Warehouse Modeling (CWM) XML
file. You can then import the CWM XML file into SAP BusinessObjects
Enterprise to create a universe.
SAP BusinessObjects Metadata Management User's Guide15
Page 16
Introduction
1
Product benefits
Product benefits
With 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 what
sources provide data for your Business Intelligence reports.
•Analyze the impact of changing a source table, column, or report field on
your 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 business
terms to objects, and search for metadata objects using familiar business
terms.
•Analyze the metadata to determine usage of objects by other objects,
such as how many reports are based on this universe or what tables are
in this universe.
These capabilities provide the following benefits:
•Lower your total cost of ownership (TCO) because you can do the
following:
•Track usage of data and reports
For example, you can determine which data in your data warehouse
is never used in your Business Intelligence reports or which reports
are never viewed by users.
•Manage change
For example, you can determine which Business Intelligence reports
would be affected if you modified your source tables and you can
identify 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 has
for accessing reports or data universes.
•Enable the discovery, common understanding, and consistent
implementation of business concepts through Metapedia, bridging the
gap of understanding between an organization's business users and IT
staff.
•Understand your entire Business Intelligence project because you can
view the relationships (such as impact and lineage) of all metadata objects
from your data integration system to your relational databases to your
Business Intelligence reports.
Product documentation
Your product CD provides the SAP BusinessObjects Metadata Management
documentation in PDF format. You can read PDF files using the latest version
of Adobe Acrobat Reader (download instructions at the Adobe website
To view these documents after you install the software, go to the Start menu,
select Programs > BusinessObjects XI 3.1 > BusinessObjects MetadataManagement, and choose:
•Release Notes–Opens the Release Notes PDF document, which includes
supported configurations and known problems in the associated software
release.
•User's Guide–Opens this document, which describes the purpose,
installation, configuration, and usage of the software.
Introduction
Product documentation
1
Obtain other relevant documents by visiting the Technical Customer
Assurance documentation page at http://service.sap.com/.
SAP BusinessObjects information
resources
A global network of SAP BusinessObjects technology experts provides
customer support, education, and consulting to ensure maximum business
intelligence benefit to your business.
Useful addresses at a glance:
ContentAddress
SAP BusinessObjects Metadata Management User's Guide17
Page 18
Introduction
1
SAP BusinessObjects information resources
ContentAddress
Customer Support, Consulting, and Education services
http://service.sap.com/
SAP BusinessObjects Data Services Community
https://www.sdn.sap.com/irj/boc/ds
Forums on SCN (SAP Community Network
https://www.sdn.sap.com/irj/scn/forums
Blueprints
http://www.sdn.sap.com/irj/boc/blueprints
Information about Technical Customer Assurance
programs, as well as links to technical articles,
downloads, and online forums. Consulting services
can provide you with information about how SAP
BusinessObjects can help maximize your business
intelligence investment. Education services can
provide information about training options and
modules. From traditional classroom learning to
targeted e-learning seminars, SAP BusinessObjects can offer a training package to suit your
learning needs and preferred learning style.
Get online and timely information about SAP BusinessObjects Data Services, including tips and
tricks, additional downloads, samples, and much
more. All content is to and from the community, so
feel free to join in and contact us if you have a
submission.
Search the SAP BusinessObjects forums on the
SAP Community Network to learn from other SAP
BusinessObjects Data Services users and start
posting questions or share your knowledge with
the community.
Blueprints for you to download and modify to fit
your needs. Each blueprint contains the necessary
SAP BusinessObjects Data Services project, jobs,
data flows, file formats, sample data, template tables, and custom functions to run the data flows in
your environment with only a few modifications.
SAP BusinessObjects product documentation.Product documentation
http://help.sap.com/businessobjects/
Products Availability Report
https://service.sap.com/bosap-support
Get information about supported platforms for SAP
BusinessObjects Data Services.
In the left panel of the window, navigate to Documentation > Supported Platforms > BusinessObjects XI 3.x. Click the BusinessObjects Data
Services link in the main window.
SAP BusinessObjects Metadata Management runs on the SAP
BusinessObjects Enterprise platform which is designed for high performance
across a broad spectrum of user and deployment scenarios. You can offload
processor intensive scheduling and processing to dedicated servers to
improve performance. The architecture is designed to meet the needs of
virtually any business intelligence (BI) deployment.
This section describes how the components of SAP BusinessObjects
Metadata Management fit into the overall platform architecture and individual
services and components that make up SAP BusinessObjects Enterprise.
This information will help administrators understand how to plan the
deployment, management, and maintenance of the metadata management
application.
Related Topics
•Architecture overview on page 20
•Metadata Management on BusinessObjects Enterprise components on
page 28
Architecture overview
The following diagram shows the SAP BusinessObjects Enterprise (BOE)
components that SAP BusinessObjects Metadata Management (BOMM)
uses.
The following table shows each SAP BusinessObjects Metadata Management
component and which BusinessObjects Enterprise component it runs on.
SAP BusinessObjects Metadata
Management component
Administration and Explorer applications
Metadata Management CMS Respository Objects
Metadata Integrators and utilities
SAP BusinessObjects Metadata Management User's Guide21
SAP BusinessObjects Enterprise
component on which it runs
BusinessObjects Enterprise Platform
Application Server
Central Management System (CMS)
•Metadata Management Job Server
(Adaptive Job Server)
•Adaptive Processing Server
Page 22
Architecture
2
Architecture overview
SAP BusinessObjects Metadata
Management component
Related Topics
•Web Application Server on page 23
•Central Management System repository objects for Metadata Management
on page 22
•Metadata integrators on page 25
•Search Server on page 27
SAP BusinessObjects Enterprise
component on which it runs
Adaptive Processing ServerRelationship Server
Adaptive Processing ServerSearch Server
Central Management System repository objects for
Metadata Management
The Central Management System (CMS) stores information that describes
the SAP BusinessObjects Metadata Management application and the
operations of the servers that Metadata Management uses for processing.
CMS uses these repository objects to manage SAP BusinessObjects
Enterprise, including the following tasks for Metadata Management:
•Managing security
The CMS manages security information, such as user accounts, group
memberships, and object rights that define user and group privileges to
access the different features of Metadata Management.
•Managing servers
When you define multiple Job Servers to run metadata integrators, the
CMS monitors these server and distributes the work processes among
them. The CMS handles load balancing and automated clustering to avoid
bottlenecks and maximize hardware efficiency.
For more information about CMS, refer to the BusinessObjects EnterpriseAdministrator's Guide.
•Managing security in Metadata Management on page 122
Web Application Server
SAP BusinessObjects Metadata Management requires a Java or Servlet
web application server to process the server-side scripts that make up web
applications 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
Architecture
Architecture overview
2
Note:
For specific version compatibility, 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.
Related Topics
•Administration on page 23
•SAP BusinessObjects Metadata Management Explorer on page 24
Administration
You use the Central Management Console (CMC) to perform SAP
BusinessObjects Metadata Management administrative tasks such as the
following:
•Configure and run metadata integrators
•Define source groups to subset the metadata when viewing relationships
such as Same As, Impact, and Lineage
SAP BusinessObjects Metadata Management User's Guide23
Page 24
Architecture
2
Architecture overview
•Administer security for the SAP BusinessObjects Metadata Management
Explorer, 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-based
interface through which you can:
•View the metadata from the different sources in an organized and easy
to understand way.
•Search for objects without the need to know the source or application in
which it exists.
•Define Metapedia terms related to your business data and organize the
terms 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 reports
are using my tables?"
•View relationships between objects, reports and documents that you
create with BusinessObjects Business Intelligence products. Relationships
include 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
•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 metadata
integrators:
Architecture
Architecture overview
Metadata collectedMetadata integrator name
2
SAP BusinessObjects Enterprise
Metadata Integrator
SAP NetWeaver Business Warehouse
Metadata Integrator
Common Warehouse Model (CWM)
Metadata Integrator
SAP BusinessObjects Data Federator
Metadata Integrator
SAP BusinessObjects Metadata Management User's Guide25
Collects metadata about objects such
as universes, Crystal Reports, Web Intelligence documents, and Desktop Intelligence documents.
Collects metadata about objects such
as Queries, InfoProviders, InfoObjects,
Transformations, and DataSources
from an SAP NetWeaver Business
Warehouse system.
Collects metadata about objects such
as catalogs, schemas, and tables from
the CWM Relational Package.
Collects metadata about objects such
as projects, catalogs, datasources, and
mapping rules from a Data Federator
repository.
Page 26
Architecture
2
Architecture overview
SAP BusinessObjects Data Services
Metadata Integrator
Meta Integration Metadata Bridge
(MIMB) Metadata Integrator (also
known as MITI Integrator)
Metadata collectedMetadata integrator name
Collects metadata about objects such
as source tables, target tables, and
column mappings from a Data Services
repository.
Collects metadata from other thirdparty sources such as the following:
•Data Modeling metadata such as
Sybase Power Designer, Embarcadero ER/Studio, and Oracle Designer
•Extract, Transform, and Load (ETL)
metadata such as Oracle Warehouse Builder, SAS ETL Studio,
and Microsoft SQL Server Integration Services (SSIS)
•OLAP and BI metadata such as
IBM DB2 Cube Views, Oracle
OLAP, and Cognos BI Reporting
Collects metadata from relational
database management systems
(RDBMS) which can be DB2, MySQL,
Relational databases Metadata Integrator
Oracle, SQL Server, Java Database
Connectivity (JDBC), or a BusinessObjects Universe connection. Collected
metadata includes the definition of objects such as tables, view, synonyms,
and aliases.
You can also obtain third-party metadata integrators for other data sources.
For more information about third-party metadata integrators, contact your
sales 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
•Exploring Relational Database metadata on page 394
•Deployment scenarios on page 36
Relationship Server
The Relationship Server computes metadata object relationships (such as
data lineage and change impact analysis). The SAP BusinessObjects
Metadata Management Explorer uses the results of these computed
relationships to display metadata relationship diagrams.
It is recommended that you install the Relationship Server on a different
computer than the web application server. An Adaptive Processing Server
of SAP BusinessObjects Enterprise must already be installed on that
computer.
You can deploy multiple Relationship Servers for load balancing and
availability.
Architecture
Architecture overview
2
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 source
while viewing metadata on the SAP BusinessObjects Metadata Management
Explorer. It uses the Lucene Search Engine.
The Search Server runs on an Adaptive Processing Server of SAP
BusinessObjects Enterprise. You can deploy multiple search servers for load
balancing and availability.
The Search Server constructs the search index during the execution of the
Metadata Integrators, and the File Repository Server stores the compressed
search index. The Search Server also updates the search index for changes
to Metapedia terms and categories, custom attributes, and annotations. If
the Search Server is not available during the construction and update
processes, the search might return incorrect results. For these situations,
SAP BusinessObjects Metadata Management User's Guide27
Page 28
Architecture
2
Metadata Management on BusinessObjects Enterprise components
Metadata Management provides a utility to reconstruct the search index. For
details, see Recreating search indexes on page 185.
Related Topics
•"Metadata Management Architecture"
•Deployment scenarios on page 36
Metadata Management on
BusinessObjects Enterprise components
The following table describes how SAP BusinessObjects Metadata
Management uses each pertinent SAP BusinessObjects Enterprise
component.
SAP BusinessObjects
Enterprise component
SAP BusinessObjects
Enterprise Application
Server
Central Management
Console (CMC)
How SAP BusinessObjects Metadata Management uses component
Deploys the SAP BusinessObjects Metadata Management application which consists of:
•Metadata Management on CMC
•Metadata Management Explorer
Manages the following for SAP BusinessObjects
Metadata Management:
Metadata Management on BusinessObjects Enterprise components
2
SAP BusinessObjects
Enterprise component
Central Management
Server (CMS)
Metadata Management
Job Server
Adaptive Processing
Server
How SAP BusinessObjects Metadata Management uses component
Responsible for maintaining a database of information about your SAP BusinessObjects Enterprise
system. The data stored by the CMS includes information about users and groups, security levels, SAP
BusinessObjects Enterprise content, and servers.
For more information about the CMS, see SAPBusinessObjects Enterprise Administrator's Guide.
When you create a configuration for a metadata
integrator source, SAP BusinessObjects Metadata
Management stores the configuration in CMS.
Launches the scheduled execution of a metadata
integrator or a Metadata Management utility.
When you install SAP BusinessObjects Metadata
Management on an Adaptive Job Server, you also
install metadata integrator types for sources installed in CMS.
Runs the following for SAP BusinessObjects Metadata Management:
•Relationship Service
•Search Service
•Test Connection Service for integrator sources
File Repository Server
SAP BusinessObjects Metadata Management User's Guide29
Stores files associated with the execution of a
metadata integrator or a search. These files include
the metadata integrator definitions, history logs, and
search indexes.
Page 30
Architecture
Metadata Management on BusinessObjects Enterprise components
To provide flexibility, reliability, and scalability, you can install the components
that make up SAP BusinessObjects Enterprise on one or many machines.
You can also install the components of SAP BusinessObjects Metadata
Management on one or many machines to take advantage of the same
benefits.
Server processes can be "vertically scaled" (where one computer runs
several, or all, server-side processes) to reduce cost, or "horizontally scaled"
(where server processes are distributed between two or more networked
machines) to improve performance. You can also run duplicate instances of
a server process on the same machine, or across several networked
machines.
For example with Metadata Management, you can install multiple Adaptive
Job Servers to run Metadata Integrators on separate computers to distribute
the workload and improve performance. You can also install the Search
Server on an Adaptive Processing Server on a different computer from the
Adaptive Job Servers. For sample deployments, see Deployment scenarios
on 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 needs
and suggestions for deployment scenarios. By evaluating your needs before
you deploy your SAP BusinessObjects Metadata Management system, you
can keep troubleshooting to a minimum.
The section includes examples and suggestions for deployment, but it is
important to note that each deployment is unique. The flexibility of the SAP
BusinessObjects Enterprise service-based architecture allows you to tailor
the deployment to serve your organization's requirements as precisely as
possible.
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 server
considerations, in addition to security, performance and scalability, and
high availability. See "Assessing your organization's environment" in the
SAP BusinessObjects Enterprise XI 3.0 Deployment Planning Guide.
3. Choose an initial deployment architecture. Which deployment architecture
will serve your needs within the limits of your resources?
For suggestions and common configurations, see Deployment scenarios
on page 36.
Deployment guidelines
Guidelines to deploy SAP BusinessObjects Metadata Management
components 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 Processing
Server, and Adaptive Job Servers to obtain a higher throughput.
•To improve database throughput, the Metadata Management repository
should be near the job server that processes the largest amount of data.
Therefore, you can install the repository on the same computer as the
Metadata Integrator that processes the largest amount of data.
•The Relationship Server should be on a separate computer than the web
application 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 this
combination is that Metadata Integrators usually run at night or other
non-business hours, and the Relationship Server runs during normal
business hours when users are viewing relationships (such as impact
and 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 that
Metadata Integrators usually run at night or other non-business hours,
Deployment
Deployment
3
SAP BusinessObjects Metadata Management User's Guide33
Page 34
Deployment
3
Deployment
and the Search Server runs during normal business hours when users
are searching on the Metadata Management Explorer.
•If your Metadata Integrators runs are constrained by a small execution
window, deploy each Metadata Integrator on a separate computer.
•For high availability, you can deploy a Metadata Integrator on multiple
computers. 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 Management
components on each computer, you must have the necessary software
already installed on that computer. The following table shows the prerequisite
software for each component.
Prerequisite softwareFeature category
Metadata Management CMS
Repository Objects
Note:
You must install this component first
(to build the Metadata Management
repository). Then you can install the
rest of the Metadata Management
components in any order on any
computer.
The CMS component of SAP BusinessObjects Enterprise XI 3.0.1 and above
Page 35
Metadata Integrators
Note:
You must install this component on a
supported Windows platform.
Deployment
Deployment
Prerequisite softwareFeature category
•Metadata Management CMS Repository Objects
component must already be installed (not necessarily on this computer)
•Following components of SAP BusinessObjects
Enterprise XI 3.0.1 and above:
•Adaptive Job Server
•Adaptive Processing Server
•Client libraries for the source system installed on
this computer. For example, the SAP BusinessObjects Enterprise Metadata Integrator requires SAP
BusinessObjects Enterprise Full Client installed on
this computer.
•For the BusinessObjects Enterprise Metadata Inte-
grator to collect Crystal Reports or universes whose
sources are SAP NetWeaver BW objects, you must
install the BusinessObjects XI Integration for SAP
Solutions on SAP BusinessObjects Enterprise
(BOE). This requirement is for reports that were
created with the Refresh on Open option because
when the Metadata Integrator collects the metadata
from the BOE system, the BOE system will connect
to the source BW system to refresh the data automatically.
•The BusinessObjects Enterprise Metadata Inte-
grator supports two drivers: SAP BW MDX
Query and SAP Operational Data Store.
•The BusinessObjects XI Integration for SAP
Solutions has prerequisites that you must install.
For more information, see the BusinessObjects
XI Integration for SAP Installation Guide.
3
Metadata Management Relationship
Server
Note:
You must install this component on a
supported Windows platform.
SAP BusinessObjects Metadata Management User's Guide35
Installing this Metadata Integrator installs the Metadata Management Job Server (MMJobServer).
•Metadata Management CMS Repository Objects
component must already be installed (not necessarily on this computer)
•Adaptive Processing Server component of SAP
BusinessObjects Enterprise XI 3.0.1 and above
Page 36
Deployment
3
Deployment
Prerequisite softwareFeature category
Metadata Management Search
Server
Note:
You must install this component on a
supported Windows platform.
Web Application
Related Topics
•To manually deploy web application server components on page 62
Deployment scenarios
•Metadata Management CMS Repository Objects
component must already be installed (not necessarily on this computer)
•Adaptive Processing Server component of SAP
BusinessObjects Enterprise XI 3.0.1 and above
•Metadata Management CMS Repository Objects
component must already be installed (not necessarily on this computer)
•Web Application Server where SAP BusinessOb-
jects Enterprise applications are deployed
Note:
If you are manually installing the Web Application, you
you must copy a .war file.
After you determine the needs of your users and the resources required for
the deployment, you can develop an initial deployment plan for SAP
BusinessObjects Metadata Management.
This section describes sample scenarios for administrators planning an
installation of Metadata Management. It is important to note that the optimal
configuration for your deployment will depend on many factors: hardware
configuration, 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 as
guidelines.
This scenario illustrates a situation in which your Metadata Integrators run
might take several hours to complete, and you want to ensure it has enough
resources to complete as fast as possible. The following diagram shows how
the components of SAP BusinessObjects Enterprise (BOE) and SAP
BusinessObjects Metadata Management (BOMM) are deployed on seven
computers.
Deployment
Deployment
3
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:
SAP BusinessObjects Metadata Management User's Guide37
Page 38
Deployment
3
Deployment
•The CWM Integrator is run very infrequently. Therefore, the CWM
Metadata Metadata Integrator and RDBMS Metadata Integrator can
be installed on the same computer (SJ-PS-02).
•The Relationship Server is run during the day and can be installed on
a computer with any Metadata Integrator, which is usually run at night.
The The SAP NetWeaver BW Metadata Integrator (BW Integrator) is
run 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 frequently
and processes a large amount of metadata. Therefore, it is installed
on its own computer (SJ-PS-04).
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, including
the 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 run
might take several hours to complete, but you have a limited number of
computers. The following diagram shows how the components of SAP
BusinessObjects Enterprise and SAP BusinessObjects Metadata
Management are deployed on four computers.
•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 Business
Warehouse (BW) Metadata Integrator.
The rationale to combine these components is that the execution time s
not very long for each of these Metadata Integrator and they can be
scheduled to run at different times.
SAP BusinessObjects Metadata Management User's Guide39
Page 40
Deployment
3
Deployment
•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 Management
repository (BOMM Repository). The assumption is that the CWM Integrator
runs very infrequently compared to the BusinessObjects Enterprise
Integrator.
Note:
To improve database throughput, the Metadata Management repository
should be near the job server that processes the largest amount of data.
Therefore, you can install the repository on the same computer as the
Metadata Integrator that processes the largest amount of data.
•1 web application server (SJ-WS-01) to host CMC applications, including
the Metadata Management application.
Scenario 3: High availability
This example shows a scenario in which you want to ensure that computers
are always available to run Metadata Integrators and the Relationship Server,
and therefore you have redundant installations. The following diagram shows
a possible deployment of redundant Metadata Integrators and Relationship
Servers across multiple computers.
SAP BusinessObjects Metadata Management provides an open and flexible
architecture that supports a multitude of deployment and configuration
scenarios. 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 Metadata
Management repository and prepare the database.
•Determine your installation method.
The following sections list the software and system requirements and the
install methods available to you for installing SAP BusinessObjects Metadata
Management.
Note:
The following Metadata Management components can only be installed on
Windows (you cannot install them on UNIX):
•Metadata Integrators
•Search Server (provides ability to search metadata on the Metadata
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://ser
vice.sap.com/bosap-support. This document includes specific version and
patch-level requirements for databases, applications, web application servers,
web browsers, and operating systems.
Generally, the following components must be preinstalled and configured
correctly 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 this
computer. See Prerequisites for each component on page 34.
Installation for Windows
Preparing to install Metadata Management
4
Metadata Management uses the Web application server and Java 2
Software Development Kit (JDK) that BusinessObjects Enterprise uses.
Note:
For UNIX, you must increase the memory setting for Web Logic in the
following directory: Weblogic_install/wlserver_10.0/samples/do
mains/wl_server/bin/setDomainEnv.sh. Change the value of the
parameter -XX:MaxPermSize from 128m to 256m .
Note:
To install Metadata Management, you must be the BusinessObjects
Enterprise Administrator.
Network requirements
When installing SAP BusinessObjects Metadata Management on multiple
computers, you must ensure that:
SAP BusinessObjects Metadata Management User's Guide45
Page 46
Installation for Windows
4
Preparing to install Metadata Management
•each target machine can communicate over TCP/IP with the machine
running the Central Management Server (CMS).
•the target machines can communicate over TCP/IP with each other. In
particular:
•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 Metadata
Management Explorer and machines where Metadata Integrators are
deployed.
For more information on the communication between components, refer to
Architecture on page 19.
User permissions for installing Metadata Management
To successfully install SAP BusinessObjects Metadata Management on
Windows, the user running the setup program must have the permissions
listed in the table below:
Administrative privileges on the local machine.Operating Sys-
4
Network
SAP BusinessObjects Enterprise
Database
Web application
server
TCP/IP access to all machines where you want to install
components - all specified ports must be available.
You must be the SAP BusinessObjects Enterprise Administrator.
Rights to add and drop database objects (such as tables and
views), plus rights to read, write, and edit table rows.
It is recommended that you use the same user account for
installing BusinessObjects Enterprise and your web application server.
To deploy Metadata Management web applications using
a user account different from the one used to install the
web application server, see "Minimum user rights for deploying web applications" in the BusinessObjects Enter-prise XI 3 Installation and Configuration Guide.
Choose components and determine component distribution
You can choose to install SAP BusinessObjects Metadata Management
components on one or more computers based on available resources and
your deployment planning. For guidelines and suggested scenarios to
distribute 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 Adaptive
Processing Server installed on it.
The following table shows the software components and their
sub-components that you can choose.
SAP BusinessObjects Metadata Management User's Guide47
Page 48
Installation for Windows
4
Preparing to install Metadata Management
DescriptionComponentFeature cateogry
Metadata Management CMS Repository Objects
Metadata Management
CMS Repository Objects
Includes definitions and location information for the SAP BusinessObjects Metadata Management application, repository,
and other objects.
SAP BusinessObjects Enterprise Metadata Integrator
SAP NetWeaver Business
Warehouse Metadata Integrator
Installation for Windows
Preparing to install Metadata Management
DescriptionComponentFeature cateogry
Extracts information from an SAP BusinessObjects Enterprise repository that includes metadata objects such as SAP
BusinessObjects Crystal Reports, Web
Intelligence documents, and Desktop Intelligence documents.
Extracts information from a NetWeaver
Business Warehouse system which includes metadata objects such as Queries,
InfoProviders, InfoObjects, Transformations, and DataSources.
4
Metadata Integrators
Common Warehouse Model (CWM) Metadata Integrator
Relational Databases
(RDBMS) Metadata Integrator
SAP BusinessObjects Data
Services Metadata Integrator
SAP BusinessObjects Data
Federator Metadata Integrator
Extracts information from the CWM Relational Package that includes definitions of
metadata objects such as catalogs,
schemas, and tables.
Extracts information from an RDBMS that
includes definitions of metadata objects
such as catalogs, schemas, stored procedures, and aliases.
Supported relational databases include
DB2, MySQL, Oracle, SQL Server,
Teradata, or a Universe connection using JDBC or ODBC. For complete details, see the Supported Platforms document.
Extracts information from an SAP BusinessObjects Data Services repository which
includes definitions of metadata objects
such as source tables and columns for
ETL jobs, datastores and configurations,
and flat files.
SAP BusinessObjects Metadata Management User's Guide49
Page 50
Installation for Windows
4
Preparing to install Metadata Management
Meta Integration Metadata
Bridge (MIMB) Metadata
Integrator
DescriptionComponentFeature cateogry
Extracts information from an SAP BusinessObjects Data Federator repository which
includes definitions of metadata objects
such as projects, catalogs, datasources,
and mapping rules.
Extracts the following metadata from other
sources:
•Data Modeling metadata such as
Sybase Power Designer, Embarcadero
ER/Studio, and Oracle Designer
•ETL metadata such as Oracle Ware-
house Builder, SAS ETL Studio, and
Microsoft SQL Server Integration Services (SSIS)
•OLAP and BI metadata such as IBM
DB2 Cube Views, Oracle OLAP, and
Cognos 8 BI Reporting
Processes object relationships (for example, impact and lineage).
Provides search capability on SAP BusinessObjects Metadata Management Explorer.
Page 51
Web Application
Related Topics
•Architecture overview on page 20
Installation for Windows
Preparing to install Metadata Management
DescriptionComponentFeature cateogry
Provides web applications that:
•administer SAP BusinessObjects
Metadata Management on the Central
Management Console (CMC)
•comprise the SAP BusinessObjects
Metadata Management Explorer
Note:
If SAP BusinessObjects Enterprise has
manually deployed the web application,
follwo the steps in the Manually deploy
web application procedure.
4
Repository database requirements and preparation
The SAP BusinessObjects Metadata Management repository is a database
that stores all metadata that the Metadata Integrators collect. You use the
information in the repository to analyze relationships between objects, as
well as to analyze impact and lineage between objects. For example, you
can find the tables and columns used by your Business Intelligence reports
and documents.
You can either create a new database for the repository or use an existing
repository. The SAP BusinessObjects Metadata Management installation
process will either create new tables or upgrade the existing tables within
the repository.
Related Topics
•Setting up a new database on page 52
•Exploring SAP BusinessObjects Enterprise metadata on page 272
SAP BusinessObjects Metadata Management User's Guide51
Page 52
Installation for Windows
4
Preparing to install Metadata Management
Setting up a new database
This procedure creates a SAP BusinessObjects Metadata Management
Repository database and configures it for the user who will connect to it. The
installation process will create the tables within the Metadata Management
Repository.
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 database
software and version requirements, see the Products Availability Report
available 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 database
as required.
Note:
If you are not the owner of the database, you must have permissions to
perform the necessary operations.
Related Topics
•To configure your Metadata Management repository on page 59
from a development to test environment or from a test to production
environment.
•Back up and restore configurations -- Backs up and restores integrator
source configuraitons Metadata Management utility configurations, and
integrator source groups.
•Distributed deployment – Installs a subset of Metadata Management
components on each computer that has the prerequisite software.
Installation for Windows
Preparing to install Metadata Management
4
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 Metadata
Management 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
SAP BusinessObjects Metadata Management User's Guide53
Page 54
Installation for Windows
4
Standard installation of Metadata Management
•Updating the license key on page 115
Standard installation of Metadata
Management
Before beginning your installation, review the Pre-installation overview to
ensure that you have prepared all necessary systems.
The following instructions lead you through the standard installation steps
of setting up your SAP BusinessObjects Metadata Management on Windows:
1.
To begin running the installation program on page 54
2.
To accept the license agreement on page 55
3.
To enter user information and a product key code on page 55
4.
To specify the CMS log on information on page 56
5.
To select components to install on page 57
6.
To configure your Metadata Management repository on page 59
7.
To configure your existing Web application server on page 60
8.
To start the installation on page 61
9.
To manually deploy web application server components on page 62
After your installation successfully completes, you access Metadata
Management from the Central Management Console (CMC) of SAP
BusinessObjects 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 Windows
administrator privileges and access to your network.
2. If you downloaded SAP BusinessObjects Metadata Management from
Electronic Software Delivery, open the Setup.exe file or Autorun.exe. Or,
insert the SAP BusinessObjects Metadata Management Installation CD
into your CD-ROM drive (if the installer does not automatically open, open
Autorun.exe from the top level of the CD contents).
3. On the "Welcome to the BusinessObjects Metadata Management
Installation 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 agreement
for SAP BusinessObjects Metadata Management. You must accept the
agreement 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.
Installation for Windows
Standard installation of Metadata Management
4
To enter user information and a product key code
On the "User Information" screen, enter user information and provide a
product code for your SAP BusinessObjects Metadata Management
installation.
1. Provide your user credentials in the Full Name and Organization fields.
This information personalizes your installation and is recorded in the
registry.
2. Enter a valid code in the Product Keycode field.
Note:
You enter a single product keycode during Metadata Management
installation. If you need to change the keycode after installation, use the
"License Keys" management area of the Central Management Console
(CMC).
3. Click Next.
SAP BusinessObjects Metadata Management User's Guide55
Page 56
Installation for Windows
4
Standard 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 connection
information 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 Central
Management Server (CMS).
DescriptionOption
Host name of the CMS (Central Management Server).
This value is required.
The CMS is responsible for maintaining a database
of information about your SAP BusinessObjects
Enterprise system. The data stored by the CMS
includes information about users and groups, secu-
Server Name
rity levels, BusinessObjects Enterprise content, and
servers. For more information about the CMS, see
SAP BusinessObjects Enterprise Administrator's
Guide.
Note:
If you are installing the Remote Job Server, specify
the CMS that you will use to configure and schedule
integrator source runs.
If you use the Secure Sockets Layer (SSL) protocol
for all network communication between clients and
servers in your BusinessObjects Enterprise deployment, select the Enable SSL.
The CMS user name to connect to the CMS server.
The default value is Administrator.
Page 57
Installation for Windows
Standard installation of Metadata Management
DescriptionOption
4
Password
Authentication
Mode
2. If you selected Enable SSL, fill in the values for the following options on
the SSL window:
•SSL Certificates Folder
•Server SSL Certificate File
•SSL Trusted Certificate File
•SSL Private Key File
•SSL Private Key File Passphrase File
For more information, see "Configuring servers for SSL" in your SAPBusinessObjects Enterprise Administrator's Guide.
3. Click Next.
The "Select Features" screen displays.
The password to connect to the CMS server to register
and run the Metadata Integrator.
The CMS authentication mode. The default value is
Enterprise. See the SAP Business Objects Admin-
istrator's Guide for available modes.
To select components to install
At the "Select Features" window, select or deselect SAP BusinessObjects
Metadata Management components that you want to install on this computer.
For a description of the feature categories and components that you can
select or deselect, see Choose components and determine component
distribution on page 91.
Note:
The Installation Wizard displays the Metadata Management components
that you can install and cannot install, based on the prerequisite software
that is installed on this computer. For details, see Prerequisites for each
component on page 34.
1. Click the icon for a component you want to select or deselect.
SAP BusinessObjects Metadata Management User's Guide57
Page 58
Installation for Windows
4
Standard installation of Metadata Management
Each component displays a drop-down menu that allows you to choose
from the following options:
•Selected components will be installed on local hard drive — Installs
only the selected component in the tree for that feature.
•Entire feature will be installed on local hard drive — Installs all
components in the tree for that feature.
•Entire feature will be unavailable — No components for that feature
are installed. An X appears next to the deselected component.
Note:
•If you deselect the Metadata Management Relationship Server, ensure
that it is installed on at least one computer in your enterprise
deployment. The Relationship Server is required to process
relationships (such as impact and lineage) of metadata objects.
•The Metadata Management web application option is available if you
have installed the Web Application option in the SAP BusinessObjects
Enterprise software. The web application installation method is the
same in both BusinessObjects Enterprise and Metadata Management.
Therefore, the installer checks whether you have manually or
automatically installed web services, and automatically chooses the
same installation option in Metadata Management. If you have
manually deployed the web application in BusinessObjects Enterprise,
follow the Manually deploy web application server components
procedure in this guide to manually deploy the web application in
Metadata Management.
2. To calculate whether sufficient disk space is available for your selected
components, click Disk Cost.
In a new window the software displays storage space available on the
local machine and mapped network drives. Drives that do not have enough
disk space for the currently selected components are highlighted.
Click OK to return to the "Select Features" window.
4
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 "Configure
BusinessObjects Metadata Management Repository database" window
opens.
To configure your Metadata Management repository
The "Configure BusinessObjects Metadata Management Repository
database" window appears if you selected the CMS Repository Objects
component.
SAP BusinessObjects Metadata Management User's Guide59
Page 60
Installation for Windows
4
Standard installation of Metadata Management
On the "Configure BusinessObjects Metadata Management Repository
database" window, enter the connection information for your SAP
BusinessObjects Metadata Management Repository. Then you can create
the 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. After
installation, if you want to improve performance, you can change the
connection string in the Central Management Console. For details, see
Viewing and editing repository information on page 189.
3. Enter the User name and Password for the Metadata Management
Repository.
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 status
window selects the Create repository option by default. The installation
program will create the Metadata Management tables in the specified
database.
If you run the installation program again and want to preserve the existing
Metadata Management Repository, select Skip repository configuration.
If you want to create a new repository (either in the same database or a
new database) select the Create repository checkbox.
6. Click Next to continue with the installation setup.
The "Configure Web Application Server " window appears if your Web
Application 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 the
Web Application component.
As part of the installation setup, you provide information about the web
application server that will work with your SAP BusinessObjects Metadata
Management applications to perform administrative tasks on the Central
Management Console or to view metadata relationships on the Metadata
Management Explorer.
The Metadata Management installation wizard detects the web application
server that your SAP BusinessObjects Enterprise system is using on this
computer. Therefore, most of the information is pre-populated in the fields
on the " Configure Web Application Server configuration" window. To properly
install web components on your web application server, you must provide
the password for your existing web application server.
1. If your web application server is Apache Tomcat, you must provide the
name of the current web application server instance (for example
“localhost”) in the Instance field.
2. If your web application server is WebLogic, WebSphere, or Oracle
Application 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
Installation for Windows
Standard installation of Metadata Management
4
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 the Back 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, and
have the -w filename parameter switch enabled, this is the point at
which you can Cancel the installation process to have the .ini file written
with all the installation parameter information. This .ini file can then be
used 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.
SAP BusinessObjects Metadata Management User's Guide61
Page 62
Installation for Windows
4
Standard installation of Metadata Management
To manually deploy web application server
components
To manually deploy the web application server components (WAR files), you
must also have manually deployed the web application server components
in SAP BusinessObjects Enterprise. You must create a web
application-specific WAR file using the wdeploy tool, and then manually
deploy the web application server components. The following section
describes how to manually deploy the web application server components
on a Tomcat application server.
Note:
If you are manually deploying the SAP BusinessObjects Enterprise Web
Application Server, you must also manually install those web application
server components. For the list of WAR files to deploy, see the most recent
version of the SAP BusinessObjects Enterprise Installation and DeploymentGuide for Windows and UNIX. For information about deploying on
administrative consoles such as WebLogic, Websphere, and SAP Application
Server, see the SAP BusinessObjects Enterprise Web Application Deployment
Guide for Windows or the SAP BusinessObjects Enterprise Web Application
Deployment Guide for UNIX.
Note:
The following procedure assumes that you have installed the same versions
of SAP BusinessObjects Metadata Management and SAP BusinessObjects
Enterprise into the default installation folder. You must have the same version
numbers to ensure that both web application server components work
seamlessly. This procedure also assumes that you do not have previous
versions of the software installed on the same machine.
1. In the wdeploy tool on the machine where you installed SAP
BusinessObjects Metadata Management, run the wdeploy predeploy
command to prepare a single web application, or wdeploy predeployall
to prepare all web applications. WAR files are typically installed to
<LINK_DIR>/BusinessObjects Metadata Management
12.1/java/applications.
For example, to create Tomcat WAR files, enter the following:
The wdeploy tool does not detect whether SAP BusinessObjects
Enterprise web application is installed on the same version of the
application server.
Silent installation
A silent installation is one that you run from the command line to install SAP
BusinessObjects Metadata Management, rather than following the install
wizard. When you run a silent installation, you specify the parameters to be
used for the install either on the command line or in an input file (also called
a response file).
Silent installation is particularly useful when you need to perform multiple
installations, as you can save time and avoid being prompted for information
by the installation program.
You can also use the silent installation command in your own scripts. For
example, if your organization uses scripts to install software on machines,
you can insert the silent installation command into your scripts.
SAP BusinessObjects Metadata Management User's Guide63
Page 64
Installation for Windows
4
Silent installation
The silent install command line includes a series of parameters that provide
information for installation settings and directory paths. You can also specify
options 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 a
specified response file. The file is generated once the installation setup
program is ready to start the installation.
To create the response file:
1. Open a command line console and navigate to the folder that contains
the installation files.
2. Mount the device that contains the installation files.
Note:
If you run the installation script without copying the files to a temporary
location, you will be prompted to specify a temporary location for the
installation.
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 to
generate.
setup.exe -w responseFilePath
•For UNIX:
Type ./install.sh -w and the file path for the response file you want to
generate.
When you specify responseFilePath, make sure you include the name
of 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 each
screen, and then records the settings in the response file at the final
screen. If the values for any settings change after installation, run the
setup program again to validate the settings.
6. Stop the installation setup when you reach the final screen in the
installation setup program.
•For Windows:
Click Cancel to abort the installation setup.
•For UNIX:
Press CTRL + X to abort the installation setup.
4
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 NAME
parameter must be specified in the response file if you are replicating an
installation. If the parameter is not specified, the local server name will be
used by default.
1. Open a command line console and navigate to the folder that contains
the installation files.
2. In the command line, type the following information:
•For Windows:
setup.exe -r responsefile
•For UNIX:
./install.sh -r responsefile
SAP BusinessObjects Metadata Management User's Guide65
Page 66
Installation for Windows
4
Silent installation
-r responsefile Specifies the name of the response file you want the
installation setup program to read for installation parameters.
3. If you want to override values in the response file, type the parameters
in the command line.
For example, if you want to override the license key, type the PIDKEY
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 silent
installation of SAP BusinessObjects Metadata Management. To use a
parameter, place it on the command line after the installation command and
after the path for the installation files. Or, you may use these parameters in
the installation .ini file.
Specifies that the user is only
prompted when the installation is
complete.
Specifies that the user is not
prompted during the install, or when
the install is complete.
Specifies that the user is not
prompted during the install, or when
the install is complete.
Specifies the machine and directory
where you want to install the product
components.
For example, C:\Program
Files\Business Objects
4
PIDKEY
DATABASEPORT
ADDLOCAL
Specifies your base product activation keycode.
Specifies the port used for the
database type. Each database type
has a default port number if it is not
specified.
Specifies which components will be
installed. Each component is specified, comma separated and grouped
within quotes.
SAP BusinessObjects Metadata Management User's Guide67
Page 68
Installation for Windows
4
Migration
Related Topics
•To start the silent installation on page 110
Migration
When you install SAP BusinessObjects Metadata Management 12.1, you
can upgrade your version 11.7 or 12.0 repository to version 12.1 to preserve
your 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 repository
to SAP BusinessObjects Metadata Management 12.x, the following objects
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
Annotations, custom attributes, and preferences that you defined in version
11.7 migrate to the version 12.x repository.
If you migrate from Metadata Management 11.7 to 12.x, the following objects
do not migrate:
•Users – Metadata Management 12.x uses the security services that SAP
BusinessObjects Enterprise provides. Therefore, you must define and
manage users of Metadata Management through the Central Management
Console (CMC).
•Log files from Metadata Integrator and utility runs – Metadata Management
12.x uses the scheduling and file repositories that BusinessObjects
Enterprise provides. Therefore, the logs are now managed as part of the
instance of the scheduled run.
If you upgrade from version 11.7, you must install the Relationship Server
on a Windows computer that has an Adaptive Processing Server installed.
The Relationship Server component is new with version 12.1 of SAP
BusinessObjects Metadata Management. It provides object relationship
analysis 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 (same
version or different version), you can preserve your existing SAP
BusinessObjects Metadata Management metadata source definitions by
using the Metadata Management installer and using the same Metadata
Management repository.
Note:
If you upgrade from version 12.0, you must install the Relationship Server
on a Windows computer that has an Adaptive Processing Server installed.
The Relationship Server component is new with version 12.1 of Metadata
Management. It provides object relationship analysis such as impact and
lineage.
Installation for Windows
Migration
4
If you move to a new BusinessObjects Enterprise system (either upgrade
the 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 new
BusinessObjects Enterprise system:
•Schedules and metadata integrator history runs
•Users and permissions
•Integrator source groups
SAP BusinessObjects Metadata Management User's Guide69
Page 70
Installation for Windows
4
Migration
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 this
Metadata Management repository migration on a computer that has SAP
BusinessObjects Enterprise XI 3.1 Central Management Server (CMS)
installed.
1. Review Release Notes for the version of SAP BusinessObjects Metadata
Management you will be installing.
2. Use your database backup utilities program to back up your existing SAP
BusinessObjects Metadata Management repository.
3. Start the installation setup.
After you downloaded the product from Service Marketplace, open the
setup.exe file.
4. On the "Welcome to the SAP BusinessObjects Metadata Management
Installation Wizard" window, click Next.
5. Go through the following steps of a standard installation:
a.
To accept the license agreement on page 55
b.
To enter user information and a product key code on page 55
c.
To specify the CMS log on information on page 56
6. At the "Select Features" window, select the components that you want
to 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 computer
as the Metadata Management CMS Repository Objects component.
When you upgrade from a previous version, the Relationship Server
is not selected by default.
Note:
The Relationship Server component is new with version 12.1 of SAP
BusinessObjects Metadata Management. It provides object relationship
analysis such as impact and lineage. You must install the Relationship
Server on a Windows computer that has an Adaptive Processing
Server installed.
c. You can select other components if you want to install them on this
same computer.
d. Click Next.
The "Configure SAP BusinessObjects Metadata Management Repository
database" 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 default
depends on the version of the repository you specified and the version
you are installing.
a. If you specify a repository whose version is older than the version that
you are installing, the "Repository Status" window displays the
Upgrade repository option selected by default.
4
ActionSituation
You want to upgrade the repository and
preserve the data.
You want to delete the existing repository and create a new one in the same
database.
b. If you specify a repository that is the same version as the version you
are installing, the Repository status window displays the Skiprepository configuration option selected by default.
You want to keep the repository
and preserve the data.
SAP BusinessObjects Metadata Management User's Guide71
Select Upgrade repository.
Select Create repository.
ActionSituation
Select Skip repository configuration.
Page 72
Installation for Windows
4
Migration
ActionSituation
You want to delete the existing
repository and create a new one in
the same database.
c. If you specify a repository that is a later version than the version you
are installing, the Repository status window displays the Create
repository option selected by default.
Create repository is your only choice because the repository needs
to match the version.
9. In the "Installation Completed" window, click OK.
Related Topics
•Objects that migrate on page 111
Select Create repository.
Migrating Metadata Management objects to a
different CMS
Use this procedure when you want to move your SAP BusinessObjects
Metadata Management system to a different SAP BusinessObjects Enterprise
system. The source and target BusinessObjects Enterprise system should
be 12.x.
1. Go through the following steps of a standard installation:
a.
To accept the license agreement on page 55
b.
To enter user information and a product key code on page 55
c.
To specify the CMS log on information on page 56
2. At the "BusinessObjects Enterprise Server Login" window, specify
connection information for the different CMS.
3.
Follow the procedure in To select components to install on page 57
4. At the "Configure SAP BusinessObjects Metadata Management Repository
database" window, specify the connection information for your existing
Metadata Management repository.
5. At the "Repository Status" window, select the Skip repository
configuration 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 select
the users and groups that have permissions to the Metadata
Management integrator source configurations. You can deselect
objects that you do not want to export.
b. On the target CMS, import the BIAR file, select "Import users and
users groups" on "Select objects to import" screen. You can deselect
objects that you do not want to import.
•Recreate the users and groups and grant permissions to the Metadata
Management objects.
Related Topics
•Adding users and assigning access levels to a group on page 131
4
Copying integrator configurations
Use this procedure if you want to copy your integrator source configurations
from a development environment to a test environment, or from test
environment to a production environment.
Note:
Life Cycle Management is not supported for promoting integrator source
configurations.
You must have Metadata Management version 3.1 on both the source and
target CMS machines.
1. Use the SAP BusinessObjects Enterprise Import Wizard to create an
output BIAR file for Metadata Management integrator source configuration
on 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.
SAP BusinessObjects Metadata Management User's Guide73
Page 74
Installation for Windows
4
Backing up and restoring Metadata Management configurations
Note:
You can select which integrator sources you want to backup (export).
d. Optionally on the "Select objects to import" screen, select the users
and groups that have permissions to the Metadata Management
integrator source configurations.
2. On the target CMS, use the Import Wizard to import the generated BIAR
file.
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 open
the Properties page.
c. Save the Properties page.
This action allocates the correct MMJobServer and updates the
configuration information.
4. Restart the CMS system and Web application.
Backing up and restoring Metadata
Management configurations
Use these procedures when you want to backup and restore configurations
from one SAP BusinessObjects Metadata Management system to another.
Note:
Use the backup utility in your Relational Database Management System to
back up the Metadata Management repository which contains the following
objects:
Backing up and restoring Metadata Management configurations
Backing up configurations
You must have SAP BusinessObjects Metadata Management version 3.1
on both the source and target SAP BusinessObjects Enterprise machines.
To back up your configurations, use the SAP BusinessObjects Enterprise
Import Wizard to create an output BIAR file for Metadata Management
configuration 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 Enterprise
machines.
2. On the "Select objects to import" screen, select only the Import
application folders and objects option.
3. On the "Select application folders and objects" screen, select Metadata
Management.
4. On the "Select objects to import" screen, select the users and groups that
have permissions to the Metadata Management integrator source
configurations.
5. On the next screen, select the users and groups that have permissions
to the Metadata Management integrator source configurations.
Installation for Windows
4
The following configuration information is backed up as a result of this
procedure:
•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.1
on both the source and target SAP BusinessObjects Enterprise machines.
To restore the configurations on the target BusinessObjects Enterprise
system:
1. Use the Import Wizard to import the generated BIAR file.
SAP BusinessObjects Metadata Management User's Guide75
Page 76
Installation for Windows
4
Remote Job Server Installation
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 open
the Properties page.
c. Save the Properties page.
This action allocates the correct MMJobServer and updates the
configuration information.
3. Restart the BusinessObjects Enterprise system and Web application.
Remote Job Server Installation
SAP BusinessObjects Metadata Management XI 3 can collect metadata from
an SAP BusinessObjects Enterprise XI R2 system by using the Remote Job
Server. The following diagram shows the relationship of this Remote Job
Server component to the other SAP BusinessObjects Metadata Mangement
(BOMM) components and the SAP BusinessObjects Enterprise (BOE)
components
If you want to collect metadata from a BusinessObjects Enterprise XI R2
system, 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 components
installed.
Note:
If any of your Crystal Reports or Web Intelligence documents were created
with the Refresh on Open option, you must also configure the database
clients to connect to the source databases. This connection is required
because whenever the report or document is opened (even to read the
metadata when the BOE Metadata Integrator collects the metadata), BOE
XI Release 2 automatically refreshes the data.
2. During installation, configure the Remote Job Service to accept requests
from BusinessObjects Enterprise XI 3 to run the BOE Metadata Integrator
on BusinessObjects Enterprise XI R2.
3. Rename the Input and Output File Repository Servers on BusinessObjects
Enterprise XI 3 to conform to the naming conventions on BusinessObjects
Enterprise XI R2.
4
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 Job
Server installation on a computer that has SAP BusinessObjects Enterprise
XI R2 full client or server installed.
During installation, you configure the Metadata Management Remote Job
Service to accept requests from BusinessObjects Enterprise XI 3 to run the
Metadata 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 54
b.
To accept the license agreement on page 55
c.
To enter user information and a product key code on page 55
d.
To specify the CMS log on information on page 56
SAP BusinessObjects Metadata Management User's Guide77
Page 78
Installation for Windows
4
Remote Job Server Installation
2. Keep the BusinessObjects Enterprise Metadata Integrator component
3. On the "Configure BusinessObjects Metadata Management Remote Job
4. Click Next.
5. On the "Start Installation" screen, verify that the Remote Job Server
Note:
You specify the logon information for the CMS system that you will
use to configure and schedule integrator source runs.
e.
To select components to install on page 57
If the Installation Wizard detects that BusinessObjects Enterprise XI R2
is installed on this computer, the "Select Features" window shows only
the BusinessObjects Enterprise Metadata Integrator component enabled.
selected and click Next.
Server service port" screen, verify the port number that the Remote Job
Service will use to listen for requests from BusinessObjects Enterprise
XI 3 to run the Metadata Integrator. If you do not want the default port
number 5005, enter a new value.
displays in the list of "Components selected for installation" and click
Next.
The "Updating System" window shows the progress of copying the files.
After you install the Remote Job Server, you must rename the Input and
Output File Repository Servers on your BusinessObjects Enterprise XI 3
system 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 Output
File Repository Servers (FRSs) on your SAP BusinessObjects Enterprise XI
3 system to conform to the naming convention on BusinessObjects Enterprise
XI Release 2. In XI Release 2, the Input FRS must start with Input and the
Output FRS must start with Output.
The directory where the Java SDK is installed.Java Home
Reserved for future use.Java Options
4
Initial memory pool (MB)
Maximum
memory pool
(MB)
The default value is 512 MB.
Consult your JVM documentation for more information
about changing your Java memory settings.
The default value is 1024 MB.
Consult your JVM documentation for more information
about changing your Java memory settings.
4. The "Listener" tab defines the port to listen for service requests and
connectivity to the Central Management Service on BusinessObjects
Enterprise XI 3 that will send service requests.
You can set the following options:
SAP BusinessObjects Metadata Management User's Guide81
Page 82
Installation for Windows
4
After installing Metadata Management
DescriptionOption
Application
port
CMS Server
name
User name
Password
Authentication mode
5. Click Test port if you want to verify that the port number is available. The
Remote Job Service uses this port to listen for requests from
BusinessObjects Enterprise XI 3 to run the Metadata Integrator.
6. Click Test connection if you want to verify that the Remote Service can
connect successfully to the CMS on BusinessObjects Enterprise XI 3.
Number of the port that the listener service will use to listen
for requests to run the BusinessObjects Enterprise Metadata
Integrator.
Host name of the CMS (Central Management Server) on
BusinessObjects Enterprise XI 3 that will send requests to
run the Metadata Integrator on BusinessObjects Enterprise
XI R2.
The CMS user name to connect to the CMS server on
BusinessObjects Enterprise XI 3.
The default value is Administrator. If you want a user
other than Administrator to run the Metadata Integrator,
change the value to the appropriate name.
The password to connect to the CMS server to register and
run the Metadata Integrator. The default is no password.
The CMS authentication mode. The default value is Enterprise. See the BusinessObjects Enterprise Administrator'sGuide for available modes.
Related Topics
•Installing a Remote Job Server on page 77
After installing Metadata Management
Verifying Metadata Management servers are running
After installing SAP BusinessObjects Metadata Management, verify that the
Metadata Management servers are running and enabled.
1. From the CMC Home page, go to the "Servers" management area.
2. Expand the Service Categories node and select Metadata Management.
The Servers List includes a State column that provides the status for
each 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 the
following:
a. Select the server name from the list.
b. Open the Actions drop-down menu and select Start Server or Enable
Server.
Related Topics
•Managing Metadata Management servers on page 120
Metadata Integrator server groups
Installation for Windows
After installing Metadata Management
4
The SAP BusinessObjectrs Metadata Management installer creates a new
server group when a new Integrator is deployed. For example, the Server
Group BusinessObjects Enterprise Metadata Integrator is created for the
BusinessObjects Enterprise Integrator. this server group is used by the
scheduler to run the integrator process on the correct Metadata Management
Job Server.
You must not create, replace or change a deployed Metadata Management
Server Group. Doing so could cause the Metadata Management Job Server
to stop working. In this case, you must re-install the Integrators.
Updating the license key
To update the SAP BusinessObjects Metadata Management license key
code in the Central Management Console (CMC), you must have SAP
BusinessObjects Enterprise XI 3.0_HF1 installed.
Situations when you might need to update your license key code for Metadata
Management include the following:
SAP BusinessObjects Metadata Management User's Guide83
Page 84
Installation for Windows
4
Uninstalling 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 product
activation 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 delete
the Evaluation key prior to adding any new license keys or product
activation 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 Management
Uninstalling SAP BusinessObjects Metadata Management removes the
integrator configurations. If you want to keep your configurations, do not
uninstall Metadata Management. To keep the existing integrator
configurations, install another version on top of an existing version (for
example install Metadata Management 12.1 on top of 12.0) and select the
Upgrade repository option.
To uninstall Metadata Management:
1. Go to Start > Settings > Control Panel > Add/Remove Programs (or
Change/Remove Programs).
2. Select BusinessObjects Metadata Management, and click Remove.
After you uninstall Metadata Management, the Metadata Management
directory in the Business Objects installation directory is not deleted because
the following files are not removed:
•zip files in ccmrestore/integrators
•MM/config/InfoObjectDelee.list
•files in MM/log
•files in MM/xml
4
SAP BusinessObjects Metadata Management User's Guide85
SAP BusinessObjects Metadata Management provides an open and flexible
architecture that supports a multitude of deployment and configuration
scenarios. 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 Metadata
Management repository and prepare the database.
•Determine your installation method.
The following sections list the software and system requirements and the
install methods available to you for installing SAP BusinessObjects Metadata
Management.
Note:
The following Metadata Management components can only be installed on
Windows (you cannot install them on UNIX):
•Metadata Integrators
•Search Server (provides ability to search metadata on the Metadata
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://ser
vice.sap.com/bosap-support. This document includes specific version and
patch-level requirements for databases, applications, web application servers,
web browsers, and operating systems.
Generally, the following components must be preinstalled and configured
correctly 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 this
computer. See Prerequisites for each component on page 34.
Installation for UNIX
Preparing to install Metadata Management
5
Metadata Management uses the Web application server and Java 2
Software Development Kit (JDK) that BusinessObjects Enterprise uses.
Note:
For UNIX, you must increase the memory setting for Web Logic in the
following directory: Weblogic_install/wlserver_10.0/samples/do
mains/wl_server/bin/setDomainEnv.sh. Change the value of the
parameter -XX:MaxPermSize from 128m to 256m .
Note:
To install Metadata Management, you must be the BusinessObjects
Enterprise Administrator.
Network requirements
When installing SAP BusinessObjects Metadata Management on multiple
computers, you must ensure that:
SAP BusinessObjects Metadata Management User's Guide89
Page 90
Installation for UNIX
5
Preparing to install Metadata Management
•each target machine can communicate over TCP/IP with the machine
running the Central Management Server (CMS).
•the target machines can communicate over TCP/IP with each other. In
particular:
•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 Metadata
Management Explorer and machines where Metadata Integrators are
deployed.
For more information on the communication between components, refer to
Architecture on page 19.
UNIX permissions
SAP BusinessObjects Metadata Management will be installed in the same
directory where SAP BusinessObjects Enterprise is installed. To install
Metadata Management on UNIX, the user account under which the install
is run must have read, write, and execute permissions to the directory where
BusinessObjects Enterprise is installed. Root privileges are not required to
install Metadata Management.
Caution:
If you attempt an installation with root privileges, you will be unsuccessful.
The following table summarizes all the required permissions for installing
Metadata Management.
Read, write, and execute permissions to the directory where
BusinessObjects Enterprise will be installed .
TCP/IP access to all machines where you want to install components - all specified ports must be available.
You must be the BusinessObjects Enterprise Administrator.BusinessOb-
Rights to add and drop database objects (such as tables and
views), plus rights to read, write, and edit table rows.
It is recommended that you use the same user account for installing BusinessObjects Enterprise and your web application
server.
To deploy Metadata Management web applications using
a user account different from the one used to install the web
application server, see "Minimum user rights for deploying
web applications" in the BusinessObjects Enterprise XI 3Installation and Configuration Guide for UNIX.
Choose components and determine component distribution
You can choose to install SAP BusinessObjects Metadata Management
components on one or more computers based on available resources and
your deployment planning. For guidelines and suggested scenarios to
distribute 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 Adaptive
Processing Server installed on it.
SAP BusinessObjects Metadata Management User's Guide91
Page 92
Installation for UNIX
5
Preparing to install Metadata Management
The following table shows the software components and their
sub-components that you can choose.
DescriptionComponentFeature cateogry
Metadata Management CMS Repository Objects
Metadata Management
CMS Repository Objects
Includes definitions and location information for the SAP BusinessObjects Metadata Management application, repository,
and other objects.
SAP BusinessObjects Enterprise Metadata Integrator
SAP NetWeaver Business
Warehouse Metadata Integrator
Installation for UNIX
Preparing to install Metadata Management
DescriptionComponentFeature cateogry
Extracts information from an SAP BusinessObjects Enterprise repository that includes metadata objects such as SAP
BusinessObjects Crystal Reports, Web
Intelligence documents, and Desktop Intelligence documents.
Extracts information from a NetWeaver
Business Warehouse system which includes metadata objects such as Queries,
InfoProviders, InfoObjects, Transformations, and DataSources.
5
Metadata Integrators
Common Warehouse Model (CWM) Metadata Integrator
Relational Databases
(RDBMS) Metadata Integrator
SAP BusinessObjects Data
Services Metadata Integrator
SAP BusinessObjects Data
Federator Metadata Integrator
Extracts information from the CWM Relational Package that includes definitions of
metadata objects such as catalogs,
schemas, and tables.
Extracts information from an RDBMS that
includes definitions of metadata objects
such as catalogs, schemas, stored procedures, and aliases.
Supported relational databases include
DB2, MySQL, Oracle, SQL Server,
Teradata, or a Universe connection using JDBC or ODBC. For complete details, see the Supported Platforms document.
Extracts information from an SAP BusinessObjects Data Services repository which
includes definitions of metadata objects
such as source tables and columns for
ETL jobs, datastores and configurations,
and flat files.
SAP BusinessObjects Metadata Management User's Guide93
Page 94
Installation for UNIX
5
Preparing to install Metadata Management
Meta Integration Metadata
Bridge (MIMB) Metadata
Integrator
DescriptionComponentFeature cateogry
Extracts information from an SAP BusinessObjects Data Federator repository which
includes definitions of metadata objects
such as projects, catalogs, datasources,
and mapping rules.
Extracts the following metadata from other
sources:
•Data Modeling metadata such as
Sybase Power Designer, Embarcadero
ER/Studio, and Oracle Designer
•ETL metadata such as Oracle Ware-
house Builder, SAS ETL Studio, and
Microsoft SQL Server Integration Services (SSIS)
•OLAP and BI metadata such as IBM
DB2 Cube Views, Oracle OLAP, and
Cognos 8 BI Reporting
Processes object relationships (for example, impact and lineage).
Provides search capability on SAP BusinessObjects Metadata Management Explorer.
Page 95
Web Application
Related Topics
•Architecture overview on page 20
Installation for UNIX
Preparing to install Metadata Management
DescriptionComponentFeature cateogry
Provides web applications that:
•administer SAP BusinessObjects
Metadata Management on the Central
Management Console (CMC)
•comprise the SAP BusinessObjects
Metadata Management Explorer
Note:
If SAP BusinessObjects Enterprise has
manually deployed the web application,
follwo the steps in the Manually deploy
web application procedure.
5
Repository database requirements and preparation
The SAP BusinessObjects Metadata Management repository is a database
that stores all metadata that the Metadata Integrators collect. You use the
information in the repository to analyze relationships between objects, as
well as to analyze impact and lineage between objects. For example, you
can find the tables and columns used by your Business Intelligence reports
and documents.
You can either create a new database for the repository or use an existing
repository. The SAP BusinessObjects Metadata Management installation
process will either create new tables or upgrade the existing tables within
the repository.
Related Topics
•Setting up a new database on page 52
•Exploring SAP BusinessObjects Enterprise metadata on page 272
SAP BusinessObjects Metadata Management User's Guide95
Page 96
Installation for UNIX
5
Preparing to install Metadata Management
Setting up a new database
This procedure creates a SAP BusinessObjects Metadata Management
Repository database and configures it for the user who will connect to it. The
installation process will create the tables within the Metadata Management
Repository.
1. Create a new database on your database server.
Compatible database types include DB2, MySQL, Oracle, and Oracle
RAC. For the most current list of supported database software and version
requirements, see the Products Availability Report available 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.
•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 specify
within 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 contain
the "=" character.
•Oracle_RAC_connection_string is the connection string
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 database
as required.
Note:
If you are not the owner of the database, you must have permissions to
perform 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 SAP
BusinessObjects 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.
Installation for UNIX
Preparing to install Metadata Management
5
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 Metadata
Management features that you want.
To purchase license keys:
•Contact your sales representative.
•Contact your regional office.
SAP BusinessObjects Metadata Management User's Guide97
Page 98
Installation for UNIX
5
Standard installation of Metadata Management on UNIX
Related Topics
•To enter product key code on page 100
•Updating the license key on page 115
Standard installation of Metadata
Management on UNIX
Before beginning your installation, review the Pre-installation overview to
ensure that you have prepared all necessary systems.
The following instructions lead you through the standard installation steps
of setting up your SAP BusinessObjects Metadata Management on UNIX:
1.
To begin running the installation program on page 98
2.
To accept the license agreement on page 99
3.
To specify the installation directory on page 99
4.
To enter product key code on page 100
5.
To specify the CMS log on information on page 100
6.
To select components to install on page 102
7.
To configure your Metadata Management repository on page 103
8.
To configure your existing Web application server on page 104
9.
To start the installation on page 104
10.
To manually deploy web application server components on page 62
After your installation successfully completes, you access Metadata
Management from the Central Management Console (CMC) of SAP
BusinessObjects 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:
Standard installation of Metadata Management on UNIX
1. Log on to your computer using an account that has read, write, and
execute permissions to the directory where SAP BusinessObjects
Enterprise is installed.
Note:
You must install Metadata Management in the same directory as
BusinessObjects Enterprise because Metadata Management uses some
of 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 agreement
for SAP BusinessObjects Metadata Management. You must accept the
agreement 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.
Installation for UNIX
5
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 SAP
BusinessObjects Enterprise installation.
Note:
You must install SAP BusinessObjects Metadata Management in the
same directory as BusinessObjects Enterprise because Metadata
Management uses some of the same libraries as BusinessObjects
Enterprise.
SAP BusinessObjects Metadata Management User's Guide99
Page 100
Installation for UNIX
5
Standard 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 your
SAP BusinessObjects Metadata Management installation.
1. Enter a valid code in the Product Keycode field.
Note:
You enter a single product keycode during Metadata Management
installation. 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 connection
information 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 Central