xi32 ds install win en

SAP BusinessObjectsData ServicesInstallation Guide for Windows

SAP BusinessObjects Data Services XI 3.2 (12.2.0)

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

Copyright

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

2009-06-03

ContentsPreparing to Install 9Chapter 1

Pre-installation overview............................................................................10System requirements...........................................................................11Network requirements..........................................................................11User permission requirements.............................................................12Choose components and determine component distribution...............13Create a database for each repository.................................................17Check port assignments.......................................................................18Check network connections.................................................................21Create a Windows cluster....................................................................21

Repository database requirements and preparation.................................23Installing MySQL as the repository database.......................................24To set up a database account..............................................................25Setting up an empty database for the repository.................................25Database-specific requirements for Data Cleanse...............................31

Installation scenarios.................................................................................33Standard installation overview..............................................................33Silent installation overview ..................................................................35

Standard Installation 37Chapter 2

Beginning your installation.........................................................................38To accept the license agreement.........................................................38To enter user information and a product keycode................................39To specify the installation location........................................................39To select which features to install.........................................................40

To select a repository.................................................................................42

SAP BusinessObjects Data Services Installation Guide for Windows 3

To configure a MySQL database server...............................................43To reuse an existing MySQL instance..................................................43To configure an existing database server.............................................44

To configure a Job Server..........................................................................45To specify login information..................................................................46

To configure an Access Server..................................................................46To configure Metadata Integrator...............................................................47

To specify Metadata Integrator configuration details............................48To specify Metadata Integrator SSL details..........................................49

To select a web application server.............................................................49To configure your Tomcat application server........................................50To configure an existing Web application server..................................50

To start the installation...............................................................................53

Silent Installation 55Chapter 3

Overview of silent installation....................................................................56Performing a scripted installation..............................................................56

To create a response file......................................................................56To run a scripted installation.................................................................57

Performing a silent installation...................................................................58

After Installation 63Chapter 4

Starting services automatically..................................................................64Logging in to the Management Console....................................................64Installing cleansing packages....................................................................64Using the Repository Manager..................................................................65

To create or upgrade repositories........................................................66To create or upgrade repositories in batch mode.................................67

Using the Server Manager.........................................................................69To configure Job Servers......................................................................70

4 SAP BusinessObjects Data Services Installation Guide for Windows

Contents

To resynchronize Job Servers..............................................................72To configure run-time resources...........................................................73To configure Access Servers................................................................74Verifying that Job and Access servers are running..............................76

Using the License Manager.......................................................................76To start License Manager.....................................................................76To view product activation keycodes....................................................77To add product activation keycodes.....................................................77To remove product activation keycodes...............................................78To use License Manager from the command line................................78

Configuring Metadata Integrator ...............................................................80Configuring Metadata Integrator in a local environment......................82Configuring Metadata Integrator in a distributed environment.............83To configure Metadata Integrator from the configuration wizard..........86To install an SAP BusinessObjects Enterprise Job Server for MetadataIntegrator..............................................................................................90To create a Program Job Server group................................................92To configure the server group settings.................................................93Metadata Integrator installation tips and troubleshooting.....................94

Connecting the Data Profiler......................................................................96Troubleshooting installation problems.......................................................97

Repository problems............................................................................97Management Console problems..........................................................98Windows Vista and Server 2008 issues...............................................99Verifying real-time connectivity...........................................................100

Control the Address Server.....................................................................107Start the Address Server....................................................................107Stop the Address Server to install data directories............................108

Citrix Support 109Chapter 5

Installing the software..............................................................................110


Contents

Initial installation.................................................................................111Running components in multi-user mode................................................112

Serial access to the License, Server, and Repository Managers.......112Parallel access to the Management Console, Locale Selector, andDesigner.............................................................................................112Using shell scripts to access the Locale Selector and Designer........113

Publishing the software............................................................................115To publish a component.....................................................................115Connection management...................................................................118Client setup........................................................................................118

Limitations................................................................................................118

Directory Data 121Chapter 6

Directory listing and update schedule......................................................122U.S. Directory expiration..........................................................................125U.S. Directory expiration schedule..........................................................125U.S. National and Auxiliary files..............................................................125Where to copy directories........................................................................126

To copy International directory files to a non-default location ...........126To install and set up Download Manager.................................................127To download directory files......................................................................128Extract directory files on Windows...........................................................128

Maintaining your installation 129Chapter 7

Upgrading the software............................................................................130Component upgrades.........................................................................130Upgrading your system......................................................................131Upgrading repositories.......................................................................136Upgrading cleansing packages..........................................................137After upgrading the software..............................................................138


Contents

Index 141


Contents


Contents

Preparing to Install

1

Pre-installation overviewSAP BusinessObjects Data Services provides an open and flexiblearchitecture 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 instanceif you want to configure a repository during installation.

• Check available port assignments and verify that all machines that willbe part of your deployment have the required network access to eachother.

• Decide whether you want to take advantage of Windows clusteringfail-over support which attempts to automatically restart your SAPBusinessObjects Data Services services in the event of a hardware orWindows software failure.

• Choose an installation method.

The following sections list the core software and system requirements, thechoices available within the core requirements, and the install methodsavailable to you for installing the software.

Related Topics• Getting Started Guide: Architecture


Preparing to Install1 Pre-installation overview

System requirements

For a detailed list of supported environments and hardware requirements,see the Products Availability Report (PAR) available in the SAPBusinessObjects Support > Supported Platforms section of the SAPService Marketplace: http://service.sap.com/bosap-support. This documentincludes 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 followingcomponents must be preinstalled and configured:

• Web application server (unless you want to use the Tomcat installationpackaged with SAP BusinessObjects solution portfolio software, or youdo not want to install the Web Tier components)

• Database software that is compatible with the SAP BusinessObjects DataServices repository (unless you want to use the MySQL installationpackaged with the software).

Note:Only the database client tools or middleware needs to be installed on theSAP BusinessObjects Data Services server; the database server itselfcan reside on a separate physical machine accessible by network fromthe SAP BusinessObjects Data Services server.

Note:For the repository, the software requires a database that stores metadataabout all objects created with the Designer. For best Designer performance,it's recommended that the repository database server and the Designercomputer 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 themachine running the database that contains the repository.

Client components, such as the Designer, require network access to the JobServer(s).


1Preparing to InstallPre-installation overview

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

Note:If your servers are firewalled, you may need to open the necessary ports toallow 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 describedin the table below.

Required permission(s)Category

Administrative privileges on the local machine.Operating System

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

Network

Permissions to add and drop tables in the database, pluspermissions to read, write, and edit table rows.

Database

In addition, it's recommended that you use the same user account forinstalling 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 Filesfolder, regular users do not have write access. Choose another installationdirectory 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 usersbelonging to the Administrators group as standard users for most tasks.When you install SAP BusinessObjects Data Services on Windows Vista orServer 2008, local system administrator privileges are required.



In addition, you must run the Designer for the first time with administratoraccess in order to properly register the application in the system registry.After the Designer has been registered, normal users can run it and mostother SAP BusinessObjects Data Services applications without requiringadministrator authentication.

The Server Manager can be run only by users belonging to the Administratorsgroup, or who can provide administrator authentication.

Choose components and determine componentdistribution

You may choose to upgrade or install components on one or more computersbased on available resources and amount of system traffic.

Note:You must install the Designer and Metadata Integrator on a supportedWindows platform. You can install the other components on Windows, UNIX,or Linux platforms.

The installation program can install multiple feature categories.

DescriptionComponentFeature category

Server that executes batch jobs.Job Server

Server Components

Server that provides real-time access,routes real-time messages to the appro-priate real-time interface.

Access Server

Integration interfaces that provide ac-cess to technologies such as JMS (JavaMessaging System) and Sales-force.com.

Technology Interfaces

Integration component that collectsmetadata from an SAP BusinessObjectsEnterprise system for impact and lin-eage analysis in the Management Con-sole.

Metadata Integrator

(Windows only)



DescriptionComponentFeature category

Graphical user interface that is used todesign and test all jobs.

Designer

(Windows only)Client Components

Interface that creates and manages alltypes of repositories (local, central, pro-filer, and cleansing package).

Repository Manager

Web application server that can be usedto deploy SAP BusinessObjects solutionportfolio software. You can also use yourown existing web application server.

Tomcat application server(optional)

Web Tier Compo-nents

Web application that manages the SAPBusinessObjects Data Services environ-ment (monitors, executes, and sched-ules jobs), as well as metadata reporting(auto-documentation, Validation andOperational dashboards, Data Qualityreports, and impact and lineage analy-sis).

Management Console

Message Client API that other applica-tions can use to integrate with real-timejobs.

Message ClientComponents

Software product documentation.DocumentationComponents

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 fromone Job Server or Access Server installation. Configure Job Server andAccess Server instances by using the Server Manager.

You can install components on one or more computers based on availableresources and the amount of traffic the system processes. Before installingcomponents, consider the following:



• A local repository connects a Designer with a Job Server. You can installa Job Server on the same computer as the repository, on a stand-alonecomputer (with repository database client software), or on the samecomputer as a Designer.

• Any Designer can access any local repository and Job Server. MultipleDesigners 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 giventime.

• Install database client software on the computer containing the Job Serverto support the repository associated with that Job Server. For example,if the repository associated with a Job Server named oradev is an Oracledatabase, then Oracle client software must be installed and configuredon the computer containing the oradev Job Server.

The following diagram depicts a simple distribution of components amongcomputers in a network. Note that you can install each component on oneor more computers. Also note that there are many possible connectionsbetween components. Each box in the diagram represents a differentcomputer.



You can install the Management Console on any computer with or withoutother components. The Management Console is Java-based; you have thechoice to deploy it to the packaged Tomcat server or a previously installedapplication server.

Note:If SAP BusinessObjects Enterprise is installed on the same machine withthe SAP BusinessObjects Enterprise-packaged Tomcat application server,the installer will detect the existing Tomcat instance and share it instead ofinstalling a new instance.

Related Topics• Getting Started Guide: Architecture• 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 andcheck-out. Also provides versioning to keep and allow restore forseveral versions for the same object.

Cleansing packageStores dictionaries for the cleansing packages used by Data Cleansetransforms.

LocalWorking repositories where you create and modify applications.

ProfilerStores profiling metadata when the built-in profiler is configured.

You associate each Job Server with one or more local repositories. Thereis no relationship between central repositories and Job Servers.

Create local repositories before you install each Job Server, or configurethem 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 samelocal repository, then the repository database connection properties for these



Job Servers must be the same. A job will not run on a Job Server withconflicting connection properties. The database connection properties fordifferent databases are shown in this table.

Connection propertyDatabase

DSNDB2

SQL Server Machine and database nameMicrosoft SQL

DSNMySQL

tnsnamesOracle

Sybase Server NameSybase ASE

The number of databases you need depends on whether you want asingle-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 centralrepository.

Note:Multiple Designers can share the same profiler, profiler repository, orcleansing package repository.

Related Topics• Repository database requirements and preparation on page 23• Using the Repository Manager on page 65• Advanced Development Guide: Multi-user development

Check port assignments

On each computer, verify that all ports to be used by SAP BusinessObjectsData Services components are available and not in use by other programs.

For a development system, you can install many components on the samecomputer. This simplifies many connections between components (the hostname is always the same), but you must still define connections based onTCP/IP protocol.



This table details the default ports:

Component

To setDefaultDescriptionPort

Job Server

Use Server Manager3500Receives commands fromDesigner, Access Server,and schedulers.

Job Server port orTCP/IP port

Use Server Manager4001Receives commands andsends data to adapters.

Adapter/SNMPcommunicationport

Packaged Tomcat Application Server

Tomcat conf\server.xml28080Supports communication be-tween web browsers and theManagement Console.

HTTP port

Tomcat conf\server.xml28005

Used to start and shut downthe Web Server which sup-ports the Management Con-sole.

Shutdown port

Access Server

Use Server Manager4000Receives and sends mes-sages from clients and ser-vices.

Communicationport

Designer

Choose Tools > Optionsin the Designer.5001Supports communication for

the debugging feature.Interactive Debug-ger port

Address Server

LINK_DIR\bin\address_server\AddressServerConfig.txt

40010Supports communication forthe Address Server.Control port



Component

To setDefaultDescriptionPort

LINK_DIR\bin\address_server\AddressServerConfig.txt

40011Supports communication forthe Address Server.Application port

Example: Default configuration

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



Check network connections

Before you install SAP BusinessObjects Data Services components, checkthe computers involved and verify network connections by executing the pingcommand on each computer.

Example: Windows Designer and UNIX Job Server

If the Designer will be on a Windows computer and your Job Server will beon a UNIX computer, from the Windows computer open the DOS promptand 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 DataServices services in a Windows Clustering Environment, you must create aWindows cluster before you install the software (refer to your Microsoftdocumentation for details). If you choose this option, in the event of ahardware failure or Windows software failure, the Windows Cluster Managerwill 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 GenericService, it requires a file share, IP address, Network Name, andavailable physical disk resources.

d. Configure Generic Service Parameters. Enter DI_JOBSERVICE asthe Service name.

