Sap Businessobjects Data Services Installation Guide For Windows

SAP BusinessObjects Data Services
Installation Guide for Windows
SAP BusinessObjects Data Services XI 3.2 SP1 (12.2.1)

Copyright © 2009 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,
ByDesign, SAP Business ByDesign, and other SAP products and services
mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries. Business Objects and the
Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks
of Business Objects S.A. in the United States and in other countries. Business
Objects is an SAP company.All other product and service names mentioned are
the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.These
materials are subject to change without notice. These materials are provided by
SAP AG and its affiliated companies ("SAP Group") for informational purposes
only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for
SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
2010-01-07
Contents
Chapter 1 Preparing to Install 9
Pre-installation overview............................................................................10
System requirements...........................................................................11
Network requirements..........................................................................11
User permission requirements.............................................................12
Choose components and determine component distribution...............13
Create a database for each repository.................................................17
Check port assignments.......................................................................18
Check network connections.................................................................21
Create a Windows cluster....................................................................21
Repository database requirements and preparation.................................23
Installing MySQL as the repository database.......................................24
To set up a database account..............................................................25
Setting up an empty database for the repository.................................26
Database-specific requirements for Data Cleanse...............................32
Installation scenarios.................................................................................34
Standard installation overview..............................................................34
Silent installation overview ..................................................................36
Chapter 2 Standard Installation 37

Beginning your installation.........................................................................38
To accept the license agreement.........................................................38
To enter user information and a product keycode................................39
To specify the installation location........................................................39
To select which features to install.........................................................40
To select a repository.................................................................................42
SAP BusinessObjects Data Services Installation Guide for Windows 3

Contents
To configure a MySQL database server...............................................43

To reuse an existing MySQL instance..................................................43
To configure an existing database server.............................................44
To configure a Job Server..........................................................................45
To specify login information..................................................................46
To configure an Access Server..................................................................46
To configure Metadata Integrator...............................................................47
To specify Metadata Integrator configuration details............................48
To specify Metadata Integrator SSL details..........................................49
To select a web application server.............................................................49
To configure your Tomcat application server........................................50
To configure an existing Web application server..................................50
To start the installation...............................................................................53
Chapter 3 Silent Installation 55

Overview of silent installation....................................................................56
Performing a scripted installation..............................................................56
To create a response file......................................................................57
To run a scripted installation.................................................................57
Performing a silent installation...................................................................58
Chapter 4 After Installation 63

Starting services automatically..................................................................64
Logging in to the Management Console....................................................64
Installing cleansing packages....................................................................64
Using the Repository Manager..................................................................65
To create or upgrade repositories........................................................66
To create or upgrade repositories in batch mode.................................67
Using the Server Manager.........................................................................69
To configure Job Servers......................................................................70
4 SAP BusinessObjects Data Services Installation Guide for Windows

Contents
To resynchronize Job Servers..............................................................72

To configure run-time resources...........................................................73
To configure Access Servers................................................................74
Verifying that Job and Access servers are running..............................76
Using the License Manager.......................................................................76
To start License Manager.....................................................................76
To view product activation keycodes....................................................77
To add product activation keycodes.....................................................77
To remove product activation keycodes...............................................78
To use License Manager from the command line................................78
Configuring Metadata Integrator ...............................................................80
Configuring Metadata Integrator in a local environment......................82
Configuring Metadata Integrator in a distributed environment.............83
To configure Metadata Integrator from the configuration wizard..........86
To install an SAP BusinessObjects Enterprise Job Server for Metadata
Integrator..............................................................................................90
To create a Program Job Server group................................................92
To configure the server group settings.................................................93
Metadata Integrator installation tips and troubleshooting.....................94
Connecting the Data Profiler......................................................................96
Installing the SAP BusinessObjects Accelerator Index Designer..............97
Troubleshooting installation problems.......................................................98
Repository problems............................................................................98
Management Console problems..........................................................98
Windows Vista and Server 2008 issues.............................................100
Verifying real-time connectivity...........................................................100
Control the Address Server.....................................................................108
Start the Address Server....................................................................108
Stop the Address Server to install data directories............................109

Contents
Chapter 5 Citrix Support 111

Installing the software..............................................................................112
Initial installation.................................................................................113
Running components in multi-user mode................................................114
Serial access to the License, Server, and Repository Managers.......114
Parallel access to the Management Console, Locale Selector, and
Designer.............................................................................................114
Using shell scripts to access the Locale Selector and Designer........115
Publishing the software............................................................................117
To publish a component.....................................................................117
Connection management...................................................................120
Client setup........................................................................................120
Limitations................................................................................................120
Chapter 6 Directory Data 123

Directory listing and update schedule......................................................124
U.S. Directory expiration..........................................................................127
U.S. Directory expiration schedule..........................................................128
U.S. National and Auxiliary files..............................................................128
Where to copy directories........................................................................129
To copy International directory files to a non-default location ...........129
To install and set up Download Manager.................................................130
To download directory files......................................................................130
Extract directory files on Windows...........................................................131
Chapter 7 Overview of wdeploy 133

Configure wdeploy...................................................................................134
Options for wdeploy.................................................................................135
Deploy all web components.....................................................................135

Contents
Deploy one web component at a time.....................................................136

Verify deployment....................................................................................137
Undeploy all web components.................................................................137
Undeploy one web component at a time.................................................138
Chapter 8 Maintaining your installation 141

Upgrading the software............................................................................142
Component upgrades.........................................................................142
Upgrading your system......................................................................144
Upgrading repositories.......................................................................148
Upgrading cleansing packages..........................................................149
After upgrading the software..............................................................151
Index 153

Contents

Preparing to Install
1
1 Preparing to Install
Pre-installation overview
SAP BusinessObjects Data Services provides an open and flexible
architecture that supports a variety of deployment and configuration scenarios.
Before you install the software you should:
• Ensure that your network and systems meet the basic requirements.
• Obtain the software as well as any required licensing keycodes.
• Review the Release Notes and the "Architecture" section of the Getting
Started Guide.
• If you are upgrading from a previous version, review the Migration
Considerations.
• Ensure that the user who will run the installation program has adequate
permissions to complete the installation tasks.
• Decide which components to install and which of your own components
to integrate.
• Determine where the components should be installed and consider how
you should prepare your infrastructure and set up your environment,
including server locations.
• If you are using an existing database server, create a database instance
if you want to configure a repository during installation.
• Check available port assignments and verify that all machines that will
be part of your deployment have the required network access to each
other.
• Decide whether you want to take advantage of Windows clustering
fail-over support which attempts to automatically restart your SAP
BusinessObjects Data Services services in the event of a hardware or
Windows software failure.
• Choose an installation method.
The following sections list the core software and system requirements, the
choices available within the core requirements, and the install methods
available to you for installing the software.
Related Topics
• Getting Started Guide: Architecture

Pre-installation overview 1
System requirements
For a detailed list of supported environments and hardware requirements,

see the Supported Platforms document available in the SAP BusinessObjects
Support > Documentation > Supported Platforms/PARs section of the SAP
Service Marketplace: http://service.sap.com/bosap-support. This document
includes specific version and patch-level requirements for databases,
applications, web application servers, web browsers, and operating systems.
Before you can install SAP BusinessObjects Data Services, the following
components must be preinstalled and configured:
• Web application server (unless you want to use the Tomcat installation
packaged with SAP BusinessObjects solution portfolio software, or you
do not want to install the Web Tier components)
• Database software that is compatible with the SAP BusinessObjects Data
Services repository (unless you want to use the MySQL installation
packaged with the software).
Note:
Only the database client tools or middleware needs to be installed on the
SAP BusinessObjects Data Services server; the database server itself
can reside on a separate physical machine accessible by network from
the SAP BusinessObjects Data Services server.
Note:
For the repository, the software requires a database that stores metadata
about all objects created with the Designer. For best Designer performance,
it's recommended that the repository database server and the Designer
computer reside in the same network.
Network requirements
When you install SAP BusinessObjects Data Services on multiple machines,

you must ensure that each machine can communicate over TCP/IP with the
machine running the database that contains the repository.
Client components, such as the Designer, require network access to the Job
Server(s).

Note:
If your servers are firewalled, you may need to open the necessary ports to
allow the client components to communicate with the servers.
User permission requirements
To successfully install SAP BusinessObjects Data Services on Windows,

the user running the installation program must have the permissions described
in the table below.
Category Required permission(s)

Operating System Administrative privileges on the local machine.
Network TCP/IP access to all machines where you want to install
components. All specified ports must be available.
Database Permissions to add and drop tables in the database, plus
permissions to read, write, and edit table rows.
In addition, it's recommended that you use the same user account for
installing the software and your web application server.
Note:
• The following scenarios are not supported:
• Installing on a domain controller.
• Installing on a machine where the Windows default security settings
given to the local Administrators group have been modified.
• To run the Designer, a user requires both read and write access to the
installation folder. If you choose to install in the default Program Files
folder, regular users do not have write access. Choose another installation
directory or assign the Designer user write access to LINK_DIR.
Windows Vista and Server 2008

Windows Vista and Server 2008 include the User Account Control (UAC)
feature for additional security. With UAC enabled, the system treats users
belonging to the Administrators group as standard users for most tasks.
When you install SAP BusinessObjects Data Services on Windows Vista or
Server 2008, local system administrator privileges are required.

In addition, you must run the Designer for the first time with administrator
access in order to properly register the application in the system registry.
After the Designer has been registered, normal users can run it and most
other SAP BusinessObjects Data Services applications without requiring
administrator authentication.
The Server Manager can be run only by users belonging to the Administrators
group, or who can provide administrator authentication.
Choose components and determine component

distribution
You may choose to upgrade or install components on one or more computers

based on available resources and amount of system traffic.
Note:
You must install the Designer and Metadata Integrator on a supported
Windows platform. You can install the other components on Windows, UNIX,
or Linux platforms.
The installation program can install multiple feature categories.
Feature category Component Description
Job Server Server that executes batch jobs.
Server that provides real-time access,

Access Server routes real-time messages to the appro-
priate real-time interface.
Integration interfaces that provide ac-

cess to technologies such as JMS (Java
Server Components Technology Interfaces
Messaging System) and Sales-
force.com.
Integration component that collects

Metadata Integrator metadata from an SAP BusinessObjects
Enterprise system for impact and lin-
(Windows only) eage analysis in the Management Con-
sole.

Feature category Component Description
Designer Graphical user interface that is used to

design and test all jobs.
(Windows only)
Client Components
Interface that creates and manages all
Repository Manager types of repositories (local, central, pro-
filer, and cleansing package).
Web application server that can be used

Tomcat application server to deploy SAP BusinessObjects solution
(optional) portfolio software. You can also use your
own existing web application server.
Web application that manages the SAP

Web Tier Compo-
BusinessObjects Data Services environ-
nents
ment (monitors, executes, and sched-
ules jobs), as well as metadata reporting
Management Console
(auto-documentation, Validation and
Operational dashboards, Data Quality
reports, and impact and lineage analy-
sis).
Message Client API that other applica-

Message Client
tions can use to integrate with real-time
Components
jobs.
Documentation
Software product documentation.
Components
For complete description of the components and how they interact, see
"Architecture" in the Getting Started Guide.
Note:
You can configure several Job Server and Access Server instances from
one Job Server or Access Server installation. Configure Job Server and
Access Server instances by using the Server Manager.
You can install components on one or more computers based on available
resources and the amount of traffic the system processes. Before installing
components, consider the following:

• A local repository connects a Designer with a Job Server. You can install
a Job Server on the same computer as the repository, on a stand-alone
computer (with repository database client software), or on the same
computer as a Designer.
• Any Designer can access any local repository and Job Server. Multiple
Designers cannot simultaneously access the same local repository.
Simultaneous access risks metadata corruption in the repository. Also,
you cannot link Designer to more than one local repository at any given
time.
• Install database client software on the computer containing the Job Server
to support the repository associated with that Job Server. For example,
if the repository associated with a Job Server named oradev is an Oracle
database, then Oracle client software must be installed and configured
on the computer containing the oradev Job Server.
The following diagram depicts a simple distribution of components among
computers in a network. Note that you can install each component on one
or more computers. Also note that there are many possible connections
between components. Each box in the diagram represents a different
computer.


You can install the Management Console on any computer with or without
other components. The Management Console is Java-based; you have the
choice to deploy it to the packaged Tomcat server or a previously installed
application server.
Note:
If SAP BusinessObjects Enterprise is installed on the same machine with
the SAP BusinessObjects Enterprise-packaged Tomcat application server,
the installer will detect the existing Tomcat instance and share it instead of
installing a new instance.
Related Topics
• Getting Started Guide: Distributed architecture
Create a database for each repository
SAP BusinessObjects Data Services uses several types of repositories:

Central
Supports multi-user development and allows for check-in and
check-out. Also provides versioning to keep and allow restore for
several versions for the same object.
Cleansing package
Stores dictionaries for the cleansing packages used by Data Cleanse
transforms.
Local
Working repositories where you create and modify applications.
Profiler
Stores profiling metadata when the built-in profiler is configured.
You associate each Job Server with one or more local repositories. There
is no relationship between central repositories and Job Servers.
Create local repositories before you install each Job Server, or configure
them after you install Job Servers by using the Repository Manager.

Note:
If you have Job Servers on more than one machine that connect to the same
local repository, then the repository database connection properties for these
Job Servers must be the same. A job will not run on a Job Server with
conflicting connection properties. The database connection properties for
different databases are shown in this table.
Database Connection property

DB2 DSN
Microsoft SQL SQL Server Machine and database name
MySQL DSN
Oracle tnsnames
Sybase ASE Sybase Server Name
The number of databases you need depends on whether you want a

single-user or multi-user development environment:
• To set up a single-user development environment, create a database for
the local repository.
• To set up a multi-user development environment, create databases for
each local repository (one per user) and a database for the central
repository.
Note:
Multiple Designers can share the same profiler, profiler repository, or
cleansing package repository.
Related Topics
• Repository database requirements and preparation
• Using the Repository Manager
• Advanced Development Guide: Multi-user development
Check port assignments
On each computer, verify that all ports to be used by SAP BusinessObjects

Data Services components are available and not in use by other programs.

For a development system, you can install many components on the same
computer. This simplifies many connections between components (the host
name is always the same), but you must still define connections based on
TCP/IP protocol.
This table details the default ports:
Component
Port Description Default To set
Job Server
Receives commands from

Job Server port or
Designer, Access Server, 3500 Use Server Manager
TCP/IP port
and schedulers.
Adapter/SNMP
Receives commands and
communication 4001 Use Server Manager
sends data to adapters.
port
Packaged Tomcat Application Server
Supports communication be-

Tomcat conf\serv
HTTP port tween web browsers and the 28080
er.xml
Management Console.
Used to start and shut down

the Web Server which sup- Tomcat conf\serv
Shutdown port 28005
ports the Management Con- er.xml
sole.
Access Server
Receives and sends mes-

Communication
sages from clients and ser- 4000 Use Server Manager
port
vices.
Designer
Interactive Debug- Supports communication for Choose Tools > Options

5001
ger port the debugging feature. in the Designer.
Address Server

Component
Port Description Default To set
LINK_DIR\bin\ad
Supports communication for dress_server\Ad
Control port 40010
the Address Server. dressServerCon
fig.txt
LINK_DIR\bin\ad
Supports communication for dress_server\Ad
Application port 40011
the Address Server. dressServerCon
fig.txt
Example: Default configuration

The following configuration diagram shows default port numbers, as well
as the packaged Tomcat installation. Default ports for other web application
servers may differ.

Check network connections
Before you install SAP BusinessObjects Data Services components, check

the computers involved and verify network connections by executing the ping
command on each computer.
Example: Windows Designer and UNIX Job Server

If the Designer will be on a Windows computer and your Job Server will be
on a UNIX computer, from the Windows computer open the DOS prompt
and enter:
C:\> ping hostname

where hostname is the host name of the UNIX computer.
Then from the UNIX computer, log in as root and from the prompt, enter:
$ ping hostname
where hostname is the host name of the Windows computer.
Create a Windows cluster
To take advantage of fail-over support for SAP BusinessObjects Data

Services services in a Windows Clustering Environment, you must create a
Windows cluster before you install the software (refer to your Microsoft
documentation for details). If you choose this option, in the event of a
hardware failure or Windows software failure, the Windows Cluster Manager
will attempt to restart your services.
After you create a Windows cluster:

1. Install the software on a shared drive from the first cluster computer.
2. After you install the software, create a new resource for the SAP
BusinessObjects Data Services service as a Generic Service.

a. Open the Cluster Administrator.

b. Under Active Resources, add a new resource. Enter a Name,
Description and choose Generic Service for the Resource Type.
c. Configure resource dependencies. Since the software is a Generic
Service, it requires a file share, IP address, Network Name, and
available physical disk resources.
d. Configure Generic Service Parameters. Enter DI_JOBSERVICE as
the Service name.
3. Create a new resource for your web application server as a Generic
Service. (If you did not install the Management Console, skip this step.)
a. Under Active Resources, add a new resource. Enter a Name,
Description and choose Generic Service for the Resource Type.
b. Configure Generic Service Parameters. Enter the service name and
click to select the Use Network Name for computer name option.
You can find the service name of your web application server by
double-clicking the service in the Windows services window. For the
packaged Tomcat installation, the service name is BOE120Tomcat.
4. Run the cluster install utility (js_cluster_install.exe located in the

bin directory of your software installation) on the other cluster computers
to populate them with the SAP BusinessObjects Data Services
service-related information.
a. Copy the js_cluster_install.exe and bodi_clus
ter_conf.txt files from the bin directory on your primary cluster
computer.
b. Paste these files to each non-primary cluster computer and run the
following commands to install the SAP BusinessObjects Data Services
and to replicate the shortcuts set up on the primary cluster computer:
js_cluster_install.exe -install if using system ac

