Business Objects products in this release may contain redistributions of software
licensed from third-party contributors. Some of these individual components may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
2008-08-11
Contents
Introduction11Chapter 1
About this guide.........................................................................................12
This guide describes the purpose, installation, configuration, and usage of
BusinessObjects™ Metadata Management.
The expected audience for this technical information include:
•Administrators who install and configure 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.
BusinessObjects Metadata Management
overview
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, Metadata Management collects and
unifies metadata from data sources such as:
•Data Integration technologies, such as Data Integrator and 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 Metadata Management repository
to a Common Warehouse Modeling (CWM) XML file. You can then import
the CWM XML file into BusinessObjects Enterprise to create a universe.
With 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.
Metadata Management product
documentation
Your product CD provides the 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 Metadata Management, go to the
Start menu, select Programs > BusinessObjects Metadata Management
> Metadata Management Documentation, and choose:
•User's Guide–Opens this document, which describes the purpose,
installation, configuration, and usage of Metadata Management.
Introduction
1
•Release Notes–Opens the Release Notes PDF document, which includes
supported configurations and known problems in the associated Metadata
Management release.
•Release Summary–Opens the Release Summary PDFdocument, which
includes a discription of features in this Metadata Management release.
Obtain other relevant documents by visiting the Business Objects Customer
Support documentation page at http://support.businessobjects.com/documen
BusinessObjects Metadata Management runs on the 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 BusinessObjects Metadata
Management fit into the overall platform architecture and individual services
and components that make up BusinessObjects Enterprise. This information
will help administrators understand how to plan the deployment, management,
and maintenance of Metadata Management.
Related Topics
•Architecture overview on page 18
•Metadata Management on BusinessObjects Enterprise components on
page 25
Architecture overview
The following diagram shows the BusinessObjects Enterprise (BOE)
components that BusinessObjects Metadata Management (BOMM) uses.
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 ServerSearch Server
Metadata Management Architecture
2
Architecture overview
Related Topics
•Web Application Server on page 21
•Central Management System repository objects for Metadata Management
on page 20
•Metadata Integrators on page 23
•Metadata Management Search Server on page 24
Central Management System repository objects for
Metadata Management
The Central Management System (CMS) stores information that describes
the Metadata Management application and the operations of the servers that
Metadata Management uses for processing. CMS uses these repository
objects to manage 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.
Related Topics
•section "Metadata Management Architecture"
•Managing security in Metadata Management on page 96
Metadata Management requires a Java or Servlet web application server to
process the server-side scripts that make up web applications that:
•you use to perform Metadata Management administrative tasks on the
Central Management Console (CMC).
•comprise the Metadata Management Explorer through which you can
view and analyze relationships such as impact and lineage.
The web application servers that Metadata Management can use include
the following:
•Apache Tomcat
•WebSphere
•WebLogic
•Oracle Application Server
Note:
For specific version compatibility, refer to the BusinessObjects Metadata
Management supported platform document guide online on our support web
site: http://support.businessobjects.com/documentation/supported_platforms.
Metadata Management Architecture
Architecture overview
2
Related Topics
•Metadata Management administration on page 21
•Metadata Management Explorer on page 22
Metadata Management administration
You use the Central Management Console (CMC) to perform 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
•Administer security for the Metadata Management Explorer, Metapedia,
For a description of the objects collected by the MIMB Integrator, see the
MIMB documentation at http://www.metaintegration.net/Prod
ucts/MIMB/Documentation/.
•Relational databases Metadata Integrator
Collects metadata from relational database management systems
(RDBMS) which can be DB2, MySQL, 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
Business Objects sales representative. You can obtain Business Objects
contact information at http://www.businessobjects.com/company/con
tact_us/default.asp.
Related Topics
•BusinessObjects Enterprise objects on page 236
•Exploring Data Modeling metadata on page 266
•Data Federator objects on page 301
•BusinessObjects Data Services objects on page 278
•Exploring Relational Database metadata on page 324
•Deployment scenarios on page 31
Metadata Management Search Server
The Search Server allows you to find an object that exists in any source
while viewing metadata on the Metadata Management Explorer. The Search
Server uses the Lucene Search Engine.
The Search Server runs on an Adaptive Processing Server of
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
Metadata Management on BusinessObjects Enterprise components
the Search Server is not available during the construction and update
processes, the search might return incorrect results. For these situations,
Metadata Management provides a utility to reconstruct the search index. For
details, see Recreating search indexes on page 152.
Related Topics
•"Metadata Management Architecture"
•Deployment scenarios on page 31
Metadata Management on
BusinessObjects Enterprise components
The following table describes how Metadata Management uses each pertinent
BusinessObjects Enterprise component .
2
BusinessObjects Enterprise component
BOE Application Server
Central Management
Console (CMC)
How Metadata Management uses component
Deploys the Metadata Management application
which consists of:
Metadata Management on BusinessObjects Enterprise components
BusinessObjects Enterprise component
Central Management
Server (CMS)
Metadata Management
Job Server
Adaptive Processing
Server
How Metadata Management uses component
Responsible for maintaining a database of information about your BusinessObjects Enterprise system.
The data stored by the CMS includes information
about users and groups, security levels, BusinessObjects Enterprise content, and servers. For more information about the CMS, see BusinessObjects Enter-prise Administrator's Guide.
When you create a configuration for a metadata
integrator source, Metadata Management stores
the configuration in CMS.
Launches the scheduled execution of a metadata
integrator or a Metadata Management utility.
When you install Metadata Management on an
Adaptive Job Server, you also install metadata
integrator types for sources installed in CMS.
Runs the Metadata Management Search Service
and the Test Connection Service for integrator
sources.
metadata integrator or a search. These files include
the metadata integrator definitions, history logs, and
search indexes.
Deployment
3
Deployment
3
Deployment
Deployment
To provide flexibility, reliability, and scalability, you can install the components
that make up BusinessObjects Enterprise on one or many machines. You
can also install the components of 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 31.
Related Topics
•Planning your Metadata Management deployment on page 28
•Deployment guidelines on page 29
•Deployment scenarios on page 31
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 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
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:
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
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 31.
Deployment guidelines
Guidelines to deploy 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 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,
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 BusinessObjects Enterprise XI 3.0Deployment Planning Guide.
Prerequisites for each Metadata Management
component
To deploy a subset of Metadata Management components on each computer,
you must have the necessary software already installed on that computer.
The following table shows the prerequisites for each component.
Necessary 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 BusinessObjects Enterprise XI 3.0.1
•Metadata Management CMS Repository
Objects component must already be installed (not necessarily on this computer)
stalled on this computer. For example, the
BusinessObjects Enterprise Metadata Integrator requires BusinessObjects Enterprise
Full Client installed on this computer.
Installing this Metadata Integrator installs
the Metadata Management Job Server
(MMJobServer).
Metadata Management Search
Server
Web Application
Deployment scenarios
After you determine the needs of your users and the resources required for
the deployment, you can develop an initial deployment plan for Metadata
Management.
Deployment
Deployment
Necessary softwareFeature category
•Metadata Management CMS Repository
Objects component must already be installed (not necessarily on this computer)
•Adaptive Processing Server component of
BusinessObjects Enterprise XI 3.0.1
•Metadata Management CMS Repository
Objects component must already be installed (not necessarily on this computer)
•Web Application Server where BusinessOb-
jects Enterprise applications are deployed
3
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.
Scenario 1: Performance in small execution window
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 BusinessObjects Enterprise (BOE) and BusinessObjects
Metadata Management (BOMM) are deployed on seven computers.
•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
BusinessObjects Enterprise and Metadata Management are deployed on
four computers.
•1 processing server (SJ-PS-02) to host the CWM Metadata Integrator,
BusinessObjects Enterprise Metadata Integrator (BOE Integrator), and
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 therefore you have
redundant installations. The following diagram shows a possible deployment
of redundant Metadata Integrators across multiple computers.
BusinessObjects Metadata Management provides an open and flexible
architecture that supports a multitude of deployment and configuration
scenarios. Before you install BusinessObjects Metadata Management you
should:
•Ensure that that your network and systems meet the basic requirements
for a BusinessObjects Metadata Management installation.
•Obtain the BusinessObjects Metadata Management software by electronic
download or on CD/DVD, as well as any required licensing keycodes.
•
Review the BusinessObjects Metadata Management Release Notes and
the section Metadata Management Architecture on page 17.
•Ensure that the user who will run the installation setup program has
adequate permissions to complete the installation tasks.
•Determine where the Metadata Management 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 your 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 BusinessObjects Metadata
Management.
Related Topics
•Metadata Management Architecture on page 17
•License keys on page 78
System requirements
For a detailed list of supported environments and hardware requirements,
see the Platforms Availability Report available on the Business Objects
•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
Metadata Management Architecture on page 17.
User permissions for installing Metadata Management
To successfully install 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 System
4
Network
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 BusinessObjects Enterprise Administrator.BusinessObjects
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 En-terprise XI 3 Installation and Configuration Guide.
Choose components and determine component distribution
You can choose to install Metadata Management components on one or
more computers based on available resources and your deployment planning.
For guidelines and suggested scenarios to distribute Metadata Management
componenets, see Deployment on page 28.
Note:
•You must install the Metadata Management CMS Repository Objects on
the same computer as the 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 and Search Server on a
supported Windows platform.
The following table shows the Metadata Management components and their
sub-components that you can choose.
Includes definitions and location information for the Metadata Management application, Metadata Management repository,
and other Metadata Management objects.
Extracts information from a BusinessObjects Enterprise repository which includes
metadata objects such as Crystal Reports,
Web Intelligence documents, and Desktop
Intelligence documents.
4
Metadata Integrators
Common Warehouse Model (CWM) Metadata Integrator
Relational Databases
(RDBMS) Metadata Integrator which can be DB2,
MySQL, Oracle, SQL Server, Teradata, or a Universe
connection using JDBC or
ODBC
BusinessObjects Data Services Metadata Integrator
Data Federator Metadata
Integrator
Meta Integration Metadata
Bridge (MIMB) Metadata
Integrator
Extracts information from the CWM Relational Package which includes definitions
of metadata objects such as catalogs,
schemas, and tables.
Extracts information from a RDBMS which
includes definitions of metadata objects
such as catalogs, schemas, stored procedures, and aliases.
Extracts information from a Data Services
repository which includes definitions of
metadata objects such as source tables
and columns for ETL jobs, datastores and
configurations, and flat files.
Extracts information from a Data Federator repository which includes definitions
of metadata objects such as projects,
catalogs, datasources, and mapping rules.
Provides search capability on Metadata
Management Explorer
Provides web applications that:
•administer Metadata Management on
the Central Management Console
(CMC)
•comprise the Metadata Management
Explorer
Repository database requirements and preparation
The 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 Metadata Management
repository or use an existing Metadata Management repository. The
installation process will either create new tables or upgrade the existing
tables within the Metadata Management Repository.
Related Topics
•Setting up a new database on page 77
•Exploring Business Intelligence metadata on page 234
Setting up a new database
This procedure creates a 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.
•For UNIX, compatible database types include DB2, MySQL, and
Oracle.
•For Windows, compatible database types include DB2, Microsoft SQL
Server, MySQL, and Oracle.
Installation for Windows
Preparing to install Metadata Management
4
Note:
For the most current list of supported database software and version
requirements, see the Platforms Availability Report available on the
Business Objects support site: http://support.businessobjects.com/docu
mentation/supported_platforms.
2. If you create a new DB2 8.x database:
a. In the creation wizard, set the code set to UTF-8.
b. Create three buffer pools, one for each page size: 8K, 16K and 32K.
The buffer pool size should be set to 1000.
c. Create one temporary system table space for the 32K buffer pool.
d. Create one regular table space for the 32K buffer pool.
3. If you create a new DB2 9.x database:
a. In the creation wizard, set the code set to UTF-8 and the default buffer
pool and table space page size to 32K.
4. Create a new user and assign a secure password.
5. Ensure that the new user has permission to create, modify, and delete
database objects so that Metadata Management can modify the database
as required.
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 BusinessObjects Metadata Management on Windows:
1.
To begin running the installation program on page 47
2.
To accept the license agreement on page 48
3.
To enter user information and a product key code on page 48
4.
To specify the CMS log on information on page 49
5.
To select components to install on page 50
6.
To configure your Metadata Management repository on page 52
7.
To configure your existing Web application server on page 52
8.
To start the installation on page 53
Installation for Windows
4
After your installation successfully completes, you access Metadata
Management from the Central Management Console (CMC) of
BusinessObjects Enterprise.
Related Topics
•Pre-installation overview on page 70
•Accessing Metadata Management for administrative tasks on page 93
To begin running the installation program
To run the 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 Metadata Management from Electronic Software
Delivery, open the Setup.exe file or Autorun.exe. Or, insert the
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 70
To accept the license agreement
At the "License Agreement" window, review and accept the license agreement
for 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.
To enter user information and a product key code
On the "User Information" screen, enter user information and provide a
product code for your 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).
At the "BusinessObjects Enterprise Server Login" window, specify connection
information for the 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 BusinessObjects Enterprise system. The data stored by the CMS includes
information about users and groups, security levels,
Server Name
BusinessObjects Enterprise content, and servers.
For more information about the CMS, see Busines-sObjects Enterprise Administrator's Guide.
Installation for Windows
4
Enable SSL
User
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.
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
BusinessObjects 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 Business Objects Administra-
tor's Guide for available modes.
To select components to install
At the "Select Features" window, select or deselect 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 73.
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
Metadata Management component on page 30.
1. Click the icon for a component you want to select or deselect.
Each component displays a drop-down menu that allows you to choose
from the following options:
•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.
4
2. To calculate if sufficient disk space is available for your selected
components, click Disk Cost.
A separate screen displays indicating 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" screen.
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
displays.
The "Configure BusinessObjects Metadata Management Repository
database" window appears if you selected the CMS Repository Objects
component.
On the "Configure BusinessObjects Metadata Management Repository
database" window, enter the connection information for your 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.
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.
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 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 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" screen 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 all the 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.
A silent installation is one that you run from the command line to install
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 BusinessObjects Metadata Management installation
command into your scripts.
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 54
•To start the silent installation on page 55
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.
setup.exe -w responseFilePath
Note:
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. Click Cancel to abort the installation setup.
You can access the response file from the directory you specified in step 2.
4
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:
setup.exe -r responsefile
-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
parameter and value in the command as follows:
The installation setup program runs in the background.
Related Topics
•To create a response file on page 54
Silent install parameters
The following table lists the most common parameters used in a silent
installation of 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 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.
INSTALLDIR
Installation for Windows
Migration
DescriptionInstallation parameter
Specifies the machine and directory
where you want to install the new
BusinessObjects Metadata Management components.
For example, C:\Program
Files\Business Objects
4
PIDKEY
DATABASEPORT
ADDLOCAL
Related Topics
•To start the silent installation on page 55
Migration
When you install Metadata Management 12.0, you can migrate your Metadata
Manager 11.x repository to Metadata Management 12.0 to preserve your
existing metadata source definitions.
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.
You can install version 12.0 on the same machine as version 11.7 if they do
not share the Tomcat Web application server and do not share the repository.
When you upgrade a Metadata Manager 11.x repository to Metadata
Management 12.0, the following objects migrate to the Central Management
Server (CMS) repository:
•Metadata Integrator configurations
•Configurations for Metadata Management utilties (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 the
previous version migrate to the Metadata Management 12.0 repository.
The following objects do not migrate:
•Users – Metadata Management 12.0 uses the security services that
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.0 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.
Related Topics
•To migrate a repository on page 86
To migrate a repository
Perform a migration of a Metadata Management repository from version 11.x
to 12.0 on a computer that has BusinessObjects Enterprise XI 3 Central
Management Server (CMS) installed.
1. Review Release Notes for the version of BusinessObjects Metadata
2. Use your database backup utilities program to back up your existing
Metadata Management repository.
3. Start the installation setup.
•For Windows, if you downloaded Metadata Management from
Electronic Software Delivery, open the Setup.exe file or Autorun.exe.
Or, insert the 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).
•For UNIX, run ./install.sh.
4. On the "Welcome to the 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 80
b.
To enter product key code on page 80
c.
To specify the CMS log on information on page 81
6. At the "Select Features" window, select the Metadata Management
InfoObjects component. You can select other components if you want to
install them on this same computer.
The "Configure BusinessObjects Metadata Management Repository
database" window appears.
4
7. Enter the following information to upgrade a Metadata Management 11.x
repository:
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 Metadata Management 11.x
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 Metadata
Management version you are installing.
a. If you specify an existing older version repository than the Metadata
Management version you are installing, the Repository status window
displays the Upgrade repository option selected by default.
Metadata Management XI 3 can collect metadata from a 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 BusinessObjects Metadata Mangement (BOMM) components and the
BusinessObjects Enterprise (BOE) components
Installation for Windows
Remote Job Server Installation
4
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 R2 full client or server installed.
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.
Related Topics
•Installing a Remote Job Server on page 62
•Renaming File Repository Servers on page 63
•Modifying the configuration of a Remote Job Service on page 64
Installing a Remote Job Server
Perform this Metadata Management Remote Job Server installation on a
computer that has 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 47
b.
To accept the license agreement on page 48
c.
To enter user information and a product key code on page 48
d.
To specify the CMS log on information on page 49
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 50
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.
2. Keep the BusinessObjects Enterprise Metadata Integrator component
selected and click Next.
3. On the "Configure BusinessObjects Metadata Management Remote Job
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.
5. On the "Start Installation" screen, verify that the Remote Job Server
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
Related Topics
•Standard installation of Metadata Management on page 47
•Renaming File Repository Servers on page 63
•Modifying the configuration of a Remote Job Service on page 64
Renaming File Repository Servers
For the Remote Job Service to work, you must rename the Input and Output
File Repository Servers on your BusinessObjects Enterprise XI 3 system to
conform to the naming convention on BusinessObjects Enterprise XI R2.
1. Log On to the Central Management Console (CMC) of BusinessObjects
Enterprise XI 3 with a valid administrator user name and password or a
user name that has Full Control access level on the CMC.
2. Click the Servers tab on the left or the Servers link under "Organize".
3. Select "hostname.InputFileRepository" from the "Server Name" list, and
select Manage > Properties from the top menu bar.
4. Change the name of the File Repository Server to the following:
Input.hostname.fileserver
Installation for Windows
Remote Job Server Installation
4
5. Click Save & Close.
6. Restart the renamed server by clicking Actions > Restart Server in the
top menu bar.
7. Select "hostname.OutputFileRepository" from the "Server Name" list,
and select Manage > Properties from the top menu bar.
8. Change the name of the File Repository Server to the following:
Output.hostname.fileserver
9. Click Save & Close.
10. Restart the renamed server by clicking Actions > Restart Server in the
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 62
After installing Metadata Management
Verifying Metadata Management servers are running
After installing 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 94
4
Updating the license key
To update the Metadata Management license key code in the Central
Management Console (CMC), you must have BusinessObjects Enterprise
XI 3.0_HF1 installed.
Situations when you might need to update your license key code for Metadata
Management include the following:
•Update an expired key code
•Upgrade from a trial version
•Include additional features that you have purchased
To update the license key:
1. Go to the "License Keys" management area of the CMC.
2. If you are upgrading from a trial version of the product, be sure to delete
the Evaluation key prior to adding any new license keys or product
activation keycodes.
a. From the list of key codes, select the Evaluation key code.
b. Click Delete.
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 80
•To enter user information and a product key code on page 48
Uninstalling Metadata Management
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.
Note:
After you uninstall Metadata Management, the log files for the integrator
source runs and utility runs will not be deleted. These log files are located
in the Business Objects installation directory in the following subdirectory
BusinessObjects Metadata Management provides an open and flexible
architecture that supports a multitude of deployment and configuration
scenarios. Before you install BusinessObjects Metadata Management you
should:
•Ensure that that your network and systems meet the basic requirements
for a BusinessObjects Metadata Management installation.
•Obtain the BusinessObjects Metadata Management software by electronic
download or on CD/DVD, as well as any required licensing keycodes.
•
Review the BusinessObjects Metadata Management Release Notes and
the section Metadata Management Architecture on page 17.
•Ensure that the user who will run the installation setup program has
adequate permissions to complete the installation tasks.
•Determine where the Metadata Management 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 your 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 BusinessObjects Metadata
Management.
Related Topics
•Metadata Management Architecture on page 17
•License keys on page 78
System requirements
For a detailed list of supported environments and hardware requirements,
see the Platforms Availability Report available on the Business Objects
•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
Metadata Management Architecture on page 17.
UNIX permissions
Metadata Management will be installed in the same directory where
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.BusinessObjects
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 En-
terprise XI 3 Installation and Configuration Guide for
UNIX.
Choose components and determine component distribution
You can choose to install Metadata Management components on one or
more computers based on available resources and your deployment planning.
For guidelines and suggested scenarios to distribute Metadata Management
componenets, see Deployment on page 28.
Note:
•You must install the Metadata Management CMS Repository Objects on
the same computer as the 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 and Search Server on a
supported Windows platform.
The following table shows the Metadata Management components and their
sub-components that you can choose.
Includes definitions and location information for the Metadata Management application, Metadata Management repository,
and other Metadata Management objects.
Extracts information from a BusinessObjects Enterprise repository which includes
metadata objects such as Crystal Reports,
Web Intelligence documents, and Desktop
Intelligence documents.
5
Metadata Integrators
Common Warehouse Model (CWM) Metadata Integrator
Relational Databases
(RDBMS) Metadata Integrator which can be DB2,
MySQL, Oracle, SQL Server, Teradata, or a Universe
connection using JDBC or
ODBC
BusinessObjects Data Services Metadata Integrator
Data Federator Metadata
Integrator
Meta Integration Metadata
Bridge (MIMB) Metadata
Integrator
Extracts information from the CWM Relational Package which includes definitions
of metadata objects such as catalogs,
schemas, and tables.
Extracts information from a RDBMS which
includes definitions of metadata objects
such as catalogs, schemas, stored procedures, and aliases.
Extracts information from a Data Services
repository which includes definitions of
metadata objects such as source tables
and columns for ETL jobs, datastores and
configurations, and flat files.
Extracts information from a Data Federator repository which includes definitions
of metadata objects such as projects,
catalogs, datasources, and mapping rules.
Provides search capability on Metadata
Management Explorer
Provides web applications that:
•administer Metadata Management on
the Central Management Console
(CMC)
•comprise the Metadata Management
Explorer
Repository database requirements and preparation
The 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 Metadata Management
repository or use an existing Metadata Management repository. The
installation process will either create new tables or upgrade the existing
tables within the Metadata Management Repository.
Related Topics
•Setting up a new database on page 77
•Exploring Business Intelligence metadata on page 234
Setting up a new database
This procedure creates a 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.
•For UNIX, compatible database types include DB2, MySQL, and
Oracle.
•For Windows, compatible database types include DB2, Microsoft SQL
Server, MySQL, and Oracle.
Installation for UNIX
Preparing to install Metadata Management
5
Note:
For the most current list of supported database software and version
requirements, see the Platforms Availability Report available on the
Business Objects support site: http://support.businessobjects.com/docu
mentation/supported_platforms.
2. If you create a new DB2 8.x database:
a. In the creation wizard, set the code set to UTF-8.
b. Create three buffer pools, one for each page size: 8K, 16K and 32K.
The buffer pool size should be set to 1000.
c. Create one temporary system table space for the 32K buffer pool.
d. Create one regular table space for the 32K buffer pool.
3. If you create a new DB2 9.x database:
a. In the creation wizard, set the code set to UTF-8 and the default buffer
pool and table space page size to 32K.
4. Create a new user and assign a secure password.
5. Ensure that the new user has permission to create, modify, and delete
database objects so that Metadata Management can modify the database
as required.
Standard installation of Metadata Management on UNIX
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 BusinessObjects Metadata Management on UNIX:
1.
To begin running the installation program on page 79
2.
To accept the license agreement on page 80
3.
To specify the installation directory on page 80
4.
To enter product key code on page 80
5.
To specify the CMS log on information on page 81
6.
To select components to install on page 82
7.
To configure your Metadata Management repository on page 83
8.
To configure your existing Web application server on page 84
9.
To start the installation on page 84
Installation for UNIX
5
After your installation successfully completes, you access Metadata
Management from the Central Management Console (CMC) of
BusinessObjects Enterprise.
Related Topics
•Pre-installation overview on page 70
•Accessing Metadata Management for administrative tasks on page 93
To begin running the installation program
To run the Metadata Management installation program:
1. Log on to your computer using an account that has read, write, and
execute permissions to the directory where 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.
Standard installation of Metadata Management on UNIX
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 70
To accept the license agreement
At the "License Agreement" screen, review and accept the license agreement
for 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. 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
BusinessObjects Enterprise installation.
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. Press Enter to continue the installation setup.
To enter product key code
At the "Enter Product Keycode" screen, provide a product keycode for your
BusinessObjects Metadata Management installation.
1. Enter a valid code in the Product Keycode field.
Standard installation of Metadata Management on UNIX
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 88
To specify the CMS log on information
At the "BusinessObjects Enterprise Server Login" screen, specify connection
information for the 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).
Installation for UNIX
5
CMS Hostname
DescriptionOption
Host name of the CMS (Central Management Server).
This value is required. The default value is local
host.
If the CMS is not on the default port number 6400,
specify a colon and the port number after the CMS
name. For example, mycmsname:6408
The CMS is responsible for maintaining a database
of information about your BusinessObjects Enterprise system. The data stored by the CMS includes
information about users and groups, security levels,
BusinessObjects Enterprise content, and servers.
For more information about the CMS, see Busines-sObjects Enterprise Administrator's Guide.
Note:
If you are installing the Remote Job Server, specify
the CMS that you will use to configure and schedule
integrator source runs.
Standard installation of Metadata Management on UNIX
Enable SSL
User name
DescriptionOption
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. By default, this option is not selected.
The CMS user name to connect to the CMS server.
The default value is Administrator.
Password
Authentication
Type
2. If you selected Enable SSL, fill in the values for the following options on
the SSL screen:
•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
BusinessObjects Enterprise Administrator's Guide.
3. Press Enter.
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 Business Objects Administra-
tor's Guide for available modes.
To select components to install
At the "Select Features" window, select or deselect Metadata Management
components that you want to install on this computer.
1. Enter an X next to each component you want to select.
Standard installation of Metadata Management on UNIX
Note:
Only the following Metadata Management components can be installed
on UNIX:
•Metadata Management CMS Repository Objects - This component
displays if the CMS server is installed on this computer.
•Web Application - This component displays if the Web application
server is installed with BusinessObjects Enterprise.
For a description of the components, see Choose components and
determine component distribution on page 73.
2. Press Enter.
If you selected the CMS Repository Objects component, the "Metadata
Management Repository Database Type" screen displays.
To configure your Metadata Management repository
The "Metadata Management Repository Database Type " screen appears
if you selected the CMS Repository Objects component.
1. Select the database type from the numbered list.
2. Press Enter to continue.
3. On the "Metadata Management Repository Information" screen, enter
the connection information for the database type.
4. Press Enter (this action also validates your input values).
The "Repository Status" screen appears.
5
5. The first time you run the installation program, the Repository status
window selects the Create a new 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 Create a new repository.
6. Press Enter to continue with the installation setup.
The "Enter Web Application Server configuration" screen appears if your
Web Application Server is Tomcat.
Standard installation of Metadata Management on UNIX
To configure your existing Web application server
The " Enter Web Application Server configuration" screen 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 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 program detects the web application
server that your BusinessObjects Enterprise system is using on this computer.
Therefore, most of the information is pre-populated in the fields on the " Enter
Web Application Server configuration" screen. 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. Press Enter to continue with the installation setup.
To start the installation
The "BusinessObjects Metadata Management Setup" screen 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, pres Ctrl-B. All entries are retained; you
do not need to re-enter all the information.
Note:
If you are running the ./install.sh program from the command line,
and have the -w filename parameter switch enabled, this is the 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.
The "In Progress" screen shows the progress of copying the files.
Migration
When you install Metadata Management 12.0, you can migrate your Metadata
Manager 11.x repository to Metadata Management 12.0 to preserve your
existing metadata source definitions.
You can install version 12.0 on the same machine as version 11.7 if they do
not share the Tomcat Web application server and do not share the repository.
Related Topics
•Objects that migrate on page 85
•To migrate a repository on page 86
Objects that migrate
Installation for UNIX
Migration
5
When you upgrade a Metadata Manager 11.x repository to Metadata
Management 12.0, the following objects migrate to the Central Management
Server (CMS) repository:
•Metadata Integrator configurations
•Configurations for Metadata Management utilties (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 the
previous version migrate to the Metadata Management 12.0 repository.
The following objects do not migrate:
•Users – Metadata Management 12.0 uses the security services that
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.0 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.
Perform a migration of a Metadata Management repository from version 11.x
to 12.0 on a computer that has BusinessObjects Enterprise XI 3 Central
Management Server (CMS) installed.
1. Review Release Notes for the version of BusinessObjects Metadata
Management you will be installing.
2. Use your database backup utilities program to back up your existing
Metadata Management repository.
3. Start the installation setup.
•For Windows, if you downloaded Metadata Management from
Electronic Software Delivery, open the Setup.exe file or Autorun.exe.
Or, insert the 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).
•For UNIX, run ./install.sh.
4. On the "Welcome to the 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 80
b.
To enter product key code on page 80
c.
To specify the CMS log on information on page 81
6. At the "Select Features" window, select the Metadata Management
InfoObjects component. You can select other components if you want to
install them on this same computer.
The "Configure BusinessObjects Metadata Management Repository
database" window appears.
7. Enter the following information to upgrade a Metadata Management 11.x
repository:
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 Metadata Management 11.x
c. If you specify a repository that is a later version than the Metadata
Management 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 Metadata Management version.
9. In the installation completed window, click OK.
Related Topics
•Objects that migrate on page 85
Updating the license key
To update the Metadata Management license key code in the Central
Management Console (CMC), you must have BusinessObjects Enterprise
XI 3.0_HF1 installed.
Situations when you might need to update your license key code for Metadata
Management include the following:
•Update an expired key code
•Upgrade from a trial version
•Include additional features that you have purchased
To update the license key:
1. Go to the "License Keys" management area of the CMC.
2. If you are upgrading from a trial version of the product, be sure to delete
the Evaluation key prior to adding any new license keys or 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.
•To enter user information and a product key code on page 48
Uninstalling Metadata Management on
UNIX
To uninstall Metadata Management:
1. Go to the directory where BusinessObjects Enterprise is installed.
2. Run AddOrRemoveProducts.sh and select BusinessObjects Metadata
Management.
3. Press Enter.
Note:
After you uninstall Metadata Management, the log files for the integrator
source runs and utility runs will not be deleted. These log files are located
in the Business Objects installation directory in the following subdirectory
BusinessObjects Metadata Management is a web application that extracts
metadata about objects from different source systems and stores the
metadata in a repository. Source systems include Business Intelligence,
Data Modeling, Data Integration (BusinessObjects Data Services and
BusinessObjects Data Federation), and Relational Database systems.
When you access Metadata Management as a user with Full Control access
level on the Central Management Console of BusinessObjects Enterprise,
you can perform the following tasks:
•Ensure that the BusinessObjects Enterprise servers required to perform
Metadata Management tasks are enabled and running (see Managing
Metadata Management servers on page 94)
•Configure integrator sources from which to collect metadata (see
Configuring sources for Metadata Integrators on page 107)
•
Run Integrators to collect metadata (see Running a Metadata Integrator
on page 130)
•
View the status of Metadata Integrator collection jobs (see Viewing
integrator run progress and history on page 142)
•Organize Metadata Integrator Sources into groups for relationship analysis
(see Grouping Metadata Integrator sources on page 144)
•Manage user security of Metadata Integrator sources, source groups,
Metapedia, and Metadata Management utilities (see Managing security
in Metadata Management on page 96
•Compute and store end-to-end impact and lineage information for
Reporting (see Computing and storing lineage information for reporting
on page 147)
•
Manage the Metadata Management search indexes (see Running the
search index recreation utility on page 155)
•View and edit the Metadata Management repository information (see
Viewing and editing repository information on page 156)
Accessing Metadata Management for administrative
tasks
To access Metadata Management to perform administrative tasks, you must
have Full Control access level on the Central Management Console (CMC)
of BusinessObjects Enterprise.
1. Access the CMC in one of the following ways:
•Type directly into your browser the name of the computer you are
accessing.
http://webserver:8080/CmcApp/
Replace webserver with the name of the web server machine. If you
changed this default virtual directory on the web server, you need to
type your URL accordingly. If necessary, change the default port
number to the number you provided when you installed
BusinessObjects Enterprise.
•Select BusinessObjects Enterprise Central Management Console
from the program group on the Windows Start menu.
6
Start > Programs > BusinessObjects XI 3.0 > BusinessObjects
Enterprise > BusinessObjects Enterprise Central Management
Console.
2. Log on to the Central Management Console (CMC) of BusinessObjects
Enterprise with a valid administrator user name and password or a user
name that has Full Control access level on the Central Management
Console of BusinessObjects Enterprise.
For details, see "To log on to the CMC from your browser" in the
BusinessObjects Enterprise Administrator's Guide.
3. On the CMC Home page, access Metadata Management in one of the
following ways:
•Click the Metadata Management link under the "Organize" area.
•Click the Metadata Management tab on the left of your screen.
•Select the Metadata Management option from the drop-down list at
a user attempts an action on a Metadata Management object, the CMS
authorizes the action only after it verifies that the user's account or group
membership has sufficient privileges.
Related Topics
•Users and groups on page 97
•Access levels for Metadata Management tasks on page 98
Users and groups
When you set up your system, the CMS allows you to create user accounts
and groups within BusinessObjects Enterprise, or reuse existing user
accounts and groups that are stored in a third-party system, such as LDAP
or Windows Active Directory (AD). The CMS supports third-party
authentication, so users can log on to BusinessObjects Enterprise with their
current LDAP, or Windows AD credentials.
BusinessObjects Enterprise provides the following default groups:
name
Metadata Management Administration
Metadata Management administration
DescriptionDefault group
6
Administrator
Everyone
You might want to create Metadata Management groups, as the following
table describes.
Members of this group have Full Control access level on
Metadata Management administrative and Explorer tasks. By
default, the Administrator group contains only the Administrator
user.
Members of this group have only the View access level on
Metadata Management administrative and Explorer tasks. Each
user is a member of the Everyone group.
Can perform all Metadata Management administrative and
Explorer tasks because members of this group have FullControl access level on Metadata Management folder.
Can run and schedule Metadata Integrators.
Can create custom metadata, edit values of custom attributes and define Metapedia categories and terms.
Members of this group have Full Control access level on
the Metapedia folder.
Can define and edit annotations, custom attributes, and
their values in the Metadata Management Explorer.
Can only view metadata in the Metadata Management Explorer.
•Access levels for Metadata Management tasks on page 98
Access levels for Metadata Management tasks
Access levels are groups of rights that users frequently need. These groups
allow administrators to set common security levels quickly and uniformly
rather than require that individual rights be set one by one.
BusinessObjects Enterprise provides predefined access levels that are based
on a model of increasing rights. Beginning with View and ending with FullControl, each access level builds upon the rights granted by the previous
level. By default, the Administrator group has Full Control access level and
the Everyone group has View access level.
The following table describes the default rights for each access level.
You can also create and customize your own access levels, which can greatly
reduce administrative and maintenance costs associated with security.
Related Topics
•Type-specific rights for Metadata Management objects on page 99
•"Working with access levels" in the BusinessObjects Enterprise
Administrator's Guide.
Type-specific rights for Metadata Management objects
Type-specific rights affect only specific object types, such as integrator
sources or Metapedia objects. The following tables describe the Metadata
Management administration and Explorer tasks that are allowed for each
type-specific right.
You must be part of the Administrator group to perform any actions in the
"Applications" area of the CMC. Because actions on the Metadata
Management utilities and repository are in the "Applications" area, you must
be part of the Administrator group to do the following tasks:
•Configure, run, modify, or delete Metadata Management utilities
•Change the user name and password for the Metadata Management
repository
Table 6-3: Metadata Management administration tasks allowed for each right
Metadata Management
object
Metadata Management
folder
Integrator Sources folder
Source Groups folder
View objects
Edit objects
Modify
rights
View objects
Add objects
View objects
Add objects
Administration tasks allowedRight
•Access the Metadata Management
area of the Central Management
Console
•Access Metadata Management in
the Application area of the Central
Management Console
Change limits for integrator source runs
Manage user security for Metadata
Management
View integrator sources, their run history, their logs, and so on.