3. Create a new resource for your web application server as a GenericService. (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 bydouble-clicking the service in the Windows services window. For thepackaged Tomcat installation, the service name is BOE120Tomcat.

4. Run the cluster install utility (js_cluster_install.exe located in thebin directory of your software installation) on the other cluster computersto populate them with the SAP BusinessObjects Data Servicesservice-related information.a. Copy the js_cluster_install.exe and bodi_cluster_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 Servicesand to replicate the shortcuts set up on the primary cluster computer:

js_cluster_install.exe -install if using system accountjs_cluster_install.exe -install -Uuser -Ppasswd -Ddomainwhen not using system account on primary nodejs_cluster_install.exe -remove

c. SAP BusinessObjects Data Services components will use a ClusterNetwork Name to communicate with other components over yournetwork. Open the Server Manager, enter the Cluster Network Nameand click Apply.

Note:If Job Servers are already configured before you enter the ClusterNetwork Name, the Server Manager will prompt you to enter apassword for each currently configured repository associated witheach configured Job Server.



d. Click Restart.

Related Topics• Beginning your installation on page 38

Repository database requirements andpreparation

SAP BusinessObjects Data Services stores your design metadata for sourceand target tables as well as database functions and definitions of built-inobjects in database tables. This set of database tables is called the repository.

You can create one repository during installation. If you want to create arepository in an existing database, you must create space for the repositorybefore you run the installation program. The installation program connectsto the repository and populates it.

A repository requires a minimum of 20 MB of free disk space on the databaseserver.

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 orderto properly prepare your repository database.

Note:You can also choose to skip creating a repository during installation, anduse the Repository Manager to create it at a later time.

Note:If you want to use multi-byte metadata, such as Japanese column nameson imported tables or multi-byte data in Data Quality reports, your databasemust be configured to use Unicode character encoding, such as UTF-8.

Related Topics• Using the Repository Manager on page 65


1Preparing to InstallRepository database requirements and preparation

Installing MySQL as the repository database

MySQL database server is an open-source database that provides local datastorage. The SAP BusinessObjects Data Services installation program caninstall and configure MySQL as the database server for an installation onWindows. If you already have MySQL installed, the installation program canbe used to configure the repository database using your existing databaseengine.

Note:

• The packaged MySQL database can be used only to store SAPBusinessObjects Data Services repository tables. You are not allowed tostore 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 databaseserver is uninstalled when you uninstall SAP BusinessObjects DataServices. If you want to uninstall the software before you upgrade to anew version, back up the repository with the MySQL administration tools.

MySQL installation details

The installation program creates a new MySQL installation with the followingdetails:

ValueProperty

DataServicesODBC datasource name

DataServicesMySQL schema name

BOE120MySQLMySQL service name

Note:The TCP/IP port number, the root user password, and the username andpassword for the account that owns the MySQL schema can be configuredduring installation.

The MySQL administration tools are also installed to the MySqlAdmin5 folderat the same level as LINK_DIR. To start or stop the MySQL service, you canuse the installed MySQL administration tools or the "Services" panel locatedin the "Administrative Tools" section of the Windows Control Panel.


Preparing to Install1 Repository database requirements and preparation

For more information about administering the MySQL installation, see theMySQL documentation at http://dev.mysql.com/doc/index.html.

Related Topics• To back up and restore the MySQL database on page 134

To set up a database account

To administer the repository database, you need to set up a databaseaccount. If you choose to install MySQL as part of your SAP BusinessObjectsData Services installation, you are prompted during installation to set up thisaccount. If you plan to use your own database, complete the steps listedbelow before you install the software.

1. Create or select a user account that provides the software with theappropriate privileges to your database server.

2. Verify that you can log on to your database and carry out administrativetasks using this account.

Setting up an empty database for the repository

If you want to use an existing database server, you must create a newdatabase on your database server before you install SAP BusinessObjectsData Services.

The following database servers are supported for the repository database:

• IBM DB2• Microsoft SQL Server• MySQL• Oracle• Sybase ASE

Note:For information related to supported database software and versionrequirements, review the Products Availability Report (PAR) available in theSAPBusinessObjects Support > Supported Platforms section of the SAPService Marketplace: http://service.sap.com/bosap-support.

To use your existing database with the software, you need to prepare it.



http://dev.mysql.com/doc/index.html


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 databasecan be modified as necessary.

4. Record the name of the database, the user account, and the passwordwhen 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 storeSAP BusinessObjects Data Services data. If you are unsure of the procedurefor creating a new database, consult your specific database serverdocumentation.

Note:If you have an existing SAP BusinessObjects Data Services or SAPBusinessObjects Data Integrator repository, you can upgrade the repositoryduring installation or use the Repository Manager to upgrade it afterinstallation. If you have an existing SAP BusinessObjects Data QualityManagement repository, create a new SAP BusinessObjects Data Servicesrepository and see the Migration Considerations.

32-bit and 64-bit notes

SAP BusinessObjects Data Services 32-bit and 64-bit software is supportedon a variety of operating systems. When you use a database client with the32-bit software, the 32-bit database client libraries must be installed andreferenced in the library paths.

For example, the default installation of the Oracle 64-bit client includesinstallation of the 32-bit client. For non-standard installations, these librariesmust be specified as part of the installation. After installation, the librariesshould be in the $ORACLE_HOME\lib32 directory.

If these 32-bit libraries are not present, you receive an error message statingthat the software cannot load the client library. Examples of error messagesinclude:

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



(5.2) 02-05-02 14:55:23 (E) (26797:0001) REP-100108: Cannotperform operation on Repository<Default Repository> because aconnection to the repository was never opened. A connectionmust be opened to the repository before performing any operation.

When you use a database client with the 64-bit software, the 64-bit clientlibraries must be installed and referenced in the library paths.

DB2 database setup requirements

A local or central SAP BusinessObjects Data Services repository requiresthat you create a dedicated database and define a user with the followingrights:

• To create a table• To start a session• To create a sequence

Install the DB2 Application Enabler software and use DB2 Control Centerand DB2 Script Center to verify the connection between the Designercomputer and the repository computer.

Note:For a repository on DB2, the software also requires a temporary table spacewith 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 betweenWindows authentication (by selecting the check box) and Microsoft SQLServer authentication (by completing the Microsoft SQL Server user nameand password fields):

• Windows authentication — Microsoft SQL Server validates the loginaccount name and password using information from the Windowsoperating system.

• Microsoft SQL Server authentication — Microsoft SQL Serverauthenticates the existing Microsoft SQL Server login account name andpassword.




Related Topics• To prepare your database on page 30

MySQL database setup requirements

To log in to the Repository Manager and the Designer later, you must supplythe following information 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 systemDSN.

Note:ODBC driver version 3.51.22 is recommended for use with MySQL.

If you select the option to install and configure MySQL that is supplied withyour installation, the installation creates a MySQL database with the defaultsettings for the repository database.


Caution:If you provide the password when creating an ODBC data source, users willbe able to log into the Designer without specifying a password. If you chooseto install the packaged MySQL server, the password is automatically specifiedfor the ODBC data source, and anyone with a valid username can accessthe Designer without specifying a password.


Oracle database setup requirements

A local or central SAP BusinessObjects Data Services repository requiresthat you create a dedicated database and define a user with the followingrights:



• To create a table• To start a session• To create a sequence

Grant the user the connect and resource roles. For Oracle 10G/R2, alsogrant the create view role.

Install the Oracle client software and use SQL*Plus to verify the connectionbetween the Designer computer and the repository.

Note:To store multi-byte characters in a repository table when the repository is onan Oracle database, you must change the Oracle database character set toa code page that supports the multi-byte language that you plan to use oryou risk corrupting your metadata. For example, to store Japanese characters,change the Oracle database character set to either SHIFT_JIS or UTF8.



Sybase database setup requirements

A local or central SAP BusinessObjects Data Services repository requiresthat you create a dedicated database and define a user.

Note:For UNIX Job Servers, when logging in to a Sybase repository in theDesigner, the case you type for the database server name must match theassociated case in the SYBASE_Home\interfaces file. If the case does notmatch, you might receive an error because the Job Server cannotcommunicate with the repository.

If you are using both Sybase and Microsoft SQL Server on a Windowsplatform, ensure the Sybase path precedes the Microsoft SQL Server pathin the environment variables %PATH% statement.





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 databaseas required.

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

4. Before you begin your installation, ensure the following are set up:

Information requiredDatabase type

DB2 database aliasDB2

Database nameMicrosoft SQL Server

ODBC datasource nameMySQL

tnsnames connect identifierOracle

Sybase server name

Database name

Sybase ASE

Note:The Sybase server name is a combination of the host name and the portnumber which is set by your database administrator in the file sql.ini.

5. Record these details because you are required to provide them duringinstallation:• 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 databaseserver documentation or your database administrator.

Related Topics• DB2 database setup requirements on page 27• Microsoft SQL Server database setup requirements on page 27• MySQL database setup requirements on page 28• Oracle database setup requirements on page 28• Sybase database setup requirements on page 29

Database-specific requirements for Data Cleanse

SAP BusinessObjects Data Services has specific requirements for thedatabase repository used by cleansing packages or custom Data Cleansedictionaries created using Universal Data Cleanse. For disk spacerequirements, see the Products Availability Report (PAR) available in theSAP BusinessObjects Support > Supported Platforms section of the SAPService Marketplace: http://service.sap.com/bosap-support.

Requirements for specific database server and client settings are describedin the following table:




Required settingsDatabase type

Server settings• Code Page – 1208• Character Set – UTF-8

Note:When creating a DB2 9 database, be sure to check theEnable 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 9client.

DB2

The MySQL server and client must be configured withUTF-8 as the default character set.

In the DSN connection configuration window, set theODBC connection code page to UTF8.

MySQL

Oracle



Required settingsDatabase type

Server settings• NLS_CHARACTERSET – AL32UTF8• NLS_NCHARSET – AL16UTF16

To determine the currently configured character set, youcan use the following select statement on the Oracleserver:

Select * from nls_database_parameters WHEREPARAMETER = 'NLS_CHARACTERSET' ORPARAMETER = 'NLS_NCHAR_CHARACTERSET'

Client settings• NLS_LANG – AMERICAN_AMERICA.AL32UTF8

Note:The Oracle client version must match the Oracle serverversion. For example, if your server uses Oracle 9, usethe Oracle 9 client.

Installation scenarios

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 excludesome components, or install only a limited set of components.

The installable feature categories include:• Server Components• Client Components• Web Tier Components• Message Client Components• Documentation Components


1Preparing to InstallInstallation scenarios

By default, MySQL is installed as the repository database, and Tomcat isinstalled as the web application server. You can also choose to use yourown database or web application server during the installation process.

Note:During installation, you can choose whether to configure many of thecomponents, such as Job Servers and Access Servers. If you skip componentconfiguration during installation, you can use the configuration tools toaccomplish these tasks after installation has finished.

Related Topics• Choose components and determine component distribution on page 13• Getting Started Guide: Architecture

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 usingthe 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 on page 10• Beginning your installation on page 38• Using the Repository Manager on page 65• Using the Server Manager on page 69• Using the License Manager on page 76• Logging in to the Management Console on page 64


Preparing to Install1 Installation scenarios

Silent installation overview

You can run a silent installation to install SAP BusinessObjects Data Servicesfrom the command line using a response file containing installationparameters. This method is particularly useful when you need to performmultiple installations or you do not want to interrupt people who are workingon machines in your system.

You can also incorporate the silent installation command into your own buildscripts. For example, if your organization uses scripts to install software onmachines, 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 on page 56


1Preparing to InstallInstallation scenarios


Preparing to Install1 Installation scenarios

Standard Installation

2

Beginning your installationThe following instructions lead you through the initial steps of setting up yourSAP BusinessObjects Data Services installation. In this stage you will dothe 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 youselect are installed on the local machine.

You can start installation by running setup.exe. After the "Welcome" screenis displayed, click Next to begin your installation.

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

Related Topics• Pre-installation overview on page 10

To accept the license agreement

At the "License Agreement" screen, review and accept the license agreementfor SAP BusinessObjects Data Services. You must accept the agreementto 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.


Standard Installation2 Beginning your installation

To enter user information and a product keycode

At the "User Information" screen, enter user information and provide a productkeycode 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 theregistry.

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

Note:You can enter a single base product keycode during installation. If youneed 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 on page 76

To specify the installation location

At the "Directory Selection" screen, enter the location for your SAPBusinessObjects Data Services installation.

1. Specify where to install the components in the Destination Folder field.The default location is C:\Program Files\BusinessObjects\BusinessObjects Data Services\.

Restriction:The maximum allowable path length is 100 characters. In addition, theDestination Folder field does not support multi-byte characters. To installthe software on a system with a multi-byte locale, you can specify theinstallation location with single-byte characters or use the default location.

Note:

• To run the Designer, a user requires both read and write access tothe installation folder.


2Standard InstallationBeginning your installation

• The installation program creates a Windows environment variablenamed LINK_DIR for this path. LINK_DIR is used throughout thesoftware documentation to refer to this path.

Depending on your component selection, the installation program maycreate other folders or files at the same level as the software installationfolder:• 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 youdo not want to install:


Standard Installation2 Beginning your installation

DescriptionFeature catego-ry

Includes the Job Server, Access Server, MySQL(Server), Metadata Integrator, Address Server, Tech-nology Interfaces, and other adapters.

All server components install by default unless dese-lected.

Server compo-nents

Includes the Designer and Repository manager.

All client components install by default unless dese-lected.

Client compo-nents

Includes the optional Tomcat application server instal-lation and the Management Console web application(including the Administrator, Impact and LineageAnalysis, Operational Dashboards, Data QualityDashboards, Auto Documentation, and Data QualityReports).

All Web Tier components install by default unless de-selected.

Web Tier com-ponents

Includes the C++ and Java libraries for integratingexternal application with real-time jobs.

The Message Client components do not install bydefault unless selected.

Message Clientcomponents

Includes software documentation as PDF documents.

The Documentation components install by defaultunless deselected.

Documentationcomponents

Each component displays a drop-down menu that allows you to choosefrom the following options:• Will be installed on local hard drive — Installs only the selected

component in the tree for that feature.


2Standard InstallationBeginning your installation

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

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

2. To check if you have enough available disk space for the selectedcomponents, 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, clickNext to continue.

To select a repositoryAt the "Repository Selection" screen, choose which type of database to usefor 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 MySqlAdmin5folder at the same level as LINK_DIR.

• Reuse an existing BOE MySQL instance

Note:This option is only available if SAP BusinessObjects Enterprise andpackaged MySQL server are installed on the system.

• Use an existing database server• Skip configurationYou can configure one local repository during installation. If you skip theconfiguration, or you need more repositories, you can configure additionalrepositories later by using the Repository Manager.

Caution:It's recommended that you do not use database tools to attempt to quicklyreplicate additional repositories. By using the Repository Manager tocreate and seed multiple repositories individually, you can avoid potentialissues related to the configuration of repository objects.

2. Click Next to continue.


Standard Installation2 To select a repository


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 MySQLPort Number field.The default port number is 3306. Use this number unless this port isunavailable.

2. Specify and confirm a password for the MySQL root user account.The root user is required for administrative and maintenance tasks onthe MySQL server, such as creating new users for more repositories orperforming backups.

3. Specify and confirm a username and password for the MySQL Repositoryuser account.


To reuse an existing MySQL instance

The "Local Repository Location" screen appears if you chose to reuse anexisting SAP BusinessObjects Enterprise MySQL instance as your repositoryfor the new SAP BusinessObjects Data Services installation. At this screen,specify the connection information for the database where the repository willbe created.

1. Choose the ODBC datasource name for the MySQL instance that youwant to reuse.

2. In the User name field, specify the user name for the account authorizedto use the database.

3. In the Password field, specify the password for the account authorizedto use the database.

4. Click Get Version to check the database connection and verify whethera version of the repository already exists. If you are upgrading from anexisting SAP BusinessObjects Data Integrator or SAP BusinessObjects


2Standard InstallationTo select a repository

Data Services repository, selectUpgrade to keep and upgrade the existingrepository. If you are creating a new repository, select Create.

Caution:If you choose to use Create on an existing repository, the repositorytables 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 anexisting database server as your repository for the new SAP BusinessObjectsData Services installation. At this screen, specify the connection informationfor 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 fieldsare displayed.

2. Provide the database-specific required information in the fields displayed.

Required informationDatabase type

DB2 datasource nameDB2

Database server name

Database name

Windows authentication

Microsoft SQLServer

ODBC datasource nameMySQL

Database connection nameOracle

Database nameSybase ASE

3. In the User name field, specify the user name for the account authorizedto use the database.


Standard Installation2 To select a repository

4. In the Password field, specify the password for the account authorizedto use the database.

5. Click Get Version to check the database connection and verify whethera version of the repository already exists. If you are upgrading from anexisting SAP BusinessObjects Data Integrator or SAP BusinessObjectsData Services repository, click Upgrade to keep and upgrade the existingrepository. If you are creating a new repository, click Create.

Caution:If you choose to use Create on an existing repository, the repositorytables are recreated, and all data in the existing repository will be lost.


To configure a Job ServerAt 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 configurationIf you skip the configuration, you can configure a Job Server later usingthe Server Manager. Any existing Job Servers from a previous SAPBusinessObjects Data Integrator or SAP BusinessObjects Data Servicesinstallation will be retained, unless it has been uninstalled or DSConfig.txt has been removed.

2. If you chose to configure a new Job Server, specify a name and portnumber for the new server in the Job Server name and Job Server portfields.The default Job Server port is 3500.

3. If you need to configure SNMP support or change the runtime resourcesfor the Job Server, click Advanced.The Job Server details screen is displayed. Make any necessaryconfiguration changes and click OK.


Note:If you are using a Sybase or DB2 repository, and need to change the localeof your Job Server, use the Locale Selector after installing the software. Touse the Locale Selector, choose Start > Programs > SAPBusinessObjects


2Standard InstallationTo configure a Job Server

XI 3.2 > SAP BusinessObjects Data Services > Data Services LocaleSelector.

Related Topics• To configure Job Servers on page 70

To specify login information

At the "Login Information" screen, specify the account that the SAPBusinessObjects Data Services service will use to start Job and AccessServers.

1. Select the type of account to use:• Use system account• Use this accountIf you use the system account, you must reboot the system following theinstallation.

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 WindowsServices tool.

2. If you chose to specify a user account, enter the username and passwordin the User and Password fields.

3. Click Next to continue the installation configuration.

To configure an Access ServerAt 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 notneed real-time processing, skip Access Server configuration. Real-time


Standard Installation2 To configure an Access Server

and transactional processing is not licensed in all SAP BusinessObjectsData Services packages and is available as an option.

If you skip the configuration, you can configure an Access Server laterby using the Server Manager. Any existing Access Servers from a previousSAP BusinessObjects Data Integrator or SAP BusinessObjects DataServices installation will be retained, unless it has been uninstalled orDSConfig.txt has been removed.

2. If you chose to configure a new Access Server, specify a directory andport number for the new server in the Directory and Communicationport fields.The default directory for the Access Server is LINK_DIR\bin\AccessServer_1 and the default port is 4000.

3. Check Enable Access Server if you want the Access Server to startwhen the system service is started. By default, Enable Access Serveris checked.


Related Topics• To configure Access Servers on page 74

To configure Metadata IntegratorIf you chose to install Metadata Integrator and SAP BusinessObjectsEnterprise is already installed, the "Configure Metadata Integrator" screenappears. 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 configurationIf you skip the configuration, you can configure Metadata Integrator laterby choosing Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects Data Services >Data ServicesMetadata Integrator.

2. If you chose to create a new Metadata Integrator configuration, type aname 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 Enterprisebefore installing Metadata Integrator. However, if you must install SAP


2Standard InstallationTo configure Metadata Integrator

BusinessObjects Enterprise later, a script is provided to configure MetadataIntegrator later.

Related Topics• To configure Metadata Integrator after installing SAP BusinessObjectsEnterprise on page 95

To specifyMetadata Integrator configuration details

At the "Configure Metadata Integrator" screen, specify details for yourMetadata Integrator configuration.

1. Specify the host name of your SAP BusinessObjects Enterprise CMSserver 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 SAPBusinessObjects Enterprise Administrator's Guide.

6. Specify the folder in which the CMS system adds the Metadata Integratoras 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 Servicesrepository database in the "Repository Database server" area.If you chose to use the packaged MySQL server or an existing SAPBusinessObjects Enterprise MySQL installation, this area is disabled.



Standard Installation2 To configure Metadata Integrator

To specify Metadata Integrator SSL details

If you chose to enable SSL for the Metadata Integrator, the "Configurerepository for Metadata Integrator" screen is displayed. At this screen, specifythe 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 appropriatefields.


To select a web application serverIf you chose to install the Web Tier Components, you need to provideinformation about the web application server that will work with your software.Use the "Select Web Application Server" screen to either install Tomcat asyour application server, or to work with your existing web application server.

To configure your web application server for SAP BusinessObjects DataServices, 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 fromthe drop-down list provided.

Tip:You can configure the server during the current installation process. Youwill need to provide access information for this server in a subsequentscreen.


Note:

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


2Standard InstallationTo select a web application server

the manual deployment on the same machine where Data Services isinstalled.

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 Products AvailabilityReport (PAR) available in the SAPBusinessObjects Support > SupportedPlatforms 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 youchoose to install Tomcat as the web application server for your current SAPBusinessObjects Data Services installation. At this screen, configure Tomcat.

1. In the fields provided, specify which port numbers will be used by Tomcatfor 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 canmodify the Tomcat setup.xml file. By default, this file is installed to theTomcat55\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 installationafter 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 webapplication server.


Standard Installation2 To select a web application server



https://service.sap.com/sap/support/notes/1347589

1. Specify the required configuration information for your existing webapplication server.


2Standard InstallationTo select a web application server

Required informationWeb ApplicationServer

• Server Instance: Name of the current web application server instance(for example, localhost).

• Application Server Installation Directory: The directory where the webapplication server is installed.

Apache Tomcat5.5

• 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.This is mandatory for Weblogic.

• 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 webapplication server instance (for example, C:\bea\weblogic10\samples\domains\wl_server).

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.This is mandatory for Weblogic.

• 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 webapplication server instance (for example, C:\bea\weblogic92\samples\domains\wl_server).

WebLogic 9

WebSphere 6.1


Standard Installation2 To select a web application server

Required informationWeb ApplicationServer

• 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:IfAdmin is Secure is not selected, you do not need to specify a usernameor a password.

• Password: Password for account with administration rights to the appli-cation server.

• Server Instance: Name of the current web application server instance(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 installedwith the secure option, this is required.

• Application Server Installation Directory: The directory for the webapplication server instance (for example, C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\AppSrv01).


Note:To deploy the Management Console to a web server farm, run the SAPBusinessObjects Data Services installation program on each web server inthe farm.

To start the installationThe "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 theBack button. All entries are retained;you do not need to re-enter all the information.

Note:If you are running the setup.exe program from the command line, andhave the -w filename parameter switch enabled, this is the point at


2Standard InstallationTo start the installation

which you canCancel the installation process to have the .ini file writtenwith all the installation parameter information. This .ini file can then beused in silent and scripted installations.

• 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 clickingFinish.

Note:To ensure proper operation, it's recommended that you restart the computerafter you install or uninstall SAP BusinessObjects Data Services.


Standard Installation2 To start the installation

Silent Installation

3

Overview of silent installationThere are two methods for running SAP BusinessObjects Data Servicesinstallations for Windows directly from the command line:

• Silent installation using a response file – referred to as a scriptedinstallation in this guide

• Silent installation specifying parameters directly on the command line

Both methods can be used to automate installations across multiplemachines. The scripted installation requires you to specify a response file.The silent installation allows you to specify parameters for running setup.exe.

Note:The silent installation without the response file is not recommended for custominstallations. This method does not allow for the same level of customizationprovided when using a response file.

Silent installation is particularly useful when you need to perform multipleinstallations, as you can save time and avoid being prompted for informationby the installation program. You can also integrate the scripts and commandsinto your own installation scripts.

Performing a scripted installationWhile setting up an installation process, you can write installation settingsto a specified response file. The file is generated once the installation setupprogram is ready to start the installation.

The response file supports the standard installation type available for SAPBusinessObjects Data Services.

Tip:You do not start the installation process to generate the response file. ClickCancel to abort the installation once you reach the final screen in theinstallation program.

To create a response file

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


Silent Installation3 Overview of silent installation

2. In the command line, type setup.exe -w and the file path for the responsefile 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 youwant 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 inthe 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. TheMACHINE NAME parameter must be specified in the response file if you arereplicating an installation. If the parameter is not specified, the local servername will be used by default.

1. Open a command line console and navigate to the folder that containsthe 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 theinstallation program to read for installation parameters.

Note:By default, the installation program will restart the system following ascripted installation. If you want to prevent the system from restarting,add REBOOT=NULL to the command. For example, setup.exe -rd:\response.ini REBOOT=NULL

3. Press Enter to launch the installation.


3Silent InstallationPerforming a scripted installation

Performing a silent installationYou can run a silent installation from the command line to automatically installSAP BusinessObjects Data Services on any machine in your system, withoutthe installation program prompting for information during the installation. Toinstall silently, run setup.exe, adding parameters that provide informationfor installation settings and directory paths.

This type of installation is particularly useful when you need to performmultiple installations. You can also use the silent installation script in yourown scripts. For example, if your organization uses scripts to install softwareon machines, you can add the silent installation command to your scripts.

The silent installation command consists of setup.exe and a number ofparameters that provide information about the installation.

The following example would perform an installation with the followingconfiguration:• SAP BusinessObjects Data Services• Tomcat• MySQL• Repository database reinitialized

Note:The example uses the most common parameters. You can choose anynumber of valid parameters, but it is good practice to keep the silentinstallation as simple as possible.

The following table lists the most common parameters used in a silentinstallation. To use a parameter, place it on the command line after setup.exe.

Note:Parameter values are case-sensitive.


Silent Installation3 Performing a silent installation

DescriptionInstallationparameter

Specifies that the user is only prompted when the installationis complete.

/qn+

Specifies that the user is not prompted during the install, orwhen the install is complete.

/qn

Specifies that the user is not prompted during the install, orwhen the install is complete.

/qa /qb

Specifies the machine and directory where you want to installthe new components.

For example, C:\Program Files\Business Objects\BusinessObjects Data Services

INSTALLDIR

Specifies your base product activation keycode.PIDKEY

Specifies the user ID for the database.

For trusted authentication this parameter is not required,use DATABASEAUTHENTICATION=trusted.

DATABASEUID

Specifies the MySQL root password.DATABASEPWD_MYSQLROOT

Specifies the account password for the database you'll beusing for the software.

For trusted authentication, this parameter is not required,use DATABASEAUTHENTICATION=trusted instead.

DATABASEPWD


3Silent InstallationPerforming a silent installation


Identify the type of database for the repository.

For Oracle, enter OracleDatabaseSubsystem.

For DB2, enter DB2DatabaseSubsystem.

For Sybase, enter SYBASEDatabaseSubsystem.

For ODBC SQL, enter ODBCDatabaseSubsystem.

For Remote MySQL, enter MySqlDatabaseSubsystem.

DATABASEDRIVER

Specifies the ODBC DSN for the repository database.DATABASEDSN

Specifies the port used for MySQL Server. Defaults to port3306 if it is not specified.

DATABASEPORT

Specifies the name of the CMS database. This databasename defaults to BOE120 if this parameter is not specified.

DATABASEDB

Changes the name of the MySQL audit database, otherwise,the default name of BOE120_Audit will be used.

DATABASEDB_AUDIT

Specifies the user ID for the database.

For trusted authentication this parameter is not required,use DATABASEAUTHENTICATION=trusted.

DATABASEUID_AUDIT

Specifies the account password for the database you'll beusing for the software.

For trusted authentication, this parameter is not required,use DATABASEAUTHENTICATION=trusted instead.

DATABSEPWD_AUDIT




Changes the default directory where Tomcat is installed.

If you don't specify this parameter, Tomcat will be installedthe directory TOMCAT under the default directory for thesoftware.

TOMCATDIR

Specifies a different connection port. If this option is notspecified, port 28080 will be used.

TOMCAT_CONNECTION_PORT

Specifies a different redirect port. If this option is not speci-fied, port 28443 will be used.

TOMCAT_REDIRECT_PORT

Specifies a different shutdown port. If this option is notspecified, port 28005 will be used.

TOMCAT_SHUTDOWN_PORT

Specifies which components will be installed. This is thesame as running a Custom install. Each component isspecified, comma separated and grouped within quotes.

ADDLOCAL


3Silent InstallationPerforming a silent installation

After Installation

4

Starting services automaticallyThe SAP BusinessObjects Data Services service and packaged Tomcatservice start automatically when the computer restarts. The service thenstarts 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 bestarted before using the Global Address Cleanse or Global Suggestion Listtransforms. If you do not need Global Address Cleanse or Global SuggestionList functionality, it's recommended that you leave the Address Server serviceas Manual and do not start it.

Logging in to the Management ConsoleAfter an Access Server is running, you can configure it by using theManagement Console.

Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects Data Services >Data Services Management Console.Log in to the Management Console using the default name (admin) andpassword (admin).

Related Topics• Management Console Administrator Guide: Logging in• Management Console problems on page 98

Installing cleansing packagesInstalling a cleansing package prepares your system to use Data Cleanseto control parsing of name and firm data for the specific cleansing packagelanguage. Ensure that your environment meets the database-specificcodepage and disk space requirements. See the Products Availability Report(PAR) available in the SAP BusinessObjects Support > Supported Platformssection of the SAP Service Marketplace: http://service.sap.com/bosap-support.


After Installation4 Starting services automatically



Note:For custom Data Cleanse dictionaries you plan to create using UniversalData Cleanse, you do not need to install a cleansing package. You can usethe local or central repository. However, you must ensure that the repositoryyou use meets the database-specific codepage and version requirements.

1. Install the cleansing package data on both the client and server systemsby running setup.exe from the cleansing package installation disc ordownloaded location.The cleansing package installer lays down the required reference datato LINK_DIR\DataQuality\datacleanse.

2. Use the Repository Manager to load the cleansing package files into yourrepository.

Related Topics• Database-specific requirements for Data Cleanse on page 31• To create or upgrade repositories on page 66

Using the Repository ManagerUse the Repository Manager to check the version, to upgrade, or to createa repository after installation:

1. Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects Data Services >Data Services RepositoryManager.

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 quicklyreplicate additional repositories. By using the Repository Manager to createand seed multiple repositories individually, you can avoid potential issuesrelated to the configuration of repository objects.

Related Topics• To create or upgrade repositories on page 66• To create or upgrade repositories in batch mode on page 67


4After InstallationUsing the Repository Manager

To create or upgrade repositories

1. If you are creating a new repository, ensure that you created a databasefor the new repository to use.

2. In the Repository Manager window, select the database type of yourrepository.

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:

DescriptionRepository type

(Default) Stores definitions of objects in your localrepository.

Local

Stores definitions of objects in a central repository formultiple-user users.

Central

Stores information generated by the Data Profiler for de-termining the quality of your data.

Profiler

Stores dictionary information for cleansing packages usedby Data Cleanse transforms.

Cleansing pack-age

6. If you are creating a new repository, click Create. If you are upgradingan existing repository, click Upgrade.

Note:For cleansing packages, onlyCreate is available. To upgrade a cleansingpackage, first export any dictionary changes using the Designer. Afterloading the new cleansing package using Create, reapply the dictionarychanges with the bulk load feature. Additionally, it's recommended thatyou use the new rule file included with a new cleansing package. Usingthe 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 through6.

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


After Installation4 Using the Repository Manager

Note:If you created a profiler repository, you must associate it to a Job Serverand connect it to the Management Console Administrator.

Related Topics• Management Console Administrator Guide: Connecting repositories tothe Administrator

• Using the Server Manager on page 69• To configure Job Servers on page 70• Repository database requirements and preparation on page 23• Designer Guide: Bulk load dictionary entries• Upgrading cleansing packages on page 137

To create or upgrade repositories in batch mode

You can use the executable called RepoManBatch.exe (stored in theLINK_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 Authentication

(Microsoft SQL Server only)-t<Type> : Repository type: local, central, pro

filer-c : Repository create-u : Repository upgrade-v : Repository version-d : Show details-a : Repository security

C:\Program Files\Business Objects\BusinessObjects Data Services\bin>


4After InstallationUsing the Repository Manager

For example:

RepoManBatch -Usa -P -NMicroSoft_SQL_Server -SServer -QJake -c -tcentral -d

or

RepoManBatch -UJake -PJake -NOracle -Sdbsvr -v

Usage:

DescriptionFlag

Repository login user

This parameter is required for all database types.-U

Repository login password

This parameter is required for all database types.-P

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

This parameter is required for all database types.

-S

Repository database type:• Microsoft_SQL_Server• DB2• Oracle• Sybase• MySQL

This parameter is required for all database types.

-N


After Installation4 Using the Repository Manager

DescriptionFlag

Repository database name

This parameter is required only for Microsoft SQL Server andSybase ASE.

-Q

Repository type:• local• central• profiler

-t

Create repository-c

Upgrade repository-u

Get repository version-v

Show details-d

Central repository security-a

Using the Server ManagerUse the Server Manager to create, edit, or delete Job Servers and AccessServers 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 JobServers and Access Servers currently configured to run on your computer.

2. Follow the procedures in the next sections to configure Job and Accessservers as needed.

3. In the Server Manager window, click Restart.


4After InstallationUsing the Server Manager

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.

DescriptionProperty

Enter a name that uniquely identifies the Job Server.Job Server name

Enter the TCP/IP port that the Job Server uses to re-ceive commands from the Designer and the AccessServer. If a computer hosts multiple Jobs Servers,each Job Server must have a unique port number.Choose a port number for a server that is not usedby another process on the computer. If you are unsureof which port number to use, use the default portnumber and increment it for each additional JobServer you configure.

Job Server port

Select this check box if the Job Server managesadapters or if this Job Server will be the one to com-municate with an SNMP agent. Each computer thathosts adapters and an SNMP agent must have exactlyone Job Server designated to manage them.

Support Adapter andSNMP communica-tion

Enter the port number that the Job Server uses forcommunicating with adapters or an SNMP agent. Thedefault is 4001.

Communication port

Check this to enables this Job Server to send eventsto the SNMP agent.Enable SNMP

4. UnderAssociated Repositories, enter the local and profiler repositoriesto associate with this Job Server. Each Job Server must be associatedwith at least one local repository.a. Click Add to associate a new local or profiler repository with this Job

Server.


After Installation4 Using the Server Manager

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 theDefault 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 profilerrepository.

e. Click Apply to save your entries and associate the repository with theJob Server.The associated repository updates with the Job Server's computername and port number.

f. Repeat steps a through e until you are done adding all associatedrepositories.

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 othernecessary steps. You can:• Add another Job Server

a. Click Add.b. Repeat steps 3 through 7.

• Change a Job Server's configurationa. Select the Job Server.b. Click Edit.c. Repeat steps 3 through 7.



• Remove a Job Servera. Select the Job Server.b. Click Delete.

Note:If the Job Server has associated repositories, you must first deletethose 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 associatedrepositories.

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 on page 72• To configure run-time resources on page 73

To resynchronize Job Servers

Situations when you must resynchronize the Job Server and the localrepository include:

• When the Job Server information is not available or not correct in thelocal repository.

• You have uninstalled SAP BusinessObjects Data Services and arereinstalling the same version without creating a new local repository.

• You created a new local repository using the Repository Manager afterinstalling SAP BusinessObjects Data Services.

To resynchronize Job Servers:

1. In the Job Server Configuration Editor window, select the name of yourJob Server.

2. Click Resync with Repository.3. In the Job Server Properties window, select an associated local repository.4. Click Resync.



5. When asked whether to update this associated repository with this localmachine 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• Management Console Administrator Guide: Connecting repositories tothe Administrator

To configure run-time resources

1. Open the Server Manager and find the "Runtime resources configuredfor this computer" section.

2. For the Specify a directory with enough disk space for pageablecache option, you can accept the default directory(LINK_DIR\Log\PCache) or click the ellipses button to browse to a differentdirectory.

Note:For memory-intensive operations such as Group By, Order By, andDetailed profiling, specify a pageable cache directory that:

• Contains enough disk space for your data. To estimate the amount ofspace 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 BusinessObjectsData Services system and operating system (such as the C: drive onWindows, or the root file system on UNIX).

• Limits the disk space that data flows consume. The pageable cacheuses all available disk space on the file system that contains thepageable cache directory. So, to limit the disk space that data flowsconsume, create a file system (or partition on Windows) with a limitedsize. Use the new file system (partition on Windows) as the pageablecache directory.



The software uses this directory:

• For pageable caching, which is the default cache type for dataflows.

• When selecting a file transfer type and Automatic is specified inthe Data_Transfer transform.

3. In the "Peer-to-peer options" area, change the values for Start port andEnd port to restrict the number of ports used by the software. The defaultvalues for Start port and End port are 1025 and 32767, respectively.

The software uses these ports for peer-to-peer communications whensending data between data flows or sub data flows.

Related Topics• To configure Access Servers on page 74• Performance Optimization Guide: Caching data• Reference Guide: Data_Transfer• Performance Optimization Guide: Using grid computing to distribute dataflows execution

To configure Access Servers

When you configure the location for an Access Server installation, SAPBusinessObjects Data Services creates space for the Access Server logfiles.

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.



DescriptionField

The location of the log files for this instance ofthe Access Server. Click the ellipses button tobrowse to the Log directory under the directorywhere you installed the software.

Do not change this value after the initial configu-ration.

Directory

The port on this computer that the AccessServer uses to listen for incoming messagesfrom clients.

Make sure that this port number is unused andis unique for each Access Server.

Communication Port

You can leave this box blank.Parameters

An option to control the automatic start of theAccess Server when the SAP BusinessObjectsData Services service starts.

Enable Access Server

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 AccessServer, click Edit, and repeat step 3.

• To remove an Access Server:

In the Access Server Configuration Editor window, highlight the AccessServer and click Delete.

5. After you configure your Access Servers, click OK to return to the ServerManager window.



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 ManagerProcesses tab for:

• al_jobservice.exe (represents the SAP BusinessObjects Data Servicesservice)

• 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 inthe Job Server event log in LINK_DIR/log/JobServername/server_eventlog.txt.

• Access Server logs are in AccessServerPathName/error_mm_dd_yyyy.log

Using the License ManagerLicense Manager lets you manage your product activation keycodes—thealphanumeric codes that are referred to each time that you run certainsoftware. By using License Manager, you can view, add, and remove productactivation 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 cannotaccess the keycodes from a remote system. When updating keycodes, makethe changes on all SAP BusinessObjects Data Services computers bylaunching License Manager on each computer, including Designer and JobServer computers.

To start License Manager

You can run License Manager after the SAP BusinessObjects Data Servicesinstallation has completed.


After Installation4 Using the License Manager

• Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects Data Services >BusinessObjects LicenseManager.

Related Topics• To use License Manager from the command line on page 78

To view product activation keycodes

1. Start License Manager.The License Manager window displays your keycode(s) sortedalphabetically.

2. Select a licensed product or feature in the Registered Keycodes tree toview 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 on page 76

To add product activation keycodes

1. Start License Manager.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 clickAdd.The keycodes that will be added are displayed in the RegisteredKeycodes 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 Managerwithout saving the changes.

4. After you have saved your changes, click Close to exit License Manager.


4After InstallationUsing the License Manager

5. To make sure the new keycode(s) take effect, restart the software.


To remove product activation keycodes

1. Start License Manager.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 affectednodes 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 Managerwithout saving the changes.

4. After you have saved your changes, click Close to exit License Manager.5. Restart the software.


To use License Manager from the command line

License Manager includes a command-line mode that you can use if youdon't want to use the graphical interface, or need to script License Manageroperations.

Syntax

LicenseManager [-v | -a keycode | -r keycode [-l location]]


After Installation4 Using the License Manager

DescriptionParameter

Displays the stored product activation keycodes in aformat similar to the License Manager graphical inter-face. For example:

------ Registered Keycodes ------EIM TitanSuite 12.0Data Services XI 3.1 PremiumKeycode: 00000-0000000-0000000-0000Trial Option: YesExpired: NoDays Remaining: 54

-v or --view

Adds the specified license keycode, and displays thestored keycodes in a format similar to the LicenseManager graphical interface. Returns status messagesfor the following conditions:

• An internal error occurred.• 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.

-a or --add keycode


4After InstallationUsing the License Manager

DescriptionParameter

Removes the specified product activation keycode,and displays the stored keycodes in a format similarto the License Manager graphical interface. If location is specified, the removal is restricted to thatnode. Returns status messages for the followingconditions:

• 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.

-r or --remove keycode [-l location]

Configuring Metadata IntegratorMetadata Integrator allows SAP BusinessObjects Data Services to collectmetadata for Business Views and Universes used by Crystal Reports, SAPBusinessObjects Desktop Intelligence documents, and SAP BusinessObjectsWeb Intelligence documents.

After your environment is configured, the Central Management Consolecontacts the defined Program Job Server to launch scheduled MetadataIntegrator jobs. The jobs collect and copy metadata from your SAPBusinessObjects Enterprise environment to your SAP BusinessObjects DataServices repository. Then you can use the SAP BusinessObjects DataServices metadata tools to browse, analyze, and produce reports on themetadata.


After Installation4 Configuring Metadata Integrator

Metadata Integrator can be configured in either a local or distributedenvironment.

In a local environment, the same Windows server hosts all of the followingcomponents:• 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 SAPBusinessObjects Enterprise Program Job Server must reside on the sameWindows server. The other components of the SAP BusinessObjectsEnterprise environment, including the Central Management Server (CMS)


4After InstallationConfiguring Metadata Integrator

reside on one or more additional systems running on a Windows or UNIXplatform.

Note:Metadata Integrator runs on Windows only. If you have a UNIX CMS, youmust create and configure a distributed environment.

If you have multiple CMS servers in your SAP BusinessObjects Enterpriseenvironment, you can create a separate Metadata Integrator configurationto point to each CMS.

Related Topics• Configuring Metadata Integrator in a local environment on page 82• Configuring Metadata Integrator in a distributed environment on page 83

Configuring Metadata Integrator in a localenvironment

In a local environment, a single Windows server hosts all of the followingcomponents, Metadata Integrator, an SAP BusinessObjects EnterpriseProgram Job Server, and an SAP BusinessObjects Enterprise CentralManagement Server (CMS). Other SAP BusinessObjects Data Servicescomponents may reside on other servers.

Note:If you have a UNIX Central Management Server, you must follow the stepsto configure a distributed environment.

Perform the tasks listed below in order to configure a local Metadata Integratorenvironment on a Windows server.

1. Confirm that an SAP BusinessObjects Enterprise Central ManagementServer (CMS) and a Program Job Server are installed and configured.See the SAP BusinessObjects Enterprise Installation and ConfigurationGuide for Windows.

2. Depending on your circumstances, install and configure MetadataIntegrator in one of the following ways:



Detailed informa-tion

ActionScenario

To configure Meta-data Integrator onpage 47

Install SAP BusinessObjects DataServices and configure Metadata Inte-grator during the installation process.

SAP BusinessOb-jects Data Ser-vices is not in-stalled.

To configure Meta-data Integratorfrom the configura-tion wizard onpage 86

Configure Metadata Integrator from theMetadata Integrator Configuration wiz-ard.

SAP BusinessOb-jects Data Ser-vices is installed,but Metadata Inte-grator was notconfigured duringthe installation.

Beginning your in-stallation onpage 38

Install and configure only the MetadataIntegrator component of SAP Busines-sObjects Data Services on the Win-dows server where the SAP Busines-sObjects Enterprise CMS and ProgramJob Server are installed.

SAP BusinessOb-jects Data Ser-vices is already in-stalled on a differ-ent server. Youwant to install onlyMetadata Integra-tor.

After your environment is configured, from the Central Management Consoleyou can schedule the Program Job Server to launch a Metadata Integratorjob which collects and moves metadata from your SAP BusinessObjectsEnterprise environment to your SAP BusinessObjects Data Servicesrepository. Then you can use SAP BusinessObjects Data Services metadatatools to browse, analyze, and produce reports on that metadata.

Related Topics• Configuring Metadata Integrator on page 80• Configuring Metadata Integrator in a distributed environment on page 83

Configuring Metadata Integrator in a distributedenvironment

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



In a distributed environment, Metadata Integrator and an associated SAPBusinessObjects Enterprise Program Job Server must reside on the sameWindows server. The other components of the SAP BusinessObjectsEnterprise environment, including the Central Management Server (CMS)can reside on one or more additional servers running on a Windows or UNIXplatform. The CMS calls the Program Job Server to launch the MetadataIntegrator job.

The following components are required:

Operat-ing Sys-tem

LocationComponent

WindowsMust reside on the same server as theSAP BusinessObjects Enterprise Pro-gram Job Server

Metadata Integrator

WindowsMust reside on the same server as theMetadata Integrator

SAP BusinessObjects Enter-prise Program Job Server

Windowsor UNIX

Resides on a separate serverSAP BusinessObjects Enter-prise Central ManagementServer (CMS)

Note:You can choose to install Metadata Integrator on the same server as otherSAP BusinessObjects Data Services components or it can be configured ona separate Windows server. However, Metadata Integrator and an SAPBusinessObjects Enterprise Program Job Server must reside on the sameWindows server.

Note:If you have a UNIX Central Management Server, you must follow the stepsto configure a distributed environment.

Perform the tasks listed below in order to configure the Metadata Integratorenvironment.

1. Confirm that an SAP BusinessObjects Enterprise Central ManagementServer (CMS) is installed and configured in your environment. See theSAP BusinessObjects Enterprise Installation and Configuration Guide foryour operating system.



2. On your Windows server, install and configure Metadata Integrator in oneof the following ways:

Detailed informa-tion

ActionScenario

To configureMetadata Integra-tor on page 47

Install SAP BusinessObjects DataServices and configure Metadata In-tegrator during the installation pro-cess.

SAP BusinessOb-jects Data Ser-vices is not in-stalled anywherein your environ-ment.

To configureMetadata Integra-tor from the config-uration wizard onpage 86

Configure Metadata Integrator fromthe Metadata Integrator Configurationwizard.

SAP BusinessOb-jects Data Ser-vices is installed,but Metadata Inte-grator was notconfigured duringthe installation.

Beginning yourinstallation onpage 38

Install and configure only the Metada-ta Integrator component of SAPBusinessObjects Data Services onthe Windows server.

SAP BusinessOb-jects Data Ser-vices is alreadyinstalled on a dif-ferent server. Youwant to install on-ly Metadata Inte-grator.

3. On your Windows server, install the following SAP BusinessObjectsEnterprise components:• Client components• Central Configuration Manager• Program Job Server• Database AccessThe 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 theWindows server.

5. Configure the default settings for that server group to use only the ProgramJob Server within the group.



After your environment is configured, from the Central Management Consoleyou can configure a Metadata Integrator job which collects and copiesmetadata from your SAP BusinessObjects Enterprise environment to yourSAP BusinessObjects Data Services repository. Then you can use SAPBusinessObjects Data Services metadata tools to browse, analyze, andproduce reports on that metadata.

Related Topics• To configure Metadata Integrator from the configuration wizard on page 86• To install an SAP BusinessObjects Enterprise Job Server for MetadataIntegrator on page 90

• To create a Program Job Server group on page 92• To configure the server group settings on page 93• Configuring Metadata Integrator on page 80• Configuring Metadata Integrator in a local environment on page 82

To configure Metadata Integrator from theconfiguration wizard

1. If you deferred the configuration or you want to modify the configuration,click Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects Data Services >Data ServicesMetadata Integratoroption. This Start menu option exists after you have installed either SAPBusinessObjects Data Services or the Metadata Integrator.

2. When the Metadata Integrator Configuration window appears, chooseone 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 thedrop-down list, and click Next

3. On the "BusinessObjects Enterprise" pane, enter the following CMSconnection information. If you need assistance with these values, consultyour administrator.



DescriptionOption

Name for this Metadata Integrator configuration. Thedefault name is Metadata Integrator followed by asequential number. For example:

Metadata Integrator_2

ConfigurationName

Host name of the Central Management Server (CMS)server.

CMS ServerName

The user name to connect to the CMS server in orderto register and execute Metadata Integrator. If youwant a different user to execute the Metadata Integra-tor, use the Central Management Console to changethe rights for the user. See the SAP BusinessObjectsEnterprise Administrator's Guide for details.

CMS User Name

The password to connect to the CMS server to registerand execute the Metadata Integrator.

CMS Password

The CMS authentication mode. For available modes,see the SAP BusinessObjects Enterprise Administra-tor's Guide.

CMS Authentica-tion Mode

The folder in which the CMS system adds MetadataIntegrator 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.

CMS FolderName

4. Click Next.5. On the "Communications Protocol" pane, do one of the following:

• If Secure Sockets Layer (SSL) was not enabled when SAPBusinessObjects Enterprise was deployed, click Next.

• If Secure Sockets Layer (SSL) was enabled when SAPBusinessObjects Enterprise was deployed, select the Enable SSLcheckbox and enter the information required to use Secure Sockets



Layer (SSL) protocol for Metadata Integrator to access metadata fromthe Central Management Server (CMS), and click Next.

See your administrator if you need assistance with these values. Formore information, see the SAP BusinessObjects EnterpriseAdministrator's Guide.

DescriptionOption

Path to the directory where all the certificates and keysare stored.

SSL CertificatesFolder

The generated server certificate file.Server SSL Certifi-cate File

The trusted certificate file.SSL Trusted Cer-tificate File

The private key for the CMS.SSL Private KeyFile

The file that stores the passphrase for the private key.SSL PassphraseFile

6. On the "Metadata Repository" pane, enter the following information toconnect to the SAP BusinessObjects Data Services repository. See yourdatabase administrator if you need assistance with these values.



DescriptionOption

The database type of the SAP BusinessObjectsData Services repository. The availabledatabase types are:• DB2• Microsoft SQL Server• Oracle• Sybase ASE• MySQL

Database type

Host name on which the repository resides.Computer Name

Port number that the Central ManagementServer (CMS) uses to connect to the repository.

Database Port

This field requires additional information basedon the Database type you select.

• Service Name/SID• Database Name• Datasource• Connection String• Database Port and

Server

The login name to connect to the repository.User Name

The login password to connect to the repository.Password

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• Configuring Metadata Integrator in a local environment on page 82• Configuring Metadata Integrator in a distributed environment on page 83



To install an SAP BusinessObjects Enterprise JobServer for Metadata Integrator

In a distributed environment, Metadata Integrator and an associated SAPBusinessObjects Enterprise Program Job Server must reside on the sameWindows server. The other components of the SAP BusinessObjectsEnterprise environment, including the Central Management Server (CMS)can reside on one or more additional servers running on a Windows or aUNIX platform. The CMS calls the Program Job Server to launch the MetadataIntegrator job.

To install and configure the Program Job Server:

1. Follow the SAP BusinessObjects Enterprise installation program until youreach the "Install Type" pane.

2. In the "Install Type" pane, clickCustom or Expand Install and clickNext.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:



DescriptionOption

The name of the Central Management Server(CMS)

Existing CMS Hostname

Port number for the CMS

The default port is 6400

The CMS will communicate with other SAPBusinessObjects Enterprise servers through thespecified port.

Existing CMS Port

The CMS Administrator passwordCMS AdministratorPassword

5. In the "Server Intelligence Agent" pane, type a name for the Windowsserver where you are installing. The name identifies this node of yourdeployment.The Server Intelligence Agent is automatically created during installation.For more information, see the SAP BusinessObjects EnterpriseAdministrator'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 CentralManagement 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 theProgram Job Server and configure the settings.

Related Topics• Configuring Metadata Integrator in a distributed environment on page 83• To configure the server group settings on page 93



To create a Program Job Server group


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 > AddMembers.9. In the "Available Servers and Server Groups" list, click the Program Job

Server installed on the Windows system and click the ">" icon to movethe job server to the "Selected Servers and Server Groups" list.

10. Click OK.

Next, from the Central Management Console configure the settings for thenew server group so that the server group to uses only the Program JobServer within the group to call the Metadata Integrator job.

Related Topics• Configuring Metadata Integrator in a distributed environment on page 83• To configure the server group settings on page 93



To configure the server group settings


Follow the steps below to configure the settings so that the server group youcreated to invoke the Metadata Integrator jobs uses only the Program JobServer within the group:

1. If necessary, log into the Central Management Console.2. On the list, click Folders.3. ExpandAll 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 theServer Group that contains the Program Job Server.

7. Click Save & Close.

Your Metadata Integrator environment is configured. You can use the CentralManagement Console to schedule a Metadata Integrator job.

Note:If you create additional Metadata Integrator configurations, repeat the processof configuring the default settings for each additional Metadata Integratorconfiguration.

Related Topics• Configuring Metadata Integrator in a distributed environment on page 83



Metadata Integrator installation tips andtroubleshooting

Below are several Metadata Integrator installation tips and problems thatyou can troubleshoot:

Configuration fails during installation

If the CMS is unavailable during the Metadata Integrator installation, or if theCMS version has changed since installation, the Metadata Integrator will notrun successfully. Is these cases, the Metadata Integrator will report an errorsuch as the following when launched:

java.lang.NoClassDefFoundError:com/crystaldecisions/sdk/exception/SDKExceptionat com.acta.crystalrepo.config.crConfigFrame.setupWizardPages(crConfigFrame.java:84)at com.acta.crystalrepo.config.crConfigFrame.run(crConfigFrame.java:73)at com.acta.crystalrepo.config.crConfigLaunch.main(crConfigLaunch.java:68)Exception in thread "main"

To reconfigure the Metadata Integrator environment

1. In LINK_DIR/ext/cmsCollector, run cmsSetEnv.cmd to reset allcommand files to point to the installed version of CMS.

2. Run cmsConfig.cmd to update any configured Metadata Integrators topoint to the installed version of CMS.

Changing repository connection information

• To change the SAP BusinessObjects Data Services repository connectioninformation supplied during configuration, run the configuration utility:

LINK_DIR/ext/cmsCollector/cmsConfig.cmd



To configure Metadata Integrator after installing SAPBusinessObjects Enterprise

It's recommended that you install SAP BusinessObjects Enterprise beforeyou install and configure SAP BusinessObjects Data Services and theMetadata Integrator.

However, if you need to install SAP BusinessObjects Data Services first, ascript 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 theLINK_DIR\ext\cmsCollector folder.

2. Set the value of the BOE_SDK variable to the location of your SAPBusinessObjects Enterprise SDK library and save the script. By default,the SDK library is installed to boe_parent_folder\Common\version\java\lib.For example, for SAP BusinessObjects Enterprise XI R2:

BOE_SDK=C:\Program Files\Business Objects\Common\3.5\java\lib

3. Navigate to LINK_DIR\ext\cmsCollector in a command prompt, andrun the MetadataIntegratorSetup.cmd script.The script performs additional configuration steps required to use theMetadata Integrator.

Metadata Collector fails to start with java version error

If the Metadata collector indicates the run has failed, click the run instanceto view the error log. If the error indicates the java run-time environmentcannot be found or is the wrong version, you must define the JAVA_HOMEenvironment variable.

To define the JAVA_HOME environment variable, add the environmentvariable and reboot your machine for it to take effect. Java 1.3.1 or higheris required. JAVA_HOME must be set to the java run-time root directory. Forexample:

JAVA_HOME=C:\Program Files\Java\j2re1.4.2_03



Metadata Collector fails to start

If the Metadata collector indicates the run has failed, click the run instanceto view the error log. The error indicates you do not have the permission torun the program.

Press the Process tab and select Logon to determine the user name andpassword used to run the collector. To check the permissions, press theRights tab to see what permissions are set. If you do not have permissionto 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 theMetadata Integrator even though it says the run was successful. The collectorwill only be in a failed state if the CMS is unable to start the program. Thereis no mechanism to get run-time errors listed as a failed run. The work aroundis to look at successful runs to see if any errors are reported.

Connecting the Data ProfilerThe Data Profiler installs automatically when you install SAP BusinessObjectsData Services. To use the Data Profiler, perform the following steps:

1. Define a profiler repository in which the Data Profiler will store thegenerated profile data.

2. Associate the profiler repository with a Job Server on which the profilertasks will run.

3. Connect the profiler repository to the Administrator which will managethe profile data and profiler tasks.

4. Connect the profiler server to the Designer from which you submit profilertasks and view the generated profile data.

5. If you plan to use Detailed profiling or Relationship profiling, ensure thatyou specify a pageable cache directory that contains enough disk spacefor your data and that you place on a separate disk or file system fromthe SAP BusinessObjects Data Services system.


After Installation4 Connecting the Data Profiler

Related Topics• To create or upgrade repositories on page 66• To configure Job Servers on page 70• To configure run-time resources on page 73• Management Console Administrator Guide: Connecting repositories tothe Administrator

• Designer Guide: Connecting to the profiler server

Troubleshooting installation problemsErrors that prevent installation progress (for example, an incorrect servername, user name, or password) result in an immediate error messagedescribing the problem.

For some common issues, such as the service scheduler failing to launchSAP BusinessObjects Data Services, reboot the computer after installationhas finished.

Related Topics• Metadata Integrator installation tips and troubleshooting on page 94

Repository problems

Common repository-related installation errors include:

• The DBMS connection was lost while building the repository tables. If thishappens, recreate the repository with the Repository Manager.

• There is not enough space available in the database for the repositorytables. If this happens, use your DBMS administration tools to allocatemore space for the repository and run the Repository Manager.

If you experience problems when upgrading or creating a repository, youcan select the Show Details check box before you click Update or Createagain. This option allows you to view the SQL code that SAP BusinessObjectsData Services uses to perform these operations. The Show Details optioncan help you diagnose problems.



4After InstallationTroubleshooting installation problems

Management Console problems

Common Management Console and web application-related installationproblems include:

• The Management Console login page cannot be found.

This problem can occur when the web application service is not runningor needs to be restarted. Restart the web application server. For thepackaged Tomcat web application server, use the Services tool in theAdministrative Tools section of the Windows Control Panel.

The problem can also occur in a high security environment. To remedythe problem, you can set a lower security on the computer, use thebrowser on a computer with a lower security setting, or add your machinename into the trusted sites. You can also manually edit the URL in thebrowser; 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 theapplication port, you may need to modify the link to the ManagementConsole. In LINK_DIR/ext/DataServices.html, replace 9080 in thefollowing 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 Tomcatapplication server.

This problem can occur when the Tomcat application server is not correctlyconfigured to use multi-byte data. You can correct this problem by addinguseBodyEncodingForURI="true" to your Tomcat server.xmlconfiguration file. For example:

<Connector port="8080"maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

enableLookups="false" redirectPort="8443" acceptCount="100"


After Installation4 Troubleshooting installation problems

debug="0" connectionTimeout="20000"disableUploadTimeout="true" useBodyEncodingForURI="true"/>

• Web services cannot be deployed to an existing Tomcat application server.

This problem can occur when Tomcat has been installed using Tomcat'sWindows installer, which does not include certain files needed by thewdeploy process used by the SAP BusinessObjects Data Servicesinstallation program. You can correct this problem by downloading Tomcatin a zip file from the Apache website. Extracting the zip file and copy anymissing 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 onWindows Vista or Windows Server 2008, you may receive messages aboutfiles in use or applications that should be closed. You can safely ignore thesemessages and continue to install or uninstall the software.

Ignoring these messages will have no impact on the installation or behaviorof the software.

Update to file access rights failed

When installing SAP BusinessObjects Data Services on Windows Vista orWindows Server 2008, you may receive this warning if the installation setupprogram is unable to set file access rights.

To manually update the file access rights, you can use the grantFileAccess.bat batch file. This batch file is installed to the LINK_DIR\bin folderand takes one parameter as input, the software installation path (LINK_DIR).

For example, if you installed the software to C:\Program Files\BusinessObjects\BusinessObjects Data Services\:

grantFileAccess.bat "C:\Program Files\Business Objects\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 SAPBusinessObjects Data Services real-time features after installation. Thesestep-by-step procedures use sample files available in the software installation.

Distributing the test files

The SAP BusinessObjects Data Services installation includes test files toexercise connectivity between each component of the system. To performthe connectivity test, place test files in the appropriate locations on the variouscomputers used in your application.

Copy toCopy fromTest file

Web client computer, C:\tempLINK_DIR\BinClientTest.exe

Web client computer, C:\tempLINK_DIR\Binmny2412d.dll

Web client computer, C:\tempLINK_DIR\Binfunctor2312d.dll

Web client computer, C:\tempLINK_DIR\Binfunctor_list2312d.dll

Web client computer, C:\tempLINK_DIR\Binitc2312d.dll

Web client computer, C:\tempLINK_DIR\Binnetwork1712d.dll

Web client computer, C:\tempLINK_DIR\Binpointer2312d.dll

Web client computer, C:\tempLINK_DIR\Binsync2312d.dll

Web client computer, C:\tempLINK_DIR\Binthread2312d.dll

Web client computer, C:\tempLINK_DIR\Binthrexcept2312d.dll

Web client computer, C:\tempLINK_DIR\Bintls7712d.dll

Web client computer, C:\tempLINK_DIR\ConnectivityTest

ClientTest.txt



Copy toCopy fromTest file

Web client computer, C:\tempLINK_DIR\ConnectivityTest

TestIn.xml

Designer computer, C:\tempLINK_DIR\ConnectivityTest

TestIn.xml


TestIn.dtd


TestOut.dtd

Note:You must keep the DLL files specified in the preceding table withClientTest.exe. To move ClientTest.exe, re-run the Message ClientSetup and point it to the directory you want.

You need not move the TestConnectivity.atl file from its location on theDesigner computer.

To test a job

When you execute a real-time job from the Designer, it always executes intest 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 verifythat a real-time job can successfully execute from the Designer. Test filesinclude the XML test input for the flow (the string “Hello World”) and thecorresponding DTD for flow input and output.

This procedure describes how to import, display, execute, and show outputfor the test flow.

1. Start SAP BusinessObjects Data Services and log into your repository.

Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects Data Services > Data Services Designer from theprogram group created by the installation. The Designer prompts you forlogin 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.7. In the Jobs tab of the object library, expand theReal-time Jobs category;

then click, drag, and drop Job_TestConnectivity over the TestConnectivityfolder 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 theorder of the two words in the string, and writes the output to theC:\Temp\TestOut.xml file.

11. Read the information in the Job Log window to verify if the TestOut.xmlfile is correct. Use the job log information to troubleshoot problems.

12. If the job was successful, navigate to the C:\Temp\ directory on theDesigner'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 canuse it to process a service request from a Web client. In production, Webclients send messages and real-time services receive and process thosemessages, triggering real-time jobs. Use the Management ConsoleAdministrator to set up real-time services.

To process a service request from a Web client1. Add and start the service in the Administrator.

The Access Server starts service providers which are instances of jobsassociated 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, thenthe service provider sends a response to the Access Server. The AccessServer returns the response to the Web client.

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

After you install the Access Server, the SAP BusinessObjects Data Servicesservice automatically launches the Access Server when your computerrestarts or when you stop and start the service.

To start the Administrator1. Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAP

BusinessObjects Data Services > Data Services ManagementConsole.

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 theAdministrator computer.

2. Log in to the Management Console using the default name (admin) andpassword (admin).

3. Click the Administrator icon to open the Web Administrator.

To add your repository for Administrator access1. 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 services1. 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 service1. 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 displaysthe configuration boxes for the new service.

3. Enter the following sample information in the Configuration section forthe service.

Accept the default values for the service parameters.

DescriptionTest ValuesField

The message type in-cluded in the call fromthe client.

TestConnectivityService Name

Browse jobs.Job_TestConnectivityJob Name

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 clickApply.

7. Click the Status tab.

The Administrator adds the new service (named after the job) and aservice provider to the list for this service. In the status row for eachservice provider, find the computer name and Job Server port where theservice provider is running. The process ID for the service provider isrelated 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 thenew service provider correctly indicate the computer where the Job Serveris installed and the port that the Job Server is configured to use.



You specified the Job Server port number when you configured the JobServer at installation.

9. In the navigation tree, click Real-Time Services to return to the firstReal-Time Service Status page.

The name of the Service should be next to a green icon which indicatesthat the Service started successfully.

When a service starts, the Administrator triggers the Access Server whichtriggers the Job Server to get job information from the repository. The jobregisters as a service with the Access Server. The Administrator displaysthe service status (started).

If the service did not start, you can start it manually from the current page.

Web client to Access ServerA Web client opens a connection to the Access Server using a call in theMessage Client library. The call includes the host and port informationrequired to make the connection.

The ClientTest executable file provided in the SAP BusinessObjects DataServices installation incorporates the library calls so you can easily test theconnection between the Web client computer and the Access Server.

To process a test request1. 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 commandprompt:

ClientTest -AHost -pPort -Uuser -Ppassword -STestConnectivity-XC:\Temp\TestIn.xml

where

Identifies the Access Server hostcomputer by name or IP address.Host

Identifies the port on which AccessServer listens for Web client re-quests.

Port



Indicates the user name you specifiedin the Security section of the AccessServer configuration file. The testconfiguration does not specify a user,but the Client Test utility expectssome value. Enter any character.

user

Indicates the password you specifiedin the Security section of the AccessServer configuration file. The testconfiguration does not specify apassword, but the Client Test utilityexpects some value. Enter any char-acter.

password

Specifies the name of the servicethat you want to invoke.

C:\Temp\TestIn.xml

Indicates the location of the sampleXML request that will be sent to theAccess Server for processing.

TestConnectivity

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 willneed. For example, you can use the existing Access Server configurationand make changes to the data flow and input files in the sample real-timejob. In particular, consider making simple additions to the data flow in thereal-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 flowof the real-time job and extract a single value to return as a response tothe client.

Control the Address ServerThe Address Server is required for processing addresses with the EMEAengine and Global Suggestion Lists. You must manually start and stop theAddress Server.

Start the Address Server

To process addresses with Global Suggestion Lists or the EMEA engine youneed to manually start the Address Server after installing SAPBusinessObjects Data Services and the data directories. If a data flowrequires the use of the Address Server, it will wait for the server to initializebefore starting a process.

Note:The software does not start the Address Server automatically due to theconsiderable amount of memory resources required to run the server. Startthe Address Server when you plan to use Global Suggestion Lists or theEMEA 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 minutesdue to the loading of the directory data. The initialization will take about


4After InstallationControl the Address Server

20 minutes each time you install updated directory files and restartthe Address Server.

• The Address Server caches the directory data for optimumperformance and will require a significant amount of memory.

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 on page 121• To copy International directory files to a non-default location on page 126


After Installation4 Control the Address Server

Citrix Support

5

You can set up SAP BusinessObjects Data Services to run under CitrixPresentation Server. Presentation Server provides an access infrastructurefor enterprise applications.

Presentation Server supports many methods of running applications. Thissection provides information about how to install one copy of an SAPBusinessObjects Data Services component, run it as a PresentationServer-published application or published desktop on a server, and set clientuser permissions for it.

Definitions

The following definitions introduce basic Citrix concepts. To learn more aboutCitrix Presentation Server, see Citrix Presentation Server documentation.

DescriptionConcept

A Citrix-defined protocol/connection to a server. The ICAclient connection allows Presentation Server to run any ap-plication on its server and manage how each client accessesthe user interface of the application.

ICA Client

The Presentation Server component installed on a client. Itmanages ICA client connections and published applicationsfor a given user.

Program Neigh-borhood

Application software (for example, the Designer) installed ona Presentation Server server and published to users. Anadministrator can choose which users may run and view theapplication.

Published Appli-cation

A set of all published applications that a user can access.When you start your Program Neighborhood software, yousee this application set, which can include multiple applica-tions published on multiple Presentation Servers.

Application Set

Installing the softwareUser interfaces for SAP BusinessObjects Data Services are certified to runon Citrix Presentation Server as an application set. The set consists of:

• Designer (includes the Metadata Reporting tool)


Citrix Support5 Installing the software

• Management Console• License Manager• Repository Manager• Locale Selector• Server Manager• Documentation Components

Initial installation

The installation process for SAP BusinessObjects Data Services onPresentation Server is slightly different from a typical installation. ThePresentation Server runs Microsoft terminal services in application mode.Therefore, you must install the software using the Add/Remove programsservice in the Windows control panel.

To install the software, follow the prompts of the Add/Remove program wizardand 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 andthe Job Server on separate computers.

After you install Job Servers and Access Servers, you must provideconnection settings to users because their remote setups will look for theservers locally by default. Similarly, manage sources, targets, and repositoriesfrom the Presentation Server in the usual fashion. However, individual clientsmust use database connection names defined on the server (not the localclient). The Designer defaults to looking for configuration information locally.For example, to connect to an Oracle repository, define the Oracle connectionname on the Presentation Server and provide the connection information toyour users.

Note:Because Citrix Presentation Server is running on a server, be aware that thefirst time you install the software, you must reboot the server.

Related Topics• Limitations on page 118


5Citrix SupportInstalling the software

Running components inmulti-usermodeWhile Presentation Server allows you to publish SAP BusinessObjects DataServices interface components to one user or multiple users at the sametime, it's recommended that you run all but the Designer, ManagementConsole, and Locale Selector in serial mode.

Serial access to the License, Server, and RepositoryManagers

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 restrictionwill not be a problem, because users typically do not access thesecomponents often. To set these components for serial access, usePresentation Server to configure their application limit to one instance perserver.

Parallel access to the Management Console, LocaleSelector, and Designer

Use Presentation Server to configure the Management Console, LocaleSelector, 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 alsomust limit the application to one instance per user and ensure that yourconfiguration preserves user settings. A DOS shell script is provided toaccomplish this for each application.

Related Topics• Publishing the software on page 115


Citrix Support5 Running components in multi-user mode

Using shell scripts to access the Locale Selector andDesigner

When you install SAP BusinessObjects Data Services, the environmentvariable LINK_DIR is set to point to the install directory. This variable allowsthe software to locate settings and persistent environment information.

Because there is only one LINK_DIR variable per installation, when multipleusers run a single Designer or Locale Selector installation (in serial orparallel), 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 eachuser with their own copy of required resource files and to create a newenvironment variable (USER_LINK_DIR) that directs the Locale Selector orDesigner to the user-specific resource copy.

The DOS batch file for the Designer is RunDSDesignerMU.bat, and the DOSbatch 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 thebatch file. For example: RunDSDesignerMU D:\UserData

The following diagram shows how the batch files enable multiple processesto run on a single computer by creating user-specific resource directories:


5Citrix SupportRunning components in multi-user mode

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


Citrix Support5 Running components in multi-user mode

Publishing the softwareAfter you install SAP BusinessObjects Data Services, you can set up its userinterface components as Published Applications to make them available toclients. The Presentation Server Management console includes a wizard tohelp you do this. Run it once for each component (Designer, ManagementConsole, Repository Manager, Server Manager, Locale Selector, and LicenseManager). You must publish each component separately.

To publish a component

1. Start the Citrix Presentation Server Management console.2. SelectApplications from the menu tree and choose Publish Application

from the menu.3. On the "Specify What to Publish" page, configure each component:

Content addressWorking direc-tory

Command linePublish asComponent

C:RunDSDesignerMU.bat

ApplicationDesigner

"$LINK_DIR"\binRepoMan.exeApplicationRepository Man-ager

"$LINK_DIR"\binAWServerConfig.exe

ApplicationServer Manager

"$LINK_DIR"\binLicenseManager.exe

ApplicationLicense Manager(optional)

"$LINK_DIR"/ext/DataServices.html

ContentManagementConsole

C:RunLocaleSelectorMU.bat

ApplicationLocale Selector

Note:a. Publish the Designer and Locale Selector .bat files instead of directly

publishing the executables.


5Citrix SupportPublishing the software

b. To allow for spaces in the install path name, use quotes around anyvariable that includes a directory name.

c. After using Presentation Server to configure the Management Consoleas content, share the ext directory with all Management Consoleusers.

The Publish Application Wizard allows you to enter a file name for thestart icon used by applications published as content. For the ManagementConsole, enter the path to Admin_small.ico if you want users to haveaccess to the icon. Note that Designer components run as a shortcut onthe client desktop.

4. Define the Program Neighborhood settings:


Citrix Support5 Publishing the software

DescriptionSetting

Choose 256 colors at minimum. Lower resolution set-tings may work but will not allow users to easily distin-guish icons and object bitmaps. Program Neighborhoodprovides an option to maximize any application atstartup. It is recommended that you do not maximizethe Designer at startup because older versions of theDesigner might fail.

Application Appear-ance

It's recommended that you use only the basic securitylevel option in Program Neighborhood. Higher levelsof security may work but have not been tested.

ICA Client Require-ments

The Designer, Locale Selector, Repository Manager,Server Manager, and License Manager were notdesigned to be run by multiple users at the sametime. However, Citrix will allow several instances ofthese programs to be active at the same time on thesame server. It's recommended that you set themaximum number of instances for the RepositoryManager, Server Manager, and License Managerexecutables to 1.

For the Designer and Locale Selector, you can allowmultiple instances of the .bat file to run, but limitone instance of each .bat file per user.

Since the Management Console is published ascontent, you can run multiple instances of it.

Application Limits

You can specify which servers in a Presentation Serverserver 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 thesoftware on several servers, publish only one.

Specify Servers

You can specify which users can access a particularapplication. If you specify three users, the componentdefined by the application appears in each of the users'Program Neighborhoods.

Specify Users


5Citrix SupportPublishing the software

Connection management

After installing SAP BusinessObjects Data Services components, give eachuser permission to establish an ICA connection with the Presentation Server.Run the Citrix Connection Configuration tool to assign user permissions toa connection.

Client setup

If users will be running SAP BusinessObjects Data Services componentsfrom client computers, install the Citrix Program Neighborhood software onthese computers.

Note:The software components were tested as a Citrix Program Neighborhoodapplication set. These components were not tested as a ProgramNeighborhood agent or web interface.

Related Topics• Initial installation on page 111

LimitationsThe following are known limitations to running SAP BusinessObjects DataServices on Citrix:

• The software stores files in the Job Server’s log directory when youcapture sample data using the View Data feature. If the Designer runson the same computer as the Job Server, the default location of the logdirectory changes each time a user logs in through Citrix. This changeprevents the Designer from locating the View Data log files for a givenuser. To avoid this issue, it's recommended that you run the Job Serveron a different computer than Designer. This limitation does not apply tothe interactive debugger.

• If the Server Manager is published to a Citrix client and you try to add aJob Server from the client, the SAP BusinessObjects Data Servicesservice might not start. If this occurs, log on to the Job Server’s computerand restart the service. You must have sufficient user privileges to restart


Citrix Support5 Limitations

a service using the computer’s operating system. When the service isinstalled, it uses the ID and password that belong to the user who runsthe installer as its default login values.

• Citrix runs the Designer process on the server and publishes only its userinterface to the client. Since the Designer runs on the server, users musthave sufficient read/write permissions for directories or files on the serverif 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 theserver or give users administrator authority on the server.


5Citrix SupportLimitations


Citrix Support5 Limitations

Directory Data

6

What are directories?

To correct addresses and assign codes with SAP BusinessObjects DataServices, the Address Cleanse transform relies on directories, or databases.When Address Cleanse uses the directories, it’s similar to the way that youuse the telephone directory. A telephone directory is a large table in whichyou look up something you know—someone’s name—and locate somethingthat you don’t know—their phone number.

You may not need to use all of the reference files depending on whichtransforms or options you use. Depending on which option you own, somedisks or online packages that you receive may contain extra files in additionto your directories. For example, you may see an Extract folder. If you donot need these extra files, do not copy them to your computer. For informationabout extra folders, see the ReadMe.txt file included with the reference files.

Directory listing and update schedule

Updated Monthly(M)

Bimonthly (B)

Quarterly (Q)

ApproximateSize

Directory filenameDirectory type

MB699 MBzip4us.dirZIP4 and Auxiliary Directories

MB2 MB

2 MB

1 MB

97 MB

4 MB

cityxx.dir

zcfxx.dir

revzip4.dir

zip4us.rev

zip4us.shs

Auxiliary Directories

Weekly1 MBewyymmdd.dirEarly Warning System Directory

M653 MBdpv_pathDPV Data

M486MBelot.dirEnhanced Line of Travel Directory


Directory Data6 Directory listing and update schedule

Updated Monthly(M)

Bimonthly (B)

Quarterly (Q)

ApproximateSize


M42 MBcanada.dir

cancity.dir

canfsa.dir

canpci.dir

Canada engine - Address Data

MQ200 MBapc.dir

aucity.dir

aus.dir

Australia engine - Address Data

Qup to 12.2 GB(for all countries)

all filesGlobal Address engine and EMEAEngine - Data

Note:You will receive files only for thosecountries your company has pur-chased.

Q720 MBcgeox.dirCentroid Level Geo Data

Q4.67 GBageox.dirAddress Level Geo Data


6Directory DataDirectory listing and update schedule

Updated Monthly(M)

Bimonthly (B)

Quarterly (Q)

ApproximateSize


QCanada: 1.6GB

Canada: 1 MB

France: 1.6 GB

France: 6 MB

USA: < 2 GB

USA: < 2 GB

geo_addr_ca_vendorx .dir

geo_cent_ca_vendorx .dir

geo_addr_fr_vendorx .dir

geo_cent_fr_vendorx .dir

geo_addr_us_vendorx<num> .dir

geo_cent_us_vendorx<num> .dir

Geocoder

M199 MBz4change.dirZ4Change Data

461 MBall filesLACSLink

Q248 MBga_region_jp_paf.dir

ga_loc12_jp_paf.dir

ga_loc34_jp_paf.dir

ga_dp_jp_paf.dir

Japan engine - Address Data

Related Topics• Designer Guide: Address Server for the EMEA engine and GlobalSuggestion Lists


Directory Data6 Directory listing and update schedule

U.S. Directory expirationWe publish and distribute the ZIP4 and supporting directory files under anon-exclusive license from the USPS. The USPS requires that our softwaredisable itself when a user attempts to use expired directories.

If you do not install new directories as you receive them, the software issuesa warning in the log files when the directories are due to expire within 30days. 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 solutionportfolio software. The system administrator must install monthly or bimonthlydirectory updates to ensure that they are compatible with the current software.

U.S. Directory expiration scheduleYou can choose to receive updated U.S. national directories on a monthlyor 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 afterdirectory creation. When running in Non-Certified mode, Zip4 and Auxiliarydirectories expire on first day of the fourteenth month after directorycreation.

• LACSLink directories expire 105 days after directory creation.

U.S. National and Auxiliary filesThe U.S. National and Auxiliary file self-extracting files are named as follows.


6Directory DataU.S. Directory expiration

Zip file nameDirectory name

us_dirs_2004.exe2004-2008 U.S. Nationaldirectory

us_ageo1_2.exe

us_ageo3_4.exe

us_ageo5_6.exe

us_ageo7_8.exe

us_ageo9_10.exe

U.S. Address-level Geo-Census

us_cgeo.exe

us_cgeo1.exe

us_cgeo2.exe

U.S. Centroid-level Geo-Census

Related Topics• Extract directory files on Windows on page 128

Where to copy directoriesWe recommend that you install the directory files in a common file systemdirectory local to the system in which SAP BusinessObjects Data Servicesis installed. By default, the software looks for directories in$LINK_DIR\DataQuality\reference_data on Windows. If you place yourdirectories in a different location, you must update your substitution file.

To copy International directory files to a non-defaultlocation

If you use the Global Address Cleanse Transform's EMEA engine or GlobalSuggestion Lists' Multi Country engine and store your data directories in alocation other than the default ($LINK_DIR\DataQuality\reference_data),do the following:


Directory Data6 Where to copy directories

1. Stop any data flows that use the EMEA engine, Global engine or GlobalSuggestion Lists.

2. Stop the Address Server.3. Copy the following files from $LINK_DIR\DataQuality\reference_data

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 softwareupdate, copy the reference files from to the default location to where youstore your directories.

4. Update the REFERENCE_DATA_DIRECTORY parameter in the AddressServerConfig.txt file located in $LINK_DIR\bin\address_server\ to the new reference directory location.

5. Update the RefFilesAddressCleanse substitution parameter configurationto the new reference directory location.

6. Restart the Address Server.

To install and set upDownloadManagerBefore you can download directory files, you need to install and set upDownload 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.


6Directory DataTo install and set up Download Manager



To download directory filesThe directories are available for download from the SAP Service Marketplace(SMP).

To download directories:

1. Access the SAP Service Marketplace (SMP) site: http://service.sap.com/bosap-support

2. Select Downloads.3. From the left pane, select Downloads > SAP Software Distribution

Center > Downloads > Installations and Upgrades > My Company'sApplication Components.A list of your company's applications and any license-free products orcomponents appear.

4. Select the files you want to download and add them to the DownloadBasket.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 DownloadManager.

7. Follow the steps included in the Download Manager documentation todownload the directory files.

Extract directory files on WindowsThe steps listed here describe how to install the self-extracting directory filesfor 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 whereyou keep your directories.

4. Repeat steps 1 through 3 for each required file.


Directory Data6 To download directory files



Maintaining your installation

7

Upgrading the softwareTo upgrade from an existing SAP BusinessObjects Data Integrator or SAPBusinessObjects Data Services installation, install the new components andthen upgrade your repositories. To upgrade from an existing SAPBusinessObjects Data Quality Management installation, see the MigrationConsiderations.

Component upgrades

In addition to upgrading repositories, you must upgrade all SAPBusinessObjects Data Services components to the same version.

It's recommended that after you back up existing repositories (using yourdatabase's backup utility) and read the release notes, you upgradecomponents in the following order:

1. Designer2. Repository3. Job Server4. Access Server5. Message Client libraries

Note:If you are using the SAP ABAP interface, re-install the SAP BusinessObjectsData Services functions for SAP applications.

Related Topics• Supplement for SAP: Installing functions on SAP Business Suite

Repository upgrades

Minor releases do not require a repository upgrade. For example, if 11.7 isa major release and 11.7.3 is a minor release, then when upgrading from11.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 availablewithout the repository upgrade. To see whether you need to upgrade yourrepository for a particular release, see the Release Notes for that release.


Maintaining your installation7 Upgrading the software

Using database backup utilities, always make a copy of your existingrepository before upgrading. Note that you will upgrade using the originalrepository (not your backup copy).

Several repository upgrade paths are available.

ProcedureTo upgrade from

Install this release using one of thefollowing methods:• Upgrade your repository during

the installation process

• Upgrade your repository after in-stalling the Client Components byrunning the Repository Managerutility and choosing the Upgradeoption.

SAP BusinessObjects Data IntegratorVersion 11.0.x, 11.5.x, 11.6.x, 11.7.x

Note:If you are using an end-of-life version of SAP BusinessObjects DataIntegrator, first upgrade to a supported version before upgrading to SAPBusinessObjects Data Services. For example, if you have version 6.5, firstupgrade to version 11.7 and then upgrade to SAP BusinessObjects DataServices.

Related Topics• Upgrading repositories on page 136

Upgrading your system

When moving to a new software version, upgrade your test or developmentenvironment before upgrading your production environment.

To install a new version on a computer hosting an existing version, run theinstallation program without uninstalling the existing version. Uninstalling theexisting version can cause a potential loss of repository information if you


7Maintaining your installationUpgrading the software

are using the packaged MySQL database server, which is uninstalled withSAP BusinessObjects Data Services.

Note:The procedure in the following section directs you to follow instructions inthis guide that explain how to use the installation program.

It's recommended that while upgrading the software you do not use theinstallation program to reconfigure Job or Access Servers or upgrade therepository. Instead, after updating components with the installation program,use the Server Manager and Repository Manager to reconfigure Job andAccess Servers and upgrade the repository.

Related Topics• Beginning your installation on page 38• Using configurations from a previous version on page 132

Using configurations from a previous version

If you want to use custom configurations from a previous version of thesoftware:

1. Move the DSConfig.txt file, from the bin subdirectory, into a newlycreated "dummy" installation directory structure before installing the newversion.

Example "dummy" directory structure:

C:\Program Files\Business Objects\BusinessObjects DataServices\bin\DSConfig.txt

During the installation process, SAP BusinessObjects Data Services willoverwrite the "dummy" directory structure with the new installationstructure, merging custom settings (such as repository and Access Serverconnections added to the Administrator) from your old DSConfig.txt fileinto the new DSConfig.txt file.

2. Before installing the new version, manually move the followingsubdirectories 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 copyof each Access Server configuration directory.Save your current copy until after you test the upgrade and confirm thatyour new system is working as expected. When you merge the oldDSConfig.txt file with the new one, the software should find the AccessServer configuration directories. If not, use the Server Manager to pointto 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• Beginning your installation on page 38

Before installing a new version

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

2. Review the Migration Considerations to identify any behavior changesfrom previous versions.

3. Open your Windows Services panel and stop all SAP BusinessObjectsData Integrator or SAP BusinessObjects Data Services services (SAPBusinessObjects Data Services service and the Address Server).You can use the Task Manager to verify that no SAP BusinessObjectsData Integrator or SAP BusinessObjects Data Services-related processes(processes beginning with al_) are running.

4. Proceed to install the new version.

Related Topics• To install a new version of the software on page 133

To install a new version of the software

1. Use the SAP BusinessObjects Data Services installation program to installthe new version.

2. Restart the computer if prompted by the installation program.3. Use the Repository Manager to create or upgrade repositories, if needed.



Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects Data Services >Data Services RepositoryManager.

4. Use the Server Manager to make changes to your Job and AccessServers.Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAPBusinessObjects 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 computerswhere they are used.If you are upgrading your Message Client library, you must stop your webapplication, install the Message Client library files, then restart your webapplication computer.

Related Topics• Beginning your installation on page 38• Upgrading repositories on page 136

To back up and restore the MySQL database

If you choose to use the packaged MySQL installation, the database serveris uninstalled when you uninstall SAP BusinessObjects Data Services. If youwant to uninstall the software before you upgrade to a new version, back upthe repository.

You can back up and restore the repository with the command-line MySQLadministration tools installed with the software. By default, the MySQLadministration tools are installed to the MySqlAdmin5 folder at the same levelas LINK_DIR.

1. Before you uninstall the software, run mysqldump from the command lineto export your repository:mysqldump -uusername -ppassword DatabaseSchema >DataServices.sql



DataServices.sql is created in the same directory where the commandwas 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 -ppasswordThe 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.sqlInclude 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 theuser is already logged in. If this happens, click Reset user and use theDesigner as normal.

Related Topics• To create or upgrade repositories on page 66• To resynchronize Job Servers on page 72



Upgrading repositories

After installing a new version of SAP BusinessObjects Data Services, youcan create new repositories or upgrade existing repositories. To associatean existing repository with your new installation of the software, you mustupgrade that repository.

Before upgrading repositories with the Repository Manager:

• Back up each repository that you intend to upgrade by using an externaldatabase backup utility. For more information, see your databasedocumentation.

• 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 BusinessObjectsData Services > Data Services Repository Manager.

2. Enter the repository connection information for your original repository inthe Repository Manager window.

Note:Do not attempt to upgrade the backup copy of your repository or you willexperience upgrade errors.

3. Click Get Version.The Repository Manager displays the version number recorded in therepository.

4. Click Upgrade.The Repository Manager converts the pre-existing repository to the formatrequired by the new version of SAP BusinessObjects Data Services andadds 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 softwareversion.

6. Click Close.



Note:If you need to create or upgrade multiple repositories, you can use the RepoManBatch.exe utility.

Related Topics• Using the Repository Manager on page 65• To create or upgrade repositories in batch mode on page 67

Upgrading cleansing packages

Restriction:Depending on the SAP BusinessObjects Data Services versions involved,you may be required to upgrade all person_firm dictionary customizationsas well as all custom dictionaries created using Universal Data Cleanse. Ifupgrade is required, it is critical that you export your dictionary changes priorto uninstalling your current version of the software in order to be able makethe dictionary information available in the upgraded version. Specific upgradeinformation is included in the Release Notes. For more information, see theRelease Notes.

In upgrades between versions of SAP BusinessObjects Data Services whena cleansing package upgrade is not required (in other words, the cleansingpackage upgrade is optional), you may still want to upgrade your existingdictionaries to take advantage of the updated data in the new cleansingpackage version. Updated data may include additional name or firm entriesor secondary information.

For custom dictionaries and rule files created with Universal Data Cleanse,if the cleansing package upgrade is optional (not required), you need notupgrade it. After upgrading your SAP BusinessObjects Data Services version,in the Designer, choose Dictionary > Manage Connection to point to andcontinue 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 themto 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 dictionaryinto 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 createdin Step 1.

• For cleansing package person_firm dictionaries, test your job with theupdated cleansing package data.

If the parsing results are not better or at par with previous results, tryimporting your customizations from the previous cleansing package.a. ChooseDictionary >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.


After upgrading the software

Run tests of your production jobs to ensure that your existing designs continueto run as expected in the new version of SAP BusinessObjects Data Services.When you are confident that the new version of the software performs aswell as or better than the previous version, consider upgrading yourproduction environment.



Unsuccessful upgrade

Errors that prevent installation progress (for example, an incorrect servername, 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 isset to the location of the directory in which you installed the software.

Related Topics• Troubleshooting installation problems on page 97



IndexAAccess Server

configuration file, upgrading 132configuring 46configuring, Windows 69, 74testing connection to Web client 105verify running 76

Address ServerInstall data directories 108start the address server 107

Administratorconfiguration file, upgrading 132

Ccleansing package

repository 31requirements 31upgrading 137

cleansing packagesupgrading 137

ClientTest.exe 138COM API, description 138components

distribution 13ports 18upgrading 130

configuringAccess Server 46Access Servers 69, 74Job Server 45Job Servers 69, 70, 97Metadata Integrator 47, 86

configuring (continued)Metadata Integrator in a distributed

environment 83Metadata Integrator in a local environment

82runtime resources for Job Servers 73Tomcat 50web application server 50

Configuring Job Server run-time resourcesresources, runtime for Job Serversconfiguring 73

connectivity, testing 100, 106

DData Profiler

configuring 96database

preparing 30repository 30

database serverconfiguring 44existing 44reusing BOE MySQL 43

directorieslist 122location 126non-default location 126U.S. directory expiration 125update schedule 122

directory data 122Directory data updates Stop and restart Address

Server 108DSConfig.txt file, upgrading custom

configurations 132


DTD samples 100

Ffunctor_list2312d.dll 138functor2312d.dll 138

Iinstallation

beginning 38errors 97files to test connectivity 100overview 33silent 35standard 33, 34starting 53testing 100, 101

installation locationspecifying 39

installed featuresselecting 40

itc2312d.dll 138

JJob Server

configuration 69, 70, 97configuring 45installing 90repository, synchronizing with 70verify running 76

Kkeycode

entering 39product 39

Llicense agreement

accepting 38LINK_DIR system variable 138log, configuration file, upgrading 132logging in

Management Console 64login information

specifying 46

MManagement Console 103, 138

log in 64troubleshooting

Management Console 98Message Client library

COM 138Metadata Integrator 90, 92, 93

configuration overview 80configuring 47, 86configuring after installing SAP

BusinessObjects Enterprise 95configuring in a distributed environment 83configuring in a local environment 82deleting 86specifying configuration details 48specifying SSL details 49troubleshooting 94

mny2012d.dll 138MySQL

backing up 134configuring 43upgrading 134

Nnetwork connections

checking 21network requirements 11network1712d.dll 138


Index

Ppointer2312d.dl 138ports

default numbers 18description 18Job Server, configuring 138

product keycodeentering 39

Program Job Serverconfiguring for Metadata Integrator 92, 93

Rrepository

central 17configuring 65creating 17creating, multiple 67Job Server, synchronizing with 70local 17troubleshooting 97upgrading 130, 136upgrading, multiple 136

repository databaseconfiguring DB2 27configuring Microsoft SQL Server 27configuring MySQL 28configuring Oracle 28configuring Sybase 29preparing 30selecting 42

Repository Manager 65requirements

cleansing package repository 31Data Cleanse 31network 11system 11

response filecreating 56

restarting services 69

Ssample test files for connectivity 100scripted installation

performing 56running 57

Server Manager 69service

user account 46services

starting automatically 64silent installation 58

overview 35, 56SNMP, enable for a Job Server on Windows

138specifying

login information 46user account 46

standard installationoverview 33performing 34

starting services 64Support adapter and SNMP option 138sync2312d.dll 138system requirements 11

TTCP/IP

port for Job Server 138testing

connectivity 100, 106real-time jobs 101service request from Web application 102,

106thread2312d.dll 138threxcept2312d.dll 138tls7712d.dll 138Tomcat

configuring 50troubleshooting

Windows Server 2008 99


Index

troubleshooting (continued)Windows Vista 99

Uupgrading

components 130paths 130repository 130, 136successful 138

user accountspecifying 46

user informationentering 39

user permissions 12

Vversions, repository 130

Wweb application server

configuring 50selecting 49

Web applicationstesting connection to Access Server 105

Windows clustercreating 21

XXML samples 100


Index

xi32 ds install win en

Documents