count
js_cluster_install.exe -install -Uuser -Ppasswd -
Ddomain when not using system account on primary
node
js_cluster_install.exe -remove
c. SAP BusinessObjects Data Services components will use a Cluster

Network Name to communicate with other components over your
network. Open the Server Manager, enter the Cluster Network Name
and click Apply.

Repository database requirements and preparation 1
Note:
If Job Servers are already configured before you enter the Cluster
Network Name, the Server Manager will prompt you to enter a
password for each currently configured repository associated with
each configured Job Server.
d. Click Restart.
Related Topics
• Beginning your installation
Repository database requirements and

preparation
SAP BusinessObjects Data Services stores your design metadata for source
and target tables as well as database functions and definitions of built-in
objects in database tables. This set of database tables is called the repository.
You can create one repository during installation. If you want to create a
repository in an existing database, you must create space for the repository
before you run the installation program. The installation program connects
to the repository and populates it.
A repository requires a minimum of 20 MB of free disk space on the database

server.
The following sections detail required settings for:
• IBM DB2
• Microsoft SQL Server
• MySQL
• Oracle
• Sybase ASE
Before you install the software, you should review this information in order
to properly prepare your repository database.
Note:
You can also choose to skip creating a repository during installation, and
use the Repository Manager to create it at a later time.

Repository database requirements and preparation
Note:
If you want to use multi-byte metadata, such as Japanese column names
on imported tables or multi-byte data in Data Quality reports, your database
must be configured to use Unicode character encoding, such as UTF-8.
Related Topics
Installing MySQL as the repository database
MySQL database server is an open-source database that provides local data

storage. The SAP BusinessObjects Data Services installation program can
install and configure MySQL as the database server for an installation on
Windows. If you already have MySQL installed, the installation program can
be used to configure the repository database using your existing database
engine.
Note:
• The packaged MySQL database can be used only to store SAP
BusinessObjects Data Services repository tables. You are not allowed to
store your own data (for example, from a datamart or data warehouse)
in this MySQL instance.
• If you choose to use the packaged MySQL installation, the database
server is uninstalled when you uninstall SAP BusinessObjects Data
Services. If you want to uninstall the software before you upgrade to a
new version, back up the repository with the MySQL administration tools.
MySQL installation details

The installation program creates a new MySQL installation with the following
details:

Property Value
ODBC datasource name DataServices
MySQL schema name DataServices
MySQL service name BOE120MySQL
Note:
The TCP/IP port number, the root user password, and the username and
password for the account that owns the MySQL schema can be configured
during installation.
The MySQL administration tools are also installed to the MySqlAdmin5
folder at the same level as LINK_DIR. To start or stop the MySQL service,
you can use the installed MySQL administration tools or the "Services" panel
located in the "Administrative Tools" section of the Windows Control Panel.
For more information about administering the MySQL installation, see the
MySQL documentation at http://dev.mysql.com/doc/index.html.
Related Topics
• To back up and restore the MySQL database
To set up a database account
To administer the repository database, you need to set up a database

account. If you choose to install MySQL as part of your SAP BusinessObjects
Data Services installation, you are prompted during installation to set up this
account. If you plan to use your own database, complete the steps listed
below before you install the software.
1. Create or select a user account that provides the software with the
appropriate privileges to your database server.
2. Verify that you can log on to your database and carry out administrative
tasks using this account.

Setting up an empty database for the repository
If you want to use an existing database server, you must create a new
database on your database server before you install SAP BusinessObjects
Data Services.
The following database servers are supported for the repository database:
• IBM DB2
• MySQL
• Oracle
• Sybase ASE
Note:
For information related to supported database software and version
requirements, see the Supported Platforms document available in the SAP
BusinessObjects Support > Documentation > Supported Platforms/PARs
section of the SAP Service Marketplace: http://service.sap.com/bosap-sup
port.
To use your existing database with the software, you need to prepare it.
1. Create a new database.
2. Create a new user account and password for the database — to be used
by the software.
3. Specify that the new user account has the required permissions to create,
modify, and delete tables and create procedures so that the database
can be modified as necessary.
4. Record the name of the database, the user account, and the password
when you run the installation program.
During the installation, you can choose to reinitialize the existing database.
This will cause new tables to be created in your existing database to store
SAP BusinessObjects Data Services data. If you are unsure of the procedure
for creating a new database, consult your specific database server
documentation.
Note:
If you have an existing SAP BusinessObjects Data Services or SAP
BusinessObjects Data Integrator repository, you can upgrade the repository
during installation or use the Repository Manager to upgrade it after
installation. If you have an existing SAP BusinessObjects Data Quality

Management repository, create a new SAP BusinessObjects Data Services
repository and see the Migration Considerations.
32-bit and 64-bit notes

SAP BusinessObjects Data Services 32-bit and 64-bit software is supported
on a variety of operating systems. When you use a database client with the
32-bit software, the 32-bit database client libraries must be installed and
referenced in the library paths.
For example, the default installation of the Oracle 64-bit client includes
installation of the 32-bit client. For non-standard installations, these libraries
must be specified as part of the installation. After installation, the libraries
should be in the $ORACLE_HOME\lib32 directory.
If these 32-bit libraries are not present, you receive an error message stating
that the software cannot load the client library. Examples of error messages
include:
(5.2) 02-05-02 14:55:23 (E) (26797:0001) CON-120103:

System call <dlopen> to load and initialize functions
failed for <libclntsh.a>. Make sure the SHARED LIBRARY
is installed and resides in the correct location.
(5.2) 02-05-02 14:55:23 (E) (26797:0001) REP-100108:

Cannot perform operation on Repository<Default Reposito
ry> because a connection to the repository was never
opened. A connection must be opened to the repository
before performing any operation.
When you use a database client with the 64-bit software, the 64-bit client
libraries must be installed and referenced in the library paths.
DB2 database setup requirements
A local or central SAP BusinessObjects Data Services repository requires

that you create a dedicated database and define a user with the following
rights:
• To create a table
• To start a session
• To create a sequence

Install the DB2 Application Enabler software and use DB2 Control Center
and DB2 Script Center to verify the connection between the Designer
computer and the repository computer.
Note:
For a repository on DB2, the software also requires a temporary table space
with a page size of 8-16K.
When the database is created, you need to prepare it for the installation.
Microsoft SQL Server database setup requirements
When you create a repository on Microsoft SQL Server, choose between

Windows authentication (by selecting the check box) and Microsoft SQL
Server authentication (by completing the Microsoft SQL Server user name
and password fields):
• Windows authentication — Microsoft SQL Server validates the login
account name and password using information from the Windows
operating system.
• Microsoft SQL Server authentication — Microsoft SQL Server
authenticates the existing Microsoft SQL Server login account name and
password.
Related Topics
• To prepare your database
MySQL database setup requirements
You must configure the following information prior to installation and supply
it when you create a repository on MySQL:
• ODBC (MySQL) Data Source Name
• Username
• Password
The ODBC name is either the user Data Source Name (DSN), or the system
DSN.

If you select the option to install and configure MySQL that is supplied with
your installation, the installation creates a MySQL database with the default
settings for the repository database.
Caution:
If you provide the password when creating an ODBC data source, users will
be able to log into the Designer without specifying a password. If you choose
to install the packaged MySQL server, the password is automatically specified
for the ODBC data source, and anyone with a valid username can access
the Designer without specifying a password.
Related Topics
Oracle database setup requirements

that you create a dedicated database and define a user with the following
rights:
• To create a table
• To start a session
• To create a sequence
Grant the user the connect and resource roles. For Oracle 10G/R2, also
grant the create view role.
Install the Oracle client software and use SQL*Plus to verify the connection
between the Designer computer and the repository.
Note:
To store multi-byte characters in a repository table when the repository is on
an Oracle database, you must change the Oracle database character set to
a code page that supports the multi-byte language that you plan to use or
you risk corrupting your metadata. For example, to store Japanese characters,
change the Oracle database character set to either SHIFT_JIS or UTF8.
Related Topics

Sybase database setup requirements

that you create a dedicated database and define a user.
Note:
For UNIX Job Servers, when logging in to a Sybase repository in the
Designer, the case you type for the database server name must match the
associated case in the SYBASE_Home\interfaces file. If the case does
not match, you might receive an error because the Job Server cannot
communicate with the repository.
If you are using both Sybase and Microsoft SQL Server on a Windows
platform, ensure the Sybase path precedes the Microsoft SQL Server path
in the environment variables %PATH% statement.
Related Topics
To prepare your database
1. Create a new, empty database on your database server.

2. Create a new user and assign it a secure password.
3. Ensure that the new account has permission to create, modify, delete
tables and create procedures so that the software 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.
4. Before you begin your installation, ensure the following are set up:

Database type Information required
DB2 DB2 database alias
Microsoft SQL Server Database name
MySQL ODBC datasource name
Oracle tnsnames connect identifier
Sybase ASE Sybase server name
Database name
Note:
The Sybase server name is a combination of the host name and the port
number which is set by your database administrator in the file sql.ini.
5. Record these details because you are required to provide them during
installation:
• The name of your database, ODBC datasource name, Sybase server
name, Oracle tnsnames connect identifier, or DB2 database alias.
• The user account and the password authorized to the database.
For information on how to create a new database, consult your database

server documentation or your database administrator.
Related Topics
• DB2 database setup requirements
• Microsoft SQL Server database setup requirements
• MySQL database setup requirements
• Oracle database setup requirements
• Sybase database setup requirements

Database-specific requirements for Data Cleanse
SAP BusinessObjects Data Services has specific requirements for the

database repository used by cleansing packages or custom Data Cleanse
dictionaries created using Universal Data Cleanse. For disk space
requirements, see the Supported Platforms document available in the SAP
BusinessObjects Support > Documentation > Supported Platforms/PARs
section of the SAP Service Marketplace: http://service.sap.com/bosap-sup
port.
Requirements for specific database server and client settings are described
in the following table:

Database type Required settings
DB2 Server settings

• Code Page – 1208
• Character Set – UTF-8
Note:
When creating a DB2 9 database, be sure to check the
Enable Database for XML option.
Client settings
• DB2CODEPAGE – 1208
You can use the db2set utility to configure this environ-

ment variable. For more information, see the DB2 docu-
mentation.
Note:
The DB2 client version must match the DB2 server version.
For example, if your server uses DB2 9, use the DB2 9
client.
MySQL The MySQL server and client must be configured with

UTF-8 as the default character set.
In the DSN connection configuration window, set the

ODBC connection code page to UTF8.
Oracle

Installation scenarios
Database type Required settings
Server settings
• NLS_CHARACTERSET – AL32UTF8
• NLS_NCHARSET – AL16UTF16
To determine the currently configured character set, you

can use the following select statement on the Oracle
server:
Select * from nls_database_parameters

WHERE
PARAMETER = 'NLS_CHARACTERSET' OR
PARAMETER = 'NLS_NCHAR_CHARACTERSET'
Client settings
• NLS_LANG – AMERICAN_AMERICA.AL32UTF8
Note:
The Oracle client version must match the Oracle server
version. For example, if your server uses Oracle 9, use
the Oracle 9 client.
Standard installation overview
A standard installation allows you to specify which components to install.

You may want to perform a custom installation when you want to exclude
some components, or install only a limited set of components.
The installable feature categories include:

• Server Components
• Client Components
• Web Tier Components
• Message Client Components

Installation scenarios 1
• Documentation Components
By default, MySQL is installed as the repository database, and Tomcat is

installed as the web application server. You can also choose to use your
own database or web application server during the installation process.
Note:
During installation, you can choose whether to configure many of the
components, such as Job Servers and Access Servers. If you skip component
configuration during installation, you can use the configuration tools to
accomplish these tasks after installation has finished.
Related Topics
• Choose components and determine component distribution
To perform a standard installation
1. Obtain the software and licensing keycodes.

2. Confirm requirements and determine component distribution.
3. Check port assignments and network connections.
4. Create databases for repositories that you want to configure during
installation.
5. Install components.
After installation, you can perform any additional configuration needed using
the configuration tools. For example, you can:
• Create additional local, central, or cleansing package repositories with
the Repository Manager.
• Register any repositories in the Management Console.
• Create and configure a profiler repository.
• Configure additional Job Servers with the Server Manager.
• Add any additional license keycodes with the License Manager.
Related Topics
• Pre-installation overview
• Using the Server Manager

• Using the License Manager

• Logging in to the Management Console
Silent installation overview
You can run a silent installation to install SAP BusinessObjects Data Services
from the command line using a response file containing installation
parameters. This method is particularly useful when you need to perform
multiple installations or you do not want to interrupt people who are working
on machines in your system.
You can also incorporate the silent installation command into your own build
scripts. For example, if your organization uses scripts to install software on
machines, you can add the silent installation command to those scripts.
You may want to choose a silent installation when:

• You are already familiar with the installation program.
• You need an automated method for performing similar installations on
several machines.
• You do not want to run the installation program.
Related Topics
• Overview of silent installation

Standard Installation
2
2 Standard Installation
Beginning your installation

The following instructions lead you through the initial steps of setting up your
SAP BusinessObjects Data Services installation. In this stage you will do
the following:
• Agree to the license terms.
• Enter the product activation keycode.
• Select where to install the software.
• Select which features to install.
When you perform the following installation, all the components that you
select are installed on the local machine.
You can start installation by running setup.exe. After the "Welcome" screen
is displayed, click Next to begin your installation.
Tip:
Before beginning your installation, review the pre-installation overview to
ensure that you have prepared all necessary systems.
Related Topics
• Pre-installation overview
To accept the license agreement
At the "License Agreement" screen, review and accept the license agreement
for SAP BusinessObjects Data Services. You must accept the agreement
to continue with the installation.
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.

Beginning your installation 2
To enter user information and a product keycode
At the "User Information" screen, enter user information and provide a product
keycode for your SAP BusinessObjects Data Services 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 can enter a single base product keycode during installation. If you
need to add additional keycodes for other features that you've purchased,
you can enter them after installation by using the License Manager.

Related Topics
• Using the License Manager
To specify the installation location
At the "Directory Selection" screen, enter the location for your SAP
BusinessObjects Data Services installation.
1. Specify where to install the components in the Destination Folder field.
The default location is C:\Program Files\Business
Objects\BusinessObjects Data Services\.
Restriction:
The maximum allowable path length is 100 characters. In addition, the
Destination Folder field does not support multi-byte characters. To install
the software on a system with a multi-byte locale, you can specify the
installation location with single-byte characters or use the default location.
Note:
• To run the Designer, a user requires both read and write access to
the installation folder.

• The installation program creates a Windows environment variable

named LINK_DIR for this path. LINK_DIR is used throughout the
software documentation to refer to this path.
Depending on your component selection, the installation program may
create other folders or files at the same level as the software installation
folder:
• BusinessObjects Enterprise 12.0
• common
• deployment
• javasdk
• Tomcat55
• LanguagePacks.xml
To select which features to install
At the "Select Features" screen, choose which components to install.

1. Select the features that you want to install or deselect features that you
do not want to install:

Beginning your installation 2
Feature catego- Description
ry
Server compo- Includes the Job Server, Access Server, MySQL

nents (Server), Metadata Integrator, Address Server, Tech-
nology Interfaces, and other adapters.
All server components install by default unless dese-

lected.
Client compo- Includes the Designer and Repository manager.

nents
All client components install by default unless dese-
lected.
Web Tier com- Includes the optional Tomcat application server instal-
ponents lation and the Management Console web application
(including the Administrator, Impact and Lineage
Analysis, Operational Dashboards, Data Quality
Dashboards, Auto Documentation, and Data Quality
Reports).
All Web Tier components install by default unless de-

selected.
Message Client Includes the C++ and Java libraries for integrating
components external application with real-time jobs.
The Message Client components do not install by

default unless selected.
Documentation Includes software documentation as PDF documents.

components
The Documentation components install by default
unless deselected.
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.

To select a repository
• 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.
2. To check if you have enough available disk space for the selected
components, click Disk Cost.
The disk cost screen appears. Click OK to return to feature selection.
3. If you want to reset the feature selection to default, click Reset.
4. When you have made your component selections, click Next to continue.
At the "Repository Selection" screen, choose which type of database to use
for the repository.
1. Select the type of repository that you want to configure.
• Install MySQL database server
Note:
The MySQL administration tools are also installed to the MySqlAdmin5
folder at the same level as LINK_DIR.
• Reuse an existing BOE MySQL instance
Note:
This option is only available if SAP BusinessObjects Enterprise and
packaged MySQL server are installed on the system.
• Use an existing database server
• Skip configuration
You can configure one local repository during installation. If you skip the
configuration, or you need more repositories, you can configure additional
repositories later by using the Repository Manager.
Caution:
It's recommended that you do not use database tools to attempt to quickly
replicate additional repositories. By using the Repository Manager to
create and seed multiple repositories individually, you can avoid potential
issues related to the configuration of repository objects.
2. Click Next to continue.

To select a repository 2
Related Topics
To configure a MySQL database server
If you chose to install MySQL as the database server for the new installation,
the "MySQL Database Server Configuration" screen appears.
1. Specify the port number for the MySQL database server in the MySQL
Port Number field.
The default port number is 3306. Use this number unless this port is
unavailable.
2. Specify and confirm a password for the MySQL root user account.
The root user is required for administrative and maintenance tasks on
the MySQL server, such as creating new users for more repositories or
performing backups.
3. Specify and confirm a username and password for the MySQL Repository
user account.
To reuse an existing MySQL instance
The "Local Repository Location" screen appears if you chose to reuse an

existing SAP BusinessObjects Enterprise MySQL instance as your repository
for the new SAP BusinessObjects Data Services installation. At this screen,
specify the connection information for the database where the repository will
be created.
1. Choose the ODBC datasource name for the MySQL instance that you
want to reuse.
2. In the User name field, specify the user name for the account authorized
to use the database.
3. In the Password field, specify the password for the account authorized
4. Click Get Version to check the database connection and verify whether
a version of the repository already exists. If you are upgrading from an
existing SAP BusinessObjects Data Integrator or SAP BusinessObjects

Data Services repository, select Upgrade to keep and upgrade the existing
repository. If you are creating a new repository, select Create.
Caution:
If you choose to use Create on an existing repository, the repository
tables are recreated, and all data in the existing repository will be lost.
To configure an existing database server
The "Local Repository Location" screen appears if you chose to use an

existing database server as your repository for the new SAP BusinessObjects
Data Services installation. At this screen, specify the connection information
for the database where the repository will be created.
1. Select a database type from the Database type drop-down list.
Depending on your database type selection, corresponding input fields
are displayed.
2. Provide the database-specific required information in the fields displayed.
Database type Required information
DB2 DB2 datasource name
Microsoft SQL Database server name

Server
Database name
Windows authentication
MySQL ODBC datasource name
Oracle Database connection name
Sybase ASE Database name
3. In the User name field, specify the user name for the account authorized

To configure a Job Server 2
4. In the Password field, specify the password for the account authorized
5. Click Get Version to check the database connection and verify whether
a version of the repository already exists. If you are upgrading from an
existing SAP BusinessObjects Data Integrator or SAP BusinessObjects
Data Services repository, click Upgrade to keep and upgrade the existing
repository. If you are creating a new repository, click Create.
Caution:
If you choose to use Create on an existing repository, the repository
tables are recreated, and all data in the existing repository will be lost.
To configure a Job Server

At the "Configure Job Server" screen, create a new job server.
1. Select the type of Job Server configuration to perform:
• Configure a new Job Server (Default)
• Skip Job Server configuration
If you skip the configuration, you can configure a Job Server later using
the Server Manager. Any existing Job Servers from a previous SAP
BusinessObjects Data Integrator or SAP BusinessObjects Data Services
installation will be retained, unless it has been uninstalled or DSCon
fig.txt has been removed.
2. If you chose to configure a new Job Server, specify a name and port
number for the new server in the Job Server name and Job Server port
fields.
The default Job Server port is 3500.
3. If you need to configure SNMP support or change the runtime resources
for the Job Server, click Advanced.
The Job Server details screen is displayed. Make any necessary
configuration changes and click OK.
Note:
If you are using a Sybase or DB2 repository, and need to change the locale
of your Job Server, use the Locale Selector after installing the software. To
use the Locale Selector, choose Start > Programs > SAP BusinessObjects

To configure an Access Server
XI 3.2 > SAP BusinessObjects Data Services > Data Services Locale
Selector.
Related Topics
• To configure Job Servers
To specify login information
At the "Login Information" screen, specify the account that the SAP
BusinessObjects Data Services service will use to start Job and Access
Servers.
1. Select the type of account to use:
• Use system account
• Use this account
If you use the system account, you must reboot the system following the
installation.
Note:
The account you use must have:
• full access to the software installation directory
• rights to Log on as a Service
You can change this account and password later using the Windows
Services tool.
2. If you chose to specify a user account, enter the username and password
in the User and Password fields.
3. Click Next to continue the installation configuration.
To configure an Access Server

At the "Configure Access Server" screen, create a new access server.
1. Select the type of Access Server configuration to perform:
• Configure a new Access Server (Default)
• Skip Access Server configuration
Note:
The Access Server is only required for real-time processing. If you do not
need real-time processing, skip Access Server configuration. Real-time

To configure Metadata Integrator 2
and transactional processing is not licensed in all SAP BusinessObjects
Data Services packages and is available as an option.
If you skip the configuration, you can configure an Access Server later
by using the Server Manager. Any existing Access Servers from a previous
SAP BusinessObjects Data Integrator or SAP BusinessObjects Data
Services installation will be retained, unless it has been uninstalled or
DSConfig.txt has been removed.
2. If you chose to configure a new Access Server, specify a directory and
port number for the new server in the Directory and Communication
port fields.
The default directory for the Access Server is LINK_DIR\bin\Ac
cessServer_1 and the default port is 4000.
3. Check Enable Access Server if you want the Access Server to start
when the system service is started. By default, Enable Access Server
is checked.
Related Topics
• To configure Access Servers
To configure Metadata Integrator

If you chose to install Metadata Integrator and SAP BusinessObjects
Enterprise is already installed, the "Configure Metadata Integrator" screen
appears. At this screen, create a new Metadata Integrator configuration.
1. Select the type of Metadata Integrator configuration to perform:
• Configure a new Metadata Integrator
• Skip Metadata Integrator configuration
If you skip the configuration, you can configure Metadata Integrator later
by choosing Start > Programs > SAP BusinessObjects XI 3.2 > SAP
BusinessObjects Data Services > Data Services Metadata Integrator.
2. If you chose to create a new Metadata Integrator configuration, type a
name for the new configuration in the Configuration name box.
3. Click Next to continue installation.
Note:
It's strongly recommended that you install SAP BusinessObjects Enterprise
before installing Metadata Integrator. However, if you must install SAP

To configure Metadata Integrator
BusinessObjects Enterprise later, a script is provided to configure Metadata

Integrator later.
Related Topics
• To configure Metadata Integrator after installing SAP BusinessObjects
Enterprise
To specify Metadata Integrator configuration details
At the "Configure Metadata Integrator" screen, specify details for your

Metadata Integrator configuration.
1. Specify the host name of your SAP BusinessObjects Enterprise CMS
server in the Server name field.
2. Check Enable SSL if you want to use a SSL secure connection.
3. Specify the user name used to connect to the CMS server to register and
execute the Metadata Integrator in the User field.
4. Specify the password for the CMS user in the Password field.
5. Select the CMS authentication mode from the Authentication Mode
drop-down list.
For more information about the available modes, see the SAP
BusinessObjects Enterprise Administrator's Guide.
6. Specify the folder in which the CMS system adds the Metadata Integrator
as a program object in the Folder name field.
The default value is Data Services. If the specified folder does not exist,
it is created automatically.
7. Specify configuration for your SAP BusinessObjects Data Services
repository database in the "Repository Database server" area.
If you chose to use the packaged MySQL server or an existing SAP
BusinessObjects Enterprise MySQL installation, this area is disabled.

To select a web application server 2
To specify Metadata Integrator SSL details
If you chose to enable SSL for the Metadata Integrator, the "Configure
repository for Metadata Integrator" screen is displayed. At this screen, specify
the SSL details for your Metadata Integrator configuration.
1. Click Browse to specify the location of your SSL certificates.
2. Specify the filenames for the Server SSL Certificate, SSL Trusted
Certificates, SSL Private key, and SSL Passphrase in the appropriate
fields.
To select a web application server

If you chose to install the Web Tier Components, you need to provide
information about the web application server that will work with your software.
Use the "Select Web Application Server" screen to either install Tomcat as
your application server, or to work with your existing web application server.
To configure your web application server for SAP BusinessObjects Data

Services, you need account information along with port information.
1. Select one of the following options:
• Use a pre-installed Web Application Server
• Install Tomcat application server
2. To use your current Web application server, choose your server type from
the drop-down list provided.
Tip:
You can configure the server during the current installation process. You
will need to provide access information for this server in a subsequent
screen.

Note:
You can use the Manual Deploy option to install the SAP BusinessObjects
Data Services web application WAR files and then manually deploy the WAR
files to a supported web application server after installation. You must perform

the manual deployment on the same machine where Data Services is

installed.
For manual deployment instructions for a specific web application server,

refer to SAP Note 1347589 in the SAP Service Marketplace.
For a list of supported web application servers, see the Supported Platforms
document available in the SAP BusinessObjects Support > Documentation
> Supported Platforms/PARs section of the SAP Service Marketplace:
http://service.sap.com/bosap-support.
Related Topics
• SAP Note 1347589
To configure your Tomcat application server
The "Configure Tomcat" screen is displayed during installation setup if you

choose to install Tomcat as the web application server for your current SAP
BusinessObjects Data Services installation. At this screen, configure Tomcat.
1. In the fields provided, specify which port numbers will be used by Tomcat
for connection, shutdown, and redirect.
Tip:
You can accept the default values for each port setting.

Note:
If you need to change the Tomcat port settings after installation, you can
modify the Tomcat setup.xml file. By default, this file is installed to the
Tomcat55\conf folder at the same level as LINK_DIR.
To configure an existing Web application server
The "Configure Web Application Server" screen is displayed during installation

after you specify an existing server in the "Select Web Application Server"
screen. To properly install web components on your web application server,
you must provide specific configuration information about your existing web
application server.

To select a web application server 2
1. Specify the required configuration information for your existing web
application server.

Web Application Required information

Server
Apache Tomcat • Server Instance: Name of the current web application server instance
5.5 (for example, localhost).
• Application Server Installation Directory: The directory where the web
application server is installed.
WebLogic 10 • Port: Administration port of the application server (for example, 7001).
This is mandatory for Weblogic.
• Username: User name with administration rights to the application server.
• Password: Password for account with administration rights to the appli-
cation server. This is mandatory for Weblogic.
• Server Instance: Name of the current web application server instance
(for example, mserver1).
• Application Server Installation Directory: The directory for the web
application server instance (for example, C:\bea\weblogic10\sam
ples\domains\wl_server).
WebLogic 9 • Port: Administration port of the application server (for example, 7001).
• Username: User name with administration rights to the application server.
cation server. This is mandatory for Weblogic.
(for example, mserver1).
application server instance (for example, C:\bea\weblogic92\sam
ples\domains\wl_server).
WebSphere 6.1

To start the installation 2
Web Application Required information
Server
• Port: Administration port of the WebSphere application server (that is,

the SOAP port). If not specified, the default SOAP port will be used.
• Username: User name with administration rights to the WebSphere ap-
plication server.
Note:
If Admin is Secure is not selected, you do not need to specify a username
or a password.
cation server.
(for example, server1).
• Virtual Host: The virtual host to which the application must be bound
(for example, default_host).
• Admin is Secure: Select this option to enable security requiring admin-
istrative access credentials to the application. If WebSphere was installed
with the secure option, this is required.
application server instance (for example, C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01).

Note:
To deploy the Management Console to a web server farm, run the SAP
BusinessObjects Data Services installation program on each web server in
the farm.
To start the installation

The "Start Installation" screen is the final screen in the installation program.
• Review the components that will be installed and any associated settings.
If you want to make changes, use the Back button. All entries are retained;
you do not need to re-enter all the information.

To start the installation
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.
• Click the Next button to start the final installation process.
• At the end of installation, you can launch the License Manager
automatically by checking Launch License Manager before clicking
Finish.
Note:
To ensure proper operation, it's recommended that you restart the computer
after you install or uninstall SAP BusinessObjects Data Services.

Silent Installation
3
3 Silent Installation
Overview of silent installation
Overview of silent installation

There are two methods for running SAP BusinessObjects Data Services
installations for Windows directly from the command line:
• Silent installation using a response file – referred to as a scripted
installation in this guide
• Silent installation specifying parameters directly on the command line
Both methods can be used to automate installations across multiple
machines. The scripted installation requires you to specify a response file.
The silent installation allows you to specify parameters for running set
up.exe.
Note:
The silent installation without the response file is not recommended for custom
installations. This method does not allow for the same level of customization
provided when using 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 integrate the scripts and commands
into your own installation scripts.
Performing a scripted installation

While setting up an installation process, you can write installation settings
to a specified response file. The file is generated once the installation setup
program is ready to start the installation.
The response file supports the standard installation type available for SAP
BusinessObjects Data Services.
Tip:
You do not start the installation process to generate the response file. Click
Cancel to abort the installation once you reach the final screen in the
installation program.

Silent Installation
Performing a scripted installation 3
To create a response file

1. Open a command line console and navigate to the folder that contains
the installation files.
2. In the command line, type setup.exe -w and the file path for the response
file you want to generate. For example:
setup.exe -w responseFilePath/responseFileName
Note:
You must include both the path and file name for the response file you
want to generate.
3. Press Enter to launch the installation program.

4. Follow the onscreen instructions to enter your preferred installation settings
until you reach the final screen of the installation program.
These settings are recorded in the response file.
5. Click Cancel to abort the installation once you reach the final screen in
the installation program.
You can access the response file from the directory you specified in step 2.
To run a scripted installation
You need to have a response file residing in a known directory.

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 response.ini
• -r filename Specifies the name of the response file you want the
installation program to read for installation parameters.
Note:
By default, the installation program will restart the system following a
scripted installation. If you want to prevent the system from restarting,
add REBOOT=NULL to the command. For example, setup.exe -r
d:\response.ini REBOOT=NULL
3. Press Enter to launch the installation.

Performing a silent installation

You can run a silent installation from the command line to automatically install
SAP BusinessObjects Data Services on any machine in your system, without
the installation program prompting for information during the installation. To
install silently, run setup.exe, adding parameters that provide information
for installation settings and directory paths.
This type of installation is particularly useful when you need to perform

multiple installations. You can also use the silent installation script in your
own scripts. For example, if your organization uses scripts to install software
on machines, you can add the silent installation command to your scripts.
The silent installation command consists of setup.exe and a number of

parameters that provide information about the installation.
The following example would perform an installation with the following

configuration:
• SAP BusinessObjects Data Services
• Tomcat
• MySQL
• Repository database reinitialized
Note:
The example uses the most common parameters. You can choose any
number of valid parameters, but it is good practice to keep the silent
installation as simple as possible.
The following table lists the most common parameters used in a silent
installation. To use a parameter, place it on the command line after set
up.exe.
Note:
Parameter values are case-sensitive.

Silent Installation
Performing a silent installation 3
Installation Description
parameter
/qn+ Specifies that the user is only prompted when the installation
is complete.
/qn Specifies that the user is not prompted during the install, or
when the install is complete.
/qa /qb Specifies that the user is not prompted during the install, or
when the install is complete.
INSTALLDIR Specifies the machine and directory where you want to install
the new components.
For example, C:\Program Files\Business Ob

jects\BusinessObjects Data Services
PIDKEY Specifies your base product activation keycode.
DATABASEUID Specifies the user ID for the database.
For trusted authentication this parameter is not required,

use DATABASEAUTHENTICATION=trusted.
DATABASEP Specifies the MySQL root password.

WD_MYSQL
ROOT
DATABASEP Specifies the account password for the database you'll be

WD using for the software.
For trusted authentication, this parameter is not required,

use DATABASEAUTHENTICATION=trusted instead.

parameter
DATABASEDRIV Identify the type of database for the repository.

ER
For Oracle, enter OracleDatabaseSubsystem.
For DB2, enter DB2DatabaseSubsystem.
For Sybase, enter SYBASEDatabaseSubsystem.
For ODBC SQL, enter ODBCDatabaseSubsystem.
For Remote MySQL, enter MySqlDatabaseSubsystem.
DATABASED Specifies the ODBC DSN for the repository database.

SN
DATABASE Specifies the port used for MySQL Server. Defaults to port
PORT 3306 if it is not specified.
DATABASEDB Specifies the name of the CMS database. This database

name defaults to BOE120 if this parameter is not specified.
DATABASEDB_AU Changes the name of the MySQL audit database, otherwise,

DIT the default name of BOE120_Audit will be used.
DATABASEUID_AU Specifies the user ID for the database.

DIT
For trusted authentication this parameter is not required,
use DATABASEAUTHENTICATION=trusted.
DATABSEP Specifies the account password for the database you'll be

WD_AUDIT using for the software.
For trusted authentication, this parameter is not required,

use DATABASEAUTHENTICATION=trusted instead.

Silent Installation
Performing a silent installation 3
parameter
TOMCATDIR Changes the default directory where Tomcat is installed.

If you don't specify this parameter, Tomcat will be installed
the directory TOMCAT under the default directory for the
software.
TOMCAT_CON Specifies a different connection port. If this option is not

NEC specified, port 28080 will be used.
TION_PORT
TOM Specifies a different redirect port. If this option is not speci-

CAT_REDI fied, port 28443 will be used.
RECT_PORT
TOM Specifies a different shutdown port. If this option is not

CAT_SHUT specified, port 28005 will be used.
DOWN_PORT
ADDLOCAL Specifies which components will be installed. This is the

same as running a Custom install. Each component is
specified, comma separated and grouped within quotes.


After Installation
4
4 After Installation
Starting services automatically
Starting services automatically

The SAP BusinessObjects Data Services service and packaged Tomcat
service start automatically when the computer restarts. The service then
starts Job Servers and Access Servers on the restarted computer.
You can change service startup to Manual in the Windows services window.
Note:
The Address Server service is set to Manual startup by default, but must be
started before using the Global Address Cleanse or Global Suggestion List
transforms. If you do not need Global Address Cleanse or Global Suggestion
List functionality, it's recommended that you leave the Address Server service
as Manual and do not start it.
Logging in to the Management Console

After an Access Server is running, you can configure it by using the
Management Console.
Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAP
BusinessObjects Data Services > Data Services Management Console.
Log in to the Management Console using the default name (admin) and
password (admin).
Related Topics
• Management Console Administrator Guide: Logging in
• Management Console problems
Installing cleansing packages

Installing a cleansing package prepares your system to use Data Cleanse
to control parsing of name and firm data for the specific cleansing package
language. Ensure that your environment meets the database-specific
codepage and disk space requirements. For more information, see the
Supported Platforms document available in the SAP BusinessObjects Support
> Documentation > Supported Platforms/PARs of the SAP Service
Marketplace: http://service.sap.com/bosap-support.

After Installation
Using the Repository Manager 4
Note:
For custom Data Cleanse dictionaries you plan to create using Universal
Data Cleanse, you do not need to install a cleansing package. You can use
the local or central repository. However, you must ensure that the repository
you use meets the database-specific codepage and version requirements.
1. Install the cleansing package data on both the client and server systems
by running setup.exe from the cleansing package installation disc or
downloaded location.
The cleansing package installer lays down the required reference data
to LINK_DIR\DataQuality\datacleanse.
2. Use the Repository Manager to load the cleansing package files into your
repository.
Related Topics
• Database-specific requirements for Data Cleanse
• To create or upgrade repositories
Using the Repository Manager

Use the Repository Manager to check the version, to upgrade, or to create
a repository after installation:
1. Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAP
BusinessObjects Data Services > Data Services Repository Manager.
2. To check the version of an existing repository, click Get version.
Caution:
It's recommended that you do not use database tools to attempt to quickly
replicate additional repositories. By using the Repository Manager to create
and seed multiple repositories individually, you can avoid potential issues
related to the configuration of repository objects.
Related Topics
• To create or upgrade repositories in batch mode

To create or upgrade repositories

1. If you are creating a new repository, ensure that you created a database
for the new repository to use.
2. In the Repository Manager window, select the database type of your
repository.
3. Complete the information for your database type.
4. Enter the user name and password that you want to use for your
repository.
5. Select one of the following repository types:
Repository type Description

Local (Default) Stores definitions of objects in your local
repository.
Central Stores definitions of objects in a central repository for
multiple-user users.
Profiler Stores information generated by the Data Profiler for de-
termining the quality of your data.
Cleansing pack- Stores dictionary information for cleansing packages used
age by Data Cleanse transforms.
6. If you are creating a new repository, click Create. If you are upgrading
an existing repository, click Upgrade.
Note:
For cleansing packages, only Create is available. To upgrade a cleansing
package, first export any dictionary changes using the Designer. After
loading the new cleansing package using Create, reapply the dictionary
changes with the bulk load feature. Additionally, it's recommended that
you use the new rule file included with a new cleansing package. Using
the new rule file with an older dictionary may cause unpredictable results.
For more information, see “Upgrading cleansing packages”.
7. If you want to create or upgrade another repository, repeat steps 1 through

6.
8. When you finish creating or upgrading repositories, click Close.

After Installation
Using the Repository Manager 4
Note:
If you created a profiler repository, you must associate it to a Job Server
and connect it to the Management Console Administrator.
Related Topics
• Management Console Administrator Guide: Connecting repositories to the
Administrator
• Using the Server Manager
• Repository database requirements and preparation
• Designer Guide: Bulk load dictionary entries
• Upgrading cleansing packages
To create or upgrade repositories in batch mode
You can use the executable called RepoManBatch.exe (stored in the

LINK_DIR\bin directory) to create or update repositories in batch mode.
Specify parameters using a command prompt.
C:\Program Files\Business Objects\BusinessObjects Data

Services\bin>RepoManBatch.exe
Usage:
-U<User> : Repository login user
-P<Password> : Repository login password
-S<Server> : Repository server name
-N<DatabaseType> : Repository database type
-Q<Database> : Repository database
-g : Repository using Windows Authen
tication (Microsoft SQL Server only)
-t<Type> : Repository type: local, central,
profiler
-c : Repository create
-u : Repository upgrade
-v : Repository version
-d : Show details
-a : Repository security

Services\bin>

For example:
RepoManBatch -Usa -P -NMicroSoft_SQL_Server -SServer -

QJake -c -tcentral -d
or
RepoManBatch -UJake -PJake -NOracle -Sdbsvr -v

Usage:
Flag Description
Repository login user

-U
This parameter is required for all database types.
Repository login password

-P
Repository server name:

• For Microsoft SQL Server: database server name
• For Oracle: database connection name
• For DB2: data source
-S
• For Sybase ASE: server
• For MySQL: ODBC data source name
Repository database type:

• Microsoft_SQL_Server
• DB2
• Oracle
-N
• Sybase
• MySQL

After Installation
Using the Server Manager 4
Flag Description
Repository database name

-Q This parameter is required only for Microsoft SQL Server and
Sybase ASE.
Repository type:
• local
-t • central
• profiler
-c Create repository
-u Upgrade repository
-v Get repository version
-d Show details
-a Central repository security
Using the Server Manager

Use the Server Manager to create, edit, or delete Job Servers and Access
Servers after installation:
1. Choose Start > Programs > SAP BusinessObjects XI 3.2 >
BusinessObjects Data Services > Data Services Server Manager.
The Server Manager utility window opens. This window shows the Job
Servers and Access Servers currently configured to run on your computer.
2. Follow the procedures in the next sections to configure Job and Access
servers as needed.
3. In the Server Manager window, click Restart.

To configure Job Servers
1. In the Server Manager window, click Edit Job Server Config.

2. In the Job Server Configuration Editor window, click Add to add a Job
Server.
3. In the Job Server Properties window, enter information about the Job
Server.
Property Description
Job Server name Enter a name that uniquely identifies the Job Server.
Enter the TCP/IP port that the Job Server uses to re-
ceive commands from the Designer and the Access
Server. If a computer hosts multiple Jobs Servers,
each Job Server must have a unique port number.
Job Server port Choose a port number for a server that is not used
by another process on the computer. If you are unsure
of which port number to use, use the default port
number and increment it for each additional Job
Server you configure.
Select this check box if the Job Server manages

Support Adapter and adapters or if this Job Server will be the one to com-
SNMP communica- municate with an SNMP agent. Each computer that
tion hosts adapters and an SNMP agent must have exactly
one Job Server designated to manage them.
Enter the port number that the Job Server uses for
Communication port communicating with adapters or an SNMP agent. The
default is 4001.
Check this to enables this Job Server to send events

Enable SNMP
to the SNMP agent.
4. Under Associated Repositories, enter the local and profiler repositories

to associate with this Job Server. Each Job Server must be associated
with at least one local repository.
a. Click Add to associate a new local or profiler repository with this Job
Server.

After Installation
b. Enter the required information for your database type.
c. Enter the user name and password that you want to use for your
repository.
d. Select the Default repository check box if this is the default repository
for this Job Server. You must specify exactly one default repository.
Note:
Do not select the Default repository check box if this is a profiler
repository.
e. Click Apply to save your entries and associate the repository with the
Job Server.
The associated repository updates with the Job Server's computer
name and port number.
f. Repeat steps a through e until you are done adding all associated
repositories.
5. To edit an associated repository:
a. Select a repository and click Edit to change the repository's default
setting.
b. Under Repository Information, enter the password.
c. Select or clear the Default repository check box, indicating whether
this is the default repository for the Job Server.
d. Click Apply to save the change.
6. To delete an associated repository:
a. Select a repository and click Delete.
b. Under Repository Information, enter the password.
c. Click Apply to remove this associated repository.
7. When you finish adding all associated repositories, including one default,
click OK.
8. From the Job Server Configuration Editor window, complete any other
necessary steps. You can:
• Add another Job Server
a. Click Add.
b. Repeat steps 3 through 7.
• Change a Job Server's configuration
a. Select the Job Server.
b. Click Edit.
c. Repeat steps 3 through 7.

• Remove a Job Server

a. Select the Job Server.
b. Click Delete.
Note:
If the Job Server has associated repositories, you must first delete
those and then click OK before you can delete the Job Server.
• Resynchronize your Job Server configuration with a local repository.

Resynchronizing registers the Job Server again in all associated
repositories.
9. When you have configured all the Job Servers you want, click OK.
You return to the Server Manager window.
10. Click Restart to restart the services with the updated configurations.
Related Topics
• Designer Guide: SNMP support
• To resynchronize Job Servers
• To configure run-time resources
To resynchronize Job Servers
Situations when you must resynchronize the Job Server and the local
repository include:
• When the Job Server information is not available or not correct in the
local repository.
• You have uninstalled SAP BusinessObjects Data Services and are
reinstalling the same version without creating a new local repository.
• You created a new local repository using the Repository Manager after
installing SAP BusinessObjects Data Services.
To resynchronize Job Servers:
1. In the Job Server Configuration Editor window, select the name of your
Job Server.
2. Click Resync with Repository.
3. In the Job Server Properties window, select an associated local repository.
4. Click Resync.

After Installation
5. When asked whether to update this associated repository with this local
machine information, click Yes.
6. Under Repository Information, enter the local repository password.
7. Click Apply.
8. Click OK on the Job Server Properties window.
If you resynchronize your Job Server configuration with a local repository,
you must reassociate this repository with the Management Console.
Related Topics
Administrator
To configure run-time resources

1. Open the Server Manager and find the "Runtime resources configured
for this computer" section.
2. For the Specify a directory with enough disk space for pageable
cache option, you can accept the default directory
(LINK_DIR\Log\PCache) or click the ellipses button to browse to a
different directory.
Note:
For memory-intensive operations such as Group By, Order By, and
Detailed profiling, specify a pageable cache directory that:
• Contains enough disk space for your data. To estimate the amount of
space required for pageable cache, consider factors such as:
• Number of concurrently running jobs or data flows.
• Amount of pageable cache required for each concurrent data flow.
• Exists on a separate disk or file system from the SAP BusinessObjects
Data Services system and operating system (such as the C: drive on
Windows, or the root file system on UNIX).
• Limits the disk space that data flows consume. The pageable cache
uses all available disk space on the file system that contains the
pageable cache directory. So, to limit the disk space that data flows
consume, create a file system (or partition on Windows) with a limited
size. Use the new file system (partition on Windows) as the pageable
cache directory.

The software uses this directory:

• For pageable caching, which is the default cache type for data
flows.
• When selecting a file transfer type and Automatic is specified in
the Data_Transfer transform.
3. In the "Peer-to-peer options" area, change the values for Start port and
End port to restrict the number of ports used by the software. The default
values for Start port and End port are 1025 and 32767, respectively.
The software uses these ports for peer-to-peer communications when
sending data between data flows or sub data flows.
Related Topics
• To configure Access Servers
• Performance Optimization Guide: Caching data
• Reference Guide: Data_Transfer
• Performance Optimization Guide: Using grid computing to distribute data
flows execution
To configure Access Servers
When you configure the location for an Access Server installation, SAP
BusinessObjects Data Services creates space for the Access Server log
files.
1. In the Server Manager window, click Edit Access Server Config.
2. In the Access Server Configuration Editor window, click Add.
3. In the Access Server Properties window, enter the Access Server
configuration information.

After Installation
Field Description
The location of the log files for this instance of

the Access Server. Click the ellipses button to
browse to the Log directory under the directory
Directory where you installed the software.
Do not change this value after the initial configu-

ration.
The port on this computer that the Access

Server uses to listen for incoming messages
Communication Port from clients.
Make sure that this port number is unused and

is unique for each Access Server.
Parameters You can leave this box blank.
An option to control the automatic start of the

Enable Access Server Access Server when the SAP BusinessObjects
Data Services service starts.
Click OK. You return to the Access Server Configuration Editor window:
4. Optionally, perform further actions:

• To change an Access Server's configuration:
In the Access Server Configuration Editor window, highlight the Access

Server, click Edit, and repeat step 3.
• To remove an Access Server:
In the Access Server Configuration Editor window, highlight the Access

Server and click Delete.
5. After you configure your Access Servers, click OK to return to the Server
Manager window.

Using the License Manager
6. Click Restart to restart the services with the updated configuration.
Verifying that Job and Access servers are running
To verify that Job Servers are running, check in the Windows Task Manager
Processes tab for:
• al_jobservice.exe (represents the SAP BusinessObjects Data
Services service)
• al_jobserver.exe (one per Job Server)
• AL_AccessServer.exe (one per Access Server)
If you do not see all the processes expected, check for error messages in
the Job Server event log in LINK_DIR/log/JobServer
name/server_eventlog.txt.
• Access Server logs are in AccessServerPathName/er
ror_mm_dd_yyyy.log

License Manager lets you manage your product activation keycodes—the
alphanumeric codes that are referred to each time that you run certain
software. By using License Manager, you can view, add, and remove product
activation keycodes for SAP BusinessObjects solution portfolio software
(such as SAP BusinessObjects Data Services) that require them.
Note:
License Manager accesses keycodes on the local system only; you cannot
access the keycodes from a remote system. When updating keycodes, make
the changes on all SAP BusinessObjects Data Services computers by
launching License Manager on each computer, including Designer and Job
Server computers.
To start License Manager
You can run License Manager after the SAP BusinessObjects Data Services
installation has completed.

After Installation
Using the License Manager 4
• Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAP
BusinessObjects Data Services > BusinessObjects License Manager.
Related Topics
• To use License Manager from the command line
To view product activation keycodes

1. Start License Manager.
The License Manager window displays your keycode(s) sorted
alphabetically.
2. Select a licensed product or feature in the Registered Keycodes tree to
view detailed information:
• Product or feature keycode
• Whether the keycode is a trial version
• Whether the keycode is expired
• Number of days remaining until the keycode expires
Related Topics
• To start License Manager
To add product activation keycodes

2. In the Product Activation Keycodes text box, enter the keycode(s) that
you want to add (each keycode must be on a separate line) and click
Add.
The keycodes that will be added are displayed in the Registered
Keycodes tree and highlighted.
3. When you are satisfied with the changes that will be made, click Save.
The keycode highlighting is removed.
Tip:
If you do not want to save the keycode changes, close License Manager
without saving the changes.
4. After you have saved your changes, click Close to exit License Manager.

5. To make sure the new keycode(s) take effect, restart the software.
Related Topics
To remove product activation keycodes

2. In the Registered Keycodes tree, select the keycode(s) that you want
to remove and click Remove.
The keycodes that will be removed are crossed out, and any affected
nodes are highlighted.
3. When you are satisfied with the changes that will be made, click Save.
The crossed-out keycodes are removed.
Tip:
If you do not want to save the keycode changes, close License Manager
without saving the changes.
4. After you have saved your changes, click Close to exit License Manager.
5. Restart the software.
Related Topics
To use License Manager from the command line
License Manager includes a command-line mode that you can use if you
don't want to use the graphical interface, or need to script License Manager
operations.
Syntax
LicenseManager [-v | -a keycode | -r keycode [-l loca

tion]]

After Installation
Using the License Manager 4
Parameter Description
Displays the stored product activation keycodes in a

format similar to the License Manager graphical inter-
face. For example:
------ Registered Keycodes ------

-v or --view EIM Titan
Suite 12.0
Data Services XI 3.1 Premium
Keycode: 00000-0000000-0000000-0000
Trial Option: Yes

Expired: No
Days Remaining: 54
Adds the specified license keycode, and displays the

stored keycodes in a format similar to the License
Manager graphical interface. Returns status messages
for the following conditions:
-a or --add key • An internal error occurred.

code • Successfully added the keycode.
• Successfully added the keycode and replaced a
trial version.
• Keycode not added because it is invalid.
• Keycode not added because it is a duplicate.

Configuring Metadata Integrator
Parameter Description
Removes the specified product activation keycode,

and displays the stored keycodes in a format similar
to the License Manager graphical interface. If loca
tion is specified, the removal is restricted to that
node. Returns status messages for the following
-r or --remove key conditions:
code [-l location]
• An internal error occurred.
• Removed one keycode.
• Removed multiple keycodes.
• Keycode not removed because it is invalid.
• Keycode not removed because it was not found.

Metadata Integrator allows SAP BusinessObjects Data Services to collect
metadata for Business Views and Universes used by Crystal Reports, SAP
BusinessObjects Desktop Intelligence documents, and SAP BusinessObjects
Web Intelligence documents.
After your environment is configured, the Central Management Console
contacts the defined Program Job Server to launch scheduled Metadata
Integrator jobs. The jobs collect and copy metadata from your SAP
BusinessObjects Enterprise environment to your SAP BusinessObjects Data
Services repository. Then you can use the SAP BusinessObjects Data
Services metadata tools to browse, analyze, and produce reports on the
metadata.

After Installation
Configuring Metadata Integrator 4
Metadata Integrator can be configured in either a local or distributed

environment.
In a local environment, the same Windows server hosts all of the following
components:
• SAP BusinessObjects Data Services Metadata Integrator
• SAP BusinessObjects Enterprise Program Job Server
• SAP BusinessObjects Enterprise Central Management Server (CMS)
In a distributed environment, Metadata Integrator and an SAP

BusinessObjects Enterprise Program Job Server must reside on the same
Windows server. The other components of the SAP BusinessObjects
Enterprise environment, including the Central Management Server (CMS)

reside on one or more additional systems running on a Windows or UNIX

platform.
Note:
Metadata Integrator runs on Windows only. If you have a UNIX CMS, you
must create and configure a distributed environment.
If you have multiple CMS servers in your SAP BusinessObjects Enterprise
environment, you can create a separate Metadata Integrator configuration
to point to each CMS.
Related Topics
• Configuring Metadata Integrator in a local environment
• Configuring Metadata Integrator in a distributed environment
Configuring Metadata Integrator in a local

environment
In a local environment, a single Windows server hosts all of the following

components, Metadata Integrator, an SAP BusinessObjects Enterprise
Program Job Server, and an SAP BusinessObjects Enterprise Central
Management Server (CMS). Other SAP BusinessObjects Data Services
components may reside on other servers.
Note:
If you have a UNIX Central Management Server, you must follow the steps
to configure a distributed environment.
Perform the tasks listed below in order to configure a local Metadata Integrator
environment on a Windows server.
1. Confirm that an SAP BusinessObjects Enterprise Central Management
Server (CMS) and a Program Job Server are installed and configured.
See the SAP BusinessObjects Enterprise Installation and Configuration
Guide for Windows.
2. Depending on your circumstances, install and configure Metadata
Integrator in one of the following ways:

After Installation
Scenario Action Detailed informa-
tion
SAP BusinessOb- Install SAP BusinessObjects Data To configure Meta-
jects Data Ser- Services and configure Metadata Inte- data Integrator
vices is not in- grator during the installation process.
stalled.
SAP BusinessOb- Configure Metadata Integrator from the To configure Meta-
jects Data Ser- Metadata Integrator Configuration wiz- data Integrator
vices is installed, ard. from the configura-
but Metadata Inte- tion wizard
grator was not
configured during
the installation.
SAP BusinessOb- Install and configure only the Metadata Beginning your in-
jects Data Ser- Integrator component of SAP Busines- stallation
vices is already in- sObjects Data Services on the Win-
stalled on a differ- dows server where the SAP Busines-
ent server. You sObjects Enterprise CMS and Program
want to install only Job Server are installed.
Metadata Integra-
tor.
After your environment is configured, from the Central Management Console

you can schedule the Program Job Server to launch a Metadata Integrator
job which collects and moves metadata from your SAP BusinessObjects
Enterprise environment to your SAP BusinessObjects Data Services
repository. Then you can use SAP BusinessObjects Data Services metadata
tools to browse, analyze, and produce reports on that metadata.
Related Topics
• Configuring Metadata Integrator
Configuring Metadata Integrator in a distributed

environment
Note:
Metadata Integrator is available only on the Windows platform.

In a distributed environment, Metadata Integrator and an associated SAP

can reside on one or more additional servers running on a Windows or UNIX
platform. The CMS calls the Program Job Server to launch the Metadata
Integrator job.
The following components are required:
Component Location Operat-

ing Sys-
tem
Metadata Integrator Must reside on the same server as the Windows
SAP BusinessObjects Enterprise Pro-
gram Job Server
SAP BusinessObjects Enter- Must reside on the same server as the Windows
prise Program Job Server Metadata Integrator
SAP BusinessObjects Enter- Resides on a separate server Windows
prise Central Management or UNIX
Server (CMS)
Note:
You can choose to install Metadata Integrator on the same server as other
SAP BusinessObjects Data Services components or it can be configured on
a separate Windows server. However, Metadata Integrator and an SAP
Windows server.
Note:
If you have a UNIX Central Management Server, you must follow the steps
to configure a distributed environment.
Perform the tasks listed below in order to configure the Metadata Integrator
environment.
1. Confirm that an SAP BusinessObjects Enterprise Central Management
Server (CMS) is installed and configured in your environment. See the
SAP BusinessObjects Enterprise Installation and Configuration Guide for
your operating system.

After Installation
2. On your Windows server, install and configure Metadata Integrator in one
of the following ways:
Scenario Action Detailed informa-

tion
SAP BusinessOb- Install SAP BusinessObjects Data To configure
jects Data Ser- Services and configure Metadata In- Metadata Integra-
vices is not integrator during the installation pro- tor
stalled anywhere cess.
in your environ-
ment.
SAP BusinessOb- Configure Metadata Integrator from To configure
jects Data Ser- the Metadata Integrator Configuration Metadata Integra-
vices is installed, wizard. tor from the config-
but Metadata Inte- uration wizard
grator was not
configured during
the installation.
SAP BusinessOb- Install and configure only the Metada- Beginning your
jects Data Ser- ta Integrator component of SAP installation
vices is already BusinessObjects Data Services on
installed on a dif- the Windows server.
ferent server. You
want to install on-
ly Metadata Inte-
grator.
3. On your Windows server, install the following SAP BusinessObjects

Enterprise components:
• Client components
• Central Configuration Manager
• Program Job Server
• Database Access
The Program Job Server communicates with the CMS.
4. From the SAP BusinessObjects Enterprise Central Management Console,
create a server group for the Program Job Server you installed on the
Windows server.
5. Configure the default settings for that server group to use only the Program
Job Server within the group.

After your environment is configured, from the Central Management Console

you can configure a Metadata Integrator job which collects and copies
metadata from your SAP BusinessObjects Enterprise environment to your
SAP BusinessObjects Data Services repository. Then you can use SAP
BusinessObjects Data Services metadata tools to browse, analyze, and
produce reports on that metadata.
Related Topics
• To configure Metadata Integrator from the configuration wizard
• To install an SAP BusinessObjects Enterprise Job Server for Metadata
Integrator
• To create a Program Job Server group
• To configure the server group settings
• Configuring Metadata Integrator
To configure Metadata Integrator from the

configuration wizard
1. If you deferred the configuration or you want to modify the configuration,
click Start > Programs > SAP BusinessObjects XI 3.2 > SAP
BusinessObjects Data Services > Data Services Metadata Integrator
option. This Start menu option exists after you have installed either SAP
BusinessObjects Data Services or the Metadata Integrator.
2. When the Metadata Integrator Configuration window appears, choose
one of the following options:
• To add a new Metadata Integrator, choose the Add Metadata
Integrator option and click Next.
• To change an existing Metadata Integrator, select the Edit Metadata
Integrator option, select the name of the Metadata Integrator in the
drop-down list, and click Next
3. On the "BusinessObjects Enterprise" pane, enter the following CMS
connection information. If you need assistance with these values, consult
your administrator.

After Installation
Option Description
Configuration Name for this Metadata Integrator configuration. The

Name default name is Metadata Integrator followed by a
sequential number. For example:
Metadata Integrator_2
CMS Server Host name of the Central Management Server (CMS)

Name server.
CMS User Name The user name to connect to the CMS server in order
to register and execute Metadata Integrator. If you
want a different user to execute the Metadata Integra-
tor, use the Central Management Console to change
the rights for the user. See the SAP BusinessObjects
Enterprise Administrator's Guide for details.
CMS Password The password to connect to the CMS server to register

and execute the Metadata Integrator.
CMS Authentica- The CMS authentication mode. For available modes,

tion Mode see the SAP BusinessObjects Enterprise Administra-
tor's Guide.
CMS Folder The folder in which the CMS system adds Metadata
Name Integrator as a program object. This folder is automat-
ically created and appears only in the Central Manage-
ment Console. The default name is Data Services.
4. Click Next.
5. On the "Communications Protocol" pane, do one of the following:
• If Secure Sockets Layer (SSL) was not enabled when SAP
BusinessObjects Enterprise was deployed, click Next.
• If Secure Sockets Layer (SSL) was enabled when SAP
BusinessObjects Enterprise was deployed, select the Enable SSL
checkbox and enter the information required to use Secure Sockets

Layer (SSL) protocol for Metadata Integrator to access metadata from

the Central Management Server (CMS), and click Next.
See your administrator if you need assistance with these values. For
more information, see the SAP BusinessObjects Enterprise
Administrator's Guide.
Option Description
SSL Certificates Path to the directory where all the certificates and keys
Folder are stored.
Server SSL Certifi- The generated server certificate file.
cate File
SSL Trusted Cer- The trusted certificate file.
tificate File
SSL Private Key The private key for the CMS.
File
SSL Passphrase The file that stores the passphrase for the private key.
File
6. On the "Metadata Repository" pane, enter the following information to

connect to the SAP BusinessObjects Data Services repository. See your
database administrator if you need assistance with these values.

After Installation
Option Description
Database type The database type of the SAP BusinessObjects

Data Services repository. The available
database types are:
• DB2
• Oracle
• Sybase ASE
• MySQL
Computer Name Host name on which the repository resides.
Database Port Port number that the Central Management

Server (CMS) uses to connect to the repository.
• Service Name/SID This field requires additional information based

• Database Name on the Database type you select.
• Datasource
• Connection String
• Database Port and
Server
User Name The login name to connect to the repository.
Password The login password to connect to the repository.
7. (Optional) To check the connection to the metadata repository, click Test.

8. Click Next.
The status window for Metadata Integrator Configuration appears.
9. Click Finish.
Related Topics

To install an SAP BusinessObjects Enterprise Job

Server for Metadata Integrator

can reside on one or more additional servers running on a Windows or a
UNIX platform. The CMS calls the Program Job Server to launch the Metadata
Integrator job.
To install and configure the Program Job Server:

1. Follow the SAP BusinessObjects Enterprise installation program until you
reach the "Install Type" pane.
2. In the "Install Type" pane, click Custom or Expand Install and click Next.
3. In the "Select Features" pane, click the icons to install the following
features and all associated subfeatures:
• Client Components
• Central Configuration Manager
• Program Job Server
• Database Access
4. In the "CMS Clustering" pane, enter the following information:

After Installation
Option Description
Existing CMS Hostname The name of the Central Management Server
(CMS)
Existing CMS Port Port number for the CMS
The default port is 6400
The CMS will communicate with other SAP

BusinessObjects Enterprise servers through the
specified port.
CMS Administrator The CMS Administrator password

Password
5. In the "Server Intelligence Agent" pane, type a name for the Windows
server where you are installing. The name identifies this node of your
deployment.
The Server Intelligence Agent is automatically created during installation.
For more information, see the SAP BusinessObjects Enterprise
Administrator's Guide.
6. Specify a port number for the SIA in the port field.
This port will be used by the SIA to communicate with the Central
Management Server (CMS).
7. Click Next.
8. Click Next to begin the installation.
9. Click Finish.
Next, from the Central Management Console create a server group for the
Program Job Server and configure the settings.
Related Topics

To create a Program Job Server group

Integrator job.
To create a group for the Program Job Server on the Windows server:
1. Log into the Central Management Console.
2. In the Central Management Console, on the list, click Servers.
3. In the Servers List, verify the following:
• The Job Server installed on the Windows system appears.
• The "State" of the server is Running. If necessary, start the server.
4. Expand Server Groups.
5. Click Server Groups and click Manage > New > Create Server Group.
6. Type a name for the new server group and, optionally, add a description.
7. Click OK.
8. Click the newly created server group and click Actions > Add Members.
9. In the "Available Servers and Server Groups" list, click the Program Job
Server installed on the Windows system and click the ">" icon to move
the job server to the "Selected Servers and Server Groups" list.
10. Click OK.
Next, from the Central Management Console configure the settings for the
new server group so that the server group to uses only the Program Job
Server within the group to call the Metadata Integrator job.
Related Topics

After Installation
To configure the server group settings

Integrator job.
Follow the steps below to configure the settings so that the server group you
created to invoke the Metadata Integrator jobs uses only the Program Job
Server within the group:
1. If necessary, log into the Central Management Console.
2. On the list, click Folders.
3. Expand All Folders and then click the folder where you installed Metadata
Integrator. Data Services is the default name.
4. From the list of objects in the right pane, click the Metadata Integrator job
and click Manage > Default Settings.
5. From the list of "Default Settings", click Scheduling Servers.
6. In the "Set the default servers to use for scheduling this object" area, click
Only use servers belonging to the selected group and select the
Server Group that contains the Program Job Server.
7. Click Save & Close.
Your Metadata Integrator environment is configured. You can use the Central
Management Console to schedule a Metadata Integrator job.
Note:
If you create additional Metadata Integrator configurations, repeat the process
of configuring the default settings for each additional Metadata Integrator
configuration.
Related Topics

Metadata Integrator installation tips and

troubleshooting
Below are several Metadata Integrator installation tips and problems that
you can troubleshoot:
Configuration fails during installation
If the CMS is unavailable during the Metadata Integrator installation, or if the

CMS version has changed since installation, the Metadata Integrator will not
run successfully. Is these cases, the Metadata Integrator will report an error
such as the following when launched:
java.lang.NoClassDefFoundError:
com/crystaldecisions/sdk/exception/SDKException
at com.acta.crystalrepo.config.crConfigFrame.setupWizard
Pages(crConfigFrame.java:84)
at com.acta.crystalrepo.config.crConfigFrame.run(crCon
figFrame.java:73)
at com.acta.crystalrepo.config.crConfigLaunch.main(crCon
figLaunch.java:68)Exception in thread "main"
To reconfigure the Metadata Integrator environment
1. In LINK_DIR/ext/cmsCollector, run cmsSetEnv.cmd to reset all

command files to point to the installed version of CMS.
2. Run cmsConfig.cmd to update any configured Metadata Integrators to
point to the installed version of CMS.
Changing repository connection information
• To change the SAP BusinessObjects Data Services repository connection

information supplied during configuration, run the configuration utility:
LINK_DIR/ext/cmsCollector/cmsConfig.cmd

After Installation
To configure Metadata Integrator after installing SAP

BusinessObjects Enterprise
It's recommended that you install SAP BusinessObjects Enterprise before

you install and configure SAP BusinessObjects Data Services and the
Metadata Integrator.
However, if you need to install SAP BusinessObjects Data Services first, a

script is provided to configure the Metadata Integrator at a later time.
1. Open MetadataIntegratorSetup.cmd in a text editor.
By default, MetadataIntegratorSetup.cmd is installed to the
LINK_DIR\ext\cmsCollector folder.
2. Set the value of the BOE_SDK variable to the location of your SAP
BusinessObjects Enterprise SDK library and save the script. By default,
the SDK library is installed to boe_parent_folder\Common\ver
sion\java\lib.
For example, for SAP BusinessObjects Enterprise XI R2:
BOE_SDK=C:\Program Files\Business Objects\Common\3.5\ja

va\lib
3. Navigate to LINK_DIR\ext\cmsCollector in a command prompt,

and run the MetadataIntegratorSetup.cmd script.
The script performs additional configuration steps required to use the
Metadata Integrator.
Metadata Collector fails to start with java version error
If the Metadata collector indicates the run has failed, click the run instance
to view the error log. If the error indicates the java run-time environment
cannot be found or is the wrong version, you must define the JAVA_HOME
environment variable.
To define the JAVA_HOME environment variable, add the environment

variable and reboot your machine for it to take effect. Java 1.3.1 or higher
is required. JAVA_HOME must be set to the java run-time root directory. For
example:
JAVA_HOME=C:\Program Files\Java\j2re1.4.2_03

Connecting the Data Profiler
Metadata Collector fails to start
If the Metadata collector indicates the run has failed, click the run instance
to view the error log. The error indicates you do not have the permission to
run the program.
Press the Process tab and select Logon to determine the user name and
password used to run the collector. To check the permissions, press the
Rights tab to see what permissions are set. If you do not have permission
to run programs, check with your administrator to get the correct permission.
Metadata Integrator runs but report information is missing
From the Central Management Console, click the run instance for the
Metadata Integrator even though it says the run was successful. The collector
will only be in a failed state if the CMS is unable to start the program. There
is no mechanism to get run-time errors listed as a failed run. The work around
is to look at successful runs to see if any errors are reported.
Connecting the Data Profiler

The Data Profiler installs automatically when you install SAP BusinessObjects
Data Services. To use the Data Profiler, perform the following steps:
1. Define a profiler repository in which the Data Profiler will store the
generated profile data.
2. Associate the profiler repository with a Job Server on which the profiler
tasks will run.
3. Connect the profiler repository to the Administrator which will manage
the profile data and profiler tasks.
4. Connect the profiler server to the Designer from which you submit profiler
tasks and view the generated profile data.
5. If you plan to use Detailed profiling or Relationship profiling, ensure that
you specify a pageable cache directory that contains enough disk space
for your data and that you place on a separate disk or file system from
the SAP BusinessObjects Data Services system.
Related Topics

After Installation
Installing the SAP BusinessObjects Accelerator Index Designer 4
• To configure run-time resources
Administrator
• Designer Guide: Connecting to the profiler server
Installing the SAP BusinessObjects

Accelerator Index Designer
Installing the SAP BusinessObjects Accelerator index designer prepares
your system to model SAP NetWeaver Business Warehouse Accelerator
indexes on top of any data source supported by SAP BusinessObjects Data
Services.
Restriction:
The index designer requires SAP NetWeaver Business Warehouse
Accelerator and can be used only in an SAP BusinessObjects Explorer,
accelerated version environment.
To install the index designer:

1. Download the index designer software from https://service.sap.com/swdc.
2. On the Windows machine where SAP BusinessObjects Data Services
Designer is installed, launch the index designer installation by
double-clicking IndexDesigner.msi.
3. At the "Welcome" page, click Next.
4. Review the license agreement.
If you accept the terms, select I agree and click Next.
5. Accept the default installation folder or browse to a different folder, then
click Next.
6. Click Next to start the index designer installation.
7. After the installation is complete, click Close.
For more information about using the index designer, see the SAP
BusinessObjects Accelerator Index Designer Guide.

Troubleshooting installation problems

Errors that prevent installation progress (for example, an incorrect server
name, user name, or password) result in an immediate error message
describing the problem.
For some common issues, such as the service scheduler failing to launch
SAP BusinessObjects Data Services, reboot the computer after installation
has finished.
Related Topics
• Metadata Integrator installation tips and troubleshooting
Repository problems
Common repository-related installation errors include:

• The DBMS connection was lost while building the repository tables. If this
happens, recreate the repository with the Repository Manager.
• There is not enough space available in the database for the repository
tables. If this happens, use your DBMS administration tools to allocate
more space for the repository and run the Repository Manager.
If you experience problems when upgrading or creating a repository, you

can select the Show Details check box before you click Update or Create
again. This option allows you to view the SQL code that SAP BusinessObjects
Data Services uses to perform these operations. The Show Details option
can help you diagnose problems.
Related Topics
Management Console problems
Common Management Console and web application-related installation

problems include:
• The Management Console login page cannot be found.

After Installation
Troubleshooting installation problems 4
This problem can occur when the web application service is not running
or needs to be restarted. Restart the web application server. For the
packaged Tomcat web application server, use the Services tool in the
Administrative Tools section of the Windows Control Panel.
The problem can also occur in a high security environment. To remedy

the problem, you can set a lower security on the computer, use the
browser on a computer with a lower security setting, or add your machine
name into the trusted sites. You can also manually edit the URL in the
browser; for example, http://localhost:28080/DataServices.
• The Management Console cannot be launched on WebSphere.
If your WebSphere installation uses a port other than 9080 for the
application port, you may need to modify the link to the Management
Console. In LINK_DIR/ext/DataServices.html, replace 9080 in
the following line with your WebSphere application port:
<META HTTP-EQUIV=Refresh CONTENT= "0;

URL=http://hostname:9080/DataServices/">
• Auto Documentation or Impact and Lineage do not work on a Tomcat

application server.
This problem can occur when the Tomcat application server is not correctly
configured to use multi-byte data. You can correct this problem by adding
useBodyEncodingForURI="true" to your Tomcat server.xml
configuration file. For example:
<Connector port="8080"
maxThreads="150" minSpareThreads="25" maxS
pareThreads="75"
enableLookups="false" redirectPort="8443" accept
Count="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true" useBodyEncoding
ForURI="true"/>
• Web services cannot be deployed to an existing Tomcat application server.
This problem can occur when Tomcat has been installed using Tomcat's
Windows installer, which does not include certain files needed by the
wdeploy process used by the SAP BusinessObjects Data Services

installation program. You can correct this problem by downloading Tomcat

in a zip file from the Apache website. Extracting the zip file and copy any
missing files to the existing Tomcat installation location.
Windows Vista and Server 2008 issues
File or application in use

When installing or uninstalling SAP BusinessObjects Data Services on
Windows Vista or Windows Server 2008, you may receive messages about
files in use or applications that should be closed. You can safely ignore these
messages and continue to install or uninstall the software.
Ignoring these messages will have no impact on the installation or behavior

of the software.
Update to file access rights failed

When installing SAP BusinessObjects Data Services on Windows Vista or
Windows Server 2008, you may receive this warning if the installation setup
program is unable to set file access rights.
To manually update the file access rights, you can use the grantFileAc
cess.bat batch file. This batch file is installed to the LINK_DIR\bin folder
and takes one parameter as input, the software installation path (LINK_DIR).
For example, if you installed the software to C:\Program Files\Business

Objects\BusinessObjects Data Services\:
grantFileAccess.bat "C:\Program Files\Business Ob

jects\BusinessObjects Data Services\"
If your installation path contains spaces, you must enclose it in double quotes.
Verifying real-time connectivity
This section describes specific steps that you can follow to test the SAP
BusinessObjects Data Services real-time features after installation. These
step-by-step procedures use sample files available in the software installation.

After Installation
Distributing the test files
The SAP BusinessObjects Data Services installation includes test files to

exercise connectivity between each component of the system. To perform
the connectivity test, place test files in the appropriate locations on the various
computers used in your application.
Test file Copy from Copy to
ClientTest.exe LINK_DIR\Bin Web client computer, C:\temp
mny2412d.dll LINK_DIR\Bin Web client computer, C:\temp
functor2312d.dll LINK_DIR\Bin Web client computer, C:\temp
func
LINK_DIR\Bin Web client computer, C:\temp
tor_list2312d.dll
itc2312d.dll LINK_DIR\Bin Web client computer, C:\temp
network1712d.dll LINK_DIR\Bin Web client computer, C:\temp
pointer2312d.dll LINK_DIR\Bin Web client computer, C:\temp
sync2312d.dll LINK_DIR\Bin Web client computer, C:\temp
thread2312d.dll LINK_DIR\Bin Web client computer, C:\temp
threxcept2312d.dll LINK_DIR\Bin Web client computer, C:\temp
tls7712d.dll LINK_DIR\Bin Web client computer, C:\temp
LINK_DIR\Connectivi
ClientTest.txt Web client computer, C:\temp
tyTest
LINK_DIR\Connectivi
TestIn.xml Web client computer, C:\temp
tyTest
LINK_DIR\Connectivi
TestIn.xml Designer computer, C:\temp
tyTest

Test file Copy from Copy to
LINK_DIR\Connectivi
TestIn.dtd Designer computer, C:\temp
tyTest
LINK_DIR\Connectivi
TestOut.dtd Designer computer, C:\temp
tyTest
Note:
You must keep the DLL files specified in the preceding table with
ClientTest.exe. To move ClientTest.exe, re-run the Message Client
Setup and point it to the directory you want.
You need not move the TestConnectivity.atl file from its location on
the Designer computer.
To test a job
When you execute a real-time job from the Designer, it always executes in
test mode using a file as input and producing a file as output.
The test files include a sample job and data flow that you can use to verify
that a real-time job can successfully execute from the Designer. Test files
include the XML test input for the flow (the string “Hello World”) and the
corresponding DTD for flow input and output.
This procedure describes how to import, display, execute, and show output
for the test flow.
1. Start SAP BusinessObjects Data Services and log into your repository.
BusinessObjects Data Services > Data Services Designer from the
program group created by the installation. The Designer prompts you for
login information associated with your repository database.
2. From the Tools menu, select Import from File.

3. Navigate in the software install directory to \ConnectivityTest.
4. Select the test ATL file TestConnectivity.atl and click Open.
5. In the Project menu, select NewProject.
6. Name the project TestConnectivity and click Create.

After Installation
7. In the Jobs tab of the object library, expand the Real-time Jobs category;
then click, drag, and drop Job_TestConnectivity over the TestConnectivity
folder in the Project area.
8. In the workspace, click the name of the data flow.
9. In the project area, right-click Job_TestConnectivity and select Execute.
10. In the Execution Properties window, click OK.
The software reads the sample file C:\Temp\TestIn.xml, inverts the
order of the two words in the string, and writes the output to the
C:\Temp\TestOut.xml file.
11. Read the information in the Job Log window to verify if the TestOut.xml
file is correct. Use the job log information to troubleshoot problems.
12. If the job was successful, navigate to the C:\Temp\ directory on the
Designer's computer and open TestOut.xml.
You can display the file in a browser or text editor.
Testing the path from client to service
When your real-time job runs in a normal production environment, you can
use it to process a service request from a Web client. In production, Web
clients send messages and real-time services receive and process those
messages, triggering real-time jobs. Use the Management Console
Administrator to set up real-time services.
To process a service request from a Web client
1. Add and start the service in the Administrator.
The Access Server starts service providers which are instances of jobs
associated with the listed services.
2. Send a request from your Web client to the Access Server.

The Access Server sends a request to the appropriate service provider, then
the service provider sends a response to the Access Server. The Access
Server returns the response to the Web client.
Configuring the Access Server

The Administrator allows you to view the status of services controlled by the
Access Server and to change their configuration.

After you install the Access Server, the SAP BusinessObjects Data Services
service automatically launches the Access Server when your computer
restarts or when you stop and start the service.
To start the Administrator
1. Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAP
BusinessObjects Data Services > Data Services Management
Console.
The Management Console browser opens.
If it does not appear:

• Check that the port number is not being used by another application.
• Use a static IP address instead of the host name to locate the
Administrator computer.
2. Log in to the Management Console using the default name (admin) and
password (admin).
3. Click the Administrator icon to open the Web Administrator.
To add your repository for Administrator access
1. In the Administrator, select Management > Repositories > Add.
2. Enter your repository connection information and click Apply.
To configure the Access Server to listen for responses from services
1. In the Administrator, add a connection to an installed Access Server by
selecting Management > Access Servers > Add.
2. Enter your Access Server's machine name and communication port,
select Ping to test the connection, then click Apply.
To add a service
1. In the Administrator's navigation tree, select Real-time > Access Server
Machine Name: Port > Real-time Services > Configuration.
2. Click Add.
The Access Server adds a service to the list (NewService1) and displays
the configuration boxes for the new service.
3. Enter the following sample information in the Configuration section for

the service.
Accept the default values for the service parameters.

After Installation
Field Test Values Description
The message type in-

Service Name TestConnectivity cluded in the call from
the client.
Job Name Job_TestConnectivity Browse jobs.
4. Click Apply.
The Administrator prompts you to assign a Job Server to the Service.
5. Under Job Servers for Service, click Add.

6. If you have one Job Server, the Administrator automatically selects it for
you. Click Apply. Otherwise, select a Job Server from the list and click
Apply.
7. Click the Status tab.
The Administrator adds the new service (named after the job) and a
service provider to the list for this service. In the status row for each
service provider, find the computer name and Job Server port where the
service provider is running. The process ID for the service provider is
related to this invocation of the Job Server.
8. Verify host name and port number for the new service provider.
In the list of service providers, verify that the host name and port for the
new service provider correctly indicate the computer where the Job Server
is installed and the port that the Job Server is configured to use.
You specified the Job Server port number when you configured the Job
Server at installation.
9. In the navigation tree, click Real-Time Services to return to the first

Real-Time Service Status page.
The name of the Service should be next to a green icon which indicates
that the Service started successfully.

When a service starts, the Administrator triggers the Access Server which
triggers the Job Server to get job information from the repository. The job
registers as a service with the Access Server. The Administrator displays
the service status (started).
If the service did not start, you can start it manually from the current page.
Web client to Access Server

A Web client opens a connection to the Access Server using a call in the
Message Client library. The call includes the host and port information
required to make the connection.
The ClientTest executable file provided in the SAP BusinessObjects Data

Services installation incorporates the library calls so you can easily test the
connection between the Web client computer and the Access Server.
To process a test request
1. On the computer where your Web client application is installed, send a
request for the software to process.
Copy the command, C:\Temp\ClientTest.txt and enter it in a
command prompt:
ClientTest -AHost -pPort -Uuser -Ppassword -STestCon

nectivity -XC:\Temp\TestIn.xml
where
Identifies the Access Server host

Host
computer by name or IP address.
Identifies the port on which Access

Port Server listens for Web client re-
quests.
Indicates the user name you specified

in the Security section of the Access
Server configuration file. The test
user
configuration does not specify a user,
but the Client Test utility expects
some value. Enter any character.

After Installation
Indicates the password you specified
in the Security section of the Access
Server configuration file. The test
password configuration does not specify a
password, but the Client Test utility
expects some value. Enter any char-
acter.
Specifies the name of the service

that you want to invoke.
TestConnectivity C:\Temp\TestIn.xml
Indicates the location of the sample
XML request that will be sent to the
Access Server for processing.
2. Look for the response in the command prompt.

3. When you are ready to configure the Access Server to run your own
services, first stop the Access Server, then restart it.
Further connectivity tests
There are more tests you can run to define that all the connections you will
need. For example, you can use the existing Access Server configuration
and make changes to the data flow and input files in the sample real-time
job. In particular, consider making simple additions to the data flow in the
real-time job to check the following connection:
• From job to ERP system
To test this connection, add a source from the ERP system in a data flow
of the real-time job and extract a single value to return as a response to
the client.

Control the Address Server

The Address Server is required for processing addresses with the EMEA
engine and Global Suggestion Lists. You must manually start and stop the
Address Server.
Start the Address Server
To process addresses with Global Suggestion Lists or the EMEA engine you
need to manually start the Address Server after installing SAP
BusinessObjects Data Services and the data directories. If a data flow
requires the use of the Address Server, it will wait for the server to initialize
before starting a process.
Note:
The software does not start the Address Server automatically due to the
considerable amount of memory resources required to run the server. Start
the Address Server when you plan to use Global Suggestion Lists or the
EMEA engine.
1. Select Start > Settings > Control Panel.
2. Select Administrative Tools.
3. Select Services.
4. Double-click BusinessObjects Address Server to view the server
properties.
5. Do one of the following.
• To start the server click Start.
• To set the server to start automatically, select the Startup Type of
Automatic and click Start.
Note:
• The first initialization of the Address Server may take up to 20 minutes
due to the loading of the directory data. The initialization will take about
20 minutes each time you install updated directory files and restart
the Address Server.
• The Address Server caches the directory data for optimum
performance and will require a significant amount of memory.

After Installation
Control the Address Server 4
Stop the Address Server to install data directories
You must stop the Address Server before installing the data directories.
1. Select Start > Settings > Control Panel .
2. Select Administrative Tools.
3. Select Services.
4. Double-click BusinessObjects Address Server to view the server
properties.
5. Click Stop.
6. Copy the directory files to the appropriate location.
7. Repeat steps 1-4.
8. Click Start to restart the Address Server.
Related Topics
• Directory Data
• To copy International directory files to a non-default location


Citrix Support
5
5 Citrix Support
Installing the software
You can set up SAP BusinessObjects Data Services to run under Citrix
Presentation Server. Presentation Server provides an access infrastructure
for enterprise applications.
Presentation Server supports many methods of running applications. This

section provides information about how to install one copy of an SAP
BusinessObjects Data Services component, run it as a Presentation
Server-published application or published desktop on a server, and set client
user permissions for it.
Definitions
The following definitions introduce basic Citrix concepts. To learn more about
Citrix Presentation Server, see Citrix Presentation Server documentation.
Concept Description
ICA Client A Citrix-defined protocol/connection to a server. The ICA
client connection allows Presentation Server to run any ap-
plication on its server and manage how each client accesses
the user interface of the application.
Program Neigh- The Presentation Server component installed on a client. It
borhood manages ICA client connections and published applications
for a given user.
Published Appli- Application software (for example, the Designer) installed on
cation a Presentation Server server and published to users. An
administrator can choose which users may run and view the
application.
Application Set A set of all published applications that a user can access.
When you start your Program Neighborhood software, you
see this application set, which can include multiple applica-
tions published on multiple Presentation Servers.
Installing the software

User interfaces for SAP BusinessObjects Data Services are certified to run
on Citrix Presentation Server as an application set. The set consists of:
• Designer (includes the Metadata Reporting tool)

Citrix Support
Installing the software 5
• Management Console
• License Manager
• Repository Manager
• Locale Selector
• Server Manager
• Documentation Components
Initial installation
The installation process for SAP BusinessObjects Data Services on

Presentation Server is slightly different from a typical installation. The
Presentation Server runs Microsoft terminal services in application mode.
Therefore, you must install the software using the Add/Remove programs
service in the Windows control panel.
To install the software, follow the prompts of the Add/Remove program wizard
and use the file browser of the wizard to run setup.exe from the install CD
(or network directory). It's recommended that you install the Designer and
the Job Server on separate computers.
After you install Job Servers and Access Servers, you must provide
connection settings to users because their remote setups will look for the
servers locally by default. Similarly, manage sources, targets, and repositories
from the Presentation Server in the usual fashion. However, individual clients
must use database connection names defined on the server (not the local
client). The Designer defaults to looking for configuration information locally.
For example, to connect to an Oracle repository, define the Oracle connection
name on the Presentation Server and provide the connection information to
your users.
Note:
Because Citrix Presentation Server is running on a server, be aware that the
first time you install the software, you must reboot the server.
Related Topics
• Limitations

5 Citrix Support
Running components in multi-user mode

While Presentation Server allows you to publish SAP BusinessObjects Data
Services interface components to one user or multiple users at the same
time, it's recommended that you run all but the Designer, Management
Console, and Locale Selector in serial mode.
Serial access to the License, Server, and Repository

Managers
It is safest to allow only one user at a time to access the License Manager,
Repository Manager, and Server Manager. In most cases, this restriction
will not be a problem, because users typically do not access these
components often. To set these components for serial access, use
Presentation Server to configure their application limit to one instance per
server.
Parallel access to the Management Console, Locale

Selector, and Designer
Use Presentation Server to configure the Management Console, Locale

Selector, and Designer to run any number of instances in parallel per server.
When you configure the Management Console, simply publish it as content.

However, when you configure the Locale Selector and Designer, you also
must limit the application to one instance per user and ensure that your
configuration preserves user settings. A DOS shell script is provided to
accomplish this for each application.
Related Topics
• Publishing the software

Citrix Support
Running components in multi-user mode 5
Using shell scripts to access the Locale Selector and

Designer
When you install SAP BusinessObjects Data Services, the environment

variable LINK_DIR is set to point to the install directory. This variable allows
the software to locate settings and persistent environment information.
Because there is only one LINK_DIR variable per installation, when multiple
users run a single Designer or Locale Selector installation (in serial or
parallel), all instances access the same path from the LINK_DIR variable.
The result is that the users will change each other’s settings.
To solve this problem for Citrix, DOS batch scripts are used to provide each
user with their own copy of required resource files and to create a new
environment variable (USER_LINK_DIR) that directs the Locale Selector or
Designer to the user-specific resource copy.
The DOS batch file for the Designer is RunDSDesignerMU.bat, and the
DOS batch file for the Locale Selector is RunLocaleSelectorMU.bat. By
default, both scripts are installed to the LINK_DIR\bin directory.
Note:
By default, the scripts create user-specific resource directories in C:\Users.
You can specify a different path by using an argument when running the
batch file. For example: RunDSDesignerMU D:\UserData
The following diagram shows how the batch files enable multiple processes
to run on a single computer by creating user-specific resource directories:

5 Citrix Support
Restriction:
The batch scripts enable multiple users to run the same SAP BusinessObjects
Data Services component concurrently from a Citrix Presentation Server.
However, the scripts do not allow a single user to run both the Designer and
Locale Selector concurrently. The provided batch scripts do not allow a user
to open one component when the other is currently running.

Citrix Support
Publishing the software 5
Publishing the software
After you install SAP BusinessObjects Data Services, you can set up its user
interface components as Published Applications to make them available to
clients. The Presentation Server Management console includes a wizard to
help you do this. Run it once for each component (Designer, Management
Console, Repository Manager, Server Manager, Locale Selector, and License
Manager). You must publish each component separately.
To publish a component
1. Start the Citrix Presentation Server Management console.
2. Select Applications from the menu tree and choose Publish Application
from the menu.
3. On the "Specify What to Publish" page, configure each component:
Component Publish as Command line Working direc- Content address

tory
Designer Application RunDSDesign C:
erMU.bat
Repository Man- Application RepoMan.exe "$LINK_DIR"\bin
ager
Server Manager Application AWServerCon "$LINK_DIR"\bin
fig.exe
License Manager Application LicenseMan "$LINK_DIR"\bin
(optional) ager.exe
Management Content "$LINK_DIR"/ext/DataSer
Console vices.html
Locale Selector Application RunLocaleSe C:
lector
MU.bat
Note:
a. Publish the Designer and Locale Selector .bat files instead of directly
publishing the executables.

5 Citrix Support
Publishing the software
b. To allow for spaces in the install path name, use quotes around any
variable that includes a directory name.
c. After using Presentation Server to configure the Management Console
as content, share the ext directory with all Management Console
users.
The Publish Application Wizard allows you to enter a file name for the
start icon used by applications published as content. For the Management
Console, enter the path to Admin_small.ico if you want users to have
access to the icon. Note that Designer components run as a shortcut on
the client desktop.
4. Define the Program Neighborhood settings:

Citrix Support
Publishing the software 5
Setting Description
Application Appear- Choose 256 colors at minimum. Lower resolution set-
ance tings may work but will not allow users to easily distin-
guish icons and object bitmaps. Program Neighborhood
provides an option to maximize any application at
startup. It is recommended that you do not maximize
the Designer at startup because older versions of the
Designer might fail.
ICA Client Require- It's recommended that you use only the basic security
ments level option in Program Neighborhood. Higher levels
of security may work but have not been tested.
Application Limits
The Designer, Locale Selector, Repository Manager,
Server Manager, and License Manager were not
designed to be run by multiple users at the same
time. However, Citrix will allow several instances of
these programs to be active at the same time on the
same server. It's recommended that you set the
maximum number of instances for the Repository
Manager, Server Manager, and License Manager
executables to 1.
For the Designer and Locale Selector, you can allow

multiple instances of the .bat file to run, but limit
one instance of each .bat file per user.
Since the Management Console is published as

content, you can run multiple instances of it.
Specify Servers You can specify which servers in a Presentation Server

server farm will run an application for client users. Se-
lect the server on which you installed SAP BusinessOb-
jects Data Services for this purpose. If you installed the
software on several servers, publish only one.
Specify Users You can specify which users can access a particular
application. If you specify three users, the component
defined by the application appears in each of the users'
Program Neighborhoods.

5 Citrix Support
Limitations
Connection management
After installing SAP BusinessObjects Data Services components, give each

user permission to establish an ICA connection with the Presentation Server.
Run the Citrix Connection Configuration tool to assign user permissions to
a connection.
Client setup
If users will be running SAP BusinessObjects Data Services components

from client computers, install the Citrix Program Neighborhood software on
these computers.
Note:
The software components were tested as a Citrix Program Neighborhood
application set. These components were not tested as a Program
Neighborhood agent or web interface.
Related Topics
• Initial installation
Limitations
The following are known limitations to running SAP BusinessObjects Data
Services on Citrix:
• The software stores files in the Job Server’s log directory when you
capture sample data using the View Data feature. If the Designer runs
on the same computer as the Job Server, the default location of the log
directory changes each time a user logs in through Citrix. This change
prevents the Designer from locating the View Data log files for a given
user. To avoid this issue, it's recommended that you run the Job Server
on a different computer than Designer. This limitation does not apply to
the interactive debugger.
• If the Server Manager is published to a Citrix client and you try to add a
Job Server from the client, the SAP BusinessObjects Data Services
service might not start. If this occurs, log on to the Job Server’s computer
and restart the service. You must have sufficient user privileges to restart

Citrix Support
Limitations 5
a service using the computer’s operating system. When the service is
installed, it uses the ID and password that belong to the user who runs
the installer as its default login values.
• Citrix runs the Designer process on the server and publishes only its user
interface to the client. Since the Designer runs on the server, users must
have sufficient read/write permissions for directories or files on the server
if you want them to access a file on the server as part of a Designer job.
• If registry popup windows appear when users attempt to start the Designer,
then either give user accounts authority to query registry keys on the
server or give users administrator authority on the server.

5 Citrix Support
Limitations

Directory Data
6
6 Directory Data
Directory listing and update schedule
What are directories?

To correct addresses and assign codes with SAP BusinessObjects Data
Services, the Address Cleanse transform relies on directories, or databases.
When Address Cleanse uses the directories, it’s similar to the way that you
use the telephone directory. A telephone directory is a large table in which
you look up something you know—someone’s name—and locate something
that you don’t know—their phone number.
You may not need to use all of the reference files depending on which
transforms or options you use. Depending on which option you own, some
disks or online packages that you receive may contain extra files in addition
to your directories. For example, you may see an Extract folder. If you do
not need these extra files, do not copy them to your computer. For information
about extra folders, see the ReadMe.txt file included with the reference
files.

Directory type Directory filename Approximate
Size
Updated Monthly
(M)
Bimonthly (B)
Quarterly (Q)
ZIP4 and Auxiliary Directories zip4us.dir 699 MB MB

Auxiliary Directories MB
cityxx.dir 2 MB
zcfxx.dir 2 MB
revzip4.dir 1 MB
zip4us.rev 97 MB
zip4us.shs 4 MB
Early Warning System Directory ewyymmdd.dir 1 MB Weekly

DPV Data dpv_path 653 MB M

Directory Data
Directory listing and update schedule 6
Size
Updated Monthly
(M)
Bimonthly (B)
Quarterly (Q)
Enhanced Line of Travel Directory elot.dir 486MB M

Canada engine - Address Data 42 MB M
canada.dir
cancity.dir
canfsa.dir
canpci.dir
Australia engine - Address Data 200 MB MQ

apc.dir
aucity.dir
aus.dir
Global Address engine and EMEA all files up to 12.2 GB Q

Engine - Data (for all countries)
Note:
You will receive files only for those
countries your company has pur-
chased.
Centroid Level Geo Data cgeox.dir 720 MB Q

Address Level Geo Data ageox.dir 4.67 GB Q

6 Directory Data

Size
Updated Monthly
(M)
Bimonthly (B)
Quarterly (Q)
Geocoder Q
geo_ad- Canada: 1.6
dr_ca_vendorx GB
.dir
Canada: 1 MB
geo_cent_ca_ven
France: 1.6 GB
dorx .dir
France: 6 MB
geo_ad-
dr_fr_vendorx USA: < 2 GB
.dir
USA: < 2 GB
geo_cent_fr_ven
dorx .dir
geo_ad-
dr_us_ven
dorx<num> .dir
geo_cent_us_ven
dorx<num> .dir

Directory Data
U.S. Directory expiration 6
Size
Updated Monthly
(M)
Bimonthly (B)
Quarterly (Q)
Z4Change Data z4change.dir 199 MB M

LACSLink all files 461 MB
Japan engine - Address Data Q
ga_re 248 MB
gion_jp_paf.dir
ga_loc12_jp_paf.dir
ga_loc34_jp_paf.dir
ga_dp_jp_paf.dir
Related Topics
• Designer Guide: Address Server for the EMEA engine and Global
Suggestion Lists
U.S. Directory expiration

We publish and distribute the ZIP4 and supporting directory files under a
non-exclusive license from the USPS. The USPS requires that our software
disable itself when a user attempts to use expired directories.
If you do not install new directories as you receive them, the software issues
a warning in the log files when the directories are due to expire within 30
days. To ensure that your projects are based on up-to-date directory data,
it's recommended that you heed the warning and install the latest directories.
Note:
Incompatible or out-of-date directories can render the software unusable.
The directories are lookup files used by SAP BusinessObjects solution
portfolio software. The system administrator must install monthly or bimonthly
directory updates to ensure that they are compatible with the current software.

6 Directory Data
U.S. Directory expiration schedule
U.S. Directory expiration schedule

You can choose to receive updated U.S. national directories on a monthly
or bimonthly basis. Bimonthly updates are distributed during the even months.
Directory expiration guidelines are:
• ZIP4 and Auxiliary Directories expire on 1st day of the fourth month after
directory creation. When running in Non-Certified mode, Zip4 and Auxiliary
directories expire on first day of the fourteenth month after directory
creation.
• LACSLink directories expire 105 days after directory creation.
U.S. National and Auxiliary files

The U.S. National and Auxiliary file self-extracting files are named as follows.
Directory name Zip file name

2004-2008 U.S. National us_dirs_2004.exe
directory
U.S. Address-level Geo-
Census
us_ageo1_2.exe
us_ageo3_4.exe
us_ageo5_6.exe
us_ageo7_8.exe
us_ageo9_10.exe
U.S. Centroid-level Geo-

Census
us_cgeo.exe
us_cgeo1.exe
us_cgeo2.exe
Related Topics
• Extract directory files on Windows

Directory Data
Where to copy directories 6
Where to copy directories
We recommend that you install the directory files in a common file system
directory local to the system in which SAP BusinessObjects Data Services
is installed. By default, the software looks for directories in
$LINK_DIR\DataQuality\reference_data on Windows. If you place
your directories in a different location, you must update your substitution file.
To copy International directory files to a non-default

location
If you use the Global Address Cleanse Transform's EMEA engine or Global
Suggestion Lists' Multi Country engine and store your data directories in a
location other than the default ($LINK_DIR\DataQuality\reference_da
ta), do the following:
1. Stop any data flows that use the EMEA engine, Global engine or Global
Suggestion Lists.
2. Stop the Address Server.
3. Copy the following files from $LINK_DIR\DataQuality\reference_da
ta to the location where you store your data directories:
• AddressServerGlobal.db
• MultiLineKeywords.db
• ga_directory_db.xml
• ga_directory_db_emea.xml
• ga_country.dir
• ga_region.dir
Note:
Every time you install an SAP BusinessObjects Data Services software
update, copy the reference files from to the default location to where you
store your directories.
4. Update the REFERENCE_DATA_DIRECTORY parameter in the Ad

dressServerConfig.txt file located in $LINK_DIR\bin\ad
dress_server\ to the new reference directory location.
5. Update the RefFilesAddressCleanse substitution parameter configuration
to the new reference directory location.

6 Directory Data
To install and set up Download Manager
6. Restart the Address Server.
To install and set up Download Manager

Before you can download directory files, you need to install and set up
Download Manager.
To install and set up Download Manager:

1. Access the SAP Service Marketplace (SMP): http://service.sap.com/bosap-
support
2. Select Downloads.
3. Select Download Basket.
4. Click the Get Download Manager button.
5. Follow the steps to install and set up the Download Manager.
To download directory files

The directories are available for download from the SAP Service Marketplace
(SMP).
To download directories:
1. Access the SAP Service Marketplace (SMP) site: http://ser
vice.sap.com/bosap-support
2. Select Downloads.
3. From the left pane, select Downloads > SAP Software Distribution
Center > Downloads > Installations and Upgrades > My Company's
Application Components.
A list of your company's applications and any license-free products or
components appear.
4. Select the files you want to download and add them to the Download
Basket.
The files you select are placed in the Download Basket.
5. To access the Download Basket, click Download Basket.
6. To access the Download Manager documentation, click Get Download
Manager.

Directory Data
Extract directory files on Windows 6
7. Follow the steps included in the Download Manager documentation to
download the directory files.
Extract directory files on Windows

The steps listed here describe how to install the self-extracting directory files
for Windows.
1. Copy the self-extracting directory files manually from the disk to the
\temporary\ folder.
2. Locate and double-click the <filename> file.
The files are extracted and placed in the \temporary\ folder.
3. Copy the directory files from the \temporary\ folder to the location
where you keep your directories.
4. Repeat steps 1 through 3 for each required file.
5.

6 Directory Data
Extract directory files on Windows

Overview of wdeploy
7
7 Overview of wdeploy
Configure wdeploy
The wdeploy command-line tool is included with SAP BusinessObjects Data

Services to aid in the command-line deployment of web applications to
Java-based web application servers.
Use the wdeploy tool to deploy Data Services Management Console to a

web application server. There are three web components to deploy:
• DataServices.war
• Doc.war
• Webservice.war
The wdeploy tool and the three web components are placed in the following
locations during the SAP BusinessObjects Data Services installation:
• The wdeploy tool is located in the \Business Objects\deployment

folder at the same level as LINK_DIR.
• The three web components are located in the \BusinessObjects
Enterprise 12.0\java\applications folder at the same level as
LINK_DIR.
.
Configure wdeploy
Before you execute any deploy or undeploy commands, modify the
configuration files to provide the information for your web application server.
To update the wdeploy configuration file, follow these steps:
1. Open the configuration file for your web application located in
the\Business Objects\deployment folder at the same level as
LINK_DIR. The configuration files are named as follows:
• config.tomcat55
• config.tomcat6
• config.weblogic9
• config.weblogic10
• config.websphere6
• config.websphere7
2. Set the parameters to match the web application server settings.
3. Save and close the configuration file.

Overview of wdeploy
Options for wdeploy 7
Options for wdeploy

There are several actions that can be performed by the wdeploy tool to control
the web application deployment process:
• deploy: Prepares and deploys a web application to a web application
server.
• deployall: Prepares and deploys all web applications to a web
application server.
• undeploy: Removes a web application from a web application server.
• undeployall: Removes all web applications from a web application
server.
Deploy all web components

Deploying all web components deploys DataServices.war, Doc.war,
and Webservice.war. To deploy all web content, follow these steps:
Note:
Replace the web_app_server_type variable with your web application. The
valid names are:
• tomcat55
• tomcat6
• weblogic9
• weblogic10
• websphere6
• websphere7
1. From the command prompt access the \Business

Objects\deploymentfolder at the same level as LINK_DIR.
2. To deploy all web content for your web application server, type wdeploy
web_app_server_type deploy all –Das_admin_password=password.
Tomcat does not require a password. Type wdeploy tomcat55 deployall
or wdeploy tomcat6 deployall.
3. Open the DataServices.html file located in LINK_DIR\ext and
change the default port number to match the port number for your web

Deploy one web component at a time
application server. For example, the default port number for Tomcat is
8080.
<META HTTP-EQUIV=Refresh CONTENT= "0; URL=http://host

name:8080/DataServices/">
After you deploy the applications on Tomcat, you must restart the Tomcat
application server for the changes to take effect.
Deploy one web component at a time

To deploy one web component at a time, follow these steps:
Note:
Replace the web_app_server_type variable with your web application.
The valid names are:
• tomcat55
• tomcat6
• weblogic9
• weblogic10
• websphere6
• websphere7
Note:
Tomcat does not require a password. To deploy a web application, type
wdeploy tomcat55 -DAPP=app_name deploy or wdeploy tomcat6
-DAPP=app_name deploy.
Objects\deployment folder at the same level as LINK_DIR.
2. To deploy DataServices.war, type wdeploy web_app_server_type
-Das_admin_password=password -DAPP=DataServices deploy
3. To deploy Doc.war, type wdeploy web_app_server_type
-Das_admin_password=password -DAPP=doc deploy
4. To deploy Webservice.war, type wdeploy web_app_server_type
-Das_admin_password=password -DAPP=webservice deploy
5. Open the DataServices.html file located in LINK_DIR\ext and
change the default port number to match the port number for your web

Overview of wdeploy
Verify deployment 7
application server. For example, the default port number for Tomcat is
8080.
<META HTTP-EQUIV=Refresh CONTENT= "0; URL=http://host

name:8080/DataServices/">
After you deploy the application on Tomcat, you must restart the Tomcat
Verify deployment
To verify the deployment was performed properly, follow these steps:
1. Check whether the web applications have been deployed to the correct
location.
• On Tomcat - $CATALINA_HOME/webapps
• On WebSphere - server_folder/in
stalledApps/Node_Cell_folder/. For example, C:\Program
Files\IBM\WebSphere\AppServer\profiles\AppSrv01\in
stalledApps\SHG-D-01-CGAONode01Cell.
• On WebLogic - server_folder/stage/ . For example,
C:\bea\wlserver_10.0\samples\domains\wl_serv
er\servers\examplesServer\stage.
2. Log in to Management Console, add a repository, and click on each of
the modules. Each module should display correctly.
3. Optional. Click the Release Notes link on the Administrator page to see
if the link opens the documentation correctly.
4. Optional. Verify that you can add a web service successfully.
5. Click About to verify that the version is up-to-date.
Undeploy all web components

Undeploying all web components undeploys DataServices.war, Doc.war,
and Webservice.war. To undeploy all web components, follow these steps:

Undeploy one web component at a time
Note:
Replace the web_app_server_type variable with your web application. The
valid names are:
• tomcat55
• tomcat6
• weblogic9
• weblogic10
• websphere6
• websphere7

2. Type wdeploy web_app_server_type undeployall
–Das_admin_password=password. Tomcat does not require a password.
Type wdeploy tomcat55 undeployall or wdeploy tomcat6 undeployall.
After you undeploy the application on Tomcat, you must restart the Tomcat

To undeploy the web components one at a time, follow these steps:
Note:
Replace the web_app_server_type variable with your web application.
The valid names are:
• tomcat55
• tomcat6
• weblogic9
• weblogic10
• websphere6
• websphere7
Note:
Tomcat does not require a password. To undeploy a web application, type
wdeploy tomcat55 -DAPP=app_name undeploy or wdeploy tomcat6
-DAPP=app_name undeploy.

Overview of wdeploy
Undeploy one web component at a time 7
1. From a command prompt access the \Business
2. To undeploy DataServices.war, type wdeploy web_app_serv
er_type -Das_admin_password=password -DAPP=DataServices
undeploy.
3. To undeploy Doc.war, type wdeploy web_app_server_type
-Das_admin_password=password -DAPP=doc undeploy.
4. To undeploy Webservice.war, type wdeploy web_app_server_type
-Das_admin_password=password -DAPP= webservice undeploy.
After you undeploy the application on Tomcat, you must restart the Tomcat


Maintaining your installation
8
8 Maintaining your installation
Upgrading the software

To upgrade from an existing SAP BusinessObjects Data Integrator or SAP
BusinessObjects Data Services installation, install the new components and
then upgrade your repositories. To upgrade from an existing SAP
BusinessObjects Data Quality Management installation, see the Migration
Considerations.
Note:
Before upgrading, ensure that you recover all unsuccessful jobs which are
in a recoverable state.
After upgrading, due to changes in the recovery checkpoint flag, executing
a job in a recoverable state will result in undefined behavior.
Related Topics
• Designer Guide: Recovery Mechanisms
Component upgrades
In addition to upgrading repositories, you must upgrade all SAP

BusinessObjects Data Services components to the same version.
It's recommended that after you back up existing repositories (using your
database's backup utility) and read the release notes, you upgrade
components in the following order:
1. Designer
2. Repository
3. Job Server
4. Access Server
5. Message Client libraries
Note:
If you are using the SAP ABAP interface, re-install the SAP BusinessObjects
Data Services functions for SAP applications.
Related Topics
• Supplement for SAP: Installing functions on SAP Business Suite

Upgrading the software 8
Repository upgrades
Minor releases do not require a repository upgrade. For example, if 11.7 is

a major release and 11.7.3 is a minor release, then when upgrading from
11.7 to 11.7.3, it would not be necessary to upgrade your repository. However,
software features introduced in the latest version might not be available
without the repository upgrade. To see whether you need to upgrade your
repository for a particular release, see the Release Notes for that release.
Using database backup utilities, always make a copy of your existing

repository before upgrading. Note that you will upgrade using the original
repository (not your backup copy).
Several repository upgrade paths are available.
To upgrade from Procedure
Install this release using one of the

following methods:
• Upgrade your repository during
the installation process
SAP BusinessObjects Data Integrator
Version 11.0.x, 11.5.x, 11.6.x, 11.7.x • Upgrade your repository after in-
stalling the Client Components by
running the Repository Manager
utility and choosing the Upgrade
option.
Note:
If you are using an end-of-life version of SAP BusinessObjects Data
Integrator, first upgrade to a supported version before upgrading to SAP
BusinessObjects Data Services. For example, if you have version 6.5, first
upgrade to version 11.7 and then upgrade to SAP BusinessObjects Data
Services.
Related Topics
• Upgrading repositories

Upgrading your system
When moving to a new software version, upgrade your test or development

environment before upgrading your production environment.
To install a new version on a computer hosting an existing version, run the

installation program without uninstalling the existing version. Uninstalling the
existing version can cause a potential loss of repository information if you
are using the packaged MySQL database server, which is uninstalled with
SAP BusinessObjects Data Services.
Note:
The procedure in the following section directs you to follow instructions in
this guide that explain how to use the installation program.
It's recommended that while upgrading the software you do not use the
installation program to reconfigure Job or Access Servers or upgrade the
repository. Instead, after updating components with the installation program,
use the Server Manager and Repository Manager to reconfigure Job and
Access Servers and upgrade the repository.
Related Topics
• Using configurations from a previous version
Using configurations from a previous version
If you want to use custom configurations from a previous version of the

software:
1. Move the DSConfig.txt file, from the bin subdirectory, into a newly
created "dummy" installation directory structure before installing the new
version.
Example "dummy" directory structure:
Services\bin\DSConfig.txt
During the installation process, SAP BusinessObjects Data Services will
overwrite the "dummy" directory structure with the new installation
structure, merging custom settings (such as repository and Access Server

connections added to the Administrator) from your old DSConfig.txt
file into the new DSConfig.txt file.
2. Before installing the new version, manually move the following
subdirectories out of your installation directory.
• Conf - Contains Administrator settings
• Log - Contains old logs
3. If your current installation includes support for real-time message handling,
then when you configured an Access Server (using the Server Manager)
you specified a location for each Access Server configuration directory.
If those directories are in the software installation directory, make a copy
of each Access Server configuration directory.
Save your current copy until after you test the upgrade and confirm that
your new system is working as expected. When you merge the old
DSConfig.txt file with the new one, the software should find the Access
Server configuration directories. If not, use the Server Manager to point
to the backup Access Server directories.
4. Uninstall the existing software.
5. Install the new software, then move the contents of the old Conf and Log
subdirectories into the new subdirectories.
Related Topics
Before installing a new version
1. Review the Release Notes for the version of SAP BusinessObjects Data
Services you will be installing.
2. Review the Migration Considerations to identify any behavior changes
from previous versions.
3. Recover all unsuccessful jobs which are in a recoverable state.
After upgrading, due to changes in the recovery checkpoint flag, executing
a job in a recoverable state will result in undefined behavior.
4. Open your Windows Services panel and stop all SAP BusinessObjects
Data Integrator or SAP BusinessObjects Data Services services (SAP
BusinessObjects Data Services service and the Address Server).

You can use the Task Manager to verify that no SAP BusinessObjects
Data Integrator or SAP BusinessObjects Data Services-related processes
(processes beginning with al_) are running.
5. Proceed to install the new version.
Related Topics
• To install a new version of the software
To install a new version of the software
1. Use the SAP BusinessObjects Data Services installation program to install

the new version.
2. Restart the computer if prompted by the installation program.
3. Use the Repository Manager to create or upgrade repositories, if needed.
BusinessObjects Data Services > Data Services Repository Manager.
4. Use the Server Manager to make changes to your Job and Access
Servers.
BusinessObjects Data Services > Data Services Server Manager.
5. Verify that the server processes are running.
In the Windows Task Manager, click the Processes tab, and look for:
• al_jobserver.exe
• al_jobservice.exe
• AL_AccessServer.exe
6. Install the new version of the Message Client libraries on any computers
where they are used.
If you are upgrading your Message Client library, you must stop your web
application, install the Message Client library files, then restart your web
application computer.
Related Topics
• Upgrading repositories

To back up and restore the MySQL database
If you choose to use the packaged MySQL installation, the database server
is uninstalled when you uninstall SAP BusinessObjects Data Services. If you
want to uninstall the software before you upgrade to a new version, back up
the repository.
You can back up and restore the repository with the command-line MySQL
administration tools installed with the software. By default, the MySQL
administration tools are installed to the MySqlAdmin5 folder at the same
level as LINK_DIR.
1. Before you uninstall the software, run mysqldump from the command
line to export your repository:
mysqldump -uusername -ppassword DatabaseSchema >
DataServices.sql
DataServices.sql is created in the same directory where the command
was run.
2. Uninstall the existing copy of the software and install the new version.
When installing the new version, create a new MySQL repository.
3. Reboot the system after installing the new version of the software.
4. Run the MySQL administration tool from the command line:
mysql -uusername -ppassword
The MySQL command-line administration tool is opened.
5. Drop the repository schema created by the installation program:
DROP DATABASE dataservices;
6. Create a new, empty repository schema:
CREATE DATABASE dataservices;
7. Activate the new schema:
USE dataservices;
8. Import the content from your existing repository backup file:
SOURCE x:/path/to/DataServices.sql
Include the full path to the repository backup file.
9. Exit the MySQL administration tool.
10. Upgrade the repository with the Repository Manager.

11. Resynchronize the Job Server with the repository with the Server Manager.
The repository is upgraded and you can use the Designer as normal.
Note:
The first time you open the Designer, you may get an error stating that the
user is already logged in. If this happens, click Reset user and use the
Designer as normal.
Related Topics
• To resynchronize Job Servers
Upgrading repositories
After installing a new version of SAP BusinessObjects Data Services, you

can create new repositories or upgrade existing repositories. To associate
an existing repository with your new installation of the software, you must
upgrade that repository.
Before upgrading repositories with the Repository Manager:

• Back up each repository that you intend to upgrade by using an external
database backup utility. For more information, see your database
documentation.
• Install the new version of the client components.
To upgrade a repository
1. On the computer where you installed the Designer, choose Start >
Programs > SAP Business Objects XI 3.2 > SAP BusinessObjects
Data Services > Data Services Repository Manager.
2. Enter the repository connection information for your original repository in
the Repository Manager window.
Note:
Do not attempt to upgrade the backup copy of your repository or you will
experience upgrade errors.
3. Click Get Version.

The Repository Manager displays the version number recorded in the
repository.
4. Click Upgrade.
The Repository Manager converts the pre-existing repository to the format
required by the new version of SAP BusinessObjects Data Services and
adds metadata for new and changed objects.
5. Repeat steps 2 through 4 for each repository you want to upgrade.
Note:
Corresponding local and central repositories must have the same software
version.
6. Click Close.
Note:
If you need to create or upgrade multiple repositories, you can use the Re
poManBatch.exe utility.
Related Topics
• To create or upgrade repositories in batch mode
Upgrading cleansing packages
Restriction:
Depending on the SAP BusinessObjects Data Services versions involved,
you may be required to upgrade all person_firm dictionary customizations
as well as all custom dictionaries created using Universal Data Cleanse. If
upgrade is required, it is critical that you export your dictionary changes prior
to uninstalling your current version of the software in order to be able make
the dictionary information available in the upgraded version. Specific upgrade
information is included in the Release Notes. For more information, see the
Release Notes.
In upgrades between versions of SAP BusinessObjects Data Services when

a cleansing package upgrade is not required (in other words, the cleansing
package upgrade is optional), you may still want to upgrade your existing
dictionaries to take advantage of the updated data in the new cleansing

package version. Updated data may include additional name or firm entries
or secondary information.
For custom dictionaries and rule files created with Universal Data Cleanse,
if the cleansing package upgrade is optional (not required), you need not
upgrade it. After upgrading your SAP BusinessObjects Data Services version,
in the Designer, choose Dictionary > Manage Connection to point to and
continue using the existing dictionary repository.
To upgrade cleansing packages
1. Choose Dictionary > Export Dictionary Changes in the Designer.

Your dictionary customizations are exported to an XML file.
2. Archive all files in LINK_DIR/DataQuality/datacleanse by moving
them to a different location.
3. Upgrade your SAP BusinessObjects Data Services version.
4. Run the cleansing package installer to install the new dictionary data and
rule file.
Note:
Run the cleansing package installer on both the server and client systems.
5. Use the Repository Manager to load the new cleansing package dictionary
into the repository.
6. Depending on your environment, do one of the following:
• For custom dictionaries created with Universal Data Cleanse, choose
Dictionary > Bulk Load in the Designer to import the XML file created
in Step 1.
• For cleansing package person_firm dictionaries, test your job with the
updated cleansing package data.
If the parsing results are not better or at par with previous results, try
importing your customizations from the previous cleansing package.
a. Choose Dictionary > Bulk Load in the Designer to import the XML
file created in Step 1.
b. Compare the rule file archived in Step 2 with the rule file installed
with the updated cleansing package.
c. Copy any rule customizations you made from the archived rule file
to the updated rule file.

Related Topics
After upgrading the software
Run tests of your production jobs to ensure that your existing designs continue
to run as expected in the new version of SAP BusinessObjects Data Services.
When you are confident that the new version of the software performs as
well as or better than the previous version, consider upgrading your
production environment.
Unsuccessful upgrade
Errors that prevent installation progress (for example, an incorrect server
name, user name, or password) yield immediate error messages.
Successful upgrade
A "successful completion" message verifies successful installation.
The LINK_DIR system variable is defined during the installation. Its value
is set to the location of the directory in which you installed the software.
Related Topics
• Troubleshooting installation problems


Index
A configuring (continued)
Metadata Integrator in a distributed
Access Server environment 83
configuration file, upgrading 144 Metadata Integrator in a local environment
configuring 46 82
configuring, Windows 69, 74 runtime resources for Job Servers 73
testing connection to Web client 106 Tomcat 50
verify running 76 web application server 50
Address Server Configuring Job Server run-time resources
Install data directories 109 resources, runtime for Job Servers
start the address server 108 configuring 73
Administrator connectivity, testing 100, 107
configuration file, upgrading 144
D
C
Data Profiler
cleansing package configuring 96
repository 32 database
requirements 32 preparing 30
upgrading 150 repository 30
cleansing packages database server
upgrading 149 configuring 44
ClientTest.exe 151 existing 44
COM API, description 151 reusing BOE MySQL 43
components directories
distribution 13 list 124
ports 18 location 129
upgrading 142 non-default location 129
configuring U.S. directory expiration 127, 128
Access Server 46 update schedule 124
Access Servers 69, 74 directory data 124
Job Server 45 Directory data updates Stop and restart Address
Job Servers 69, 70, 98 Server 109
Metadata Integrator 47, 86 DSConfig.txt file, upgrading custom
configurations 144

Index
DTD samples 101 L

license agreement
F accepting 38
functor_list2312d.dll 151 LINK_DIR system variable 151
functor2312d.dll 151 log, configuration file, upgrading 144
logging in
Management Console 64
I login information
specifying 46
index designer
installing 97
installation M
beginning 38
errors 98 Management Console 104, 151
files to test connectivity 101 log in 64
overview 34 troubleshooting
silent 36 Management Console 98
standard 34, 35 Message Client library
starting 53 COM 151
testing 100, 102 Metadata Integrator 90, 92, 93
installation location configuration overview 80
specifying 39 configuring 47, 86
installed features configuring after installing SAP
selecting 40 BusinessObjects Enterprise 95
itc2312d.dll 151 configuring in a distributed environment 83
configuring in a local environment 82
deleting 86
J specifying configuration details 48
specifying SSL details 49
Job Server troubleshooting 94
configuration 69, 70, 98 mny2012d.dll 151
configuring 45 MySQL
installing 90 backing up 147
repository, synchronizing with 70 configuring 43
verify running 76 upgrading 147
K N
keycode network connections
entering 39 checking 21
product 39 network requirements 11
network1712d.dll 151

Index
P S
pointer2312d.dl 151 sample test files for connectivity 101
ports scripted installation
default numbers 18 performing 56
description 18 running 57
Job Server, configuring 151 Server Manager 69
product keycode service
entering 39 user account 46
Program Job Server services
configuring for Metadata Integrator 92, 93 starting automatically 64
silent installation 58
overview 36, 56
R SNMP, enable for a Job Server on Windows
repository 151
central 17 specifying
configuring 65 login information 46
creating 17 user account 46
creating, multiple 67 standard installation
Job Server, synchronizing with 70 overview 34
local 17 performing 35
troubleshooting 98 starting services 64
upgrading 143, 148 Support adapter and SNMP option 151
upgrading, multiple 148 sync2312d.dll 151
repository database system requirements 11
configuring DB2 27
configuring Microsoft SQL Server 28 T
configuring MySQL 28
configuring Oracle 29 TCP/IP
configuring Sybase 30 port for Job Server 151
preparing 30 testing
selecting 42 connectivity 101, 107
Repository Manager 65 real-time jobs 102
requirements service request from Web application 103,
cleansing package repository 32 107
Data Cleanse 32 thread2312d.dll 151
network 11 threxcept2312d.dll 151
system 11 tls7712d.dll 151
response file Tomcat
creating 57 configuring 50
restarting services 69 troubleshooting
Windows Server 2008 100

Index
troubleshooting (continued) V
Windows Vista 100
versions, repository 143
U
W
upgrading
components 142 web application server
paths 142 configuring 50
repository 143, 148 selecting 49
successful 151 Web applications
user account testing connection to Access Server 106
specifying 46 Windows cluster
user information creating 21
entering 39
user permissions 12
X
XML samples 101

Sap Businessobjects Data Services Installation Guide For Windows

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Businessobjects Data Services Installation Guide For Windows

Uploaded by

Copyright:

Available Formats

SAP BusinessObjects Data Services

Installation Guide for Windows

SAP BusinessObjects Data Services XI 3.2 SP1 (12.2.1)

Chapter 2 Standard Installation 37

SAP BusinessObjects Data Services Installation Guide for Windows 3

To configure a MySQL database server...............................................43

Chapter 3 Silent Installation 55

Chapter 4 After Installation 63

4 SAP BusinessObjects Data Services Installation Guide for Windows

To resynchronize Job Servers..............................................................72

SAP BusinessObjects Data Services Installation Guide for Windows 5

Chapter 5 Citrix Support 111

Chapter 6 Directory Data 123

Chapter 7 Overview of wdeploy 133

6 SAP BusinessObjects Data Services Installation Guide for Windows

Deploy one web component at a time.....................................................136

Chapter 8 Maintaining your installation 141

SAP BusinessObjects Data Services Installation Guide for Windows 7

8 SAP BusinessObjects Data Services Installation Guide for Windows

10 SAP BusinessObjects Data Services Installation Guide for Windows

For a detailed list of supported environments and hardware requirements,

When you install SAP BusinessObjects Data Services on multiple machines,

SAP BusinessObjects Data Services Installation Guide for Windows 11

User permission requirements

To successfully install SAP BusinessObjects Data Services on Windows,

Category Required permission(s)

Windows Vista and Server 2008

12 SAP BusinessObjects Data Services Installation Guide for Windows

Choose components and determine component

You may choose to upgrade or install components on one or more computers

Feature category Component Description

Job Server Server that executes batch jobs.

Server that provides real-time access,

Integration interfaces that provide ac-

Integration component that collects

SAP BusinessObjects Data Services Installation Guide for Windows 13

Feature category Component Description

Designer Graphical user interface that is used to

Web application server that can be used

Web application that manages the SAP

Message Client API that other applica-

14 SAP BusinessObjects Data Services Installation Guide for Windows

SAP BusinessObjects Data Services Installation Guide for Windows 15

16 SAP BusinessObjects Data Services Installation Guide for Windows

Create a database for each repository

SAP BusinessObjects Data Services uses several types of repositories:

SAP BusinessObjects Data Services Installation Guide for Windows 17

Database Connection property

The number of databases you need depends on whether you want a

Check port assignments

On each computer, verify that all ports to be used by SAP BusinessObjects

18 SAP BusinessObjects Data Services Installation Guide for Windows

This table details the default ports:

Port Description Default To set

Receives commands from

Packaged Tomcat Application Server

Supports communication be-

Used to start and shut down

Receives and sends mes-

Interactive Debug- Supports communication for Choose Tools > Options

SAP BusinessObjects Data Services Installation Guide for Windows 19

Port Description Default To set

Example: Default configuration